JP7450381B2 - Article management system and article management device - Google Patents

Description

The present invention relates to an article management system and an article management device.

BACKGROUND ART Conventionally, in financial institutions, supermarkets, and other distribution stores, keys used to operate processing equipment and keys used to open and close managed areas have been strictly controlled. In particular, key management devices that require electronic authentication are used to manage keys that require user restrictions and recording of usage history.
One of this type of key management device is the device described in Patent Document 1. The key management device described in Patent Document 1 is provided with a mounting hole into which a key chain to which an item to be managed, such as a key, can be attached is removably attached, and only a person who has successfully authenticated can insert the key into the mounting hole. The key chain can be attached and detached.

JP 2019-27203 Publication

Conventional key management devices manage the history and who has attached or removed a key chain to which a key or the like is attached, but they do not track the items attached to the key chain.

An object of the present invention is to make it possible to manage articles that are objects of management.

The invention according to claim 1 provides a storage section into which a member to which at least one or more articles to be managed is connected is attached and detached, and a type of article connected to the specific member that is attached to and detached from the storage section. a management unit that manages information in association with at least one of a specific storage section and a specific member; a control unit that reads information identifying the article from the article connected to the member; and a reading section, the control section determining whether or not to read information identifying the article from the article connected to the member, based on the information regarding the type, and when reading is performed. If the determination is made, the article management system controls the reading section to read information identifying the article.
The invention according to claim 2 provides a storage section into which a member to which at least one or more objects to be managed is connected is attached and detached, and a type of article connected to the specific member that is attached to and detached from the storage section. a management unit that manages information related to the storage unit in association with at least one of the specific storage unit and the specific member, a reception unit that receives registration of information related to the type, a control unit, and a control unit that is connected to the member. a reading section that reads information identifying the article from the article connected to the member, and the control section reads information identifying the article from the article connected to the member based on the information regarding the type. The article management system determines whether or not to perform reading, and when it is determined to perform reading, controls the reading section to read information that identifies the article.
In the invention according to claim 3 , the control unit determines whether or not to read information identifying the article from the article connected to the member, based on the information regarding the type, and 3. The article management system according to claim 1 , wherein if it is determined that the reading is not performed, the reading section does not control the reading of information for identifying the article.
The invention according to claim 4 is any one of claims 1 to 3, wherein the control section manages information identifying the article in association with the corresponding storage section or the corresponding member. This is an article management system described in .
In the invention according to claim 5 , when it is determined based on the information regarding the type that a storage medium is included in the article connected to the member attached to the accommodating part, the control unit 5. The article management system according to claim 1 , wherein the article management system determines whether or not a virus check has been performed on the article.
In the invention according to claim 6 , the control unit determines whether virus checks for all storage media connected to the member have been completed based on information identifying the article read from the storage medium. 6. The article management system according to claim 5 .
The invention according to claim 7 is characterized in that the control section permits attachment of the member to a specific storage section based on the execution date and time of a virus check on the storage medium attached to the member . Or the article management system described in 6 .
In the invention according to claim 8 , the control unit determines whether the virus check is executed within a time determined according to at least one of the number and data capacity of storage media to be subjected to the virus check. , an article management system according to claim 7 .
The invention according to claim 9 is the article management system according to any one of claims 5 to 8 , further comprising a virus check execution unit that executes a virus check.
In the invention according to claim 10 , when it is determined based on the information regarding the type that a storage medium is included in the article connected to the member attached to the accommodating part, the controller 10. The article management system according to claim 1 , wherein the article management system determines whether erasure of data for the article has been executed.
In the invention according to claim 11 , the control unit determines whether the storage medium is prohibited from erasing data before executing data erasure, and if it is determined that erasure of data is prohibited, the control unit deletes the data. 11. The article management system according to claim 10 , wherein the article management system does not perform deletion of the item.
In the invention according to claim 12 , the control unit determines whether data has been erased from all storage media connected to the member, based on information identifying the article read from the storage medium. The article management system according to any one of claims 9 to 11 , wherein the article management system makes a determination.
In the invention according to claim 13 , when the storage medium mounted as a target for erasing data is not associated with the storage unit or the member taken out from the storage unit, the control unit erases the data. The article management system according to any one of claims 9 to 12 , wherein the article management system does not execute.
The invention according to claim 14 is the article management system according to any one of claims 9 to 13 , wherein the control unit manages a history of execution of data deletion in association with a storage medium.
The invention according to claim 15 is characterized in that the control unit permits attachment of the member to a specific storage unit based on the execution date and time of erasing data from a storage medium attached to the member. The article management system according to any one of Items 9 to 14 .
In the invention according to claim 16 , the control unit determines whether data deletion has been performed within a time determined according to either the number of storage media that are data deletion targets or the data capacity. The article management system according to claim 15 , wherein the article management system makes a determination.
The invention according to claim 17 is the article management system according to any one of claims 10 to 16 , further comprising a data erasure execution unit that executes erasure of data on a storage medium.
In the invention according to claim 18 , when it is determined that a storage medium is included in the article connected to the member to be removed from the accommodating part, based on the information regarding the type, the control unit controls the storage medium. The article management system according to any one of claims 1 to 15 , which determines whether a virus check has been performed.
In the invention according to claim 19 , when it is determined based on the information regarding the type that the article connected to the member to be removed from the storage section includes a storage medium, the control section The article management system according to any one of claims 1 to 14 , wherein the article management system determines whether or not data has been erased for the article.
The invention according to claim 20 provides a storage section to which a member to which at least one or more objects to be managed is connected is attached and detached, and a type of article connected to the specific member that is attached to and detached from the storage section. a management unit that manages information in association with at least one of a specific storage section and a specific member; a control unit that reads information identifying the article from the article connected to the member; and a reading section, the control section determining whether or not to read information identifying the article from the article connected to the member, based on the information regarding the type, and when reading is performed. If the determination is made, the article management device controls the reading unit to read information that identifies the article.
The invention as set forth in claim 21 provides a storage section to which a member to which at least one or more articles to be managed is connected is attached and detached, and a type of article connected to the specific member that is attached to and detached from the storage section. a management unit that manages information related to the storage unit in association with at least one of the specific storage unit and the specific member, a reception unit that receives registration of information related to the type, a control unit, and a control unit that is connected to the member. a reading section that reads information identifying the article from the article connected to the member, and the control section reads information identifying the article from the article connected to the member based on the information regarding the type. The article management device determines whether or not to perform reading, and when it is determined to perform reading, controls the reading section to read information that identifies the article.

According to the present invention, it is possible to manage articles that are objects of management.

1 is a diagram illustrating a schematic configuration of a key management device used in Embodiment 1. FIG. FIG. 3 is a diagram illustrating a USB port provided at the upper left side of the housing. It is a figure explaining the example of composition of a holder accommodation area and a holder accommodation part. It is a figure explaining the example of composition of the key chain used in this embodiment. (A) is an example of the appearance of the key holder viewed diagonally from the front side, and (B) is an example of the appearance of the key holder viewed diagonally from the back side. It is a figure explaining two members which constitute a key holder. (A) shows a state in which the two members are integrated, and (B) shows a state in which the two members are released from integration. FIG. 3 is a diagram illustrating an example of connecting an article to a key holder. (A) shows an example in which one key is connected to a key holder, and (B) shows an example in which one USB memory is connected to the key holder. FIG. 2 is a diagram illustrating a configuration example of a control system of a key management device. It is a flowchart which shows an example of the processing operation which a control part performs when a user matches a key holder with a holder accommodating part, and registers it. It is a figure showing an example of a menu screen. It is a figure which shows an example of the screen used for setting a folder name. It is a figure which shows an example of the screen used for the setting of the goods managed with a key holder. It is a figure which shows the example of the screen displayed when a USB memory is included in the article|item targeted for management. FIG. 3 is a diagram illustrating an example of a screen displayed after a USB memory is attached to a USB port. FIG. 6 is a diagram illustrating an example of a setting confirmation screen displayed after the serial number of the USB memory is registered. FIG. 3 is a diagram illustrating an example of a management table stored in a storage unit after setting a holder name. It is a flowchart which shows an example of the processing operation which a control part performs when a user removes a key holder from a holder accommodating part. It is a figure showing an example of a menu screen. FIG. 3 is a diagram showing an example of a screen used to select a keychain to be removed. It is a figure which shows the example of the screen displayed when a USB memory is included in the article|item targeted for management. FIG. 7 is a diagram illustrating an example of a screen displayed when a USB memory that is not registered in a holder accommodating part from which a key holder is removed is attached to a USB port. FIG. 6 is a diagram illustrating an example of a screen displayed when erasing data from a USB memory attached to a USB port is prohibited. FIG. 3 is a diagram illustrating an example of a virus check management table used to manage the execution history of virus checks. FIG. 3 is a diagram illustrating an example of a data erasure management table used to manage data erasure execution history. FIG. 6 is a diagram illustrating an example of a screen that is displayed when the work time for virus checking or data deletion has exceeded. It is a flowchart which shows an example of the processing operation which a control part performs when a user returns a key holder to a holder storage part. It is a figure showing an example of a menu screen. It is a figure which shows an example of the screen used for selecting the key chain to return. It is a figure which shows the example of the screen displayed when a USB memory is included in the article|item targeted for management. FIG. 3 is a diagram illustrating a schematic configuration of a key management device used in another embodiment. 1 is a diagram illustrating a configuration example of a key management system in which a key management device and a server are connected via a network. FIG.

