JP6904930B2 - Security system and central management system - Google Patents

Description

The present invention relates to a security system that controls security terminal devices such as electric locks and security gates.

In recent years, due to increasing awareness of information leakage and internal control, an increasing number of companies have introduced security systems such as entry / exit management systems, key management systems, and storage management systems. What is common to all security systems is that 1) the user is authenticated, 2) the security of the security terminal device is released for the user who succeeded in the authentication, and 3) It means keeping a record of when and who unlocked which security terminal device. For this reason, the security system contains user-specific information such as the user's name and ID number, personal authentication information that is collated during personal authentication, and user information that includes conditions for determining whether or not security can be released. Must be registered.

The security system is scalable. For example, in the case of an entry / exit management system, it is possible to start by introducing an electric lock at one door and expand the scope of application to one room, one floor, and the entire building. Furthermore, it is possible to build one large security system by connecting the subsystems built at each geographically separated base with a telecommunication line. Here, the problem in increasing the scale of the security system is the management of user information. That is, if the user information is managed independently in each subsystem, when a user of one base A visits another base B, the user information of that user is not registered in the base B, so that the user information is not registered. There is an inconvenience that the user cannot release the security of the security terminal device of the base B.

As a solution to this problem, when a user of base A visits base B, the user information of the user is transferred from base A to base B in advance, and the user information of the user is temporarily transferred to base B. (For example, refer to Patent Document 1). In addition, the user information of all users of the security system is centrally managed at the center, and the user information of the user is transferred from the center to the visited base before the user visits another base. (See, for example, Patent Documents 2 and 3).

JP-A-2002-73919 Japanese Unexamined Patent Publication No. 2004-265158 Japanese Unexamined Patent Publication No. 2010-26956

All of the conventional solutions transfer user information to the visited base "in advance", but this solution requires advance application for the base visit, which is not convenient. If you forget to apply in advance, you will have to go through the procedure for registering user information at the site you are visiting, and you will be stuck for a while. In addition, if you applied in advance but did not actually visit, or if the schedule was changed but you did not cancel the application, user information will be unnecessarily registered at the base you plan to visit. There are concerns about security issues.

Instead of forwarding the user information to the visited base in advance, contact the center every time you try to unlock the security terminal device at the visited base to perform personal authentication and security cancellation judgment. You can also do it. However, in that case, inquiries to the center occur at each action such as passing through a security gate, opening an auto-lock door, or taking out a key or an item from a key management device or a storage management device at the visited base. It is not convenient because you have to wait every time. In addition, inquiries to the center frequently occur, the amount of communication increases, which is not preferable because it causes pressure on the communication band.

A possible solution is to register the user information of all users of the security system in each subsystem. In that case, it is necessary to mount a memory having a capacity sufficiently large enough to store all user information in the control device of the subsystem, which is not preferable from the viewpoint of cost reduction. Further, if a large amount of user information is stored in the control device, it takes time to authenticate the person, and smooth security release cannot be realized, resulting in lack of convenience.

In view of such a problem, it is an object of the present invention to realize smooth security release while reducing the amount of user information to be stored in the control device of each base in a large-scale security system.

According to one aspect of the present invention, a user who is arranged at each base and is provided corresponding to one or a plurality of security terminal devices and the security terminal device individually and intends to release the security of the corresponding security terminal device. It is a security system configured by connecting a control device to which one or more authentication machines that read personal authentication information are connected and a central management device by a telecommunication line, and the central management device is the personal authentication information and In the user information master in which the user information of each user is registered, including the conditions related to the security release of the security terminal device, the database engine that searches the data of the user information master, and the user information master. On the other hand, the master management unit that adds, updates, and deletes the user information and the user information of any user that the database engine searches for and acquires the user information master are transferred to the control device. The control device includes a user information transfer unit, and the control device includes a user information table that holds the user information of some users, not all users, transferred from the central management device, and the user information table. The person who is trying to unlock the security of the security terminal device by collating the person authentication information read by the certifier with the person authentication information contained in the user information held in the user information table. A personal authentication unit that performs authentication, and a terminal device that controls the operation of the security terminal device according to the user information of the user held in the user information table when the user's personal authentication is successful. When the control unit and the user information table do not have the user information and the user's identity authentication fails, the central management device is requested for the user information of the user, and the request is made. Provided is a security system including a user information management unit that adds the user information transferred from the central management device to the user information table.

