Key management device and key management system

Abstract

To provide a key management device capable of carrying out key management using one dimensional or two dimensional codes more flexibly.SOLUTION: A key management device is provided with: a plurality of accommodation sections for accommodating holders holding keys; a reading section for reading one dimensional or two dimensional codes; and a carrying-out section for carrying out a first process capable of making a holder pulled out from another key management device return to one of the plurality of accommodation sections when a code read with the reading section is a first code, and carrying out a second process to enable the holder returned in the first process to be pulled out when the read code with the reading section is a second code.SELECTED DRAWING: Figure 6

Description

[Technical field]

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

[0002] Patent document 1 describes that the external terminal notifies the user or person in charge by email, which includes the release ID (which can be a two-dimensional code), and the user or person in charge goes to the location of the key management device and enters the release ID notified by email. The key management device then queries the external terminal for the entered release ID, and if it is a registered release ID, it unlocks the holder registered and linked to the release ID, allowing the user or person in charge to remove the holder. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2022-174809 A Summary of the Invention [Problem to be solved by the invention]

[0004] Unless a configuration is adopted in which multiple types of one-dimensional or two-dimensional codes are used or processing is switched depending on the type of code, key management using one-dimensional or two-dimensional codes cannot be performed more flexibly.

[0005] An object of the present invention is to provide more flexibility in key management using one- or two-dimensional codes. [Means for solving the problem]

[0006] With this objective in mind, the present invention provides a key management device comprising a plurality of storage units for storing holders that hold keys, a reading unit for reading one-dimensional or two-dimensional codes, and an execution unit for, if the code read by the reading unit is a first code, executing a first process that enables a holder that has been removed from another key management device to be returned to one of the plurality of storage units, and, if the code read by the reading unit is a second code, executing a second process that enables the holder that has been returned by the first process to be removed.

[0007] The second code may be issued in response to a reservation for use of the key held by the holder removed by the second process or the object to be used with the key. In this case, the first code may be issued together with the second code in response to the reservation for use.

[0008] The first code may include holder identification information for identifying a holder to be replaced by the first process, and the execution unit may specify a holder that can be replaced by the first process based on the holder identification information. In this case, the execution unit may specify a storage unit to which the holder is to be replaced by the first process based on the holder identification information.

[0009] The second code may include holder identification information for identifying a holder to be removed by the second process, and the execution unit may specify a holder to be made removable by the second process based on the holder identification information. In this case, the execution unit may specify a storage unit from which the holder is to be removed by the second process based on the holder identification information.

[0010] The second code may include period information, and the execution unit may be configured to prevent the holder that was put back in by the first processing from being removed by the second processing if the current date and time is outside the period information included in the second code read by the reading unit.

[0011] The execution unit may be configured to execute a third process that enables the holder removed by the second process to be returned to any one of the multiple storage units when the code read by the reading unit is a third code.

[0012] In that case, the third code may be the second code, and the execution unit may be configured to execute the second process if the code read by the reading unit is the second code and the holder put back in by the first process has not been removed, and execute the third process if the holder put back in by the first process has been removed. In that case, the second code may include period information, and the execution unit may be configured to make the holder put back in by the first process unremovable by the second process and make the holder removed by the second process returnable by the third process if the current date and time is outside the period information included in the second code read by the reading unit.

[0013] Furthermore, the execution unit may execute a fourth process for making it possible to remove the holder that was put back in by the third process when the code read by the reading unit is the fourth code. In this case, the return destination of the holder that was removed by the second process may be set to the own device, and the return destination of the holder that was removed by the fourth process may be set to another key management device. Furthermore, the first code, the second code, the third code, and the fourth code may include code identification information for identifying the codes, and the execution unit may determine whether the code read by the reading unit is the first code, the second code, the third code, or the fourth code based on the code identification information. Furthermore, at least one of the first code, the second code, the third code, and the fourth code may include user identification information for identifying a user of the code, and the execution unit may store a processing history including the user identification information.

[0014] The present invention also provides a key management device comprising a plurality of storage units for storing holders that hold keys, a reading unit for reading one-dimensional or two-dimensional codes, and an execution unit for executing a fifth process that enables a holder to be removed from one of the plurality of storage units to be returned to another key management device if the code read by the reading unit is a fifth code, and for executing a sixth process that enables the holder removed from the other key management device to be returned to one of the plurality of storage units if the code read by the reading unit is a sixth code.

[0015] The fifth code may be issued in response to a reservation for use of the key held by the holder removed by the fifth process or the object to be used with the key, and the sixth code may be issued after the holder returned by the sixth process is returned to another key management device.

[0016] The fifth code may include holder identification information for identifying a holder to be removed by the fifth process, and the execution unit may specify a holder to be made removable by the fifth process based on the holder identification information. In this case, the execution unit may specify a storage unit from which the holder is to be removed by the fifth process based on the holder identification information.

[0017] The sixth code may include holder identification information for identifying the holder to be replaced by the sixth process, and the execution unit may specify the holder to be made replaceable by the sixth process based on the holder identification information. In this case, the execution unit may specify the storage unit to which the holder is to be replaced by the sixth process based on the holder identification information.

[0018] Furthermore, the present invention also provides a key management system including a first key management device and a second key management device, the first key management device having a plurality of first storage units for storing a holder that holds a key, a first reading unit for reading a one-dimensional or two-dimensional code, and a first execution unit for executing a first process to enable a holder removed from the second key management device to be returned to one of the plurality of first storage units if the code read by the first reading unit is a first code, and for executing a second process to enable the holder returned by the first process to be removed if the code read by the first reading unit is a second code.

[0019] The first execution unit may execute a third process to enable the holder removed by the second process to be returned to any one of the first storage units when the code read by the first reading unit is the third code, and execute a fourth process to enable the holder returned by the third process to be removed when the code read by the first reading unit is the fourth code. In this case, the second key management device may include a plurality of second storage units that store holders that hold keys, a second reading unit that reads one-dimensional or two-dimensional codes, and a second execution unit that executes a fifth process to enable the holder returned by the first process to be removed from any one of the second storage units when the code read by the second reading unit is the first code, and executes a sixth process to enable the holder removed by the fourth process to be returned to any one of the second storage units when the code read by the second reading unit is the fourth code. Effect of the Invention

[0020] According to the present invention, key management using one-dimensional or two-dimensional codes can be performed more flexibly. [Brief description of the drawings]

[0021] [Figure 1] 1 is a diagram illustrating an example of the overall configuration of a key management system according to an embodiment of the present invention; [Diagram 2]2 is a diagram showing an example of the external configuration of a first key management device in the present embodiment. FIG. [Diagram 3] 2 is a diagram showing an example of the external configuration of a second key management device according to the present embodiment. FIG. [Figure 4] 1A to 1C are diagrams showing examples of the external configuration of a holder and a key used in the present embodiment. [Diagram 5] 2 is a block diagram showing an example of a functional configuration of a code issuing device according to the present embodiment. FIG. [Figure 6] 2 is a block diagram showing an example of a functional configuration of a first key management device in the present embodiment. FIG. [Figure 7] 4] FIG. 4 is a block diagram showing an example of a functional configuration of a second key management device in the present embodiment. [Figure 8] 10 is a flowchart showing an example of the operation of a control unit of the code issuing device when a user reserves use of a key. [Figure 9] 13 is a flowchart showing an example of the operation of a control unit of the code issuing device after a user returns a key to the first key management device. [Figure 10] 13 is a flowchart showing an example of the operation of a control unit of the first key management device when the code read by the reading unit is a first administrator code. [Figure 11-1] 10 is a flowchart showing an example of the operation of a control unit of the first key management device when the code read by the reading unit is a user code. [Figure 11-2] 10 is a flowchart showing an example of the operation of a control unit of the first key management device when the code read by the reading unit is a user code. [Figure 12] 13 is a flowchart showing an example of the operation of a control unit of the first key management device when the code read by the reading unit is a code for a second administrator. [Figure 13] 13 is a flowchart showing an example of the operation of a control unit of the second key management device when the code read by the reading unit is a code for the first administrator. [Figure 14] 13 is a flowchart showing an example of the operation of a control unit of the second key management device when the code read by the reading unit is a code for the second administrator. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0022] Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