Hereinafter, embodiments will be described in detail with reference to the accompanying drawings.
<Embodiment 1>
<Overall configuration of the device>
Below, the device configuration and the like of the key management device according to this embodiment will be explained using FIGS. 1 to 5.
FIG. 1 is a diagram illustrating a schematic configuration of a key management device 10 used in the first embodiment. Note that the key management device 10 is an example of an article management device.
The key management device 10 shown in FIG. 1 has a substantially rectangular parallelepiped-shaped housing 11, and a front door 12 that can be opened and closed is provided on the front side of the housing 11. The front door 12 shown in FIG. 1 is in an open state. When the front door 12 is open, the user can access the key holder 30 housed in the housing 11. In other words, the user can remove the key holder 30 from inside the housing 11 or return the key holder 30 to the inside of the housing 11.

The front door 12 is provided with a door locking section 13 (not shown) (see FIG. 7) that locks the front door 12.
If the front door 12 is closed and locked, the user cannot open the front door 12. Naturally, the user cannot access the key holder 30 housed in the housing 11.
On the other hand, when the front door 12 is unlocked, the user can open the front door 12 and access the key holder 30 housed in the housing 11.

A handle 14 is provided on the top surface of the housing 11 shown in FIG. The handle 14 shown in FIG. 1 has a generally U-shape and is rotatably attached to the housing 11.
The handle 14 shown in FIG. 1 is in a stored state and is in a state where it falls down along the top surface of the housing 11. On the other hand, when carrying the key management device 10, the handle 14 is raised approximately perpendicular to the top surface of the housing 11. The state in which the handle 14 is raised is called the standing state. The key management device 10 can be carried by the user grasping and lifting the handle 14 in a standing position.
Note that the handle 14 may be able to be inserted into and removed from the upper surface of the housing 11 in a vertical direction. In this case, in the stored state, the handle 14 is stored inside the casing 11 except for the portion that the user grips. On the other hand, when in use, the handle 14 is pulled upward from the housing 11.

Inside the casing 11, a power source (battery) (not shown) is built-in. Further, the housing 11 is provided with a power switch (not shown). When the user turns on the power switch, power is supplied to each part constituting the key management device 10, and the key management device 10 is enabled to operate. In this way, the key management device 10 in this embodiment can operate without receiving power from an external power source.
At the upper part of the front side of the housing 11, an operation display section 15 composed of, for example, a touch panel, and an authentication section 16 used for user authentication are provided. In the case of FIG. 1, the operation display section 15 and the authentication section 16 are arranged side by side on the left and right sides of a plate-shaped substrate. The plate-shaped substrate in this embodiment is rotatably attached to the housing 11. In the case of FIG. 1, the plate-shaped substrate is raised so as to be approximately perpendicular to the upper surface of the casing 11. Note that the locations where the operation display section 15 and the authentication section 16 are attached are merely examples, and they may be attached to different members or positions.

The operation display section 15 displays an operation screen, a screen showing the storage status of articles, and the like, and is also used to receive operations from the user. The user gives various instructions to the control unit 40 (see FIG. 7), not shown, through touch operations on the operation display unit 15.
The authentication unit 16 includes an IC card reader 16A that reads information that identifies the user from an IC (Integrated Circuit) card owned by the user who uses the key management device 10. IC cards are also called smart cards. However, the device whose information is to be read by the authentication unit 16 is not limited to an IC card, but may be a smartphone, a wearable computer, or other information terminal.
The authentication unit 16 in this embodiment reads a user ID (=IDentification) and other information that identifies the user, and transmits it to the control unit 40. The authentication unit 16 is also used to read information necessary to confirm the authority of the user who owns the IC card. However, information regarding user authentication and authority confirmation may be common.

The user ID in this embodiment includes, for example, the user's name, employee number, department to which the user belongs, and other information.
The authentication result is used not only to unlock or lock the front door 12 but also when the key holder 30 is removed or returned.
Only users who are successfully authenticated are allowed to unlock or lock the front door 12. Furthermore, access to the key holder 30 is permitted within the scope of the confirmed authority. By utilizing the authority information, for example, it becomes possible to allow a certain user to access all key holders 30, while allowing another user to access only a specific key holder 30.

The authentication unit 16 in this embodiment uses the IC card reader 16A to acquire information that identifies the user, but it is also possible to use a vein authentication unit that acquires information about veins in fingers, palms, etc. . The vein authentication unit includes an LED (=Light Emitting Diode) that outputs far-infrared light, and a camera that captures an image of the far-infrared light that has passed through or been reflected at the target site. When using the vein authentication unit, the control unit 40 (see FIG. 7) authenticates the user using a vein pattern registered for each user.
Further, the upper part of the front side of the housing 11 is provided with a lock release part 17 used to release the locked state of the lock mechanism provided on the key holder 30. In the case of the present embodiment, the lock mechanism provided on the key holder 30 can be locked only by the unlocking part 17. By releasing the locked state, it becomes possible to remove the ring 31 connected to the key holder 30 and to attach or remove an article (not shown) from the ring 31.

The lock release portion 17 is provided with an accommodation hole 17A for accommodating the key holder 30 to be released from the locked state. An antenna (not shown) is provided in the inner part of the accommodation hole 17A. This antenna is used to read information that physically identifies the key holder 30 from the key holder 30 while the key holder 30 is accommodated in the accommodation hole 17A. The information read by the antenna is transmitted to the serial number reading section 40C of the control section 40. In the case of this embodiment, communication between the key holder 30 and the antenna conforms to the short-range communication standard. However, to read the information that physically identifies the key holder 30, it is also possible to use optical communication or image reading using a camera.

In addition, a USB (=Universal Serial Bus) port 18 is provided on the upper left side of the housing 11. FIG. 2 is a diagram illustrating the USB port 18 provided on the upper left side of the housing 11. The USB port 18 is provided with a USB interface circuit section 18A. The USB interface circuit section 18A is used for reading and writing data to and from the USB memory.
Further, inside the housing 11, a holder accommodation area 19 for accommodating a plurality of key holders 30 is provided. The holder accommodating area 19 is provided with a plurality of holder accommodating portions 20 that accommodate the key holders 30 . The holder accommodating portion 20 includes a cylindrical accommodating hole 20A (see FIG. 3) extending in the depth direction (Y-axis direction).
The key holder 30 here is an example of a member to which articles to be managed are connected, and the holder housing section 20 is an example of a housing section to which a member to which articles to be managed are connected is attached and detached. .

In the case of the key management device 10 shown in FIG. 1, the holder storage area 19 is divided into three stages in the height direction (Z-axis direction), and ten holder storage sections 20 are arranged in each stage. As shown in FIG. 1, ten holder accommodating parts 20 in each stage are arranged in the width direction (X-axis direction). As a result, 30 holder accommodating portions 20 are provided in the holder accommodating area 19 shown in FIG.
In the case of this embodiment, all the key holders 30 attached to the holder accommodating portion 20 have the same external shape. For this reason, the shape of the holder accommodating portion 20 on the side to which the key holder 30 is attached is also all the same. Therefore, the key holder 30 can be attached to any holder accommodating section 20.

The thirty holder accommodating parts 20 are given identification numbers. In the case of this embodiment, the holder accommodating portion 20 located at the top level is numbered from "1" to "10" in order from the left end to the right. Further, the holder accommodating portions 20 located in the middle stage are numbered "11" to "20" in order from the left end to the right. The holder accommodating portions 20 located at the lowest stage are numbered "21" to "30" in order from the left end to the right.
Note that a light guide 21 is attached to the outer periphery of the accommodation hole 20A that constitutes the holder accommodation section 20. The light guide 21 includes, for example, a built-in LED. When a plurality of LEDs with different colors of light are built into the light guide 21, the color of the light emitted by the LEDs can also inform the user of the position to attach or detach the key holder 30, etc.

<Configuration of holder accommodation area>
FIG. 3 is a diagram illustrating a configuration example of the holder accommodation area 19 and the holder accommodation section 20. As shown in FIG. The structure shown in FIG. 3 represents a portion of the holder accommodation area 19 corresponding to a certain stage.
The holder accommodation area 19 is formed by a holder accommodation plate 19A. The holder accommodating plate 19A is provided with ten openings 19B corresponding to the ten holder accommodating parts 20. In FIG. 3, only five of the ten holder housing parts 20 are depicted. The key holder 30 passes through the opening 19B and is attached to and detached from the holder accommodating portion 20.
Although not shown in FIG. 3, a number is written above the opening 19B of the holder housing plate 19A to identify the holder housing portion 20 corresponding to the opening 19B.

The light guide 21 described above is attached to the holder accommodation plate 19A from the back side of the opening 19B, as shown in FIG. The light from the light guide 21 can be visually observed by the user while attached to the holder accommodation plate 19A.
Approximately half of the tip end side of the key holder 30 that has passed through the opening 19B of the holder accommodation plate 19A is accommodated in the accommodation hole 20A.
A locking mechanism (not shown) is provided inside the holder accommodating portion 20. The locking mechanism (not shown) is electric, and locking and unlocking are controlled by electric signals from the control unit 40. A lock mechanism (not shown) prevents an unauthorized user from removing the key holder 30 from the accommodation hole 20A. In addition, the side surface of the key holder 30 shown in FIG. 3 is provided with a protrusion 30C that comes into contact with a flexible latch provided inside the accommodation hole 20A when the key holder 30 is inserted into the accommodation hole 20A. .

