JP2020024647A - Security system, control unit, and central management device - Google Patents

Abstract

To achieve, in a large-scale security system, security releases in a smooth manner while reducing user information to be stored in control units at each base.SOLUTION: In a security system (100), a central management device (20) comprises a user information master (205), a database engine (207), a master management section (208), and a user information forwarding section (209). And a control unit (13) comprises: a user information table (135) for retaining user information not on all users but on some users; a principal authentication section (136); a terminal apparatus control unit (137) for controlling operations of a security terminal apparatus (11) when a principal authentication is successful; and a user information management section (138) for, when the principal authentication fails, requesting the central management device (20) for the user information, and adding the forwarded user information into the user information table (135).SELECTED DRAWING: Figure 3

Description

  The present invention relates to a security system that controls security terminal devices such as an electric lock and a security gate.

  2. Description of the Related Art In recent years, due to increased awareness of information leakage and internal control, an increasing number of companies have introduced security systems such as an access control system, a key management system, and a storage management system. Common to all security systems are 1) user authentication, 2) security of the security terminal device is released to the user who succeeds in authentication under predetermined conditions, and 3) This means keeping a record of when and who unlocked security on which security device. For this reason, the security system stores user identification information such as the user's name and ID number, user authentication information to be collated at the time of personal authentication, and user information including conditions for determining whether or not to release security. You need to register.

  The security system is scalable. For example, in the case of an entry / exit management system, the application range can be expanded to one room, one floor, and the entire building, starting from introducing an electric lock at one door. Further, one large security system can be constructed by connecting subsystems constructed at geographically distant bases via a telecommunication line. Here, management of user information is a problem when the security system is scaled up. That is, if user information is independently managed in each subsystem, when a user at a certain base A visits another base B, the user information of the user is not registered at the base B, so that There is a disadvantage that the user cannot release the security of the security terminal device at the base B.

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

JP-A-2002-73919 JP-A-2004-265158 JP 2010-26956 A

  All of the conventional solutions transfer user information “in advance” to a site to be visited, but this solution requires advance application for a site visit and is not convenient. If you forget to apply in advance, you will have to go through a procedure for registering user information at the base you visit, and this will be stopped for a while. In addition, in the case that the application was made in advance but did not actually visit, or the schedule was changed but the application was not canceled, the user information will be registered unnecessarily at the site where the visit is scheduled This raises concerns about security issues.

  Instead of transferring user information to the visited site in advance, every time an attempt is made to release the security of the security terminal device at the visited site, the center is contacted to determine the identity and to determine the security release. You can also. However, in such a case, the center will be inquired every time an action is taken, such as passing through a security gate, opening an automatic lock door, or removing a key or item from a key management device or a storage management device at a visited base. You will have to wait every time and it is not convenient. In addition, the number of inquiries to the center occurs frequently and the amount of communication increases, which is a factor that presses the communication band, which is not preferable.

  A possible solution is to register user information of all users of the security system in each subsystem. In this case, it is necessary to mount a memory having a capacity large enough to store all user information in the control device of the subsystem, but this is not preferable from the viewpoint of cost reduction. In addition, if a large amount of user information is stored in the control device, it takes a long time to authenticate the user, making it impossible to realize a smooth security release, resulting in a lack of convenience.

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

  According to one aspect of the present invention, one or more security terminal devices are provided at each site and provided for each of the security terminal devices, and a user who wants to release the security of the corresponding security terminal device is provided. A control system to which one or a plurality of authenticators that read the personal authentication information is connected, and a central management device is a security system configured to be connected by a telecommunication line, wherein the central management device includes the personal authentication information and A user information master in which user information of each user is registered, including a condition relating to security release of the security terminal device; a database engine for performing data search of the user information master; A master management unit for adding, updating, and deleting the user information; A user information transfer unit that transfers the user information of any user obtained by searching for the user information master to the control device. The transferred user information table holding the user information of some of the users who are not all users, the user authentication information read by the authentication device, and the use information stored in the user information table. An identity authentication unit that authenticates a user who intends to release security of the security terminal device by comparing the identity authentication information included in the user information with the identity authentication information. A terminal device control unit for controlling operation of the security terminal device according to the user information of the user held in the user information table; If there is no information and the user authentication fails, the central management device requests the user information of the user, and the user information transferred from the central management device in response to the request is A security system comprising a user information management unit for adding to a user information table is provided.

  According to another aspect of the present invention, one or more security terminal devices and personal authentication information of a user who is provided corresponding to each of the security terminal devices and intends to release the security of the corresponding security terminal device are provided. A control device to which one or a plurality of authenticators to be read can be connected, and a user information table holding user information of each user including personal authentication information and a condition relating to security release of the security terminal device; By comparing the personal authentication information read by the authentication device with the personal authentication information included in the user information held in the user information table, the user who wants to release the security of the security terminal device is checked. An identity authentication unit for performing identity authentication, and, when the identity of the user is successfully authenticated, the user information is stored in the user information table. A terminal device control unit for controlling the operation of the security terminal device according to the user information of the user, and when the user information table does not have the user information and user authentication fails. A user who requests the user information of the user from an external device holding the user information, and adds the user information transferred from the external device to the request to the user information table A control device comprising an information management unit is provided.

  According to still another aspect of the present invention, each of the security terminals is disposed at each base, and is provided corresponding to each of the security terminal and the security terminal, and attempts to release the security of the corresponding security terminal. A central management device that can be connected by a telecommunications line to a control device to which one or more authenticators that read the user's identity information are connected, wherein the condition relating to the identity authentication information and the security release of the security terminal device is set. A user information master in which user information of each user is registered, a database engine for performing data search of the user information master, and addition, update, and deletion of the user information to the user information master A master management unit for performing deletion, and a function for searching and acquiring the user information master by the database engine. A user information transfer unit for transferring the user information of the user to the control device, wherein the user information transfer unit receives a request for the user information of any user from the control device. In this case, a central management device is provided, wherein the central management device is configured to transfer the user information of the user to another control device at a base where the control device is located.

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