According to yet another aspect of the present invention, an attempt is made to release the security of one or more security terminal devices and the corresponding security terminal devices individually provided at each base. It is a central management device that can be connected to a control device connected to one or more authentication devices that read the user's personal authentication information via a telecommunication line, and the conditions related to the personal authentication information and the security release of the security terminal device. Including, a user information master in which user information of each user is registered, a database engine that searches data of the user information master, and addition / update of the user information to the user information master, and The user information transfer unit is provided with a master management unit for deleting and a user information transfer unit for transferring the user information of an arbitrary user acquired by the database engine by searching the user information master to the control device. When the person information transfer unit receives a request for the user information of an arbitrary user from the control device, the use of the user by the other control device at the base where the control device is located. A central management device is provided that is configured to transfer personal information.

According to the present invention, in a large-scale security system, it is possible to realize smooth security release while reducing the amount of user information to be stored in the control device of each base.

Overall schematic block diagram of the security system according to one embodiment of the present invention Detailed configuration diagram of the subsystem according to an example Block diagram of central management device and control device Flowchart of security release process of security terminal device Another flow chart of the security release process of the security terminal device Flowchart of user information update (addition of security release conditions) processing in the central management device Flowchart of user information deletion process in the control device Flowchart of user information deletion processing in the control device when the remaining memory capacity is prioritized Flowchart of user information update (security release condition deletion) processing in the central management device

Hereinafter, embodiments will be described in detail with reference to the drawings as appropriate. However, more detailed explanation than necessary may be omitted. For example, detailed explanations of already well-known matters and duplicate explanations for substantially the same configuration may be omitted. This is to avoid unnecessary redundancy of the following description and to facilitate the understanding of those skilled in the art.

It should be noted that the inventor provides the accompanying drawings and the following description in order for those skilled in the art to fully understand the present invention, and is not intended to limit the subject matter described in the claims by these. do not have. In addition, the dimensions, thickness, detailed shape of details, etc. of each member drawn in the drawing may differ from the actual ones.

≪Composition≫
FIG. 1 is a diagram showing an overall schematic configuration of a security system according to an embodiment of the present invention. In the security system 100 according to the present embodiment, a subsystem 10 constructed at each base such as a corporate head office, a branch office, a business office, a laboratory, and a factory, and a central management device 20 that centrally manages the security system 100 are used. It is constructed by being connected by a telecommunication line 30 such as a dedicated communication line or a VPN (Virtual Private Network) using the Internet. The base may be overseas as well as domestic. The central management device 20 may be arranged at an arbitrary base (for example, the head office), or may be arranged at a place other than each base, for example, a cloud environment.

Each subsystem 10 includes one or more security terminal devices 11, one or more authentication machines 12, and one or more control devices 13. In addition to this, each subsystem 10 includes a surveillance camera, various sensors, and the like, but these facilities are not directly related to the present invention, and therefore, illustration and description thereof are omitted in the present specification.

Each control device 13 is provided with one or more security terminal devices 11 and the security terminal devices 11 individually, and reads the personal authentication information of a user who intends to release the security of the corresponding security terminal devices 11. One or more authentication machines 12 are connected. Each control device 13 is connected to a LAN (Local Area Network) 14, and is further connected to a telecommunication line 30 via a gateway 15 so as to be able to communicate with the central management device 20.

The number of bases and the number of security terminal devices 11, authentication machines 12, and control devices 13 at each base are arbitrary, but when a large number of security terminal devices 11 are arranged at each base, a plurality of control devices 13 are required. May become. For example, only one control device 13 is arranged at the small-scale base “base A” shown in FIG. 1, but a plurality of control devices 13 are arranged at the large-scale base “base B”. Further, the security terminal device 11, the authentication device 12, the control device 13, and the gateway 15 may be physically integrated as in the small-scale base “base C”.

FIG. 2 is a diagram showing a detailed configuration of the subsystem 10 according to an example. A specific example of the security terminal device 11 will be described with reference to the figure. The security terminal device 11 is a general term for electric locks, automatic doors, security gates, key management devices, storage management devices, and the like.