<Key chain configuration>
FIG. 4 is a diagram illustrating a configuration example of the key holder 30 used in this embodiment. (A) is an example of the external appearance of the key holder 30 as seen diagonally from the front side, and (B) is an example of the external appearance of the key holder 30 as seen from the diagonally rear side. The front side here refers to the side visible to the user when the key holder 30 is attached to the key management device 10. The back side refers to the side of the key holder 30 that is attached to the accommodation hole 20A (see FIG. 3) of the key management device 10. In addition, in this embodiment, the surface of the key holder 30 on the side to be attached to the key management device 10 is also referred to as the back surface.
FIG. 5 is a diagram illustrating two members that constitute the key holder 30. As shown in FIG. (A) shows a state in which the two members are integrated, and (B) shows a state in which the two members are released from integration.
The two members here are the main body member 30A and the drawer member 30B. In the case of this embodiment, the drawer member 30B is attached to the main body member 30A so that it can be pulled out in the long side direction of the main body member 30A.
In other words, the main body member 30A is a member that is attached to and removed from the accommodation hole 20A of the holder accommodation section 20, and the drawer member 30B is a member that holds the article to be managed.

A locking mechanism (not shown) is provided inside the main body member 30A, and the pull-out member 30B pushed into the main body member 30A can be mechanically locked. The locked state of the main body member 30A and the drawer member 30B can be released only by the lock release section 17 (see FIG. 1). In the case of this embodiment, when the drawer member 30B is pushed into the main body member 30A, the locking state is automatically established, and the two members are integrated.
Note that the main body member 30A and the drawer member 30B are provided with a space that forms a ring attachment hole 30D to which the ring 31 is attached when the two members are integrated. When the main body member 30A and the drawer member 30B are in a locked state, the ring 31 cannot be removed from the ring attachment hole 30D. In other words, the ring 31 cannot be removed from the key holder 30. Note that the ring 31 is rotatably supported in the ring attachment hole 30D.
On the other hand, when the drawer member 30B is pulled out from the main body member 30A, the ring 31 can be removed from the ring attachment hole 30D through the path formed between the main body member 30A and the drawer member 30B. In other words, the ring 31 can be removed from the key holder 30.

FIG. 6 is a diagram illustrating an example of connecting an article to the key holder 30. (A) shows an example in which one key 32 is connected to the key holder 30, and (B) shows an example in which one USB memory 33 is connected to the key holder 30.
However, the number of items managed by key holder 30 in this embodiment is arbitrary. For example, it is also possible to manage a plurality of keys 32 and a plurality of USB memories 33 with the key holder 30. Furthermore, it is also possible to manage different types of articles with one key holder 30. For example, one key holder 30 can manage one key 32 and one USB memory 33.
Although FIG. 6 shows the key 32 and the USB memory 33 as examples of objects to be managed, the objects to be managed are arbitrary as long as they can be attached to the ring 31. For example, IC cards and magnetic cards may be objects of management.

As shown in FIG. 6, the main body member 30A (see FIG. 5) that is attached to and detached from the holder accommodating portion 20 and the drawer member 30B (see FIG. 5) that holds the key 32 etc. are integrated into the key holder 30. In this embodiment, the state in which the keys 32 and the like are held is referred to as a state in which the object to be managed, such as the key 32, is directly connected to the key holder 30.
Note that when the member that is attached to and removed from the holder housing part 20 and the member that holds the key 32 etc. are not integrated, the key 32 etc. can be attached to and removed from the holder housing part 20 via other members. connected to the member to be connected. In this specification, this state is referred to as a state in which the keys 32 and the like are indirectly connected.
As described above, in this embodiment, the expression "connection" is used to include not only the case where the objects to be managed are directly connected, but also the case where they are indirectly connected.

In addition, an IC tag 30E (see FIG. 4) is attached to the back of the main body member 30A (see FIG. 5) constituting the key holder 30. The IC tag 30E is attached to the accommodation hole 20A (see FIG. 3) of the holder accommodation section 20 (see FIG. 3), and is connected to the reader/writer 20B (see FIG. 7) provided in the deep part of the accommodation hole 20A. They are placed in facing positions. Communication is possible when the IC tag 30E and the reader/writer 20B face each other with a slight gap in between.
Information stored in a storage section (not shown) of the IC tag 30E is read out by the reader/writer 20B. For example, a storage unit (not shown) stores a serial number (hereinafter also referred to as "SN"), which is information that physically identifies the key holder 30.
Furthermore, information can be written in a storage section (not shown) of the IC tag 30E through the reader/writer 20B. For example, it is possible to write information identifying the type of article or article connected to the key holder 30.
Note that establishment of communication between the IC tag 30E and the reader/writer 20B is also used to detect the position of the holder accommodating section 20 to which the key holder 30 is attached.

<Control system configuration>
FIG. 7 is a diagram illustrating a configuration example of a control system of the key management device 10.
The key management device 10 is provided with a control section 40 that controls the operation of each section. The control unit 40 is a so-called computer, and includes a CPU (=Central Processing Unit), an MPU (Micro Processing Unit), a ROM (=Read Only Memory), a RAM (=Random Access Memory), and the like. The ROM stores basic programs executed by the CPU and MPU, various settings, and the like. Further, the RAM is used as a work area for programs read from the ROM or the like. The functions described below are realized by executing programs by the CPU or MPU.

The control unit 40 shown in FIG. 7 includes a door locking unit 13, a reader/writer 20B built in the holder accommodating unit 20, an unlocking unit 17, an operation display unit 15, an authentication unit 16, and a storage unit 22. , and the USB interface circuit section 18A.
The control unit 40 reads necessary information and controls operations through communication with each of these units. For example, the control unit 40 controls locking and unlocking of the front door 12 through communication with the door locking unit 13. Locking and unlocking by the door locking unit 13 is performed with the front door 12 closed. As described above, when the front door 12 is locked by the door locking section 13, the key holder 30 (see FIG. 1) housed in the housing 11 (see FIG. 1) cannot be accessed. On the other hand, when the door lock part 13 is unlocked, it becomes possible to open the front door 12 and access the inside of the housing 11.

The operation display unit 15 is used to receive instructions and information input by the user, and to present information to the user.
For example, the operation display section 15 is used to register a key holder 30 (see FIG. 3) and input the number of the holder storage section 20 corresponding to the key holder 30 desired to be taken out or returned. Further, for example, the operation display section 15 is used to present information regarding the holder storage section 20 that can be accessed by an authenticated user and the articles to be managed.

The authentication unit 16 is used to read information for identifying a user. The read information and authentication results are transmitted from the authentication section 16 to the control section 40. The control unit 40 uses the received information to verify the authentication of the individual and the presence or absence of authority. For example, if the authority is confirmed, the control unit 40 instructs the door locking unit 13 to unlock. Further, for example, when the user is authenticated, the control unit 40 causes the operation display unit 15 or the like to present the number of the holder accommodating unit 20 that can be operated by the authenticated individual.
The lock release unit 17 has an antenna for reading information on the IC tag 30E at a position facing the IC tag 30E of the key holder 30 attached to the holder accommodating unit 20. The IC tag 30E of the key holder 30 stores information that physically identifies the key holder 30. Information read by the antenna is transmitted to the control unit 40.

The USB interface circuit section 18A is provided in the USB port 18 (see FIG. 2). The USB interface circuit unit 18A writes and reads information to and from the USB memory 33 (see FIG. 6) attached to the USB port 18. Information read from and written to the USB memory 33 is exchanged with the control unit 40 . In the case of this embodiment, the USB interface circuit section 18A is used for erasing data in the USB memory 33 and executing a virus check.
The holder accommodating portion 20 is provided with a reader/writer 20B. The reader/writer 20B is used to read and write information on the IC tag 30E of the key holder 30 attached to the holder accommodating section 20. For example, the reader/writer 20B is used to read information that identifies the key holder 30. It is also possible to write information that physically identifies the key 32 (see FIG. 6) and the USB memory 33 (see FIG. 6) attached to the key holder 30 in the IC tag 30E of the key holder 30.

The storage unit 22 is used to store information related to the settings of the key management device 10, information identifying users who can use the key management device 10, the status of accommodation of the key holder 30 in the holder storage unit 20, and the like. Furthermore, the storage unit 22 stores the relationship between the users who can use the key management device 10 and the holder storage unit 20 that stores the key holders 30 that each user is permitted to handle.
Furthermore, in the storage unit 22 in this embodiment, information regarding the article connected to each key holder 30 is stored in both information that physically identifies the key holder 30 and information that physically identifies the holder accommodating unit 20. are associated and stored.

Note that the information regarding the article connected to the key holder 30 may be stored in association with only one of the information that physically identifies the key holder 30 and the information that physically identifies the holder accommodating section 20.
In the case of this embodiment, the information regarding the article includes information regarding the type of article connected to the key holder 30. The information regarding the type of article includes the name of the article, symbols used for managing the type of article, numbers, and other information.
In this embodiment, "key" and "USB memory" are used as names of articles. In addition, when managing the type of article by a symbol, the key 32 is represented by, for example, "A", and the USB memory 33 is represented, for example, by "B". Furthermore, when managing the type of article numerically, the key 32 is represented by, for example, "001", and the USB memory 33 is represented by, for example, "002".

If the article is a key 32, the information about the article includes the number of keys 32 connected to the key holder 30, the location where the keys 32 are used, the identification number of the storage shelf or safe that is unlocked by the key 32, etc. It is stored in the storage unit 22. Note that if an IC tag or the like in which information for physically identifying the key 32 is stored is attached to the key 32, the identification information read from the IC tag or the like is stored in the storage unit 22. be done.
If the article is a USB memory 33, the number of USB memories 33 connected to the key holder 30, information for physically identifying the USB memory 33, etc. are stored in the storage unit 22 as information regarding the article.