Overall schematic configuration diagram of a security system according to an embodiment of the present invention Detailed configuration diagram of a subsystem according to an example Block diagram of central management unit and control unit Flowchart of security terminal device security release processing Flowchart of another example of security release processing of security terminal device Flow chart of user information update (security release condition addition) processing in the central management device Flowchart of user information deletion processing in control device Flowchart of user information deletion processing in the control device when priority is given to remaining memory capacity Flow chart 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, an unnecessary detailed description may be omitted. For example, a detailed description of a well-known item or a redundant description of substantially the same configuration may be omitted. This is to prevent the following description from being unnecessarily redundant and to facilitate understanding by those skilled in the art.

  The inventor provides the accompanying drawings and the following description so that those skilled in the art can fully understand the present invention, and these are not intended to limit the subject matter described in the claims. Absent. In addition, dimensions, thicknesses, detailed detailed shapes, and the like of each member illustrated in the drawings may be different from actual ones.

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

  Each subsystem 10 includes one or a plurality of security terminal devices 11, one or a plurality of authenticators 12, and one or a plurality of control devices 13. In addition, each subsystem 10 includes a surveillance camera, various sensors, and the like. However, since these facilities are not directly related to the present invention, illustration and description are omitted in this specification.

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

  The number of sites and the number of security terminal devices 11, authentication devices 12, and control devices 13 at each site are arbitrary. However, when a large number of security terminal devices 11 are arranged at the sites, a plurality of control devices 13 are required. May be. For example, only one control device 13 is arranged at the small base “base A” shown in FIG. 1, but a plurality of control devices 13 are arranged at the large 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 like a small site "site C".

  FIG. 2 is a diagram illustrating 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 FIG. The security terminal device 11 is a general term for an electric lock, an automatic door, a security gate, a key management device, a storage management device, and the like.

  The electric lock 11a is an electric member that performs locking and unlocking by operation of an actuator, and is mainly incorporated in a door of a hinged door type, a storage door, a safe door, and the like. The automatic door 11b is a device that automatically opens and closes a door of a swing door type mainly by the driving force of an electric motor, and is installed at an entrance of a partitioned indoor space such as a room or a lobby. The security gate 11c is a facility for automatically opening and closing the gate with the driving force of the electric motor or for restricting the opening operation of the gate by the operation of an actuator. Is done. The key management device 11d is a device that collectively stores small items such as a key, a USB (Universal Serial Bus) memory, a key bunch, a seal, and a card in one place, and stores a key ring that holds individual items and an individual item. It has a key box to accommodate. In some cases, the key management device 11d includes a tray or a case box that can store 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 released by operation of an actuator. The storage management device 11e is an aggregate of cabinets that store and store various documents, ledgers, files, articles, and the like. An electric lock is incorporated in the door of each cabinet, and the door is locked and unlocked by the operation of the actuator. In addition, the storage management device 11e may incorporate a key management device, a safe with improved 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 device 12 and the control device 13 are unitized and incorporated in the management device body.

  The authentication device 12 includes a contactless 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. It is a generic term for biometric authentication devices such as code readers, fixed, scrambled and display-type passwords, numeric keys, fingerprints, finger veins, palm veins, palm veins, face and iris. The non-contact type IC card reader, magnetic stripe type card reader and RFID card reader read the unique identification information of the card or ID tag possessed by the user as the personal authentication information. The QR code (registered trademark) reader and the bar code reader read a QR code (registered trademark) or a bar code displayed on a mobile phone or the like owned by the user as personal identification information. The password numeric keypad reads the password input by the user as personal identification information. The biometric authentication device reads an image pattern of a part of a user's body as personal authentication information.

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

  Next, a 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. The user information includes the user's name, ID number, affiliation, post, grade, length of service, personal authentication information, and conditions for releasing security of the security terminal device 11. In the case of card authentication or ID tag authentication, the personal authentication information is the unique identification information of the card or ID tag distributed to each user, in the case of PIN authentication, several digits set by each user, In the case of authentication, it is an image pattern of a part of the body of each user. The conditions related to the release of the security of the security terminal device 11 include whether or not the security of the security terminal device 11 can be released and the time period during which the security can be released (for example, from what day of the week to what time of day). Further, 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, “user information” indicates the above-mentioned user information of each user. Further, when it is referred to as “device information”, it indicates the device information of each control device 13 described above.

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

  The volatile memory 202 is used for temporary data storage such as a 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 nonvolatile memory 131, a volatile memory 132, a communication interface 133, and a control interface 134. A user information table 135 for holding user information is placed in the nonvolatile memory 131. The user information is acquired by the user information management unit 138 described later from the central management device 20 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 information under the control of the control device 13. It is limited to user information of users who may use the terminal device 11. In other words, the user information table 135 holds the user information of some but not all users transferred from the central management device 20.

  The microcomputer 130 reads and executes a computer program stored in the nonvolatile memory 131 to function as the personal authentication unit 136, the terminal device control unit 137, the user information management unit 138, and the event recording unit 139. The personal authentication unit 136 compares the personal authentication information read by the authentication device 12 with the personal authentication information included in the user information stored in the user information table 135 to release the security of the security terminal device 11. The user is authenticated. The terminal device control unit 137 opens and closes unillustrated electrical contacts in the control interface 134 according to the user information of the user stored in the user information table 135 when the user authentication is successful. 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 Each time the security of the security terminal device 11 is released, the event recording unit 139 records, in a predetermined storage area of the nonvolatile memory 131, an event indicating when and who released the security of the security terminal device 11. Further, the event recording unit 139 may record an event of security release failure when the user attempts 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 necessary, so that the administrator can confirm the event log.

  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 unillustrated electrical contacts that are opened and closed by the terminal device control unit 137, and the actuators and electric motors of the security terminal devices 11 are connected to the electrical contacts. In addition, power for driving an actuator or an electric motor is supplied to each security terminal device 11 from a power supply unit (not shown). For communication with each authentication device 12, for example, an LON conforming to the LONWORKS (registered trademark) specification can be used.