The electric lock 11a is an electric member that locks and unlocks by the operation of an actuator, and is mainly incorporated in a hinged door type door, a storage door, a safe door, and the like. The automatic door 11b is a facility that automatically opens and closes a hinged door type door mainly by the driving force of an electric motor, and is installed at the entrance / exit of a partitioned indoor space such as a room or a lobby. The security gate 11c is a facility that automatically opens and closes the gate by the driving force of an electric motor or restricts the opening operation of the gate by the operation of an actuator, and is installed at the boundary of the zone indoors or outdoors for the purpose of restricting the passage of people. Will be done. The key management device 11d is a device for storing small items such as keys, USB (Universal Serial Bus) memory, key bundles, seals, and cards in one place, and holds key chains and individual items for holding individual items. It is equipped with a key box to store it. In some cases, the key management device 11d is provided with a tray or a case box capable of accommodating valuables such as watches and precious metals, mobile phones, and the like. These key chains, key boxes, trays, and case boxes can be individually locked and unlocked by the operation of the actuator. The storage management device 11e is an aggregate of cabinets for storing and storing various documents, ledgers, files, articles, and the like. An electric lock is built into the door of each cabinet, and the door is locked and unlocked by the operation of the actuator. Further, the storage management device 11e may incorporate a key management device, a safe with enhanced anti-theft and fire resistance, and the like. In the case of the key management device 11d and the storage management device 11e, the authentication machine 12 and the control device 13 are unitized and incorporated in the management device main body.

The authentication machine 12 includes a non-contact IC card reader such as FeliCa (registered trademark), MIFARE (registered trademark), and Type B, a magnetic stripe card reader, an RFID (Radio Frequency Identifier) reader, a QR code (registered trademark) reader, and a bar. Code reader, fixed, scrambled and display type PIN code Tenkey, fingerprint, finger vein, back vein, palm vein, biometric authentication machine such as face and iris. The contactless IC card reader, magnetic stripe card reader, and RFID card reader read the unique identification information of the card or ID tag possessed by the user as personal authentication information. The QR code (registered trademark) reader and the barcode reader read the QR code (registered trademark) or the barcode displayed on the mobile phone or the like possessed by the user as personal identification information. The security code numeric keypad reads the security code entered by the user as personal authentication information. The biometric authentication machine reads an image pattern of a part of the user's body as personal authentication information.

In the security terminal device 11 provided at a place where people come and go, such as a door in which an electric lock 11a is incorporated, an automatic door 11b, and a security gate 11c, one authentication machine 12 is provided on each side. In particular, a non-contact IC card reader is integrally incorporated in the security gate 11c. A unit-type device such as the key management device 11d and the storage management device 11e is provided with one authentication machine 12.

Next, the detailed configuration of the central management device 20 and the control device 13 will be described. FIG. 3 is a block diagram of the central management device 20 and the control device 13.

The central management device 20 includes a processor 200, a non-volatile memory 201, a volatile memory 202, a storage 203, and a communication interface 204. In the storage 203, a user information master 205 in which user information of each user of the security system 100 is registered and a device information master 206 in which device information of each control device 13 is registered are placed. The user information includes the user's name, ID number, affiliation, job title, grade, years of service, personal authentication information, and conditions related to security release of the security terminal device 11. The personal authentication information is the unique identification information of the card or ID tag distributed to each user in the case of card authentication or ID tag authentication, the several-digit number set by each user in the case of PIN authentication, and the living body. In the case of authentication, it is an image pattern of a part of each user's body. The conditions for unlocking the security terminal device 11 include whether or not the security terminal device 11 can be unlocked and the time zone during which the security can be unlocked (for example, from what time to what time on what day of the week). In addition, the device information includes information such as the location of the control device 13 and the connection status of the security terminal device 11.

In the following, the term "user information" refers to the user information of each user described above. Further, when the term "device information" is used, it refers to the device information of each of the above-mentioned control devices 13.

The processor 200 executes the basic software for the server and the database software stored in the non-volatile memory 201 or the storage 203, and further reads and executes the computer program for the security system stored in the non-volatile memory 201 or the storage 203. It functions as a database engine 207, a master management unit 208, and a user information transfer unit 209. The database engine 207 searches the data of the user information master 205 and the device information master 206. The master management unit 208 adds, updates, and deletes user information and device information to the user information master 205 and the device information master 206. The user information transfer unit 209 transfers the user information of an arbitrary user acquired by the database engine 207 by searching the user information master 205 to the control device 13.

The volatile memory 202 is used for temporary data storage such as work memory when the processor 200 executes a computer program. The communication interface 204 is an interface that enables communication with an external device such as the control device 13.

The control device 13 includes a microcomputer 130, a non-volatile memory 131, a volatile memory 132, a communication interface 133, and a control interface 134. A user information table 135 that holds user information is placed in the non-volatile memory 131. The user information is acquired from the central management device 20 by the user information management unit 138, which will be described later, and stored in the user information table 135. However, due to the memory capacity, the user information stored in the user information table 135 is not the user information of all users managed by the central management device 20, but the security under the control of the control device 13. It is limited to the user information of the user who may use the terminal device 11. That is, the user information table 135 holds the user information of some users, not all users, transferred from the central management device 20.