The control unit 40 in this embodiment operates as a plurality of functional units through execution of a program. FIG. 7 shows a reception section 40A, a management section 40B, a serial number (SN) reading section 40C, a virus check execution section 40D, and a data deletion section 40E as representative examples of functional sections.
The reception unit 40A realizes a function used to receive registration of information regarding an article connected to the key holder 30. The information related to the article connected to the key holder 30 also includes information regarding the type of article to be managed.
The reception unit 40A converts information input through the operation display unit 15, such as the number of the holder accommodating unit 20 to which the key holder 30 is attached and the type of article connected to the key holder 30, into information that physically identifies the holder accommodating unit 20. The serial number and key holder 30 are stored in the storage unit 22 in association with the serial number that physically identifies the key holder 30.

The management unit 40B manages information regarding articles connected to the key holder 30 in association with one or both of the specific holder storage unit 20 and the specific key holder 30. When the USB memory 33 (see FIG. 6) is connected to the key holder 30, the management unit 40B stores the serial number that physically identifies the USB memory 33, the serial number that physically identifies the holder accommodating section 20, and the key holder 30. are managed by associating them with serial numbers that physically identify them.
The serial number reading unit 40C realizes a function of registering a serial number (ie, SN) read from the key holder 30 or the USB memory 33 into the storage unit 22. Note that to read the serial number stored in the IC tag 30E of the key holder 30, an antenna (not shown) provided in the unlocking section 17 and a reader/writer 20B provided in the holder accommodating section 20 are used. Note that the thirty holder accommodating sections 20 are pre-numbered from "1" to "30". The serial number reading section 40C is an example of a reading section.

When the USB memory 33 is connected to the key holder 30, the virus check execution unit 40D performs a check when the key holder 30 is registered, when the key holder 30 is removed from the holder accommodating part 20, and when the key holder 30 is returned to the holder accommodating part 20. This function executes a virus check on the data stored in the USB memory 33. The data to be subjected to the virus check is read to the virus check execution section 40D through the USB interface circuit section 18A.
When the USB memory 33 is connected to the key holder 30, the data erasing unit 40E performs the following operations when registering the key holder 30, when removing the key holder 30 from the holder accommodating unit 20, and when returning the key holder 30 to the holder accommodating unit 20. This is a function to erase data stored in the USB memory 33. In this embodiment, the process of erasing all data stored in the USB memory 33 is called initialization. The data erasure unit 40E is an example of a data erasure execution unit.

<Processing operation example>
In the following, the processing operations executed by the key management device 10 (see FIG. 1) used in this embodiment will be described. 30 and when the key holder 30 is returned to the holder accommodating section 20 will be explained.

<Processing operation when registering a keychain>
FIG. 8 is a flowchart illustrating an example of a processing operation performed by the control unit 40 when the user registers the key holder 30 in association with the holder storage unit 20. The symbol S in the figure means a step. Of course, the processing operation shown in FIG. 8 is executed by the control unit 40 through execution of a program.
First, the control unit 40 determines whether the operation selected by the user is to set a holder name (step 1). Specifically, it is determined whether the holder name setting button 51 (see FIG. 9) has been operated on the menu screen 50 (see FIG. 9). If a negative result is obtained in step 1, the control unit 40 proceeds to step 11 (see FIG. 16).

On the other hand, if a positive result is obtained in step 1, the control unit 40 accepts the settings input by the user (step 2). The holder name setting is performed on the holder accommodating section 20 to which the key holder 30 is not associated. The fact that the key holder 30 is not associated can be distinguished from the fact that the holder name field is blank on the management screen of the holder accommodating unit 20.
If there are multiple holder accommodating units 20 in which the holder name field is blank, the control unit 40 does not accept the character string input in the blank field corresponding to the management number specified by the user or in the blank field specified by the user. Execute. The control unit 40 also accepts settings for the type of article to be connected to the key holder 30 and the number of articles to be connected.

When the reception of the settings is completed, the control unit 40 determines whether the USB memory 33 is connected to the key holder 30 attached to the holder accommodating section 20 for which the name has been set (step 3).
If a negative result is obtained in step 3, the control unit 40 ends the process.
On the other hand, if a positive result is obtained in step 3, the control unit 40 displays a guide on the operation display unit 15 to prompt the user to insert the USB memory 33 into the USB port 18 (see FIG. 2) (step 4). After this, the control unit 40 enters a state in which it waits for the USB memory 33 to be inserted into the USB port 18.
When the USB memory 33 is attached to the USB port 18, the control section 40 reads the serial number of the USB memory 33 through the USB interface circuit section 18A (step 5).

Next, the control unit 40 registers the read serial number in association with the holder accommodating unit 20 (step 6). Specifically, the serial number of the USB memory 33 is linked to the serial number assigned to the holder accommodating section 20. The relationship between the serial number used for managing the holder accommodating section 20 and the serial number of the USB memory 33 connected to the key holder 30 attached to the holder accommodating section 20 is stored in the storage section 22 (see FIG. 7). .
Thereafter, the control unit 40 determines whether the USB memory 33 whose serial number has been read is the last one to be registered (step 7). The determination here uses, for example, the content instructed by the user on the inquiry screen displayed on the operation display section 15.
If there remains another USB memory 33 to be registered, the control unit 40 obtains a negative result in step 7. When the control unit 40 obtains a negative result in step 7, the process returns to step 4. Specifically, a guide prompting the user to attach the remaining USB memory 33 to the USB port 18 is displayed on the operation display section 15. After this, the serial number read from another USB memory 33 is added to the above-mentioned relationship.

On the other hand, if there is no other USB memory 33 to be registered, the control unit 40 obtains a positive result in step 7. If a positive result is obtained in step 7, the control unit 40 ends the registration of the holder name.
Thereafter, the user attaches the key holder 30 to which the USB memory 33 or the like is connected to the holder accommodating section 20 in which the holder name has been registered. A serial number that physically identifies the key holder 30 is read from the IC tag 30E (see FIG. 4) of the key holder 30 attached to the holder accommodating section 20, and a management number for the holder accommodating section 20 to which the key holder 30 is attached is read. is linked to.
As a result, the management number of the holder accommodating section 20 is associated with a serial number that physically identifies the USB memory 33 connected to the key holder 30 and a serial number that physically identifies the key holder 30. In other words, the serial number that physically identifies the USB memory 33 connected to the key holder 30 and the serial number that physically identifies the key holder 30 are indirectly communicated via the management number of the holder accommodating section 20. Can be tied.

An example of an operation screen displayed when setting a holder name and a data table that is updated will be described below using FIGS. 9 to 15.
FIG. 9 is a diagram showing an example of the menu screen 50. On the menu screen 50 shown in FIG. 9, a holder name setting button 51, a key holder removal button 52, and a key holder return button 53 are arranged as operation buttons. In FIG. 9, the state in which the holder name setting button 51 is selected is represented by shading.
In addition to these, the menu screen 50 also includes an explanatory text 54 regarding operations requested of the user, a button 55 for returning to the previous screen, and a button 56 used for confirming the selection.
In the case of FIG. 9, since the holder name setting button 51 is selected, an affirmative result is obtained in step 1 described above (see FIG. 8).

FIG. 10 is a diagram showing an example of a screen 60 used for setting a folder name. In the case of FIG. 10, the management serial number "2" has been selected by the user. For this reason, the serial number "2" is shaded.
In addition, in FIG. 10, the name "first conference room" is set to the holder accommodating section 20 corresponding to the serial number "2".
As mentioned above, the casing 11 of the key management device 10 (see FIG. 1) in this embodiment is provided with 30 holder accommodating sections 20, but the serial number is displayed on the screen 60 shown in FIG. Only 10 input fields 61 corresponding to "1" to "10" are prepared. In the case of FIG. 10, since this is the first registration of the holder name, the input fields 61 other than the serial number "2" are blank. However, if there is a name already registered, the name of the holder is displayed in the corresponding input field 61.

In the case of FIG. 10, below the input field 61 are page information 62 indicating the relationship between the position of the page displayed on the screen 60 and the total number of pages, and a button 63 used to change the position of the displayed page. is located. The denominator of the page information 62 indicates the total number of pages, and the numerator indicates the position of the displayed page. In the case of FIG. 10, the total number of pages is three, of which the first page is displayed.
Incidentally, when the button 63 with a rightward arrow is operated, the page displayed on the screen 60 is switched to the second page. When switching to the second page, the serial numbers displayed on the screen 60 switch from "11" to "20".
Note that the button 63 on the left side of the page information 62 is blank because, in the case of FIG. 10, the current page is the first page. When the second page is displayed on the screen 60, a leftward arrow button 63 is displayed on the left side of the page information 62.
In addition, the screen 60 includes a button 64 for returning to the previous screen and a button 65 for confirming the input of a holder name. Incidentally, when the button 64 is operated, the screen switches to the menu screen 50 shown in FIG. 9.