≪ operation ≫
Next, the characteristic security release processing and the user information deletion (update) processing in the security system 100 according to the present embodiment will be described with reference to flowcharts.

  FIG. 4 is a flowchart of the security release processing of the security terminal device 11. First, a user (hereinafter, referred to as a “target user”) tries to release the security of a certain security terminal device 11 (hereinafter, referred to as a target security terminal device 11), for example, to pass through a security gate, and possesses, for example. When the user holds the IC card over the authentication device 12, the authentication device 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 checks the unique information of the IC card read by the authentication device 12 against the personal authentication information included in the read user information (S102). As a method for reading the personal authentication information from the user information table 135, a search using an embedded database, a tree structure search, and the like can be performed. If they match (YES in S103), it means that the user authentication has succeeded, and next, the terminal device control unit 137 reads the user information of the noted user stored in the user information table 135. Then, it is determined whether the security of the target security terminal device 11 can be released (S104). As a result of the determination, if the security can 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, thereby closing the target security terminal. The security of the device 11 is released, for example, a security gate is opened (S106). Then, the event recording unit 139 records an event indicating when and who released the security of which security terminal device 11 (S107), and the security release processing ends. On the other hand, as a result of the determination, if the security should not be released (NO in S105), the terminal device control unit 137 does not close the electrical contacts in the control interface 134, that is, the security of the target security terminal device 11 Without releasing (S108), the security release ends in failure. In this case, the event recording unit 139 records an event indicating when and who failed to release security of which security terminal device 11 (S107), and the security release processing ends.

  In the security system 100 according to the present embodiment, the control device 13 (more specifically, the user information table 135) registers only as little user information as possible, preferably as little as possible. Therefore, for example, since the user information of the employee who travels to another site is not registered in the control device 13 of the another site, the employee can release the security of the security terminal device 11 at the another site. A problem arises that it is not possible. 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 at the different 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 this case, the user information management unit 138 requests the central management device 20 for the user information of the target user (S109). Upon receiving the request from the control device 13, the central management device 20 transfers the corresponding user information to the control device 13, or notifies the control device 13 that the user information of the noted user is not registered. Notify to If the user information can be obtained 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 compares the unique information of the IC card read by the authentication device 12 with the personal authentication information included in the added user information. Then, the user authentication of the noticed user is retried (S112). If they match (YES in S113), it means that the personal authentication has succeeded, and the process proceeds to the terminal device control unit 137 to determine whether or not the security can be released (S104). Thereafter, the security is released by the above-described procedure. . On the other hand, if the notice that the user information of the noted user is not registered is received from the central management device 20 (NO in S110), or if the terminal device control unit 137 determines that the security can be released, the security If the terminal should not be released (NO in S105), the terminal device control unit 137 does not close the electrical contacts in the control interface 134, that is, without releasing the security of the target security terminal device 11 (S108). , The security release fails. In this case, the event recording unit 139 records an event indicating when and who failed to release security of which security terminal device 11 (S107), and the security release processing ends.

  FIG. 5 is a flowchart of another example of the security release processing of the security terminal device 11. 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 noticed user and sets the authentication device 12 The personal authentication information read by the user of interest is transferred (S109). When the central management device 20 receives the request and the information from the control device 13, the database engine 207 refers to the user information master 205 and determines whether or not to authenticate the user of interest and release the security of the target security terminal device 11. Is performed, the user information transfer unit 209 transfers the user information of the noted user obtained by the database engine 207 searching the user information master 205 to the control device 13, and the user authentication and security by the database engine 207 are performed. Notify the result of the release possibility determination. Alternatively, the central management device 20 notifies the control device 13 that the user information of the noted user is not registered. If the user information can be obtained 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, in a case where the terminal device control unit 137 may release the security according to the result of the personal authentication of the noticed user and the determination whether the security of the target security terminal device 11 can be released received from the central management device 20 ( (YES in S105), the security of the target security terminal device 11 is released (S106). On the other hand, if the security should 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, the control device 13 requests the central management device 20 for the user information of an arbitrary user and transfers the personal authentication information to the central management device 20 so that the central management device 20 can perform personal authentication and security. 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 released efficiently.

  In the case where the security of the security terminal device 11 may be released at once if the personal authentication succeeds, only the personal authentication information may be transferred from the control device 13 to the central management device 20 as described above. In a 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 perform the security release determination, the control device 13 sends the security management device 20 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 that is the target of the security release permission determination is specified, and the central management device 20 refers to the user information master 205 and authenticates the target user and identifies the target security terminal device. 11 can be determined.

  Supplementary information about the transfer of the user information from the central management device 20 to the control device 13 will be added. In the user information master 205, which security terminal device 11 can be released with which security for each user and under what conditions are registered. However, for the security terminal device 11 at a base where the user is not involved, there are no conditions. May not be registered. In this case, there is no user information for the site, and there is a problem that the user information cannot be transferred in response to a request from the control device 13 at the site. In order to cope with such a problem, as described below, a mechanism for automatically adding a condition for releasing the security of the security terminal device 11 at an arbitrary site and updating the user information by introducing the central management device 20 is introduced. Is also good.

  FIG. 6 is a flowchart of the 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 the device information master 206 and The location where the control device 13 is located (hereinafter, referred to as “target location”) is specified (S21), and the user information master 205 is searched to acquire the user information of the target user (S22). Note that the execution order of S21 and S22 may be reversed. When the corresponding user information is acquired, the master management unit 208 checks whether or not a condition related to the security release of the security terminal device 11 at the point of interest is set in the user information. If it is not set (NO in S23), the master management unit 208 sets a condition for releasing the security of the security terminal device 11 at the target site according to the security authority of the target user included in the acquired user information. Is set (S24), and the user information of the noted user registered in the user information master 205 is updated (S25). The affiliation, post, grade, years of service, and the like can be used as the security authority. For example, an officer of manager level or higher can release security of all security terminal devices 11 at a noted base, and a general employee can set such that only some security terminal devices 11 can release security. When the user information is updated, the database engine 207 specifies another control device 13 at the point of interest (S26), and the user information transfer unit 208 transmits the request source control device 13 and the other specified 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 specifies another control device 13 at the point of interest (S26), and the user information transfer unit 208 sends the request to the control device 13 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 sort the user information temporarily added to the control device 13 according to the above procedure. Therefore, the security system 100 according to the present embodiment introduces a mechanism for deleting the temporarily added user information 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 expired user information. Is deleted from the user information table 135. The setting of the expiration date may be performed by the central management device 20, or may be performed by the user information management unit 138.

  In addition, the 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 users who have passed a predetermined period from the last use date and time (S32). Note that the last use date and time refers to the latest date and time when the user has released 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 ascending 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 whose affiliation is the base, an officer, an employee receiving a special order, or the like. The determination as to whether or not the user is a special user can be made 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 The central management device 20 is notified 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 is no user to be picked up in S33 (S37).

  Regardless of whether or not a predetermined period has elapsed since the last use date and time, when the remaining memory capacity allocated to the user information table 135 becomes equal to or less than a predetermined value, the user gives priority to the remaining memory capacity as follows. It is desirable to delete information. FIG. 8 is a flowchart of the user information deletion process in the control device 13 in the case where priority is given to the remaining memory capacity. 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 users one by one in the order of the extracted last use date and time, and It is determined 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 The central management device 20 is notified 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 in the user information table 135 is secured (S46).

  Next, an operation of the central management device 20 when the deletion of the user information of an arbitrary user is notified from the control device 13 will be described. FIG. 9 is a flowchart of the 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 control device 13 that the user information of an arbitrary user (hereinafter, referred to as “attention user”) has been deleted, the database engine 207 transmits the device information master. 206 is searched to identify a base where the control device 13 is located (hereinafter, referred to as a “target base”) (S51), and the user information master 205 is searched to obtain user information of the target user (S51). S52). Note that the execution order of S51 and S52 may be reversed. When the corresponding user information is obtained, the database engine 207 further searches the device information master 206 and specifies all the security terminal devices 11 at the point of interest (S53). The execution order of S52 and S53 may be reversed. When all the security terminal devices 11 at the point of interest are specified, the master management unit 208 deletes the condition related to the security release of all the specified security terminal devices 11 from the acquired user information (S54). Then, the user information of the user information master 205 is updated (S55). As a result, the condition relating to the security release of all the security terminal devices 11 at the point of interest is deleted from the user information of the target user managed by the central management device 20, and the user information of the target 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 user information to be stored in the control device 13 at each site. As a result, the memory capacity for storing user information in the control device 13 can be reduced, and the memory capacity does not need to be increased even if the number of system users increases. In addition, since the user information to be stored in the control device 13 is reduced, the user can be quickly authenticated, and a smooth security release can be realized.

  Furthermore, even if the user does not make an advance application when visiting another base on a business trip or the like, or suddenly visits another base due to a schedule change, the smooth release of security of each security terminal device 11 at the base can be performed. It becomes possible. As a result, troublesome prior application is released, and convenience is improved. In addition, in the case that the application was made in advance but did not actually visit, or the schedule was changed but the application was not canceled, the user information will be registered unnecessarily at the site where the visit is scheduled There is no. As a result, user information to be stored in the control device 13 can be suppressed, and unnecessary user information registration can be eliminated to further strengthen security.