The microcomputer 130 functions as a personal authentication unit 136, a terminal device control unit 137, a user information management unit 138, and an event recording unit 139 by reading and executing a computer program stored in the non-volatile memory 131. The personal authentication unit 136 will collate the personal authentication information read by the authentication machine 12 with the personal authentication information included in the user information held in the user information table 135 to release the security of the security terminal device 11. Authenticate the user. When the terminal device control unit 137 succeeds in authenticating the user's identity, the terminal device control unit 137 opens and closes the electrical contact (not shown) in the control interface 134 according to the user information of the user held in the user information table 135. Controls the operation of the target security terminal device 11. The user information management unit 138 acquires necessary user information from the central management device 20 and adds it to the user information table 135, or deletes unnecessary user information held in the user information table 135. Or The event recording unit 139 records an event of when and who released the security of which security terminal device 11 in a predetermined storage area of the non-volatile memory 131 each time the security of the security terminal device 11 is released. Further, the event recording unit 139 may record the event of the security release failure when the user tries to release the security of the security terminal device 11 and fails. The recorded event log is transferred to the central management device 20 as needed so that the administrator can check it.

The volatile memory 132 is used for temporary data storage such as a work memory when the microcomputer 130 executes a computer program. The communication interface 133 is an interface that enables communication with an external device such as the central management device 20. The control interface 134 is an interface that enables communication with one or more security terminal devices 11 under the control of the control device 13 and one or more authentication devices 12 corresponding to the individual security terminal devices 11. The control interface 134 includes a plurality of electrical contacts (not shown) whose opening and closing is controlled by the terminal device control unit 137, and an actuator or an electric motor of each security terminal device 11 is connected to each electrical contact. Each security terminal device 11 is supplied with electric power for driving an actuator or an electric motor from a power supply unit (not shown). For communication with each authentication machine 12, for example, a LON conforming to the LONWORKS (registered trademark) specification can be used.

≪Operation≫
Next, the security release process and the user information deletion (update) process, which are characteristic of the security system 100 according to the present embodiment, will be described with reference to the flowchart.

FIG. 4 is a flowchart of the security release process of the security terminal device 11. First, a user (hereinafter referred to as "attention user") tries to unlock the security of a security terminal device 11 (hereinafter referred to as a target security terminal device 11), for example, tries to pass through a security gate, and possesses, for example. When the IC card is held over the authentication machine 12, the authentication machine 12 reads the unique information of the IC card as the personal authentication information (S101). The personal authentication unit 136 reads the personal authentication information from the user information table 135, and collates the unique information of the IC card read by the authentication machine 12 with the personal authentication information included in the read user information (S102). As a method of reading the personal authentication information from the user information table 135, a search using an embedded database, a tree structure search, or the like is possible. If they match (YES in S103), it means that the personal authentication was successful. Next, the terminal device control unit 137 reads out the user information of the attention user held in the user information table 135. Then, it is determined whether or not the security of the target security terminal device 11 can be released (S104). As a result of the determination, if the security may be released (YES in S105), the terminal device control unit 137 closes the electrical contact corresponding to the target security terminal device 11 in the control interface 134 to close the target security terminal. The security of the device 11 is released, for example, the security gate is opened (S106). Then, the event recording unit 139 records an event of when and who released the security of which security terminal device 11 (S107), and the security release process ends. On the other hand, as a result of the determination, when the security must not be released (NO in S105), the terminal device control unit 137 does not close the electrical contact in the control interface 134, that is, the security of the target security terminal device 11. (S108), the security release ends in failure. In this case, the event recording unit 139 records an event indicating when and who tried to release the security of which security terminal device 11 and failed (S107), and the security release process ends.

In the security system 100 according to the present embodiment, as little user information as possible, preferably the minimum necessary user information, is registered in the control device 13 (more specifically, the user information table 135). Therefore, for example, since the user information of an employee who travels to another base is not registered in the control device 13 of the other base, the employee can release the security of the security terminal device 11 at the other base. The problem arises that it cannot be done. Therefore, the security system 100 according to the present embodiment introduces a mechanism for temporarily adding the user information of the employee to the control device 13 of the other base as follows.