FIG. 11 is a diagram showing an example of a screen 70 used for setting items managed by the key holder 30. As shown in FIG. The screen 70 is displayed after setting the name of the holder accommodating section 20 to which the key holder 30 is attached. That is, the screen 70 is displayed on the operation display section 15 after the button 65 (see FIG. 10) is operated.
In the case of FIG. 11, the serial number attached to the holder housing section 20 (see FIG. 3) is "2", and the holder name is "first conference room".
A screen 70 shown in FIG. 11 includes a button 71 indicating that the object to be managed is the USB memory 33 (see FIG. 6), and a button 71 indicating that the object to be managed is the key 32 (see FIG. 6). A button 72 indicating that the item to be managed is a mixture of a plurality of types, and a button 73 indicating that the item to be managed is a mixture of a plurality of types are arranged.

In the case of FIG. 11, the button 73 indicates that the objects to be managed are both the USB memory 33 and the key 32.
Note that the items to be managed are arbitrary as long as they can be connected to the key holder 30, so it is also possible to arrange a button such as "Others". In FIG. 11, the state in which the button 73 indicating a mixture of a plurality of types is selected is represented by shading.
In the case of this embodiment, when any button is selected, a screen for setting the number of articles to be connected to key holder 30 is displayed. When the button 73 indicating a mixture of a plurality of types is selected, it may be possible to individually set not only the total number of items to be managed, but also the number of USB memories 33 and the number of keys 32.

In addition to these, the screen 70 also includes an explanatory text 74 regarding the operation requested of the user, a button 75 for returning to the previous screen, and a button 76 used for confirming the selection. In the case of FIG. 11, since the button 73 indicating that the article to be managed is a mixture of a plurality of types is selected, an affirmative result is obtained in step 3 described above (see FIG. 8).
FIG. 12 is a diagram showing an example of a screen 80 that is displayed when the USB memory 33 (see FIG. 6) is included in the item to be managed. The screen 80 is presented when a positive result is obtained in step 4 (see FIG. 8).
In the case of the screen 80 shown in FIG. 12, an explanation 81 is included that says, "Please insert the USB memory to be managed into the USB port on the upper left side when facing the main body."
The screen 80 is displayed not only when the button 73 (see FIG. 11) is operated, but also when the button 71 (see FIG. 11) is operated.
Although the screen 80 including the explanatory text 81 is displayed for the purpose of prompting the user's operation, it is also possible to not display the screen 80 depending on settings or the like. For example, in the case of a user who is accustomed to operations, the user is expected to perform an operation to attach the USB memory 33 to the USB port 18 even if the screen 80 is not displayed.
When the USB memory 33 is attached to the USB port 18, the serial number of the USB memory 33 is read out by the USB interface circuit section 18A and linked to the number of the holder accommodating section 20 shown on the screen 70.

FIG. 13 is a diagram illustrating an example of a screen 90 displayed after the USB memory 33 (see FIG. 6) is attached to the USB port 18. Presentation of screen 90 corresponds to step 7 (see FIG. 8).
A screen 90 shown in FIG. 13 is displayed when the number of USB memories 33 connected to the key holder 30 is not registered in advance. In the case of FIG. 13, the screen 90 includes an inquiry 91 asking, "Is this the last USB memory to be registered? Yes/No."
At the bottom of the screen 90, a button 92 is operated when there is no other USB memory 33 to be registered, and a button 93 is operated when there are remaining USB memories 33 to be registered.
Note that if the number of USB memories 33 connected to the key holder 30 has been registered in advance, the registered number can be confirmed from the serial number read from the USB port 18, so the screen 90 will not be displayed. You can.
After the button 93 on the screen 90 is operated and the registered USB memory 33 is removed from the USB port 18, the screen 80 (see FIG. 12) is displayed again on the operation display section 15 (see FIG. 1). On the other hand, when the registered USB memory 33 is removed from the USB port 18 after the button 92 is operated, a confirmation screen 100 (see FIG. 14) for confirming the settings is displayed on the operation display section 15. Ru.

FIG. 14 is a diagram illustrating an example of a setting confirmation screen 100 that is displayed after the serial number of the USB memory 33 (see FIG. 6) is registered.
The confirmation screen 100 shown in FIG. 14 displays the set name, the number of articles to be managed, and the type of articles to be managed in association with the serial number assigned for management of the holder storage section 20. Information 101 is presented.
In the case of FIG. 14, since the holder accommodating section 20 corresponding to the serial number "2" is the target of setting, the serial number "2" is shown so as to be distinguishable from other numbers. In the case of FIG. 14, the name of the holder storage unit 20 corresponding to the serial number "2" indicates "1st conference room", the number of objects to be managed indicates "2", and the number of objects to be managed is "2". "Mixed" is indicated as the target product type. The user who confirms the confirmation screen 100 can confirm the set contents using letters and numbers.

Note that, at the bottom of the confirmation screen 100, page information 102 indicating the relationship between the position of the page displayed on the confirmation screen 100 and the total number of pages, and a button 103 used to change the position of the displayed page are arranged. has been done. The denominator of the page information 102 indicates the total number of pages, and the numerator indicates the position of the displayed page. In the case of FIG. 14, the total number of pages is six, of which the first page is displayed. In the case of FIG. 14, the number of holder storage units 20 allocated to one page is five.
Therefore, when the button 103 with a rightward arrow is operated, the page displayed on the confirmation screen 100 is switched to the second page. When switching to the second page, the serial numbers displayed on the confirmation screen 100 switch from "6" to "10".
Note that the button 103 located on the left side of the page information 102 is blank because, in the case of FIG. 14, the current page is the first page. When the second page is displayed on the confirmation screen 100, a leftward arrow button 103 is displayed on the left side of the page information 102.
In addition, a button 104 for returning to the previous screen is also arranged on the confirmation screen 100.

FIG. 15 is a diagram illustrating an example of the management table 110 stored in the storage unit 22 after setting the folder name.
In the case of the management table 110 shown in FIG. 15, set information is linked to the serial number assigned to the holder accommodating section 20. In the case of FIG. 15, the serial number is written as "holder accommodating part number."
In the case of FIG. 15, "105258" is set in the serial number column of the key holder 30 corresponding to the serial number "2" assigned to the holder storage section 20, and "2" is set in the managed number column. .
In the case of the management table 110 shown in FIG. 15, the key data string and the USB A data string for memory is provided.

In the case of this embodiment, the serial number of the key 32 is left blank because it is not subject to management.
On the other hand, the serial number of the USB memory 33 is set to "PUT52894" read from the USB port 18 (see FIG. 2). Further, in the column for managing users who have usage authority, information for identifying a user who is authenticated when starting setting a holder name is set. In the case of FIG. 15, "user A" is set. Note that if the number of users having usage authority is plural, information for identifying users is set for the number of users.
As shown in FIG. 15, among the articles connected to the key holder 30, the serial number of the USB memory 33 is managed by being linked to the number of the holder accommodating section 20 to which the key holder 30 is attached. Furthermore, the serial number of the USB memory 33 among the articles connected to the key holder 30 is indirectly linked to the serial number of the key holder 30 through the number of the holder accommodating section 20 .
The serial number information of the USB memory 33 connected to each key holder 30 is written on the IC tag 30E (see FIG. 4) of the corresponding key holder 30 when the key holder 30 is attached to the corresponding holder housing 20. It may be included.

In addition, when the serial number that physically manages the key 32 is to be managed, an optical scanner, a camera, a magnetic reader, a reader that reads information from an IC tag, or other information reading device provided in the key management device 10 is used. It is also possible to record the information read through the holder accommodating section 20 in association with the serial number assigned to the holder accommodating section 20.
For example, if a serial number is stamped on the key 32, it is also possible to read the serial number by processing an image taken by a camera. For example, if a barcode or QR code (registered trademark) is attached to the key 32, it is also possible to read the serial number via a code reader corresponding to the barcode or QR code (registered trademark). For example, if an IC tag is attached to the key 32, it is also possible to read the serial number via a reader corresponding to the IC tag. Further, if an item other than the key 32 is to be managed, it is also possible to read information such as a serial number stored on the magnetic stripe with a magnetic reader. Note that the information for identifying the article to be managed can also be manually set by the user.

<Processing operation when removing the keychain>
FIG. 16 is a flowchart illustrating an example of a processing operation performed by the control unit 40 when the user removes the key holder 30 from the holder accommodating part 20. The symbol S in the figure means a step. The processing operation shown in FIG. 16 is executed by the control unit 40 through execution of a program. Note that the process shown in FIG. 16 is executed when a negative result is obtained in step 1 (see FIG. 8).
First, the control unit 40 determines whether the operation selected by the user is to remove the key holder 30 from the holder accommodating unit 20 (step 11). Specifically, it is determined whether the key holder removal button 52 (see FIG. 17) has been operated on the menu screen 50 (see FIG. 17). If a negative result is obtained in step 11, the control unit 40 proceeds to step 31 (see FIG. 25).

On the other hand, if a positive result is obtained in step 11, the control unit 40 accepts the selection of the key holder 30 (step 12). The selection of the key holder 30 to be removed is performed on the operation screen of the operation display unit 15 (see FIG. 1). Note that the key holder 30 that can be selected is the key holder 30 that is attached to the holder housing section 20. Therefore, the key holder 30 that has been removed from the holder housing section 20 cannot be selected. Note that the position of the holder accommodating section 20 in which the key holder 30 that can be removed by the user is attached may be displayed on the operation display section 15 using the information of the authenticated user.
When the selection of the key holder 30 to be removed is confirmed, the control unit 40 controls a locking mechanism (not shown) to unlock the holder accommodating part 20 (step 13). By releasing the lock, it becomes possible to remove the key holder 30 from the holder accommodating portion 20.