≪Application and deformation≫
A user who is known to use the security terminal device 11 under the control of the control device 13, for example, a user whose affiliation is at the base where the control device 13 is located, or an officer User information such as a certain number of officials such as directors and directors may be registered in the user information table 135 in advance. More specifically, the user information is arranged for each site, the user information is transferred from the central management device 20 to the control device 13 of each site, and the user information is stored in the user information table 135 in advance, or , User information is organized according to the types of security terminal devices 11 such as security gates, key management devices, and storage management devices, and the user information is transferred from the central management device 20 to the control device 13 that controls the 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 arranged for each site and for each type of the security terminal device 11, and the user information is transferred from the central management device 20 to the control device 13 which controls each security terminal device 11 at each site, and the user information is stored in advance. The table 135 may hold user information. As described above, for a user who is known to use the security terminal device 11 under the control of the control device 13, the user information is registered in the user information table 135 in advance, so that the control device 13 It is possible to quickly perform personal authentication and release security by omitting the inquiry to the central management device 20.

  In addition, priorities are set for the user information held in the user information table 135, and the user authentication unit 136 refers to the user information with the highest priority first when performing personal authentication. Is also good. For example, of the user information stored in the user information table 135, the user information of the user whose affiliation is located at the base where the control device 13 is arranged, and the officer or director regardless of the affiliation. User information of a certain level of officials, user information for users whose predetermined period has not yet elapsed since the last use date, etc., is managed as active information, and other user information is managed as inactive information. At the time of personal authentication by the authentication unit 136, the active information may be referred to first. Thus, the user who frequently uses the security terminal device 11 under the control of the control device 13 can quickly perform the personal authentication.

  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 release stored in the nonvolatile memory 131 is not stored in the user information table 135. 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 using the event history without changing the specifications of the existing user information table 135.

  Although the above security system 100 is based on the existence of the central management device 20, in the case of a small-scale system, it is possible to independently manage user information by the control device 13 at each site without the central management device 20. is there. In such a configuration, user information that is not held by the control device 13 at a certain site can be requested and acquired from the control device 13 at another site.

  As described above, the embodiments have been described as examples of the technology according to the present invention. For that purpose, the accompanying drawings and the detailed description have been provided.

  Therefore, among the components described in the accompanying drawings and the detailed description, not only components that are essential for solving the problem, but also components that are not essential for solving the problem, in order to illustrate the above technology. May also be included. Therefore, it should not be immediately recognized that these non-essential components are essential based on the fact that the non-essential components are described in the accompanying drawings and the detailed description.

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

  Reference Signs List 100 security system, 11 security terminal device, 12 authentication device, 13 control device, 14 LAN, 15 gateway, 135 user information table, 136 personal authentication unit, 137 terminal device control unit, 138 ... user information management unit, 139 ... event recording unit, 20 ... central management device, 205 ... user information master, 207 ... database engine, 208 ... master management unit, 209 ... user information transfer unit, 30 ... electric communication line