If the user information is not registered in the control device 13, the personal authentication by the personal authentication unit 136 fails (NO in S103). In that case, the user information management unit 138 requests the user information of the user of interest from the central management device 20 (S109). When the central management device 20 receives a request from the control device 13, the central management device 20 transfers the corresponding user information to the control device 13, or the control device 13 indicates that the user information of the attention user is not registered. Notify to. If the user information management unit 138 can acquire the user information from the central management device 20 (YES in S110), the user information management unit 138 adds the user information to the user information table 135 (S111). When the user information is added to the user information table 135, the personal authentication unit 136 collates the unique information of the IC card read by the authentication machine 12 with the personal authentication information included in the added user information. The personal authentication of the attention user is retried (S112). If they match (YES in S113), it means that the person authentication was successful, so the terminal device control unit 137 proceeds to determine whether or not the security can be released (S104), and then the security is released by the above procedure. .. On the other hand, when the central management device 20 notifies that the user information of the user of interest is not registered (NO in S110), or as a result of the terminal device control unit 137 determining whether or not the security can be released, the security is determined. If it cannot be released (NO in S105), the terminal device control unit 137 does not close the electrical contact in the control interface 134, that is, without releasing the security of the target security terminal device 11 (S108). , Security release ends in failure. In this case, the event recording unit 139 records an event indicating when and who tried to release the security of which security terminal device 11 and failed (S107), and the security release process ends.

FIG. 5 is a flowchart of another example of the security release process of the security terminal device 11. The same part as in FIG. 4 will not be repeated, and only the points different from FIG. 4 will be described. In this alternative example, when the personal authentication by the personal authentication unit 136 fails (NO in S103), the user information management unit 138 requests the central management device 20 for the user information of the user of interest, and the authentication machine 12 Transfers the personal authentication information of the attention user read by (S109). When the central management device 20 receives a request and information from the control device 13, the database engine 207 refers to the user information master 205 to identify the user of interest and determine whether or not the security of the target security terminal device 11 can be released. The user information transfer unit 209 transfers the user information of the attention user acquired by the database engine 207 by searching the user information master 205 to the control device 13, and the personal authentication and security by the database engine 207. Notify the result of the cancellation approval / disapproval judgment. Alternatively, the central management device 20 notifies the control device 13 that the user information of the attention user is not registered. If the user information management unit 138 can acquire the user information from the central management device 20 (YES in S110), the user information management unit 138 adds the user information to the user information table 135 (S111). Then, when the terminal device control unit 137 may release the security according to the result of the personal authentication of the attention user received from the central management device 20 and the determination of whether or not the security of the target security terminal device 11 can be released ( YES in S105), the security of the target security terminal device 11 is released (S106). On the other hand, if the security must not be released (NO in S105), the terminal device control unit 137 does not release the security of the target security terminal device 11 (S108).

In this way, in addition to requesting the user information of an arbitrary user from the control device 13 to the central management device 20, the personal authentication information is transferred to the central management device 20 to perform personal authentication and security on the central management device 20 side. By determining whether or not the security of the terminal device 11 can be released, the control device 13 does not need to retry the personal authentication, and the security of the target security terminal device 11 can be efficiently released.

In the case where the security of the security terminal device 11 may be released at once if the personal authentication is successful, only the personal authentication information may be transferred from the control device 13 to the central management device 20 as described above, but the control In the case where a large number of security terminal devices 11 are connected to the device 13 and the central management device 20 does not know which security terminal device 11 should be released from security, the person himself / herself from the control device 13 to the central management device 20. The identification information of the target security terminal device 11 may be transferred together with the authentication information. By doing so, the security terminal device 11 to be subject to the determination of whether or not the security can be released is specified, and the central management device 20 refers to the user information master 205 to authenticate the identity of the user of interest and the target security terminal device. It is possible to determine whether or not the security of 11 can be released.

The transfer of user information from the central management device 20 to the control device 13 described above will be supplemented. In the user information master 205, it is registered under what conditions the security of which security terminal device 11 can be released for each user, but there are no conditions for the security terminal device 11 at a base where the user is not involved. May not be registered. In that case, the user information does not exist for the base, and there is a problem that the user information cannot be transferred in response to the request from the control device 13 of the base. In order to deal with such a problem, as described below, a mechanism has been introduced in which the central management device 20 automatically adds a condition for unlocking the security of the security terminal device 11 at an arbitrary base and updates the user information. May be good.