Subsequently, the control unit 40 determines whether or not the USB memory 33 (see FIG. 6) is included in the management target of the removable key holder 30 (step 14). For this determination, for example, the management table 110 (see FIG. 15) is referred to. When the USB memory 33 is connected to the key holder 30 to be removed, the serial number of the USB memory 33 is set in the management table 110 in association with the number of the holder accommodating section 20.

If a negative result is obtained in step 14, the control unit 40 ends the process.
On the other hand, if a positive result is obtained in step 14, the control unit 40 displays a guide on the operation display unit 15 to prompt the user to insert the USB memory 33 into the USB port 18 (see FIG. 2) (step 15). After this, the control unit 40 enters a state in which it waits for the USB memory 33 to be inserted into the USB port 18.
When the USB memory 33 is attached to the USB port 18, the control section 40 reads the serial number of the USB memory 33 through the USB interface circuit section 18A (step 16).

When the serial number is read, the control unit 40 determines whether the read serial number has been registered in the target holder storage unit 20 (step 17).
If the serial number has not been registered, the control unit 40 obtains a negative result in step 17 and returns to step 15. This is to encourage attachment of the correct USB memory 33.
If the read serial number is registered in the corresponding holder storage unit 20, the control unit 40 obtains a positive result in step 17.
When a positive result is obtained in step 17, the control unit 40 determines whether or not the virus check for the USB memory 33 attached to the USB port 18 has not been processed (step 18). If the virus check has already been performed, the control unit 40 obtains a negative result in step 18. On the other hand, if the virus check has not been performed, the control unit 40 obtains a positive result in step 18.

If a negative result is obtained in step 18, the control unit 40 in this embodiment proceeds to step 22.
On the other hand, if a positive result is obtained in step 18, the control unit 40 executes a virus check (step 19). By executing the virus check, it is possible to prevent a situation in which the USB memory 33 infected with a virus is used in another information terminal and the information terminal infected with a virus is spread.
Subsequently, the control unit 40 determines whether data protection is set for the USB memory 33 attached to the USB port 18 (step 20). For example, data protection is set on the USB memory 33 in which an installation program is stored to prevent data from being accidentally erased. Information regarding data protection settings may also be managed in the management table 110 (see FIG. 15).
If a positive result is obtained in step 20, the control unit 40 directly proceeds to step 22 without erasing the data.
On the other hand, if a negative result is obtained in step 20, the control unit 40 erases the data in the USB memory 33 (step 21). When data erasure is completed, the control unit 40 moves to step 22.

In step 22, the control unit 40 determines whether all the USB memories 33 registered in the holder accommodating unit 20 have been installed.
While the USB memory 33 that is not attached to the USB port 18 remains, the control unit 40 obtains a negative result in step 22 and returns to step 15.
On the other hand, if a positive result is obtained in step 22, the control unit 40 ends the process.

Hereinafter, an example of the operation screen displayed when the key holder 30 is removed and the data table that is updated will be explained using FIGS. 17 to 24.
FIG. 17 is a diagram showing an example of the menu screen 50. In FIG. 17, parts corresponding to those in FIG. 9 are shown with corresponding symbols. The menu screen 50 shown in FIG. 17 is the same as the menu screen 50 shown in FIG.
However, in the case of the menu screen 50 shown in FIG. 17, the removal button 52 of the key holder 30 is selected by the user. Therefore, the removal button 52 of the key holder 30 is shown shaded.
When the removal button 52 of the key holder 30 is operated in FIG. 17, an affirmative result is obtained in step 11 (see FIG. 16).

FIG. 18 is a diagram showing an example of the screen 120 used to select the key holder 30 to be removed. The screen 120 shown in FIG. 18 is used to accept the selection of the key holder 30 in step 12 (see FIG. 16).
In the case of FIG. 18, the management serial number "2" has been selected by the user. For this reason, the serial number "2" is shaded.
Note that in FIG. 18, the name "first conference room" is set for the holder accommodating section 20 corresponding to the serial number "2". Incidentally, the holder housing section 20 corresponding to the serial number "7" is named "safe", and the holder housing section 20 corresponding to the serial number "8" is named "second conference room". has been done.
Also in the case of the screen 120 shown in FIG. 18, ten holder accommodating sections 20 are allocated to one page. Therefore, in the page information 122, the denominator indicating the total number of pages is "3". Note that since the serial numbers of the holder accommodating portion 20 shown in FIG. 18 are from "1" to "10", "1" is shown in the numerator indicating the current page position in the page information 122.

Incidentally, when the button 123 with a rightward arrow is operated, the page displayed on the screen 120 is switched to the second page. When switching to the second page, the serial numbers displayed on the screen 120 switch from "11" to "20".
Note that the button 123 on the left side of the page information 122 is blank because, in the case of FIG. 18, the current page is the first page. When the second page is displayed on the screen 120, a leftward arrow button 123 is displayed on the left side of the page information 122.
In addition, a button 124 for returning to the previous screen and a button 125 for confirming the selection of the number of the holder accommodating section 20 from which the key holder 30 is to be removed are arranged on the screen 120. Incidentally, when the button 124 is operated, the screen switches to a menu screen 50 shown in FIG. 17.

FIG. 19 is a diagram showing an example of the screen 130 that is displayed when the USB memory 33 (see FIG. 6) is included in the item to be managed. The presentation of screen 130 corresponds to the case where a positive result is obtained in step 14 (see FIG. 16).
In the case of the screen 130 shown in FIG. 19, an explanatory text 131 is included that reads, "Please insert the USB memory to be managed into the USB port on the upper left side when facing the main body."
Although the screen 130 including the explanatory text 131 is displayed for the purpose of prompting the user's operation, it is also possible to not present the screen 130 depending on settings or the like. For example, a user who is accustomed to operations is expected to attach the USB memory 33 to the USB port 18 and perform a virus check, etc., even without the screen 130 being presented.

FIG. 20 is displayed when a USB memory 33 (see FIG. 6) that is not registered in the holder housing section 20 (see FIG. 3) from which the key holder 30 (see FIG. 1) has been removed is attached to the USB port 18. 14 is a diagram showing an example of a screen 140. FIG.
When the key holder 30 is removed from the holder storage unit 20, it is assumed that a virus check will be performed on the USB memory 33 connected to the removed key holder 30, but a malicious user may check the history of virus check execution. There is a possibility that an unregistered USB memory 33 may be attached to the USB port 18 for the purpose of preserving the data.
Screen 140 is displayed on operation display section 15 (see FIG. 1) when a negative result is obtained in step 17 (see FIG. 16).
In the case of the screen 140, an explanatory text 141 is included that says, "An incorrect USB memory has been inserted. Please remove the incorrect USB memory from the USB port and insert the correct USB memory."
The term "wrong USB memory" here refers to the USB memory 33 that is not tied to the holder accommodating section 20 from which the key holder 30 has been removed.
The screen 140 is erased from the screen of the operation display unit 15 when the correct USB memory 33 is inserted into the USB port 18.

FIG. 21 is a diagram showing an example of a screen 150 that is displayed when erasing data in the USB memory 33 attached to the USB port 18 is prohibited.
In the case of the present embodiment, a process for erasing the data in the USB memory 33 is scheduled after execution of the virus check, but there are cases where the data should not be erased. For example, the USB memory 33 that stores installation programs and master data needs to be excluded from the erasure target. In this embodiment, information regarding data protection settings is also stored in the management table 110 (see FIG. 15).
Screen 150 is displayed if a positive result is obtained in step 20 (see FIG. 16). In the case of the screen 150 shown in FIG. 21, an explanatory text 151 is included that reads, "Erasure of data on this USB memory is prohibited. Please insert another USB memory."
The screen 150 is erased from the screen of the operation display unit 15 when the correct USB memory 33 is inserted into the USB port 18.

Note that the history of virus checking and data deletion is managed in association with the number of the holder storage unit 20.
FIG. 22 is a diagram illustrating an example of the virus check management table 160 used to manage the execution history of virus checks.
FIG. 23 is a diagram illustrating an example of a data deletion management table 170 used for managing data deletion execution history.
In the case of this embodiment, both the virus check management table 160 and the data erasure management table 170 are stored in the storage unit 22 (see FIG. 7).
The virus check management table 160 shown in FIG. 22 and the data erasure management table 170 shown in FIG. 23 are prepared separately for the holder storage unit 20 with the management number "8". However, the virus check management table 160 and the data erasure management table 170 do not need to be prepared separately, and a single table may manage the execution of the virus check and the execution of data erasure. Furthermore, a column for managing the execution of a virus check and a column for managing the execution of data deletion may be added to the management table 110 (see FIG. 15) described above.

In the case of FIGS. 22 and 23, two USB memories 33 are connected to the key holder 30.
Since the virus check is executed for all USB memories 33, the virus check management table 160 shown in FIG. Data is recorded.
On the other hand, in the case of FIG. 23, one of the two USB memories 33 is subject to data protection. Therefore, the execution history is not recorded for the USB memory 33 with data protection "with", and the execution history is recorded only with respect to the USB memory 33 with data protection "no".
In the case of the flowchart explained in FIG. 16, in step 22, it is only determined whether or not all the USB memories 33 that are subject to virus checking and data deletion are subject to processing, but each process requires The length of time spent may be added to the determination.

For example, the time required to complete a virus check on all USB memories 33 may be several hours, or the time required to complete data deletion on all USB memories 33 that are not subject to data protection. If this occurs for a period of time that would not occur under normal usage, the possibility of fraud by the user cannot be denied.
Therefore, when executing step 22, the control unit 40 determines whether the virus check has been executed within a time determined according to at least one of the number and data capacity of the USB memories 33 that are the targets of the virus check. It's okay. If the time required to execute the virus check exceeds the set time length, by requesting another virus check for all USB memories 33, at least fraud can be prevented at the time the key holder 30 is removed from the holder housing section 20. can be eliminated.