[0023] [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 the present embodiment. The key management system 1 may manage any keys, but the following description will be given taking as an example a case where the key management system 1 manages keys for construction machines in a construction machine rental service.

[0024] As shown in the figure, the key management system 1 includes a first key management device 10a as an example of a first key management device, a second key management device 10b as an example of a second key management device, and a code issuing device 40.

[0025] The first key management device 10a is a so-called outdoor key management device installed outdoors in the construction machinery rental service office F so that keys for construction machinery can be rented out, for example, even at night. The first key management device 10a is operated by an administrator or a user. The administrator is a user who manages the keys, such as a staff member of a company that provides the construction machinery rental service. The user is a user who uses the keys, such as a customer who receives the construction machinery rental service. Although only one first key management device 10a is shown in the figure, multiple first key management devices 10a may be installed.

[0026] The second key management device 10b is a so-called centralized management board installed in the office F of the construction equipment rental service so as to enable centralized management of keys that may be rented out by the first key management device 10a. The second key management device 10b is operated by an administrator. However, the second key management device 10b may also lend and return keys in the same manner as the first key management device 10a, in which case the second key management device 10b is also operated by a user. Note that although only one second key management device 10b is shown in the figure, multiple second key management devices 10b may be installed.

[0027] The code issuing device 40 issues a code that can give instructions to the first key management device 10a or the second key management device 10b by holding the code issuing device 40 over a reader of the first key management device 10a or the second key management device 10b. The code may be a one-dimensional or two-dimensional code. Alternatively, the code may be a graphic code. A representative example of the code is a QR code (registered trademark). For example, a user contacts an administrator to make a reservation for use of a key, including information such as a user ID, a key to be used, and a usage period. The administrator then accepts the reservation and inputs information such as the user ID, the key to be used, and a usage period to the code issuing device 40. The code issuing device 40 then issues a code based on the input information. The code issuing device 40 is shown outside the office F in the figure, but may be installed inside the office F.

[0028] Although not shown in the figure, the key management system 1 may include a reservation system. A user or an administrator may input a reservation for key use, including information such as a user ID, a key to be used, and a period of use, into the reservation system, and the code issuing device 40 may obtain this information from the reservation system and issue a code based on that information.

[0029] [External configuration of the first key management device] Fig. 2 is a diagram showing an example of the external configuration of the first key management device 10a in this embodiment. As shown in Fig. 2, the first key management device 10a has a parent door 21a that can be opened and closed on its front side, and a key storage unit 23a that can be opened and closed by the parent door 21a. The first key management device 10a also has a display operation unit 25a, a card reader 26a, and a reading unit 27a on its front side. The first key management device 10a also has a storage box 29a.

[0030] The key storage section 23a is provided with a plurality of child doors 22a on its front surface so as to be able to open and close, and is provided with a plurality of individual storage sections 24a, each of which is opened and closed by a corresponding child door 22a. The individual storage sections 24a detachably store holders 31 for holding keys. In this embodiment, a plurality of individual storage sections 24a are provided as an example of a plurality of storage sections for storing holders that hold keys, and as an example of a plurality of first storage sections for storing holders that hold keys.

[0031] Each individual storage unit 24a is provided with a lock mechanism 241a to permit or prohibit removal of the holder 31. The first key management device 10a controls the lock mechanism 241a for each individual storage unit 24a, thereby controlling permission or prohibition of removal of each holder 31. A light emitting unit 242a is also provided on the front surface of the child door 22a corresponding to each individual storage unit 24a. The light emitting unit 242a is, for example, an LED (Light Emitting Diode). Furthermore, a reading unit 243a is provided in the space within the child door 22a corresponding to each individual storage unit 24a. The reading unit 243a is, for example, an RFID (Radio Frequency IDentification) reader.

[0032] The display operation unit 25a is, for example, a touch panel display, which accepts operations by the user and displays various information. The card reader 26a is a reading device that reads information from a card carried by a user. Examples of cards include magnetic cards, IC (Integrated Circuit) cards, etc. When a user passes a card through the card reader 26a, the card reader 26a reads a user ID from the card and performs user authentication based on the read user ID. The reading unit 27a is a reading device that reads codes from various media. For example, the reading unit 27a may be a QR code reader that reads a QR code (registered trademark) from a display screen of a terminal device on which a QR code (registered trademark) is displayed or from a sheet of paper on which a QR code (registered trademark) is printed. In this embodiment, the reading unit 27a is provided as an example of a reading unit that reads a one-dimensional or two-dimensional code, and as an example of a first reading unit that reads a one-dimensional or two-dimensional code.

[0033] The storage box 29a is a box capable of storing various items. An insertion port for inserting the items to be stored is not shown in the figure.

[0034] 2 are merely examples, and the first key management device 10a may include other components. For example, the first key management device 10a may include a speaker. In that case, instead of displaying a warning on the display operation unit 25a, an alarm may be output from the speaker.

[0035] [External configuration of the second key management device] Fig. 3 is a diagram showing an example of the external configuration of the second key management device 10b in this embodiment. As shown in Fig. 3, the second key management device 10b is provided with a key storage unit 23b and a display operation unit 25b on its front side. Furthermore, the second key management device 10b has a reading unit 27b.

[0036] The key storage section 23b is provided with a plurality of individual storage sections 24b. The individual storage sections 24b detachably store holders 31 for holding keys. In this embodiment, a plurality of individual storage sections 24b are provided as an example of a plurality of storage sections for storing holders that hold keys, and as an example of a plurality of second storage sections for storing holders that hold keys.

[0037] Each individual storage unit 24b is provided with a locking mechanism 241b to permit or prohibit removal of the holder 31. The second key management device 10b controls the locking mechanism 241b for each individual storage unit 24b, thereby controlling whether or not each holder 31 can be removed. Each individual storage unit 24b is also provided with a light emitting unit 242b. The light emitting unit 242b is, for example, an LED. Furthermore, the individual storage unit 24b is provided with a reading unit 243b. The reading unit 243b is, for example, an RFID reader.

[0038] The display operation unit 25b is, for example, a touch panel display, which accepts operations by the user and displays various information. The reading unit 27b is a reading device that reads codes from various media. For example, the reading unit 27b may be a QR code reader that reads a QR code (registered trademark) from a display screen of a terminal device on which a QR code (registered trademark) is displayed or from a sheet of paper on which a QR code (registered trademark) is printed. In this embodiment, the reading unit 27b is provided as an example of a reading unit that reads a one-dimensional or two-dimensional code, and as an example of a second reading unit that reads a one-dimensional or two-dimensional code.

[0039] 3 are merely examples, and the second key management device 10b may include other components. For example, the second key management device 10b may include a speaker. In that case, instead of displaying a warning on the display operation unit 25b, an alarm may be output from the speaker. The second key management device 10b may also include a card reader.

[0040] [Holder and key configuration] 4 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. The holder 31 is provided with an IC tag 34. The IC tag 34 is, for example, an RFID tag. The IC tag 34 has a holder ID which is identification information for identifying the holder 31. To provide the IC tag 34 on the holder 31, for example, a sticker-type IC tag 34 may be attached to the holder 31, or the IC tag 34 may be embedded in the holder 31.

[0041] [Functional configuration of the code issuing device] 5 is a block diagram showing an example of a functional configuration of the code issuing device 40 according to the present embodiment. As shown in the figure, the code issuing device 40 includes a control unit 41, a storage unit 42, a communication unit 43, a display unit 44, and an operation unit 45.

[0042] The control unit 41 includes an arithmetic circuit such as a CPU (Central Processing Unit), and controls each unit of the code issuing 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 (Read Only Memory), a RAM (Random Access Memory), etc., stores the operation program of the control unit 41, and is 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 later. When the code issuing device 40 is connected to another device via a communication line, the communication unit 43 communicates information with the other device via the communication line. The display unit 44 is, for example, a display, and displays various information. The operation unit 45 is, for example, a keyboard and a mouse, and is used by the user to input operation information.

[0043] Here, a specific description will be given of the configuration of the control unit 41. The control unit 41 includes an information acquisition unit 411, a code generation unit 412, and a code issuing unit 413.

[0044] The information acquisition unit 411 acquires the user ID of the user input by the administrator using the operation unit 45, the holder ID of the holder 31 that holds the key 33 to be used, period information indicating the period during which the user will use the key 33, etc.

[0045] The code generation unit 412 generates a code including a code ID for identifying the type of code, and the user ID, holder ID, etc. acquired by the information acquisition unit 411. The code ID is an example of code identification information for identifying a code. The user ID is an example of user identification information for identifying a user, and the holder ID is an example of holder identification information for identifying a holder.

[0046] Specifically, the code generating unit 412 generates a first code for causing the first key management device 10a to execute a first process that enables the administrator to return the holder 31 to the first key management device 10a in order to move the key 33 from the second key management device 10b. The first code includes a code ID, a user ID, and a holder ID. The code ID indicates that this code is a first code for causing the first key management device 10a to execute the first process. The user ID indicates the user of the key 33 to be moved from the second key management device 10b by the first process. The holder ID indicates the holder 31 to be returned to the first key management device 10a by the first process. In the following, the first code may be referred to as a "first administrator code."

[0047] The code generating unit 412 also generates a second code for causing the first key management device 10a to execute a second process that enables the user to remove the holder 31 from the first key management device 10a to borrow the key 33. The second code includes a code ID, a user ID, a holder ID, and period information. The code ID indicates that this code is a second code for causing the first key management device 10a to execute the second process. The user ID indicates the user of the key 33 to be borrowed by the second process. The holder ID indicates the holder 31 to be removed from the first key management device 10a by the second process. The period information indicates the usage period of the key 33 to be borrowed by the second process. Hereinafter, the second code may be referred to as a "user code."

[0048] The code generating unit 412 also generates a third code for causing the first key management device 10a to execute a third process that enables the user to return the holder 31 to the first key management device 10a in order to return the key 33. The third code includes a code ID, a user ID, a holder ID, and period information. The code ID indicates that this code is a third code for causing the first key management device 10a to execute the third process. The user ID indicates the user of the key 33 to be returned by the third process. The holder ID indicates the holder 31 to be returned to the first key management device 10a by the third process. The period information indicates the usage period of the key 33 to be returned by the third process. The third code may be the same as the second code. In that case, the third code may also be called a "user code".

[0049] The code generating unit 412 also generates a fourth code for causing the first key management device 10a to execute a fourth process that enables the administrator to remove the holder 31 from the first key management device 10a to move the key 33 to the second key management device 10b. The fourth code includes a code ID, a user ID, and a holder ID. The code ID indicates that this code is the fourth code for causing the first key management device 10a to execute the fourth process. The user ID indicates the user of the key 33 to be moved to the second key management device 10b by the fourth process. The holder ID indicates the holder 31 to be removed from the first key management device 10a by the fourth process. Hereinafter, the fourth code may be referred to as a "second administrator code."

[0050] Furthermore, the code generating unit 412 generates a fifth code for causing the second key management device 10b to execute a fifth process that enables the administrator to remove the holder 31 from the second key management device 10b to move the key 33 to the first key management device 10a. The fifth code includes a code ID, a user ID, and a holder ID. The code ID indicates that this code is a fifth code for causing the second key management device 10b to execute the fifth process. The user ID indicates the user of the key 33 to be moved to the first key management device 10a by the fifth process. The holder ID indicates the holder 31 to be removed from the second key management device 10b by the fifth process. The fifth code may be the same as the first code. In that case, the fifth code may also be called the "first administrator code."

[0051] The code generating unit 412 also generates a sixth code for causing the second key management device 10b to execute a sixth process that enables the administrator to return the holder 31 to the second key management device 10b in order to move the key 33 from the first key management device 10a. The sixth code includes a code ID, a user ID, and a holder ID. The code ID indicates that this code is a sixth code for causing the second key management device 10b to execute the sixth process. The user ID indicates the user of the key 33 to be moved from the first key management device 10a by the sixth process. The holder ID indicates the holder 31 to be returned to the second key management device 10b by the sixth process. The sixth code may be the same as the fourth code. In that case, the sixth code may also be called a "second administrator code."

[0052] Incidentally, the first process, the third process, and the sixth process are all processes that enable the holder 31 to be returned to the key management device. Here, "returning" refers to the operation of returning the removed key. However, the term "returning" is used not only to mean returning the key to the key management device from which it was removed, but also to mean returning the key to system management. Note that "returning" may be an operation performed on any individual storage unit in which the holder 31 is not loaded, or an operation performed on a fixed individual storage unit that is pre-tied to the holder 31, but the following description will be given assuming the former operation. Moreover, the second process, the fourth process, and the fifth process are all processes that allow the holder 31 to be removed from the key management device. Here, "removal" is not limited to the operation of removing the holder 31 from a storage section shaped to receive the holder 31, but may be any operation of removing the holder 31 from the storage section. In particular, the second process and the fourth process are processes that allow the holder 31 to be removed from the first key management device 10a. The second process and the fourth process can be distinguished in that the return destination of the holder removed by the second process is set to the first key management device, whereas the return destination of the holder removed by the fourth process is set to another key management device.

[0053] The code generating unit 412 may generate a code that further includes the user ID of the user of the code. The user of the first code, fourth code, fifth code, and sixth code is the administrator, and the user ID is the administrator ID of the administrator. Therefore, the code generating unit 412 generates codes including the user ID and the administrator ID as the first code, fourth code, fifth code, and sixth code. The user of the second code and the third code is the user, and the user ID is the user ID. Therefore, the code generating unit 412 generates, as the second code and the third code, codes that include the user ID but do not include the administrator ID, as described above. The user ID is an example of user identification information that identifies a user of the code. Furthermore, all of the first to sixth codes do not have to include a user ID. For example, at least one of the first to sixth codes may include a user ID, or at least one of the first to fourth codes may include a user ID, and at least one of the fifth and sixth codes may include a user ID.

[0054] Furthermore, when multiple first key management devices 10a are installed, the code generation unit 412 may generate a code that further includes the device ID of the first key management device 10a. When multiple second key management devices 10b are installed, the code generation unit 412 may generate a code that further includes the device ID of the second key management device 10b. Furthermore, the code generating unit 412 may generate a code including the storage unit number of the individual storage unit 24a or the individual storage unit 24b instead of or in addition to the holder ID.

[0055] The code issuing unit 413 issues the code generated by the code generating unit 412 . At this time, the code issuing unit 413 may issue the code generated by the code generating unit 412 in an issuing format according to the type of the code. For example, the code issuing unit 413 may issue the first, fourth, fifth, and sixth codes used by the administrator in an analog manner among the codes generated by the code generating unit 412. The analog manner of issuing is, for example, a manner in which the codes are printed on paper by a printer (not shown). The code issuing unit 413 may issue, in a digital manner, the second code and the third code to be used by the user among the codes generated by the code generating unit 412. The digital manner of issuing is, for example, a manner in which the codes are transmitted from the communication unit 43 to the terminal device by email.

[0056] Furthermore, the code issuing unit 413 may issue the code generated by the code generating unit 412 at a timing according to the type of code.

[0057] For example, the code issuing unit 413 may issue the first code, the second code, the third code, and the fifth code from among the codes generated by the code generating unit 412 in response to a reservation for use of a key held by the holder 31 or an object to be used with the key. Issuing the second code in this way is an example of issuing the second code in response to a reservation for use of a key held by a holder to be removed by the second process or an object to be used with the key. Also, issuing the first code in this way is an example of issuing the first code together with the second code in response to a reservation for use. Furthermore, issuing the fifth code in this way is an example of issuing the fifth code in response to a reservation for use of a key held by a holder to be removed by the fifth process or an object to be used with the key. As described above, the second code and the third code are user codes, and the first code and the fifth code are first administrator codes. In this case, the code issuing unit 413 issues a set of a user code and a first administrator code in response to a reservation for use of a key held by the holder 31 or an object to be used with the key. However, the code issuing unit 413 may issue only a user code in response to a reservation for use, and may not issue a first administrator code in cases where there is no need to move the key, etc.

[0058] The code issuing unit 413 may issue the fourth code and the sixth code from among the codes generated by the code generating unit 412 after the holder 31 is returned to the first key management device 10a. Issuing the sixth code in this manner is an example of issuing the sixth code after the holder, which is returned by the sixth process, is returned to another key management device. As described above, it is assumed that the fourth code and the sixth code are the second administrator code. In this case, the code issuing unit 413 issues the second administrator code after the holder 31 is returned to the first key management device 10a.

[0059] In this embodiment, the code issuing device 40 issues a code including a code ID, a user ID, a holder ID, period information, a user ID, a device ID, and a storage unit number in the most common case, but this is not limited to the above. For example, the code issuing device 40 may issue a code including only information for identifying each code, and the first key management device 10a or the second key management device 10b may obtain other information from a database within the device or a database outside the device.

[0060] [Functional configuration of the first key management device] 6 is a block diagram showing an example of a functional configuration of the first key management device 10a in this embodiment. As shown in the figure, the first key management device 10a includes a control unit 11a, a storage unit 12a, a communication unit 13a, a master door locking mechanism 141a, a slave door locking mechanism 142a, a locking mechanism 241a, a light emitting unit 242a, a reading unit 243a, a display operation unit 25a, a card reader 26a, and a reading unit 27a.

[0061] The control unit 11a is equipped with an arithmetic circuit such as a CPU, and controls each part of the first key management device 10a (communication unit 13a, parent door locking mechanism 141a, child door locking mechanism 142a, locking mechanism 241a, light emitting unit 242a, reading unit 243a, display operation unit 25a, card reader 26a, reading unit 27a, etc.) in accordance with the operating program stored in the memory unit 12a. The storage unit 12a includes a ROM, a RAM, etc., stores the operation program of the control unit 11a, and is used as a work area during the control processing of the control unit 11a. The operation program includes a program for the control unit 11a to execute the processing described below. When the first key management device 10a is connected to another device via a communication line, the communication unit 13a communicates information with the other device via the communication line. The main door locking mechanism 141a is a mechanism that locks the main door 21a. The sub-door locking mechanism 142a is a mechanism that locks the sub-door 22a. The lock mechanism 241a, the light emitting unit 242a, the reading unit 243a, the display operation unit 25a, the card reader 26a, and the reading unit 27a have already been described with reference to FIG. 2, and therefore will not be described here.

[0062] Here, the information stored in the storage unit 12a will be specifically described. The storage unit 12a stores the first storage information 121a. The first storage information 121a is information that associates the storage unit number of the individual storage unit 24a with the holder ID attached to the holder 31 stored in the individual storage unit 24a. Although not shown, the storage unit 12a also stores a processing history of each process.

[0063] Next, the configuration of the control unit 11a will be specifically described. The control unit 11a includes a code processing unit 111a, a lock mechanism control unit 112a, a lock / unlock control unit 113a, a light emission control unit 114a, a storage detection unit 115a, a determination unit 116a, a communication control unit 117a, a display control unit 118a, and a storage control unit 119a.

[0064] The code processing unit 111a acquires a code ID from the code read by the reading unit 27a, and determines whether the read code is the first code, the second code, the third code, or the fourth code based on the code ID. Then, the code processing unit 111a specifies the process to be executed by the first key management device 10a based on the determination result. Specifically, when the code read by the reader 27a is the first code, the code processor 111a specifies the first process as the process to be executed by the first key management device 10a. If the code read by the reader 27a is the second code, the code processor 111a identifies the second process as the process to be executed by the first key management device 10a. When the code read by the reader 27a is the third code, the code processor 111a identifies the third process as the process to be executed by the first key management device 10a. When the code read by the reader 27a is the fourth code, the code processor 111a identifies the fourth process as the process to be executed by the first key management device 10a. In this embodiment, this function is provided in the code processing unit 111a as an example of an execution unit that determines whether the code read by the reading unit is the first code, the second code, the third code, or the fourth code based on the code identification information.

[0065] As described above, it is assumed that the second code and the third code are user codes, the first code is the first administrator code, and the fourth code is the second administrator code. In this case, the code processing unit 111a determines whether the code read by the reading unit 27a is the user code, the first administrator code, or the second administrator code. Then, based on the determination result, the code processing unit 111a specifies the process to be executed by the first key management device 10a. Specifically, when the code read by the reader 27a is the first administrator code, the code processor 111a specifies a first process as the process to be executed by the first key management device 10a. When the code read by the reader 27a is the user code, the code processor 111a specifies the second process or the third process as the process to be executed by the first key management device 10a. When the code read by the reader 27a is the second administrator code, the code processor 111a specifies the fourth process as the process to be executed by the first key management device 10a.

[0066] Furthermore, the code processing unit 111a acquires a holder ID from the code read by the reading unit 27a, and identifies the holder 31 that is to be the target of the process executed by the first key management device 10a, based on the holder ID.

[0067] Specifically, when the code read by the reading unit 27a is a first code, the code processing unit 111a identifies the holder 31 having the holder ID included in the code read by the reading unit 27a as the holder 31 that can be returned to the individual storage unit 24a by the first processing. In this embodiment, the code processing unit 111a has this function as an example of an execution unit that specifies the folder that can be returned by the first process based on the folder identification information.

[0068] When the code read by the reading unit 27a is the second code, the code processing unit 111a identifies the holder 31 having the holder ID included in the code read by the reading unit 27a as the holder 31 that can be removed from the individual storage unit 24a by the second processing. In this embodiment, this function is provided in the code processing unit 111a as an example of an execution unit that specifies a folder that can be removed by the second process based on the folder identification information.

[0069] When the code read by the reading unit 27a is the third code, the code processing unit 111a identifies the holder 31 having the holder ID included in the code read by the reading unit 27a as the holder 31 that can be returned to the individual storage unit 24a by the third processing.

[0070] When the code read by the reading unit 27a is the fourth code, the code processing unit 111a identifies the holder 31 having the holder ID included in the code read by the reading unit 27a as the holder 31 that can be removed from the individual storage unit 24a by the fourth processing.

[0071] The lock mechanism control unit 112a controls the lock mechanism 241a so as to prohibit or permit removal of the holder 31 from the individual storage unit 24a.

[0072] Specifically, when the result of the discrimination by the code processing unit 111a is the second code, the lock mechanism control unit 112a controls the lock mechanism 241a to permit removal of the holder 31 from the individual storage unit 24a. In this embodiment, a lock mechanism control unit 112a is provided as an example of an execution unit that executes a second process that enables the holder that was put back in by the first process to be removed when the code read by the reading unit is the second code. In addition, in this embodiment, a lock mechanism control unit 112a is provided as an example of a first execution unit that executes a second process to enable removal of the holder that has been put back in by the first process when the code read by the first reading unit is the second code.

[0073] If the second code is the same as the third code, when the discrimination result of the code processing unit 111a is the second code, the first key management device 10a cannot determine whether to execute the second process or the third process. Therefore, the lock mechanism control unit 112a executes the second process if the holder 31 identified by the code processing unit 111a has not been removed from the individual storage unit 24a, and controls the lock mechanism 241a to permit removal of the holder 31 from the individual storage unit. In this embodiment, when the code read by the reading unit is the second code, if the holder that was put back in by the first process has not been removed, a lock mechanism control unit 112a is provided as an example of an execution unit that executes the second process.

[0074] Furthermore, when the determining unit 116a determines that the current date and time is outside the usage period, the lock mechanism control unit 112a may control the lock mechanism 241a to prohibit removal of the holder 31 from the individual storage unit 24a. In this embodiment, a lock mechanism control unit 112a is provided as an example of an execution unit that prevents the holder that was put back in by the first processing from being removed by the second processing if the current date and time is outside the period information contained in the second code read by the reading unit.

[0075] When the result of the discrimination by the code processing unit 111a is the fourth code, the lock mechanism control unit 112a controls the lock mechanism 241a to permit removal of the holder 31 from the individual storage unit 24a. In this embodiment, a lock mechanism control unit 112a is provided as an example of an execution unit that executes a fourth process that enables the holder that was put back in by the third process to be removed when the code read by the reading unit is the fourth code. In addition, in this embodiment, a lock mechanism control unit 112a is provided as an example of a first execution unit that executes a fourth process that enables the holder that was put back in by the third process to be removed when the code read by the first reading unit is the fourth code.

[0076] When the memory control unit 119a identifies an individual storage unit 24a as described below, the locking / unlocking control unit 113a controls the parent door locking mechanism 141a to unlock the parent door 21a, and controls the child door locking mechanism 142a to unlock the child door 22a of the individual storage unit 24a. When the holder 31 is removed from the individual storage unit 24a or returned to the individual storage unit 24a, the locking / unlocking control unit 113a controls the child door locking mechanism 142a to lock the child door 22a of the individual storage unit 24a, and controls the parent door locking mechanism 141a to lock the parent door 21a.

[0077] When the lock mechanism control unit 112a permits removal of the holder 31 from the individual storage unit 24a and the locking / unlocking control unit 113a unlocks the child door 22a corresponding to the individual storage unit 24a, the light emission control unit 114a controls to light up the light emitting unit 242a provided on the child door 22a. When the holder 31 is removed from the individual storage unit 24a and the locking / unlocking control unit 113a locks the child door 22a corresponding to the individual storage unit 24a, the light emission control unit 114a controls to turn off the light emitting unit 242a provided on the child door 22a.

[0078] The storage detection section 115a detects the removal of the holder 31 from the individual storage section 24a or the return of the holder 31 to the individual storage section 24a. Furthermore, the storage detection unit 115a acquires the holder ID read from the holder 31 by the reading unit 243a when the holder 31 is returned to the individual storage unit 24a.

[0079] The determination unit 116a performs the following two determinations. The first determination is whether or not the holder ID acquired by the code processing unit 111a matches the holder ID acquired by the storage detection unit 115a. The second determination is whether or not the user has read the second code during the period designated as the period during which the key 33 is to be used in the reservation for use of the key 33. Specifically, the determination unit 116a determines whether or not the current date and time is within the period information included in the code read by the reading unit 27a.

[0080] The communication control unit 117a receives information from other devices and transmits information to other devices via the communication unit 13a. The display control unit 118a controls the display of information on the display operation unit 25a.

[0081] The storage control unit 119a controls writing of data to the storage unit 12a and reading of data from the storage unit 12a.

[0082] Specifically, when the discrimination result of the code processing unit 111a is the first code, the storage control unit 119a controls so as to store the holder ID of the holder 31 in the first storage information 121a when the holder 31 specified by the code processing unit 111a is returned to the individual storage unit 24a. Since the holder 31 can be physically stored in any individual storage unit 24a, the process of returning the holder 31 is completed by storing the holder ID in the first storage information 121a. In this embodiment, a memory control unit 119a is provided as an example of an execution unit that executes a first process that enables a holder removed from another key management device to be returned to one of a plurality of storage units when the code read by the reading unit is a first code. In addition, in this embodiment, a memory control unit 119a is provided as an example of a first execution unit that executes a first process that enables a holder removed from the second key management device to be returned to any one of a plurality of first storage units when the code read by the first reading unit is the first code.

[0083] If the discrimination result of the code processing unit 111a is the third code, when the holder 31 specified by the code processing unit 111a is returned to the individual storage unit 24a, the storage control unit 119a controls to store the holder ID of the holder 31 in the first storage information 121a. Since the holder 31 can be physically stored in any individual storage unit 24a, the process of returning the holder 31 is completed by storing the holder ID in the first storage information 121a. In this embodiment, a memory control unit 119a is provided as an example of an execution unit that executes a third process that enables the holder removed by the second process to be returned to one of the multiple storage units when the code read by the reading unit is the third code. In addition, in this embodiment, a memory control unit 119a is provided as an example of a first execution unit that executes a third process that enables the holder removed by the second process to be returned to any one of the multiple first storage units when the code read by the first reading unit is the third code.

[0084] If the third code is the same as the second code, when the determination result of the code processing unit 111a is the third code, the first key management device 10a cannot determine whether to execute the second process or the third process. Therefore, if the holder 31 identified by the code processing unit 111a has been removed from the individual storage unit 24a, the storage control unit 119a executes the third process and completes the process of putting the holder 31 back into the individual storage unit. In this embodiment, when the code read by the reading unit is the second code, and the holder that was put back in by the first process is removed, a memory control unit 119a is provided as an example of an execution unit that executes a third process.

[0085] Furthermore, even if the determining unit 116a determines that the current date and time is outside the usage period, the storage control unit 119a may complete the process of returning the holder 31 to the individual storage unit 24a. In this embodiment, a memory control unit 119a is provided as an example of an execution unit that enables a holder removed by the second process to be put back in by a third process when the current date and time is outside the period information contained in the second code read by the reading unit.

[0086] In addition, the memory control unit 119a refers to the first storage information 121a stored in the memory unit 12a to identify the individual storage unit 24a into which the holder 31 identified by the code processing unit 111a is to be returned or from which it is to be removed.

[0087] For example, when the discrimination result of the code processing unit 111a is the first code or the third code, the memory control unit 119a identifies the individual storage unit 24a that is not associated with any holder ID among the individual storage units 24a included in the first storage information 121a. In this way, the memory control unit 119a identifies the individual storage unit 24a to which the holder 31 is to be returned. In this embodiment, memory control unit 119a is provided as an example of an execution unit that specifies, based on the holder identification information, the storage unit to which the holder is to be returned by the first process.

[0088] When the discrimination result of the code processing unit 111a is the second code or the fourth code, the memory control unit 119a identifies the individual storage unit 24a associated with the holder ID acquired by the code processing unit 111a from among the individual storage units 24a included in the first storage information 121a. In this way, the memory control unit 119a identifies the individual storage unit 24a from which the holder 31 is to be removed. In this embodiment, the memory control unit 119a is provided as an example of an execution unit that specifies the storage unit from which the holder is to be removed in the second process based on the holder identification information.

[0089] Furthermore, when the first key management device 10a executes any one of the first to fourth processes, the storage control unit 119a controls the storage unit 12a to store the processing history of that process in a manner that distinguishes it from the processing history of other processes. At that time, the storage control unit 119a may include the user ID of the user of the code used to execute that process in the processing history. In this embodiment, a storage control unit 119a is provided as an example of an execution unit that stores a processing history including user identification information.

[0090] [Functional configuration of the second key management device] 7 is a block diagram showing an example of a functional configuration of the second key management device 10b in the present embodiment. As shown in the figure, the second key management device 10b includes a control unit 11b, a storage unit 12b, a communication unit 13b, a lock mechanism 241b, a light emitting unit 242b, a reading unit 243b, a display operation unit 25b, and a reading unit 27b.

[0091] The control unit 11b is equipped with an arithmetic circuit such as a CPU, and controls each part of the second key management device 10b (communication unit 13b, lock mechanism 241b, light-emitting unit 242b, reading unit 243b, display operation unit 25b, reading unit 27b, etc.) in accordance with the operating program stored in the memory unit 12b. The storage unit 12b includes a ROM, a RAM, etc., stores the operation program of the control unit 11b, and is used as a work area during the control processing of the control unit 11b. The operation program includes a program for the control unit 11b to execute the processing described below. When the second key management device 10b is connected to another device via a communication line, the communication unit 13b communicates information with the other device via the communication line. The lock mechanism 241b, the light emitting unit 242b, the reading unit 243b, the display operation unit 25b, and the reading unit 27b have already been described with reference to FIG. 3, and therefore description thereof will be omitted here.

[0092] Here, the information stored in the storage unit 12b will be specifically described. The storage unit 12b stores the second storage information 121b. The second storage information 121b is information that associates the storage unit number of the individual storage unit 24b with the holder ID attached to the holder 31 stored in the individual storage unit 24b. Although not shown, the storage unit 12b also stores a processing history of each process.

[0093] Next, the configuration of the control unit 11b will be specifically described. The control unit 11b includes a code processing unit 111b, a lock mechanism control unit 112b, a light emission control unit 114b, a storage detection unit 115b, a determination unit 116b, a communication control unit 117b, a display control unit 118b, and a storage control unit 119b.

[0094] The code processing unit 111b acquires a code ID from the code read by the reading unit 27b, and determines whether the read code is the fifth code or the sixth code based on the code ID. Then, the code processing unit 111b specifies the process to be executed by the second key management device 10b based on the result of the determination. Specifically, when the code read by the reader 27b is the fifth code, the code processor 111b identifies the fifth process as the process to be executed by the second key management device 10b. If the code read by the reader 27b is the sixth code, the code processor 111b identifies the sixth process as the process to be executed by the second key management device 10b.

[0095] As described above, it is assumed that the fifth code is the first administrator code and the sixth code is the second administrator code. In this case, the code processing unit 111b determines whether the code read by the reading unit 27b is the first administrator code or the second administrator code. Then, based on the determination result, the code processing unit 111b specifies the process to be executed by the second key management device 10b. Specifically, when the code read by the reader 27b is the first administrator code, the code processor 111b specifies a fifth process as the process to be executed by the second key management device 10b. The code processing unit 111b specifies a sixth process as the process to be executed by the second key management device 10b when the code read by the reading unit 27b is the second administrator code.

[0096] Furthermore, the code processing unit 111b acquires a holder ID from the code read by the reading unit 27b, and identifies the holder 31 that is to be the target of the process executed by the second key management device 10b based on the holder ID.

[0097] Specifically, when the code read by the reading unit 27b is the fifth code, the code processing unit 111b identifies the holder 31 having the holder ID included in the code read by the reading unit 27b as the holder 31 that can be removed from the individual storage unit 24b by the fifth process. In this embodiment, this function is provided in the code processing unit 111b as an example of an execution unit that specifies a folder to be made removable by the fifth process based on the folder identification information.

[0098] When the code read by the reading unit 27b is the sixth code, the code processing unit 111b identifies the holder 31 having the holder ID included in the code read by the reading unit 27b as the holder 31 that can be returned to the individual storage unit 24b by the sixth process. In this embodiment, the code processing unit 111b has this function as an example of an execution unit that specifies the folder that can be returned by the sixth process based on the folder identification information.

[0099] The lock mechanism control unit 112b controls the lock mechanism 241b so as to prohibit or permit removal of the holder 31 from the individual storage unit 24b.

[0100] Specifically, when the discrimination result of the code processing unit 111b is the fifth code, the lock mechanism control unit 112b controls the lock mechanism 241b to permit removal of the holder 31 from the individual storage unit 24b. If the fifth code is the same as the first code, the lock mechanism control unit 112b performs the same control even when the discrimination result of the code processing unit 111b is the first code. In this embodiment, a lock mechanism control unit 112b is provided as an example of an execution unit that executes a fifth process that enables the holder to be removed from one of multiple storage units and returned to another key management device when the code read by the reading unit is the fifth code. In addition, in this embodiment, a lock mechanism control unit 112b is provided as an example of a second execution unit that executes a fifth process that enables the holder that is put back in by the first process to be removed from any of the multiple second storage units when the code read by the second reading unit is the first code.

[0101] When the lock mechanism control unit 112b permits removal of the holder 31 from the individual storage unit 24b, the light emission control unit 114b controls the light emitting unit 242b provided in the individual storage unit 24b to light up. When the holder 31 is removed from the individual storage unit 24b, the light emission control unit 114b controls the light emitting unit 242b provided in the individual storage unit 24b to turn off.

[0102] The storage detection section 115b detects the removal of the holder 31 from the individual storage section 24b or the return of the holder 31 to the individual storage section 24b. Furthermore, the storage detection unit 115b acquires the holder ID read from the holder 31 by the reading unit 243b when the holder 31 is returned to the individual storage unit 24b.

[0103] The determining unit 116b determines whether the holder ID acquired by the code processing unit 111b matches the holder ID acquired by the storage detecting unit 115b.

[0104] The communication control unit 117b receives information from other devices and transmits information to other devices via the communication unit 13b. The display control unit 118b controls the display of information on the display operation unit 25b.

[0105] The storage control unit 119b controls writing of data to the storage unit 12b and reading of data from the storage unit 12b.

[0106] Specifically, when the discrimination result of the code processing unit 111b is the sixth code, the memory control unit 119b controls so that when the holder 31 specified by the code processing unit 111b is returned to the individual storage unit 24b, the holder ID of the holder 31 is stored in the second storage information 121b. Since the holder 31 can be physically stored in any individual storage unit 24b, the return process is completed by storing the holder ID in the second storage information 121b. Note that if the sixth code is the same as the fourth code, the memory control unit 119b performs the same control even when the discrimination result of the code processing unit 111b is the fourth code. In this embodiment, a memory control unit 119b is provided as an example of an execution unit that executes a sixth process that enables a holder removed from another key management device to be returned to one of a plurality of storage units when the code read by the reading unit is the sixth code. In addition, in this embodiment, a memory control unit 119b is provided as an example of a second execution unit that executes a sixth process that enables the holder removed by the fourth process to be returned to any one of the multiple second storage units when the code read by the second reading unit is the fourth code.

[0107] In addition, the memory control unit 119b refers to the second storage information 121b stored in the memory unit 12b to identify the individual storage unit 24b into which the holder 31 identified by the code processing unit 111b is to be returned or from which it is to be removed.

[0108] For example, when the discrimination result of the code processing unit 111b is the fifth code, the memory control unit 119b identifies the individual storage unit 24b associated with the holder ID acquired by the code processing unit 111b among the individual storage units 24b included in the second storage information 121b. In this way, the memory control unit 119b identifies the individual storage unit 24b from which the holder 31 is to be removed. In the present embodiment, memory control section 119b is provided as an example of an execution section that specifies the storage section from which the holder is to be removed in the fifth process based on the holder identification information.

[0109] When the discrimination result of the code processing unit 111b is the sixth code, the memory control unit 119b identifies the individual storage unit 24b not associated with any holder ID among the individual storage units 24b included in the second storage information 121b. In this way, the memory control unit 119b identifies the individual storage unit 24b to which the holder 31 is to be returned. In this embodiment, memory control section 119b is provided as an example of an execution section that specifies the storage section to which the holder is to be returned in the sixth process based on the holder identification information.

[0110] Furthermore, when the second key management device 10b executes either the fifth or sixth process, the storage control unit 119b controls so that the processing history of that process is stored in the storage unit 12b separately from the processing history of other processes. At that time, the storage control unit 119b may include the user ID of the user of the code used to execute that process in the processing history.

[0111] [Code issuing device operation] In the code issuing device 40, a control unit 41 controls the code issuing device 40 to issue a code. In the above, the codes are mainly assumed to be the first code, the second code, the third code, the fourth code, the fifth code, and the sixth code. In the following, the second and third codes will be described as the codes for users, the first and fifth codes as the codes for the first administrator, and the fourth and sixth codes as the codes for the second administrator. Specifically, the control unit 41 controls the issuing of a user code and a first administrator code when a user reserves the use of the key 33. In addition, the control unit 41 controls the issuing of a second administrator code after the user returns the key 33 to the first key management device 10a. Therefore, the operation of the code issuing device 40 will be explained below according to the operation timing.

[0112] FIG. 8 is a flow chart showing an example of the operation of the control unit 41 of the code issuing device 40 when a user reserves the use of the key 33.

[0113] As shown in the figure, in the control unit 41, first, the information acquisition unit 411 acquires a user ID, a holder ID, and period information (step 401). For example, the information acquisition unit 411 may acquire the user ID of the user input by the administrator in response to the user's reservation for use. Furthermore, for example, the information acquisition unit 411 may acquire the holder ID of the holder 31 that holds the key 33 based on information on the key 33 to be used input by the administrator in response to the user's reservation for use. Furthermore, for example, the information acquisition unit 411 may acquire period information based on the usage period of the key 33 input by the administrator in response to the user's reservation for use.

[0114] Next, the code generating unit 412 generates a user code (step 402). Specifically, the code generating unit 412 generates a user code including the user ID, the holder ID, and the period information acquired in step 401. Furthermore, the code generating unit 412 generates a first administrator code (step 403). Specifically, the code generating unit 412 generates a first administrator code including the user ID and the holder ID acquired in step 401.

[0115] Next, the code issuing unit 413 controls the communication unit 43 so as to transmit the user code generated in step 402 to the user's terminal device, for example, by email (step 404). Next, the code issuing unit 413 controls a printer (not shown) to print the first administrator code generated in step 403 on paper or the like (step 405).

[0116] 9 is a flowchart showing an example of the operation of the control unit 41 of the code issuing device 40 after the user returns the key 33 to the first key management device 10a. Note that, although it is described here as after the key 33 is returned, this may be any timing when it is assumed that the key 33 has been returned. Examples of such timing include the end of the usage period of the key 33, or the time when the user reports the end of usage of the key 33 even before the end of the usage period of the key 33.

[0117] As shown in the figure, in the control unit 41, first, the information acquisition unit 411 acquires a user ID and a holder ID (step 421). The information acquisition unit 411 may acquire the user ID of the user and the holder ID of the holder 31 that holds the key 33 to be used from information input and stored by the administrator in response to a usage reservation by the user, for example.

[0118] Next, the code generating unit 412 generates a second administrator code (step 422). Specifically, the code generating unit 412 generates a second administrator code including the user ID acquired in step 421 and the holder ID.

[0119] Next, the code issuing unit 413 controls a printer (not shown) to print the second administrator code generated in step 422 on paper or the like (step 423).

[0120] [Operation of the first key management device] In the first key management device 10a, first, the code processing unit 111a of the control unit 11a determines whether the code read by the reading unit 27a is the user code, the first administrator code, or the second administrator code.

[0121] First, a case will be described in which the code processor 111a determines that the code read by the reader 27a is the code for the first administrator. In this case, the first key management device 10a executes a first process that enables the administrator to return the holder 31 to the first key management device 10a in order to move the key 33 from the second key management device 10b. 10 is a flow chart showing an example of the operation of the control unit 11a of the first key management device 10a in this case. In the following description, it is assumed that the master door 21a is already unlocked.

[0122] As shown in the figure, in the control unit 11a, first, the code processing unit 111a acquires the holder ID of the holder 31 to be returned to the individual storage unit 24a by the first process (step 501). For example, the code processing unit 111a may acquire the holder ID included in the first administrator code read by the reading unit 27a as the holder ID of the holder 31 to be returned to the individual storage unit 24a.

[0123] Next, the storage control unit 119a identifies an individual storage unit 24a to which the holder 31 of the holder ID acquired in step 501 is to be returned (step 502). For example, the storage control unit 119a may identify any individual storage unit 24a not associated with a holder ID among the individual storage units 24a included in the first storage information 121a as the individual storage unit 24a to which the holder 31 is to be returned.

[0124] Next, the locking / unlocking control unit 113a controls the child door locking mechanism 142a so as to unlock the child door 22a of the individual storage unit 24a specified in step 502 (step 503). Then, the light emission control unit 114a controls the light emitting unit 242a provided on the sub-door 22a of the individual storage unit 24a specified in step 502 so as to emit light (step 504).

[0125] As a result, the manager recognizes the individual storage unit 24a to which the key has been moved, opens the sub-door 22a of the individual storage unit 24a, and returns the holder 31 to the individual storage unit 24a. Then, the storage detection unit 115a determines whether the holder 31 has been returned to the individual storage unit 24a (step 505). If it is not determined in step 505 that the holder 31 has been returned to the individual storage section 24a, the storage detection section 115a repeats the process of step 505. If it is determined in step 505 that the holder 31 has been returned to the individual storage section 24a, the control section 11a advances the process to step 506.

[0126] That is, the storage detection unit 115a acquires the holder ID of the holder 31 that has been returned to the individual storage unit 24a (step 506). For example, the storage detection unit 115a may acquire the holder ID read by the reading unit 243a as the holder ID of the holder 31 that has been returned to the individual storage unit 24a. Then, the determining unit 116a determines whether the holder ID acquired in step 501 matches the holder ID acquired in step 506 (step 507). If it is not determined in step 507 that the folder IDs match, the control section 11 a returns the process to step 505 . If it is determined in step 507 that the holder IDs match, the storage control unit 119a stores this holder ID in the first storage information 121a stored in the storage unit 12a (step 508). For example, the storage control unit 119a may store this holder ID in the first storage information 121a in association with the storage unit number of the individual storage unit 24a identified in step 502.

[0127] Finally, the storage control unit 119a stores the processing history of the first process in the storage unit 12a in a manner distinguishable from the processing history of other processes (step 509). If the first administrator code includes a user ID of the user of this code, the storage control unit 119a may include this user ID in the processing history.

[0128] Secondly, a case will be described where the code processing unit 111a determines that the code read by the reading unit 27a is a user code. In this case, the first key management device 10a executes a second process to enable the user to remove the holder 31 from the first key management device 10a to borrow the key 33, or a third process to enable the user to return the holder 31 to the first key management device 10a to return the key 33. 11-1 and 11-2 are flow charts showing an example of the operation of the control unit 11a of the first key management device 10a in this case. In the following description, it is assumed that the master door 21a is already unlocked.

[0129] 11-1, in the control unit 11a, first, the code processing unit 111a acquires the holder ID of the holder 31 to be removed from the individual storage unit 24a by the second process or the holder 31 to be returned to the individual storage unit 24a by the third process (step 521). For example, the code processing unit 111a may acquire the holder ID included in the user code read by the reading unit 27a as the holder ID of the holder 31 to be removed from the individual storage unit 24a or the holder 31 to be returned to the individual storage unit 24a.

[0130] Next, the storage control unit 119a judges whether the holder ID acquired in step 521 is stored in the storage unit 12a (step 522). The storage control unit 119a may judge, for example, whether the holder ID is stored in association with the individual storage unit 24a in the first storage information 121a. In this way, the storage control unit 119a judges whether the holder 31 with the holder ID acquired in step 521 has been removed from the individual storage unit 24a. If it is determined in step 522 that the holder ID is stored in the memory unit 12a, the holder 31 corresponding to that holder ID has not been removed from the individual storage unit 24a, and the first key management device 10a therefore executes the second process.

[0131] That is, the memory control unit 119a identifies the individual storage unit 24a from which the holder 31 of the holder ID acquired in step 521 is to be removed (step 523). For example, the memory control unit 119a may identify, from among the individual storage units 24a included in the first storage information 121a, the individual storage unit 24a to which the holder ID is associated, as the individual storage unit 24a from which the holder 31 is to be removed.

[0132] Next, the determination unit 116a determines whether the current time is within the usage period of the key 33 (step 524). The determination unit 116a may, for example, identify the usage period included in the user code read by the reading unit 27a as the usage period of the key 33.

[0133] If it is not determined in step 524 that the current time is within the usage period, the first key management device 10a ends the process. If it is determined in step 524 that the current time is within the usage period, the lock mechanism control unit 112a controls the lock mechanism 241a of the individual storage unit 24a so as to permit removal of the holder 31 from the individual storage unit 24a identified in step 523 (step 525). Furthermore, the locking / unlocking control section 113a controls the child door locking mechanism 142a so as to unlock the child door 22a of the individual storage section 24a specified in step 523 (step 526). Then, the light emission control unit 114a controls the light emitting unit 242a provided on the sub-door 22a of the individual storage unit 24a specified in step 523 so as to emit light (step 527).

[0134] As a result, the user recognizes the individual storage unit 24a from which the key was borrowed, opens the sub-door 22a of the individual storage unit 24a, and removes the holder 31 from the individual storage unit 24a. Then, the storage detection unit 115a determines whether the holder 31 has been removed from the individual storage unit 24a (step 528). If it is not determined in step 528 that the holder 31 has been removed from the individual storage section 24a, the storage detection section 115a repeats the process of step 528. If it is determined in step 528 that the holder 31 has been removed from the individual storage section 24a, the control section 11a advances the process to step 529.

[0135] That is, the storage control unit 119a deletes the holder ID acquired in step 521 from the first storage information 121a stored in the storage unit 12a (step 529). For example, the storage control unit 119a may delete the holder ID associated with the storage unit number of the individual storage unit 24a identified in step 523 from the first storage information 121a.

[0136] Finally, the storage control unit 119a stores the processing history of the second process in the storage unit 12a in a manner distinguishable from the processing history of other processes (step 530). If the user code includes a user ID of the user of this code, the storage control unit 119a may include this user ID in the processing history.

[0137] On the other hand, if it is not determined in step 522 that the holder ID is stored in the memory unit 12a, the holder 31 corresponding to that holder ID has been removed from the individual storage unit 24a, and the first key management device 10a executes the third process.

[0138] 11-2, the storage control unit 119a identifies an individual storage unit 24a to which the holder 31 of the holder ID acquired in step 521 is to be returned (step 531). For example, the storage control unit 119a may identify any individual storage unit 24a not associated with a holder ID among the individual storage units 24a included in the first storage information 121a as the individual storage unit 24a to which the holder 31 is to be returned.

[0139] Next, the locking / unlocking control unit 113a controls the child door locking mechanism 142a so as to unlock the child door 22a of the individual storage unit 24a specified in step 531 (step 532). Then, the light emission control unit 114a controls the light emitting unit 242a provided on the sub-door 22a of the individual storage unit 24a specified in step 531 so as to emit light (step 533).

[0140] This allows the user to recognize the individual storage unit 24a to which the key is to be returned, and opens the sub-door 22a of that individual storage unit 24a to return the holder 31 to that individual storage unit 24a. Then, the storage detection unit 115a determines whether the holder 31 has been returned to the individual storage unit 24a (step 534). If it is not determined in step 534 that the holder 31 has been returned to the individual storage section 24a, the storage detection section 115a repeats the process of step 534. If it is determined in step 534 that the holder 31 has been returned to the individual storage section 24a, the control section 11a advances the process to step 535.

[0141] That is, the storage detection unit 115a acquires the holder ID of the holder 31 that has been returned to the individual storage unit 24a (step 535). For example, the storage detection unit 115a may acquire the holder ID read by the reading unit 243a as the holder ID of the holder 31 that has been returned to the individual storage unit 24a. Then, the determining unit 116a determines whether the holder ID acquired in step 521 matches the holder ID acquired in step 535 (step 536). If it is not determined in step 536 that the folder IDs match, the control section 11a returns the process to step 534. If it is determined in step 536 that the holder IDs match, the storage control unit 119a stores this holder ID in the first storage information 121a stored in the storage unit 12a (step 537). For example, the storage control unit 119a may store this holder ID in the first storage information 121a in association with the storage unit number of the individual storage unit 24a identified in step 531.

[0142] Finally, the storage control unit 119a stores the processing history of the third process in the storage unit 12a in a manner distinguishable from the processing history of the other processes (step 538). If the user code includes a user ID of the user of this code, the storage control unit 119a may include this user ID in the processing history.

[0143] Thirdly, a case will be described in which the code processing unit 111a determines that the code read by the reading unit 27a is the code for the second administrator. In this case, the first key management device 10a executes a fourth process to enable the administrator to remove the holder 31 from the first key management device 10a in order to move the key 33 to the second key management device 10b. 12 is a flow chart showing an example of the operation of the control unit 11a of the first key management device 10a in this case. Note that in the following description, it is assumed that the master door 21a is already unlocked.

[0144] As shown in the figure, in the control unit 11a, first, the code processing unit 111a acquires the holder ID of the holder 31 to be removed from the individual storage unit 24a by the fourth process (step 541). For example, the code processing unit 111a may acquire the holder ID included in the second administrator code read by the reading unit 27a as the holder ID of the holder 31 to be removed from the individual storage unit 24a.

[0145] Next, the memory control unit 119a identifies the individual storage unit 24a from which the holder 31 of the holder ID acquired in step 541 is to be removed (step 542). For example, the memory control unit 119a may identify, from among the individual storage units 24a included in the first storage information 121a, the individual storage unit 24a to which the holder ID is associated as the individual storage unit 24a from which the holder 31 is to be removed.

[0146] Next, the lock mechanism control section 112a controls the lock mechanism 241a of the individual housing section 24a so as to permit removal of the holder 31 from the individual housing section 24a specified in step 542 (step 543). Furthermore, the lock / unlock control unit 113a controls the child door locking mechanism 142a so as to unlock the child door 22a of the individual storage unit 24a identified in step 542 (step 544). Then, the light emission control unit 114a controls the light emitting unit 242a provided on the sub-door 22a of the individual storage unit 24a specified in step 542 so as to emit light (step 545).

[0147] As a result, the manager recognizes the individual storage unit 24a from which the key was moved, opens the sub-door 22a of the individual storage unit 24a, and removes the holder 31 from the individual storage unit 24a. Then, the storage detection unit 115a determines whether the holder 31 has been removed from the individual storage unit 24a (step 546). If it is not determined in step 546 that the holder 31 has been removed from the individual storage section 24a, the storage detection section 115a repeats the process of step 546. If it is determined in step 546 that the holder 31 has been removed from the individual storage section 24a, the control section 11a advances the process to step 547.

[0148] That is, the storage control unit 119a deletes the holder ID acquired in step 541 from the first storage information 121a stored in the storage unit 12a (step 547). For example, the storage control unit 119a may delete the holder ID associated with the storage unit number of the individual storage unit 24a identified in step 542 from the first storage information 121a.

[0149] Finally, the storage control unit 119a stores the processing history of the fourth process in the storage unit 12a so as to be distinguishable from the processing history of the other processes (step 548). If the second administrator code includes the user ID of the user of this code, the storage control unit 119a may include this user ID in the processing history.

[0150] [Operation of the second key management device] In the second key management device 10b, first, the code processing unit 111b of the control unit 11b determines whether the code read by the reading unit 27b is the first administrator code or the second administrator code.

[0151] First, a case will be described in which the code processor 111b determines that the code read by the reader 27b is the code for the first administrator. In this case, the second key management device 10b executes a fifth process to enable the administrator to remove the holder 31 from the second key management device 10b in order to move the key 33 to the first key management device 10a. FIG. 13 is a flowchart showing an example of the operation of the control unit 11b of the second key management device 10b in this case.

[0152] As shown in the figure, in the control unit 11b, first, the code processing unit 111b acquires the holder ID of the holder 31 to be removed from the individual storage unit 24b by the fifth process (step 601). For example, the code processing unit 111b may acquire the holder ID included in the first administrator code read by the reading unit 27b as the holder ID of the holder 31 to be removed from the individual storage unit 24b.

[0153] Next, the memory control unit 119b specifies the individual storage unit 24b from which the holder 31 of the holder ID acquired in step 601 is to be removed (step 602). For example, the memory control unit 119b may specify, among the individual storage units 24b included in the second storage information 121b, the individual storage unit 24b to which the holder ID is associated as the individual storage unit 24b from which the holder 31 is to be removed.

[0154] Next, the lock mechanism control section 112b controls the lock mechanism 241b of the individual housing section 24b so as to permit removal of the holder 31 from the individual housing section 24b specified in step 602 (step 603). Then, the light emission control unit 114b controls the light emitting unit 242b provided in the vicinity of the individual storage unit 24b identified in step 602 so as to emit light (step 604).

[0155] This allows the administrator to recognize the individual storage unit 24b from which the key was moved, and remove the holder 31 from that individual storage unit 24b. Then, the storage detection unit 115b determines whether the holder 31 has been removed from the individual storage unit 24b (step 605). If it is not determined in step 605 that the holder 31 has been removed from the individual storage section 24b, the storage detection section 115b repeats the process of step 605. If it is determined in step 605 that the holder 31 has been removed from the individual storage section 24b, the control section 11b advances the process to step 606.

[0156] That is, the storage control unit 119b deletes the holder ID acquired in step 601 from the second storage information 121b stored in the storage unit 12b (step 606). For example, the storage control unit 119b may delete the holder ID associated with the storage unit number of the individual storage unit 24b identified in step 602 from the second storage information 121b.

[0157] Finally, the storage control unit 119b stores the processing history of the fifth process in the storage unit 12b in a manner distinguishable from the processing history of the other processes (step 607). If the first administrator code includes a user ID of the user of this code, the storage control unit 119b may include this user ID in the processing history.

[0158] Secondly, a case will be described in which the code processing unit 111b determines that the code read by the reading unit 27b is the code for the second administrator. In this case, the second key management device 10b executes a sixth process to enable the administrator to return the holder 31 to the second key management device 10b in order to move the key 33 from the first key management device 10a. FIG. 14 is a flowchart showing an example of the operation of the control unit 11b of the second key management device 10b in this case.

[0159] As shown in the figure, in the control unit 11b, first, the code processing unit 111b acquires the holder ID of the holder 31 to be returned to the individual storage unit 24b by the sixth process (step 621). For example, the code processing unit 111b may acquire the holder ID included in the second administrator code read by the reading unit 27b as the holder ID of the holder 31 to be returned to the individual storage unit 24b.

[0160] Next, the memory control unit 119b identifies an individual storage unit 24b to which the holder 31 of the holder ID acquired in step 621 is to be returned (step 622). For example, the memory control unit 119b may identify any individual storage unit 24b not associated with a holder ID among the individual storage units 24b included in the second storage information 121b as the individual storage unit 24b to which the holder 31 is to be returned.

[0161] Next, the light emission control unit 114b controls the light emitting unit 242b provided in the vicinity of the individual storage unit 24b identified in step 622 so as to emit light (step 623).

[0162] This allows the manager to recognize the individual storage unit 24b to which the key has been moved, and to return the holder 31 to that individual storage unit 24b. The storage detection unit 115b then determines whether the holder 31 has been returned to the individual storage unit 24b (step 624). If it is not determined in step 624 that the holder 31 has been returned to the individual storage section 24b, the storage detection section 115b repeats the process of step 624. If it is determined in step 624 that the holder 31 has been returned to the individual storage section 24b, the control section 11b advances the process to step 625.

[0163] That is, the storage detection unit 115b acquires the holder ID of the holder 31 that has been returned to the individual storage unit 24b (step 625). For example, the storage detection unit 115b may acquire the holder ID read by the reading unit 243b as the holder ID of the holder 31 that has been returned to the individual storage unit 24b. Then, the determining unit 116b determines whether the folder ID acquired in step 621 matches the folder ID acquired in step 625 (step 626). If it is not determined in step 626 that the folder IDs match, the control section 11b returns the process to step 624. If it is determined in step 626 that the holder IDs match, the storage control unit 119b stores this holder ID in the second storage information 121b stored in the storage unit 12b (step 627). For example, the storage control unit 119b may store this holder ID in the second storage information 121b in association with the storage unit number of the individual storage unit 24b identified in step 622.

[0164] Finally, the storage control unit 119b stores the processing history of the sixth process in the storage unit 12b in a manner distinguishable from the processing history of the other processes (step 628). If the second administrator code includes a user ID of the user of this code, the storage control unit 119b may include this user ID in the processing history.

[0165] In the above, the fifth process of enabling the administrator to remove the holder 31 in order to move the key 33 to the first key management device 10a and the sixth process of enabling the administrator to return the holder 31 in order to move the key 33 from the first key management device 10a have been shown as processes executed by the second key management device 10b. However, the second key management device 10b may lend and return the key 33 to general users, similar to the first key management device 10a. In that case, the second key management device 10b may further execute a process of enabling the user to remove the holder 31 in order to borrow the key 33 and a process of enabling the user to return the holder 31 in order to return the key 33.

[0166] [First Modification] In the first modification, the key management system 1 leaves a trail of identity authentication of the user of the key 33 in the form of a one-time password and a camera image. First, the user contacts the administrator to reserve the use of the key 33, including information such as the user ID, the key 33 to be used, and the period of use. It is assumed that the user has registered an image of his or her face in advance. The administrator then accepts this reservation and inputs information such as the user ID, the key 33 to be used, and the period of use into the key management system 1. In response to this, the key management system 1 issues a user code. The key management system 1 also issues a one-time password several hours before the key 33 starts to be used. Thereafter, the user authenticates himself / herself using the user code, one-time password, and camera image, and extracts and uses the key 33 from the first key management device 10a. Here, the user code and one-time password are issued by the key management system 1. The camera image is an image of the user's face taken by a camera (not shown) provided in the first key management device 10a. The key management system 1 then records at least the one-time password and the camera image used for the identity authentication.

[0167] [Second modified example] In a second modified example, the key management system 1 leaves a trail of identity authentication of the user of the key 33 in the form of driver's license read data. First, the user contacts the administrator to reserve the use of the key 33, including information such as the user ID, the key 33 to be used, and the period of use. It is assumed that the user has registered an image of his or her face in advance. The administrator then accepts this reservation and inputs information such as the user ID, the key 33 to be used, and the period of use into the key management system 1. In response to this, the key management system 1 issues a user code. Thereafter, the user authenticates himself / herself using the user code and the driver's license read data, and extracts the key 33 from the first key management device 10a to use it. Here, the user code is issued by the key management system 1. The driver's license read data is data obtained by reading the driver's license with a scanner (not shown) provided in the first key management device 10a. The key management system 1 then records at least the driver's license read data used for the identity authentication.

[0168] [Third modified example] In the third modification, when the key management system 1 manages the keys 33 of the in-store devices, it switches the notification mode of the removable keys 33 according to the status and priority of the in-store devices. For example, when the money handling machine is in an error state, the keys 33 needed to clear the error are highlighted in red. Another example of switching the notification mode is when the amount of money stored in the money handling machine is nearly empty (a state where the amount of money is getting low), and the keys 33 needed to replenish the money are highlighted in yellow.

[0169] [Fourth Variation] In a fourth variant, the key management system 1 is capable of storing the name of the key 33 (for example, the key for ATM No. 1) in association with the location where the key 33 is used (for example, the second ATM from the left in the ATM corner).

[0170] [Fifth Variation] In the fifth modification, the key management system 1 is provided with a name search function relating to the name of the key 33 or the place where the key 33 is used, and is capable of notifying the holder 31 of a search word that is found.

[0171] [Sixth Variation] The sixth modified example provides an item management device that manages items such as seals, USB memory sticks, etc., in addition to keys. In that case, the invention can be understood by replacing all the "keys" described so far with "items." In other words, the sixth variant can be understood as "an item management device comprising a plurality of storage units for storing holders for holding items, a reading unit for reading one-dimensional or two-dimensional codes, and an execution unit for, if the code read by the reading unit is a first code, executing a first process to enable a holder removed from another item management device to be returned to one of the plurality of storage units, and, if the code read by the reading unit is a second code, executing a second process to enable the holder that was returned by the first process to be removed." The sixth variant can also be interpreted as "an item management device comprising a plurality of storage units for storing holders for holding items, a reading unit for reading one-dimensional or two-dimensional codes, and an execution unit for executing a fifth process that enables a holder to be removed from one of the plurality of storage units to be returned to another item management device if the code read by the reading unit is a fifth code, and for executing a sixth process that enables a holder removed from another item management device to be returned to one of the plurality of storage units if the code read by the reading unit is a sixth code." Furthermore, the sixth variant can also be interpreted as "an item management system including a first item management device and a second item management device, the first item management device having a plurality of first storage sections for storing holders for holding items, a first reading section for reading one-dimensional or two-dimensional codes, and a first execution section for executing a first process to enable a holder removed from the second item management device to be returned to one of the plurality of first storage sections if the code read by the first reading section is a first code, and for executing a second process to enable the holder returned by the first process to be removed if the code read by the first reading section is a second code."

[0172] [effect] In this embodiment, the administrator issues a first administrator code for moving the key 33 from the second key management device 10b to the first key management device 10a, and a user code for the user to use the key 33 moved to the first key management device 10a. This improves the convenience of using the codes to lend out the key 33 using the first key management device 10a. [Explanation of symbols]

[0173] 1...Key management system, 10a...First key management device, 10b...Second key management device, 11a, 11b...Control unit, 12a, 12b...Memory unit, 13a, 13b...Communication unit, 141a...Master door locking mechanism, 142a...Child door locking mechanism, 24a, 24b...Individual storage unit, 241a, 241b...Lock mechanism, 242a, 242b...Light emitting unit, 243a, 243b...Reading unit, 25a, 25b...Display operation unit, 26a...Card reader, 27a, 27b...Reading unit, 40...Code issuing device

Claims

1. a plurality of storage sections for storing holders for holding keys; a reading unit that reads one-dimensional or two-dimensional codes; If the code read by the reading unit is a first code, a first process is executed to enable the holder to be returned to any one of the plurality of storage units; an execution unit that executes a second process to make it possible to remove the holder that has been returned by the first process when the code read by the reading unit is a second code; A key management device comprising:

2. The key management device according to claim 1 , wherein the second code is issued in response to a reservation for use of a key held by a holder extracted by the second process, or an object to be used with the key.

3. The key management device according to claim 2 , wherein the first code is issued together with the second code in response to the reservation for use.

4. the first code includes holder identification information that identifies a holder to be returned by the first process; The key management device according to claim 1 , wherein the execution unit identifies a holder that can be returned by the first process based on the holder identification information.

5. The key management device according to claim 4 , wherein the execution unit identifies a storage unit into which the holder is to be returned by the first process based on the holder identification information.

6. the second code includes holder identification information for identifying a holder to be removed by the second process, The key management device according to claim 1 , wherein the execution unit identifies a holder that is to be made removable by the second process based on the holder identification information.

7. The key management device according to claim 6 , wherein the execution unit identifies a storage unit from which the holder is to be removed in the second process based on the holder identification information.

8. the second code includes period information; The key management device of claim 1, wherein the execution unit prevents the holder returned by the first processing from being removed by the second processing if the current date and time is outside the period information contained in the second code read by the reading unit.

9. The key management device of claim 1, wherein the execution unit executes a third process that enables a holder removed by the second process to be returned to any of the plurality of storage units when the code read by the reading unit is a third code.

10. the third code is the second code, The key management device of claim 9, wherein the execution unit executes the second process if the code read by the reading unit is the second code and the holder that was put back in by the first process has not been removed, and executes the third process if the holder that was put back in by the first process has been removed.

11. the second code includes period information; The key management device described in claim 10, wherein the execution unit makes a holder that was put back by the first processing unable to be removed by the second processing when the current date and time is outside the period information contained in the second code read by the reading unit, and makes a holder that was removed by the second processing able to be put back by the third processing.

12. The key management device according to claim 9, wherein the execution unit executes a fourth process that enables removal of the holder that was put back in by the third process when the code read by the reading unit is a fourth code.

13. The destination for returning the holder removed by the second process is set to the device itself, The key management device according to claim 12 , wherein a destination for returning the holder removed by the fourth process is set to another key management device.

14. the first code, the second code, the third code, and the fourth code each include code identification information for identifying the code; 13. The key management device according to claim 12, wherein the execution unit determines whether the code read by the reading unit is the first code, the second code, the third code, or the fourth code based on the code identification information.

15. at least one of the first code, the second code, the third code, and the fourth code includes user identification information that identifies a user of the code; The key management device according to claim 12 , wherein the execution unit stores a processing history including the user identification information.

16. a plurality of storage sections for storing holders for holding keys; a reading unit that reads one-dimensional or two-dimensional codes; If the code read by the reading unit is a fifth code, a fifth process is executed to enable a holder to be returned to another key management device to be removed from any of the plurality of storage units; an execution unit that executes a sixth process to allow the holder to be returned to any one of the plurality of storage units when the code read by the reading unit is a sixth code; A key management device comprising:

17. The holder returned by the sixth process is a holder removed from another key management device, the fifth code is issued in response to a reservation for use of a key held by the holder removed by the fifth process or an object to be used with the key, The key management device according to claim 16 , wherein the sixth code is issued after the holder returned by the sixth process is returned to the other key management device.

18. the fifth code includes holder identification information for identifying a holder to be removed by the fifth process, The key management device according to claim 16 , wherein the execution unit identifies a holder that is to be made removable by the fifth process based on the holder identification information.

19. The key management device according to claim 18 , wherein the execution unit identifies a storage unit from which the holder is to be removed in the fifth process based on the holder identification information.

20. the sixth code includes holder identification information for identifying a holder to be replaced by the sixth process; The key management device according to claim 16 , wherein the execution unit identifies a holder that can be returned by the sixth process based on the holder identification information.

21. The key management device according to claim 20 , wherein the execution unit identifies a storage unit into which the holder is to be returned by the sixth process based on the holder identification information.

22. a first key management device and a second key management device; the first key management device, a plurality of first storage sections for storing holders for holding keys; a first reading unit that reads one-dimensional or two-dimensional codes; If the code read by the first reading unit is a first code, a first process is executed to enable the holder removed from the second key management device to be returned to any one of the plurality of first storage units; a first execution unit that executes a second process to enable removal of the holder that has been returned by the first process when the code read by the first reading unit is the second code; 1. A key management system comprising:

23. The first execution unit: if the code read by the first reading unit is a third code, a third process is executed to enable the holder removed by the second process to be returned to any one of the plurality of first storage units; 23. The key management system according to claim 22, wherein, if the code read by the first reading unit is a fourth code, a fourth process is executed to enable removal of the holder that was put back in by the third process.

24. the second key management device, a plurality of second storage sections for storing holders for holding keys; a second reading unit for reading one-dimensional or two-dimensional codes; if the code read by the second reading unit is the first code, a fifth process is executed to enable the holder returned by the first process to be removed from any one of the plurality of second storage units; a second execution unit that executes a sixth process to enable the holder removed by the fourth process to be returned to any one of the plurality of second storage units when the code read by the second reading unit is the fourth code; 24. The key management system of claim 23, comprising:

Images