FIG. 6 is a flowchart of user information update (security release condition addition) processing in the central management device 20. First, when the central management device 20 receives a request for user information of an arbitrary user (hereinafter referred to as "attention user") from an arbitrary control device 13, the database engine 207 searches for the device information master 206. The base where the control device 13 is arranged (hereinafter referred to as “attention base”) is specified (S21), the user information master 205 is searched, and the user information of the attention user is acquired (S22). The execution order of S21 and S22 may be reversed. When the corresponding user information is acquired, the master management unit 208 confirms whether the user information is set with the conditions for unlocking the security terminal device 11 at the base of interest. If it is not set (NO in S23), the condition for unlocking the security terminal device 11 at the attention base according to the security authority of the attention user included in the acquired user information by the master management unit 208. Is set (S24), and the user information of the attention user registered in the user information master 205 is updated (S25). As security authority, affiliation, job title, grade, years of service, etc. can be used. For example, an officer in the managerial class or higher can unlock all the security terminal devices 11 at the base of interest, and a general employee can set only some security terminal devices 11 to unlock. When the user information is updated, the database engine 207 identifies another control device 13 at the base of interest (S26), and the user information transfer unit 208 identifies the requesting control device 13 and the other identified control device 13. The updated user information is transferred to the control device 13 (S27). On the other hand, if it is set (YES in S23), the database engine 207 identifies another control device 13 at the base of interest (S26), and the user information transfer unit 208 causes the requesting control device 13 and The acquired user information is transferred to the other specified control device 13 (S27).

In order to reduce the user information registered in the user information table 135 as much as possible, it is necessary to regularly or irregularly organize the user information temporarily added to the control device 13 according to the above procedure. Therefore, in the security system 100 according to the present embodiment, a mechanism for temporarily deleting the added user information is introduced as follows.

As the simplest deletion method, an expiration date is set for the user information temporarily added to the user information table 135, and the user information management unit 138 uses the user information whose expiration date has passed. It is to be deleted from the person information table 135. The expiration date may be set by the central management device 20 or by the user information management unit 138.

In addition to this, user information can be deleted as follows. FIG. 7 is a flowchart of the user information deletion process in the control device 13. First, the user information management unit 138 extracts the last use date and time of each user from the user information table 135 (S31), and narrows down the users whose predetermined period has passed from the last use date and time (S32). The last use date and time means the latest date and time when the user unlocks the security of any security terminal device 11 connected to the control device 13. The last use date and time is recorded in the user information table 135 for each user by the event recording unit 139 when the security of the security terminal device 11 is released. The users narrowed down here are users who have not released the security of the security terminal device 11 for a predetermined period from the last use date and time. The user information management unit 138 picks up the narrowed down users one by one in chronological order of the last use date and time, and determines whether or not the user is a special user (S33). The special user is, for example, an employee, an officer, an employee who has received a special order, etc., to whom the affiliation belongs. Whether or not the user is a special user can be determined based on the user information. If the user is not a special user (NO in S34), the user information management unit 138 deletes the user information of the user from the user information table 135 (S35), and the user of the user. Notify the central management device 20 that the information has been deleted (S36). The reason for notifying the central management device 20 of the deletion of the user information is that the central management device 20 also needs to update the user information of the user. This will be described later. On the other hand, if the user is a special user (YES in S34), the user information of the user is left in the user information table 135. The procedure from S33 to S36 is repeated until there are no more users to pick up in S33 (S37).

When the remaining memory capacity allocated to the user information table 135 is less than or equal to the predetermined value regardless of whether or not a predetermined period has elapsed from the last usage date and time, the user gives priority to the remaining memory capacity as follows. It is desirable to delete the information. FIG. 8 is a flowchart of the user information deletion process in the control device 13 in the case where the remaining memory capacity is prioritized. First, the user information management unit 138 extracts the last use date and time of each user from the user information table 135 (S41), picks up the users one by one in the order of the extracted last use date and time, and the user. Determines whether or not is a special user (S42). If the user is not a special user (NO in S43), the user information management unit 138 deletes the user information of the user from the user information table 135 (S44), and the user of the user. Notify the central management device 20 that the information has been deleted (S45). On the other hand, if the user is a special user (YES in S43), the user information of the user is left in the user information table 135. The procedure from S42 to S45 is repeated until the free space of the user information table 135 is secured (S46).