The same applies to erasing data. That is, when executing step 22, the control unit 40 determines whether data deletion has been performed within a time determined according to at least one of the number and data capacity of the USB memories 33 that are the targets of data deletion. It's okay. If the time required for erasing data exceeds the set time length, by requesting data erasure from all USB memories 33 again, fraud can be prevented at least at the time when the key holder 30 is removed from the holder housing section 20. can be eliminated.
FIG. 24 is a diagram illustrating an example of a screen 180 that is displayed when the work time for virus checking or data erasure is over.
The screen 180 includes an explanatory text 181 that reads, "The work time has exceeded. Please retry the work on all USB memories."

<Processing operation when returning the keychain>
FIG. 25 is a flowchart illustrating an example of a processing operation performed by the control unit 40 when the user returns the key holder 30 to the holder storage unit 20. The symbol S in the figure means a step. The processing operation shown in FIG. 25 is executed by the control unit 40 through execution of a program. Note that the process shown in FIG. 25 is executed when a negative result is obtained in step 11 (see FIG. 16).
First, the control unit 40 determines whether the operation selected by the user is to return the key holder 30 (step 31). Specifically, it is determined whether the return button 53 (see FIG. 26) of the key holder 30 has been operated on the menu screen 50 (see FIG. 26).
If a negative result is obtained in step 31, the control unit 40 executes a process corresponding to a button that is not assumed in this embodiment. However, in the case of FIG. 25, if a negative result is obtained in step 31, the process ends without executing the process described later.

On the other hand, if a positive result is obtained in step 31, the control unit 40 accepts the selection of the key holder 30 to be returned (step 32). The selection of the key holder 30 to be returned is performed on the operation screen of the operation display unit 15 (see FIG. 1). Note that the key holders 30 that can be selected are the key holders 30 that are not attached to the holder accommodating section 20. Therefore, it is not possible to select the number of the holder accommodating section 20 in which the key holder 30 is already attached. Note that the position of the holder accommodating section 20 to which the key holder 30 that the user first removed may be attached may be displayed on the operation display section 15 using the information of the authenticated user.
When the selection of the key holder 30 to be returned is confirmed, the control unit 40 determines whether the USB memory 33 (see FIG. 6) is included in the management target of the key holder 30 to be returned (step 33). For this determination, for example, the management table 110 (see FIG. 15) is referred to. When the USB memory 33 is connected to the key holder 30 to be removed, the serial number of the USB memory 33 is set in the management table 110 in association with the number of the holder accommodating section 20.

If a negative result is obtained in step 33, the control unit 40 ends the process.
On the other hand, if a positive result is obtained in step 33, the control unit 40 displays a guide on the operation display unit 15 to prompt the user to insert the USB memory 33 into the USB port 18 (see FIG. 2) (step 34). Thereafter, the control unit 40 enters a state in which it waits for the USB memory 33 to be inserted into the USB port 18.
When the USB memory 33 is attached to the USB port 18, the control section 40 reads the serial number of the USB memory 33 through the USB interface circuit section 18A (step 35).
When the serial number is read, the control unit 40 determines whether the read serial number has been registered in the target holder storage unit 20 (step 36).
If the serial number has not been registered, the control unit 40 obtains a negative result in step 36 and returns to step 34. This is to encourage the correct USB memory 33 to be installed.

If the read serial number is registered in the corresponding holder storage unit 20, the control unit 40 obtains a positive result in step 36.
When a positive result is obtained in step 36, the control unit 40 determines whether the virus check for the USB memory 33 attached to the USB port 18 has not been processed yet (step 37).
If a negative result is obtained in step 37, the control unit 40 in this embodiment proceeds to step 41.

On the other hand, if a positive result is obtained in step 37, the control unit 40 executes a virus check (step 38). By executing the virus check, it is possible to prevent a situation in which the USB memory 33 infected with a virus is returned.
Subsequently, the control unit 40 determines whether data protection is set for the USB memory 33 attached to the USB port 18 (step 39). For example, data protection is set on the USB memory 33 in which an installation program is stored to prevent data from being accidentally erased. In the determination at step 39, for example, the management table 110 (see FIG. 15) is referred to.
If a positive result is obtained in step 39, the control unit 40 directly proceeds to step 41.
On the other hand, if a negative result is obtained in step 39, the control unit 40 erases the data in the USB memory 33 (step 40). When data erasure is completed, the control unit 40 moves to step 41.

In step 41, the control unit 40 determines whether all the USB memories 33 registered in the holder accommodating unit 20 have been installed.
While there remains a USB memory 33 that is not attached to the USB port 18, the control unit 40 obtains a negative result in step 41 and returns to step 34.
On the other hand, if a positive result is obtained in step 41, the control unit 40 permits the return of the key holder 30 (step 42), and then ends the process.

Hereinafter, an example of the operation screen displayed when the key holder 30 is returned and the data table that is updated will be explained using FIGS. 26 to 28.
FIG. 26 is a diagram showing an example of the menu screen 50. In FIG. 26, parts corresponding to those in FIGS. 9 and 17 are shown with corresponding symbols. The menu screen 50 shown in FIG. 26 is the same as the menu screen 50 shown in FIGS. 9 and 17.
However, in the case of the menu screen 50 shown in FIG. 26, the return button 53 of the key holder 30 has been selected by the user. For this reason, the return button 53 of the key holder 30 is shown shaded.
When the return button 53 of the key holder 30 is operated in FIG. 26, an affirmative result is obtained in step 31 (see FIG. 25).

FIG. 27 is a diagram illustrating an example of a screen 190 used to select the key holder 30 to be returned. The screen 190 shown in FIG. 18 is used to accept the selection of the key holder 30 in step 32 (see FIG. 25).
In the case of FIG. 27, the management serial number "2" has been selected by the user. For this reason, the serial number "2" is shaded.
In addition, in FIG. 27, the name "first conference room" is set to the holder accommodating section 20 corresponding to the serial number "2".
Also in the case of the screen 190 shown in FIG. 27, ten holder accommodating sections 20 are allocated to one page. Therefore, "3" is shown in the denominator of the page information 192 indicating the total number of pages. Note that since the serial numbers of the holder accommodating portions 20 shown in FIG. 27 are from "1" to "10", "1" is shown in the numerator indicating the current page position in the page information 192.

Incidentally, when the button 193 with a rightward arrow is operated, the page displayed on the screen 190 is switched to the second page. When switching to the second page, the serial numbers displayed on the screen 190 switch from "11" to "20".
Note that the button 193 on the left side of the page information 192 is blank because, in the case of FIG. 27, the current page is the first page. When the second page is displayed on the screen 190, a leftward arrow button 193 is displayed on the left side of the page information 192.
In addition, on the screen 190, a button 194 for returning to the previous screen and a button 195 for determining the number of the holder accommodating section 20 to be returned are arranged. Incidentally, when the button 194 is operated, the screen switches to the menu screen 50 shown in FIG. 26.

FIG. 28 is a diagram showing an example of a screen 200 that is displayed when the USB memory 33 (see FIG. 6) is included in the item to be managed. Presentation of screen 200 corresponds to the case where a positive result is obtained in step 33 (see FIG. 25).
In the case of the screen 200 shown in FIG. 28, an explanatory text 201 is included that reads, "Please insert the USB memory of the key holder into the USB port on the upper left side when facing the main body."
Although the screen 200 including the explanatory text 201 is displayed for the purpose of prompting the user's operation, it is also possible to not present the screen 200 depending on settings or the like. For example, a user who is accustomed to operations is expected to attach the USB memory 33 to the USB port 18 and perform a virus check, etc., even without the screen 200 being presented.
Note that even when returning the key holder 30, if a USB memory 33 (see FIG. 6) that is not registered in the holder storage unit 20 (see FIG. 3) is attached to the USB port 18, the screen 140 shown in FIG. 20 will be displayed. is displayed on the operation display section 15 (see FIG. 1).
Furthermore, when a USB memory 33 whose data is prohibited from being erased is inserted into the USB port 18, a screen 150 shown in FIG. 21 is displayed on the operation display unit 15 (see FIG. 1).

Note that the history of virus checks and data deletion performed when the key holder 30 is returned is also managed in association with the number of the holder storage unit 20. Specifically, virus check management table 160 shown in FIG. 22 and data deletion management table 170 shown in FIG. 23 manage virus check execution and data deletion execution.
The virus check management table 160 and the data erasure management table 170 used to manage when the key holder 30 is returned are different from the virus check management table 160 and the data erasure management table 170 used when the key holder 30 is removed.
In addition, in the case of the flowchart described in FIG. 25, in step 41, it is only determined whether or not all the USB memories 33 that are subject to virus checking and data deletion are subject to processing, but the key chain 30 As in the case of removal, the length of time required for each process may be added to the determination.

Specifically, when executing step 41, it is determined whether the virus check has been executed within a time determined according to at least one of the number and data capacity of the USB memories 33 that are the targets of the virus check. good. If the time required to execute the virus check exceeds the set time length, by requesting another virus check for all USB memories 33, the USB Virus writing to the memory 33 can be eliminated.
Further, when executing step 41, it may be determined whether data deletion has been performed within a time determined according to at least one of the number and data capacity of USB memories 33 that are data deletion targets. If the time required to erase the data exceeds the set time length, by requesting the data to be erased again from all USB memories 33, the key chain 30 will contain viruses at the time the key chain 30 is returned to the holder storage unit 20. Data contamination can be eliminated.
Note that if the work time for virus checking or data deletion is over, a screen 180 shown in FIG. 24 may be displayed on the operation display section 15.