Claims (9)

One or more security terminal devices located at each base and reading one or more security terminal devices and personal authentication information of a user who is provided corresponding to each of the security terminal devices and intends to release the security of the corresponding security terminal devices. A control system to which the authentication machine is connected, and a central management device, a security system configured by being connected by a telecommunication line,
The central management device,
A user information master in which user information of each user is registered, including user authentication information and conditions relating to security release of the security terminal device;
A database engine for performing data search of the user information master;
A master management unit that performs addition, update and deletion of the user information with respect to the user information master;
A user information transfer unit that transfers the user information of any user obtained by searching the user information master by the database engine to the control device,
The control device includes:
A user information table that holds the user information of some but not all users transferred from the central management device;
By comparing the personal authentication information read by the authentication device with the personal authentication information included in the user information held in the user information table, the user who wants to release the security of the security terminal device is checked. An identity authentication unit that performs identity authentication;
A 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 when the user authentication is successful;
When the user information table does not have the user information and the authentication of the user fails, the central management device requests the user information of the user from the central management device. A user information management unit for adding the transferred user information to the user information table.   When the user information is added to the user information table, the user authentication unit collates the user authentication information read by the authentication device with the user authentication information included in the added user information. The security system according to claim 1, wherein the security system is configured to retry authentication of a user. When the user information management unit does not have the user information in the user information table and authentication of the user fails, the user information management unit requests the user information of the user from the central management device, and Configured to forward the user's identity information read by the authenticator,
The database engine receives personal authentication information of any user from the control device, refers to the user information master, performs personal authentication of the user, and releases security of the security terminal device by the user. It is configured to perform availability determination,
The user information transfer unit transfers the user information of any user obtained by the database engine searching and acquiring the user information master to the control device, and performs identity authentication and security release by the database engine. Is configured to notify the result of the determination of
2. The security system according to claim 1, wherein the terminal device control unit is configured to control an operation of the security terminal device according to a result of the personal authentication and the determination whether or not to release security received from the central management device. .   When the user information transfer unit receives a request for the user information of an arbitrary user from the control device, the user information transfer unit also transmits the user information to another control device at a base where the control device is located. 4. The security system according to claim 1, wherein the security system is configured to transfer the user information. The condition relating to the security release of the security terminal device included in the user information is 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 located, according to the security authority of the user. It is configured to set a condition relating 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 claim 1, wherein the user information transfer unit is configured to transfer the updated user information to the control device.   The user information management unit according to claim 1, wherein 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. The security system described. An 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 6, 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 a plurality of security terminals can be connected to one or more security terminal devices and one or more authentication devices that are provided corresponding to each of the security terminal devices and read personal authentication information of a user who intends to release security of the corresponding security terminal device. Control device,
A user information table holding user information of each user, including personal authentication information and a condition relating to security release of the security terminal device;
The personal authentication information read by the authentication device is compared with the personal authentication information included in the user information held in the user information table, and the user who wants to release the security of the security terminal device is checked. An identity authentication unit that performs identity authentication;
A 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 when the user authentication is successful;
When the user information table does not have the user information and the user authentication fails, the external device holding the user information is requested for the user information of the user. A control device, comprising: a user information management unit that adds the user information transferred from the external device to the user information table. One or more security terminal devices located at each base and reading one or more security terminal devices and personal authentication information of a user who is provided corresponding to each of the security terminal devices and intends to release the security of the corresponding security terminal devices. A central management device that can be connected by a telecommunication line to a control device to which the authentication machine is connected,
A user information master in which user information of each user is registered, including user authentication information and conditions relating to security release of the security terminal device;
A database engine for performing data search of the user information master;
A master management unit for adding, updating, and deleting the user information with respect to the user information master;
A user information transfer unit that transfers the user information of any user obtained by searching the user information master by the database engine 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 information transfer unit also transmits the user information to another control device at a base where the control device is located. A central management device configured to transfer the user information.

Images