Next, the operation of the central management device 20 when the control device 13 notifies the deletion of the user information of any user will be described. FIG. 9 is a flowchart of user information update (security release condition deletion) processing in the central management device 20. First, when the central management device 20 receives a notification from the arbitrary control device 13 that the user information of an arbitrary user (hereinafter referred to as "attention user") has been deleted, the database engine 207 causes the device information master. The 206 is searched to identify the base where the control device 13 is located (hereinafter referred to as "attention base") (S51), and the user information master 205 is searched to acquire the user information of the attention user (hereinafter, the attention user information). S52). The execution order of S51 and S52 may be reversed. When the corresponding user information is acquired, the database engine 207 further searches the device information master 206 to identify all the security terminal devices 11 at the base of interest (S53). The execution order of S52 and S53 may be reversed. When all the security terminal devices 11 in the base of interest are identified, the master management unit 208 deletes the conditions related to the security release of all the security terminal devices 11 identified from the acquired user information (S54). , Update the user information of the user information master 205 (S55). As a result, the conditions related to the security release of all the security terminal devices 11 at the attention base are deleted from the user information of the attention user managed by the central management device 20, and the user information of the attention user is restored to the original state. return.

≪Effect≫
The security system 100 according to the present embodiment has the following effects. First, in the large-scale security system 100, it is possible to reduce the amount of user information to be stored in the control device 13 at each base. As a result, the memory capacity for storing user information in the control device 13 can be reduced, and the memory capacity does not have to be increased even if the number of system users increases. Further, since the amount of user information to be stored in the control device 13 is reduced, the user can be quickly authenticated and the security can be smoothly released.

Furthermore, even if you do not apply in advance when visiting another base on a business trip, or if you suddenly visit another base due to a schedule change, the security of each security terminal device 11 can be smoothly released at that base. It will be possible. This frees you from troublesome pre-applications and improves convenience. In addition, if you applied in advance but did not actually visit, or if you changed your schedule but did not cancel your application, user information will be unnecessarily registered at the site you plan to visit. There is no. As a result, the user information to be stored in the control device 13 can be suppressed, and the registration of unnecessary user information can be eliminated to further strengthen the security.

≪Application / transformation≫
A user who is known to use the security terminal device 11 under the control of the control device 13, for example, an officer regardless of the user or the affiliation where the control device 13 is located. User information such as a certain number of managers such as directors and directors may be registered in the user information table 135 in advance. Specifically, the user information is organized by base, the user information is transferred from the central management device 20 to the control device 13 of each base, and the user information is stored in the user information table 135 in advance. , Security gate, key management device, storage management device, etc. User information is organized according to the type of security terminal device 11, and user information is transferred from the central management device 20 to the control device 13 that controls various security terminal devices 11. Then, the user information may be stored in the user information table 135 in advance. Alternatively, the user information is organized by base and by the type of security terminal device 11, and the user information is transferred from the central management device 20 to the control device 13 that controls each security terminal device 11 at each base, and the user information is transferred in advance. User information may be stored in table 135. As described above, for the user who is known to use the security terminal device 11 under the control of the control device 13, the user information can be registered in the user information table 135 in advance from the control device 13. It is possible to quickly authenticate the person and unlock the security by omitting the inquiry to the central management device 20.

In addition, the priority is set for the user information stored in the user information table 135, and the user information having the highest priority is referred to first when the personal authentication unit 136 performs personal authentication. May be good. For example, among the user information held in the user information table 135, the user information of the user whose affiliation is at the base where the control device 13 is located, the officers and directors regardless of the affiliation, etc. User information of managers above a certain level, user information of users whose predetermined period has not passed since the last use date and time, etc. are managed as active information, and other user information is managed as inactive information, and the person himself / herself. The active information may be referred to first when the person is authenticated by the authentication unit 136. As a result, the user who frequently uses the security terminal device 11 under the control of the control device 13 can be quickly authenticated.

In S31 of FIG. 7 and S41 of FIG. 8, the last use date and time of each user is extracted from the user information table 135, but the security is released not stored in the user information table 135 but in the non-volatile memory 131. From the event history, the last use date and time when the security of the security terminal device 11 is released may be specified for each user whose user information is registered in the user information table 135. By doing so, it is possible to specify the last use date and time of each user by utilizing the event history without changing the specifications of the existing user information table 135.

The above security system 100 is premised on the existence of a central management device 20, but in the case of a small-scale system, user information can be independently managed by the control device 13 at each site without installing the central management device 20. be. In such a configuration, user information that is not held by the control device 13 at a certain base can be requested and acquired from the control device 13 at another base.

As described above, an embodiment has been described as an example of the technique in the present invention. To that end, the accompanying drawings and detailed description are provided.

Therefore, among the components described in the attached drawings and the detailed description, not only the components essential for solving the problem but also the components not essential for solving the problem in order to exemplify the above technology. Can also be included. Therefore, the fact that those non-essential components are described in the accompanying drawings and detailed description should not immediately determine that those non-essential components are essential.