<Other embodiments>
Although the embodiments of the present invention have been described above, the technical scope of the present invention is not limited to the range described in the embodiments described above. It is clear from the claims that various changes or improvements made to the embodiments described above are also included within the technical scope of the present invention.

For example, in the case of the above-described key management device 10 (see FIG. 1), it is assumed that information used for user authentication is read from an IC card, but it may also be assumed that information is read from a magnetic card.
FIG. 29 is a diagram illustrating a schematic configuration of a key management device 10A used in another embodiment. In FIG. 29, parts corresponding to those in FIG. 1 are shown with corresponding symbols.
In the case of the key management device 10A shown in FIG. 29, an authentication section 16 including a magnetic card reader 16B is attached.
Note that the front door 12 of the key management device 10A shown in FIG. 29 is closed. Therefore, the inside of the confirmed casing 11 is not depicted in FIG.

For example, in the case of the above-described key management device 10 (see FIG. 1), a case has been described in which all information related to the management of items connected to the key holder 30 is managed by the key management device 10, but the management table 110 (see FIG. 15), the virus check management table 160 (see FIG. 22), and the data erasure management table 170 (see FIG. 23), one or more, or all of which are external devices connected to the key management device 10 via a network. may be managed by
Furthermore, in the case of the above-mentioned key management device 10 (see FIG. 1), a case has been described in which all functions related to the management of items connected to the key holder 30 are executed by the key management device 10. A part, a plurality of them, or all of them may be executed by an external device connected to the key management device 10 via a network.
FIG. 30 is a diagram illustrating a configuration example of a key management system 230 in which the key management device 10 and the server 220 are connected via the network 210. The key management system 230 is an example of an article management system.
Note that although FIG. 30 shows one server 220 as an example of an external device, a plurality of servers 220 may be connected. Further, instead of the server 220 as an example of an external device, a tablet terminal, a smartphone, or other portable terminal may be used.

In the case of the embodiment described above, an example is given in which information regarding the type of article connected to the key holder 30 (see FIG. 1) is received through the screen 70 (see FIG. 11) displayed on the operation display unit 15 (see FIG. 1). As described above, if the key management device 10 etc. stores information regarding the type of article connected to the key holder 30, it is not necessary to provide the key management device 10 etc. with a function to receive information regarding the type of article.
In the case of the embodiment described above, a distinction is made between the USB memory 33 in which data is protected and the USB memory 33 in which data is not protected, but data deletion is performed on all USB memories 33. Good too.
In the case of the above embodiment, the USB memory 33 is assumed as an example of a storage medium connected to the key holder 30, but it is not limited to a USB memory as long as it is an electrically readable/writable nonvolatile memory. . That is, the storage medium connected to the key holder 30 may be a flash memory compliant with other standards.

In the case of the above-described embodiment, the key 32 and the USB memory 33 were illustrated as examples of the articles to be connected to the key holder 30, but the type of the article does not matter as long as it can be connected to the key holder 30.
Further, in the case of the above-described embodiment, the USB memory 33 is assumed to be the target for reading the information that physically identifies the article connected to the key holder 30, but the When identifiable information is attached, the identification information read through a reading device according to the manner in which each piece of information is attached may be registered in the key management device 10 or the like.
In the case of the above-mentioned embodiment, the key management device 10 including 30 holder accommodating parts 20 has been described, but the number of holder accommodating parts 20 may be arbitrary. For example, the number of holder storage units 20 provided in the key management device 10 may be ten or twenty.
Further, in the case of the above-described embodiment, a case has been described in which a specific type of article is not assigned to a specific holder storage section 20, but a holder storage section dedicated to the management of keys 32 (see FIG. 6) A holder accommodating section 20 dedicated to managing the storage section 20 and the USB memory 33 (see FIG. 6) may be prepared. For example, the serial numbers "1" to "10" assigned to the holder housing section 20 may be used exclusively for managing the keys 32, and the serial numbers "11" to "20" assigned to the holder housing section 20 may be used exclusively for managing the USB memory 33.

10, 10A...Key management device, 40...Control unit, 40A...Reception unit, 40B...Management unit, 40C...Serial number reading unit, 40D...Virus check execution unit, 40E...Data erasing unit, 110...Management table, 160... Virus check management table, 170...Data erasure management table

Claims (21)

a storage section into which a member to which at least one or more items to be managed is connected is attached and detached;
a management unit that manages information regarding the type of article connected to the specific member that is attached to and removed from the storage unit in association with at least one of the specific storage unit and the specific member;
a control unit;
a reading unit that reads information identifying the article from the article connected to the member;
The control unit determines whether or not to read information that identifies the article from the article connected to the member, based on the information regarding the type, and if it is determined that the information is to be read, the control unit An article management system that controls the department to read information that identifies the article. a storage section into which a member to which at least one or more items to be managed is connected is attached and detached;
a management unit that manages information regarding the type of article connected to the specific member that is attached to and removed from the storage unit in association with at least one of the specific storage unit and the specific member;
a reception unit that accepts registration of information regarding the type;
a control unit;
a reading unit that reads information identifying the article from the article connected to the member;
The control unit determines whether or not to read information identifying the article from the article connected to the member, based on the information regarding the type, and if it is determined that the information is to be read, the control unit An article management system that controls the department to read information that identifies the article. The control unit determines whether or not to read information identifying the article from the article connected to the member, based on the information regarding the type, and if it is determined that the information is not to be read, the control unit The article management system according to claim 1 or 2 , wherein the reading unit does not control the reading of information for identifying the article. The article management system according to any one of claims 1 to 3 , wherein the control section manages information identifying the article in association with the corresponding storage section or the corresponding member. When it is determined based on the information regarding the type that a storage medium is included in the article connected to the member attached to the storage unit, the control unit determines whether a virus check has been performed on the storage medium. The article management system according to any one of claims 1 to 4 , which determines. The article according to claim 5 , wherein the control unit determines whether virus checks have been completed for all storage media connected to the member, based on information identifying the article read from the storage medium. management system. The article management system according to claim 5 or 6 , wherein the control unit permits attachment of the member to a specific storage unit based on the execution date and time of a virus check on a storage medium attached to the member. The article management according to claim 7 , wherein the control unit determines whether the virus check has been performed within a time determined according to at least one of the number and data capacity of storage media that are the targets of the virus check. system. The article management system according to any one of claims 5 to 8 , further comprising a virus check execution unit that executes a virus check. If it is determined based on the information regarding the type that a storage medium is included in the article connected to the member attached to the accommodating section, the control section determines whether data has been erased from the storage medium. The article management system according to any one of claims 1 to 9 , wherein the article management system determines whether the 10. The control unit, before executing data erasure, determines whether or not data erasure is prohibited from the storage medium, and when it is determined that data erasure is prohibited, does not execute data erasure . The goods management system described in . 12. The control unit according to claim 9 , wherein the control unit determines whether data has been erased from all storage media connected to the member, based on information identifying the article read from the storage medium. The article management system according to any one of these items. Claims 9 to 12, wherein the control unit does not erase data if a storage medium attached as a target for erasing data is not associated with the storage unit or the member taken out from the storage unit. The article management system according to any one of the items. The article management system according to any one of claims 9 to 13 , wherein the control unit manages a history of execution of data deletion in association with a storage medium. Any one of claims 9 to 14 , wherein the control unit permits attachment of the member to a specific storage unit based on the execution date and time of erasing data from a storage medium attached to the member. The goods management system described in . 16. The controller according to claim 15 , wherein the control unit determines whether data deletion is performed within a time determined according to either the number of storage media that are data deletion targets or the data capacity. Goods management system. The article management system according to any one of claims 10 to 16 , further comprising a data erasure execution unit that erases data from a storage medium. When it is determined based on the information regarding the type that a storage medium is included in the article connected to the member to be removed from the storage unit, the control unit determines whether a virus check has been performed on the storage medium. The article management system according to any one of claims 1 to 15, which makes a determination. If it is determined that the article connected to the member to be removed from the storage unit includes a storage medium based on the information regarding the type, the control unit determines whether data on the storage medium has been erased. The article management system according to any one of claims 1 to 14 , which determines whether the a storage section into which a member to which at least one or more items to be managed is connected is attached and detached;
a management unit that manages information regarding the type of article connected to the specific member that is attached to and removed from the storage unit in association with at least one of the specific storage unit and the specific member;
a control unit;
a reading unit that reads information identifying the article from the article connected to the member;
The control unit determines whether or not to read information identifying the article from the article connected to the member, based on the information regarding the type, and if it is determined that the information is to be read, the control unit An article management device that controls the section to read information that identifies the article. a storage section into which a member to which at least one or more items to be managed is connected is attached and detached;
a management unit that manages information regarding the type of article connected to the specific member that is attached to and removed from the storage unit in association with at least one of the specific storage unit and the specific member;
a reception unit that accepts registration of information regarding the type;
a control unit;
a reading unit that reads information identifying the article from the article connected to the member;
The control unit determines whether or not to read information identifying the article from the article connected to the member, based on the information regarding the type, and if it is determined that the information is to be read, the control unit An article management device that controls the section to read information that identifies the article.

Images