Further, since the above-described embodiment is for exemplifying the technique of the present invention, various changes, replacements, additions, omissions, etc. can be made within the scope of claims or the equivalent scope thereof.

100 ... Security system, 11 ... Security terminal device, 12 ... Authentication machine, 13 ... Control device, 14 ... LAN, 15 ... Gateway, 135 ... User information table, 136 ... Personal authentication unit, 137 ... Terminal device control unit, 138 ... User Information Management Department, 139 ... Event Recording Department, 20 ... Central Management Device, 205 ... User Information Master, 207 ... Database Engine, 208 ... Master Management Department, 209 ... User Information Transfer Department, 30 ... Telecommunications Line

Claims (7)

One or more security terminal devices located at each site and one or more of the security terminal devices individually provided to read the personal authentication information of a user who intends to release the security of the corresponding security terminal device. It is a security system configured by connecting a control device to which the authentication machine of the above is connected and a central management device by a telecommunication line.
The central management device
A user information master in which user information of each user is registered, including personal authentication information and conditions related to security release of the security terminal device, and
A database engine that searches the data of the user information master and
A master management unit that adds, updates, and deletes user information to the user information master.
The database engine includes a user information transfer unit that transfers the user information of any user acquired by searching the user information master to the control device.
The control device is
A user information table that holds the user information of some users, not all users, transferred from the central management device.
A user who attempts to release the security of the security terminal device by collating the personal authentication information read by the authentication machine with the personal authentication information included in the user information held in the user information table. The person authentication department that authenticates the person and
When the user's identity authentication is successful, the terminal device control unit that controls the operation of the security terminal device according to the user information of the user held in the user information table, and the terminal device control unit.
When the user information does not exist in the user information table and the user's personal authentication fails, the central management device is requested for the user information of the user, and the central management device responds to the request. It is equipped with a user information management unit that adds the transferred user information to the user information table.
When the user information transfer unit receives a request for the user information of an arbitrary user from the control device, the user's information is also transferred to another control device at the base where the control device is located. A security system characterized in that it is configured to transfer the user information. When the user information is added to the user information table, the personal authentication unit collates the personal authentication information read by the authentication machine with the personal authentication information included in the added user information. The security system according to claim 1, which is configured to retry the user's personal authentication. When the user information management unit does not have the user information in the user information table and fails to authenticate the user's identity, the central management device requests the user information of the user and the user information is described. It is configured to transfer the user's personal authentication information read by the certifier.
The database engine receives the personal authentication information of an arbitrary user from the control device, refers to the user information master, authenticates the user, and unlocks the security of the security terminal device by the user. It is configured to make a pass / fail judgment,
The user information transfer unit transfers the user information of an arbitrary user acquired by the database engine by searching the user information master to the control device, and at the same time, personal authentication and security release by the database engine. It is configured to notify the result of the approval / disapproval judgment of
The security system according to claim 1, wherein the terminal device control unit is configured to control the operation of the security terminal device according to the result of personal authentication and security release determination received from the central management device. .. The conditions for unlocking the security terminal device included in the user information are determined according to the security authority of the user.
When the master management unit receives a request for the user information of an arbitrary user from the control device, the security terminal at the base where the control device is arranged according to the security authority of the user. It is configured to set the conditions related to the security release of the device and update the user information of the user registered in the user information master.
The security system according to any one of claims 1 to 3, wherein the user information transfer unit is configured to transfer the updated user information to the control device. The user information management unit is configured to delete the user information added to the user information table from the user information table as needed, according to any one of claims 1 to 4. The security system described. The expiration date is set for the user information added to the user information table by the user information management unit.
The security system according to claim 5, wherein the user information management unit is configured to delete the user information whose expiration date has passed from the user information table. One or more security terminal devices located at each site and one or more of the security terminal devices individually provided to read the personal authentication information of a user who intends to release the security of the corresponding security terminal device. It is a central management device that can be connected to the control device to which the authentication machine is connected via a telecommunication line.
A user information master in which user information of each user is registered, including personal authentication information and conditions related to security release of the security terminal device, and
A database engine that searches the data of the user information master and
A master management unit that adds, updates, and deletes user information to the user information master.
The database engine includes a user information transfer unit that transfers the user information of any user acquired by searching the user information master to the control device.
When the user information transfer unit receives a request for the user information of an arbitrary user from the control device, the user's information is also transferred to another control device at the base where the control device is located. A central management device characterized in that it is configured to transfer the user information.

Images