JP2010144483A - Entry control system - Google Patents

Abstract

An object of the present invention is to provide an admission management system capable of shortening the time from the server that manages verification information to the completion of storage of the verification information in all reader devices.
A center server having a single processor is executed by switching each thread TH1 to TH3 for transmitting verification information to a different entrance management device for each thread, and the thread TH1 in the execution state is used for verification. When the transmission of information (step S20) is completed, the thread TH1 transitions to the standby state until the completion notification that the fingerprint reader 300A has completed storing the verification information is received from the admission management device 200A (steps S21 to S23). Let The center server 100 executes the threads TH2 and TH3 in the same manner as the thread TH1 instead of the thread TH1 that has been changed to the standby state.
[Selection] Figure 8

Description

  The present invention relates to an entrance management system, and more particularly, to a technique for transmitting information for verification to a reader device that reads information on a visitor and compares the information with verification information stored in advance.

  A plurality of reader devices that are installed in a plurality of management target areas such as a building entrance and each room, read information on a person who intends to enter (for example, information on an IC card or biometric information such as a fingerprint), and identify the person An admission management system including a plurality of admission management devices that perform authentication related to admission of a person specified by a reader device associated in advance is known (for example, Patent Document 1).

In such an entrance management system, in order to identify the person who intends to enter each reader device, information on each prospective person (hereinafter referred to as “verification information”, for example, information on the IC card of the prospective person or It is necessary to store in advance in each reader device.
If the administrator of the entrance management system individually performs the work of storing the verification information for each reader device, the work burden on the administrator will be excessive, so the verification information will be A method is conceivable in which a server to be managed is provided, and verification information is transmitted from the server to each reader device and stored.

Specifically, for example, the server transmits the verification information to the reader device associated with the admission management device via one admission management device, and after the storage in the reader device is completed, When the notification is received, a method of sequentially transmitting and storing the verification information, such as starting transmission of verification information to the next reader device via the next admission management device, can be considered. This method is very simple and can easily and reliably store the verification information in each reader device.
JP 2005-107588 A

However, when the size of the verification information is large (such as when the number of prospective visitors is particularly large, or when the verification information is biometric information of each prospective visitor), one reader device can store the verification information. It takes longer to complete the memory.
Therefore, particularly when this method is used in a large-scale admission management system including a large number of reader devices, it takes an excessive amount of time to complete the storage of verification information in all reader devices. There's a problem. As a result, for example, when a new admission management system is introduced, it takes time until admission management of all the management target areas can be started.

In recent years, due to increasing security awareness, each company has come to manage the entrance to more rooms than before, and this problem is because the entrance management system tends to become larger. It is desirable to solve this problem.
Therefore, the present invention has been made in view of such problems, and an admission management system capable of shortening the time from the server that manages the verification information to the completion of the storage of the verification information in all the reader devices. The purpose is to provide.

  In order to solve the above-mentioned problems, an admission management system according to the present invention reads a visitor's information, compares it with stored verification information, identifies a visitor, and each reader device identifies An entrance management system including a plurality of management devices that perform authentication of the visitors and lock and unlock the door, and a server for transmitting verification information to each reader device via each management device, The management apparatus transfers and stores the verification information received by the reception means to the reader device for one or more reader devices associated in advance with the reception means for receiving the verification information from the server, Transfer control means for transmitting a completion notification to the server when storage of the reader device is completed, and the server transmits verification information to a different management device for each thread, and completes corresponding to the transmission A plurality of threads that perform processing according to knowledge are executed in parallel, and after the execution state thread transmits the verification information, the thread is shifted to a waiting state until a completion notification corresponding to the transmission is received. It is characterized by comprising an execution control means for controlling the above.

  Here, executing a plurality of threads in parallel is so-called multi-thread processing, and here, it is so-called pseudo-parallel processing executed by switching a plurality of threads by one processor. In general, multi-thread processing performs control such that each thread transits at least an execution state (RUN), a standby state (WAIT), and an executable state (READY).

The collation information is information for identifying an individual, for example, medium identification information recorded on a medium such as a magnetic card or an IC card, or biological information such as a fingerprint, a voiceprint, an iris, or a vein.
In addition, the door is a door that allows only persons specified by the predetermined identification information and prohibits other persons from passing, and can be in any form such as a swing door, sliding door, bar, gate, etc. It may be realized.

  In the admission management system according to the present invention having the above-described configuration, when the thread in the execution state transmits the verification information to a certain management apparatus, the server waits until the completion notification corresponding to the transmission is received. Therefore, without waiting for the completion of storage of the verification information in the reader device associated with the management device, the other thread is shifted to the execution state and the verification information is transmitted to the other management device. Can start.

Therefore, after the completion of the storage of the verification information in the reader device associated with a certain management device, the verification information in all the reader devices is compared with the case where the verification information is transmitted to the next management device. The time until the storage is completed can be shortened.
In addition, the total number of threads executed by the execution control unit is less than the total number of management devices, and whether the server has transmitted one different number to each management device and verification information to the management device. Transmission status storage means for storing transmission status information associated with information indicating whether or not, each thread transmits verification information with reference to the transmission status information when execution of the thread is started The verification information may be transmitted to the management device associated with the smallest number among the management devices that have not been used.

  Thereby, when the execution is started, each thread transmits the verification information to another management apparatus associated with the minimum management number for which the verification information has not yet been transmitted. In other words, the transmission target of the verification information in each thread is not determined in advance, and the transmission target can be determined according to the transmission status of the verification information. Even when it takes a relatively long time to complete the storage of the verification information in the corresponding reader device, it is affected by this thread until the storage of the verification information is completed in all the reader devices. It is possible to prevent the time from being extended unnecessarily.

  The total number of threads executed by the execution control means is less than the total number of management devices, and the server associates each management device with a different number so that each number is continuous, and the management device Transmission status storage means for storing transmission status information associated with information indicating whether or not the verification information has been transmitted to each thread, and when each thread starts execution of the thread, the transmission status information The management information that is determined according to the remainder obtained by dividing the associated number by the total number of threads and the value preset for the own thread among the management devices that do not transmit the verification information with reference to May be transmitted.

  As a result, serial numbers are associated with each management apparatus, and each thread has a remainder obtained by dividing the associated number by the total number of threads among the management apparatuses that have not yet transmitted verification information. Since the verification information is transmitted to the management device that matches the value set in advance for the own thread, the number of verification information transmission targets (management devices) in each thread can be equalized. That is, it is possible to appropriately prevent the effect of executing a plurality of threads in parallel due to the concentration of processing in one thread.

In addition, the server includes a management device information storage unit that stores management device information for specifying a management device in operation among the management devices, and each thread is started when execution of the thread is started. Referring to the management device information, the verification information may be transmitted only to the operating management device.
Thereby, when the execution is started, each thread transmits the verification information only to the operating management device based on the management device information for specifying the operating management device. Therefore, for example, it is possible to reduce the possibility of sending verification information to a management device that cannot communicate, such as a management device that is not turned on, and sending verification information to such a management device is effective. It is possible to prevent the time until the storage of the verification information is completed in the reader device from being unnecessarily extended.

The server may further include an update unit that updates the management device information as a management device operating when the data is received from the management device.
Accordingly, when the server receives the data, the server updates the management apparatus information with the transmission source management apparatus as the active management apparatus. Therefore, each thread is operating based on the management device information when the execution is started without having the server or the like store information related to the management device in operation beforehand. The verification information can be transmitted only to the management device. Therefore, for example, it is possible to reduce the possibility of sending verification information to a management device that cannot communicate, such as a management device that is not turned on, and sending verification information to such a management device is effective. It is possible to prevent the time until the storage of the verification information is completed in the reader device from being unnecessarily extended.

  Each management device further includes response means for transmitting a response signal when receiving a request signal from the server, and the server further transmits a request signal to each management device and receives a response signal for the request signal. The update unit may include a communication unit, and for each management device, when receiving a response signal to the request signal transmitted to the management device, the management unit may update the management device information as a management device operating. Good.

  As a result, when the server receives a response signal to the transmitted request signal, the server updates the management device information as a management device that is operating the transmission source management device, and each thread is started when execution is started. Based on the management apparatus information, the verification information is transmitted only to the operating management apparatus. Therefore, even when there is no data to be transmitted to each server by each management device, the server transmits a request signal and transmits a response signal to each management device, so that the management device in operation can be grasped more accurately. For example, it is possible to further reduce the possibility of sending verification information to a management device that is unable to communicate, such as a management device that is not turned on or a management device that is out of order, and sending verification information to such a management device As a result, it is possible to prevent the time until the storage of the verification information is completed in an effective reader device from being unnecessarily extended.

  The verification information includes information about each visitor, and the verification information includes two types of information, medium information for identifying the visitor and biometric information of the visitor, The server further includes, for each management device, a type storage unit that stores information indicating a type of verification information used for verification by a reader device corresponding to the management device, and each thread is stored in the type storage unit Based on the information, the verification information may be transmitted to a management device associated with a reader device that performs verification using one type of verification information preset in the own thread.

  Thereby, the thread | sled which transmits the information for collation which consists of each medium information for identifying a visitor, and the thread | sled which transmits the information for collation which consists of each biometric information of a visitor can be performed in parallel. Therefore, for example, when the transmission target (management device) of verification information by each thread is determined so as to equalize the processing load of each thread regardless of the type of verification information, the transmission order is the latter half. Even in the management apparatus, when the reader device associated with the management apparatus performs collation using the collation information including each medium information, transmission of the collation information to the management apparatus may be given priority. is there.

The medium information for identifying the visitor and the biometric information of the visitor generally has a larger data size than the biometric information of the visitor. The device can store the media information for identifying the visitor in a shorter time.
The reader apparatus can be used by prioritizing the transmission of the collation information to the management apparatus associated with the reader apparatus that performs collation using the collation information composed of each medium information that can be stored in a short time. This can contribute to the improvement of convenience for visitors.

Hereinafter, as an embodiment of an admission management system according to the present invention, an admission management system for managing admission to a plurality of rooms will be described as an example with reference to the drawings.
<< Embodiment 1 >>
<Overview>
The admission management system according to the first embodiment is a conventional admission management system that performs authentication using the fingerprint of a person who intends to enter (hereinafter simply referred to as “entrance”). This is an improvement to shorten the time until storage of information (information for identifying visitors, including fingerprint data of each prospective visitor) is completed.

This admission management system is composed of a center server having one processor in addition to the plurality of fingerprint readers described above and a plurality of admission management devices. The center server and each admission management device are connected to each other, and each admission management device Are connected to one different fingerprint reader.
In order to store the verification information in each fingerprint reader, the center server transmits the verification information managed by the server to each fingerprint reader via each entrance management device. The fingerprint reader that has received the verification information writes it in the flash memory in its own reader, and when the writing is completed, sends a completion notification to the center server via the connected admission management device.

Here, writing of data to the flash memory is generally slow, and when the size of the entire verification information (for example, about 1000 bytes per case) is large, the writing time in each fingerprint reader becomes long.
Therefore, in a large-scale admission management system including a larger number of admission management devices and fingerprint readers, if the center server processes sequentially, that is, the connection destination of the connection destination via one admission management device. Send verification information to the fingerprint reader, wait for receipt of the completion notification from the fingerprint reader, and then send the verification information to the connected fingerprint reader via the next admission management device. If this processing is performed, it takes an excessive amount of time to complete the storage of the verification information in all the fingerprint readers.

Therefore, the center server (provided with one processor) in this admission management system executes by switching a plurality of threads for transmitting verification information to different admission management devices for each thread (so-called pseudo-parallel processing). The verification information is transmitted to each entrance management device.
By doing in this way, compared with the case where it processes sequentially as mentioned above, time until storage of the information for collation to all the fingerprint readers can be shortened.

<Configuration>
First, the configuration of the admission management system 1000 according to the present embodiment will be described.
<Admission management system>
FIG. 1 is a system configuration diagram of the admission management system 1000.
As shown in the figure, the admission management system 1000 includes a center server 100, admission management devices 200A to 200F, and fingerprint readers 300A to 300F installed in the vicinity of doors for admission to each area for managing admission. It consists of and.

The center server 100 and each entrance management device are connected via a LAN (Local Area Network) 1, and each entrance management device and each fingerprint reader are connected via cables 2A to 2F, respectively.
Here, the center server 100 is a PC (Personal Computer) or the like having one processor, and has a function of managing verification information and transmitting the verification information to each entrance management device. The transmission of the verification information to each entrance management device is realized by executing (pseudo parallel processing) while switching a plurality of threads that transmit the verification information to different entrance management devices for each thread. A method for determining to which admission management device each thread transmits the verification information will be described later.

  Each of the entrance management devices (200A to 200F) receives information (hereinafter referred to as “employee ID”) indicating a visitor received from the connected fingerprint reader and an authentication information table 80 (FIG. 4D). ) See)) and the function for controlling the locking / unlocking of the door on which the connected fingerprint reader is installed according to the authentication result, as well as the verification information received from the center server 100 Is transferred to the fingerprint reader of the connection destination, and the completion notification received from the fingerprint reader of the connection destination is transferred to the center server 100 together with the identification information of the own device (hereinafter referred to as “management device ID”) stored in advance. Have

  Each of the fingerprint readers (300A to 300F) has a function of registering the verification information received from the connected admission management device in the verification information table 10 (see FIG. 4 (a)), and a function for registering each area for managing the entrance. It has a function of reading an image of a visitor's fingerprint, specifying the employee's employee ID using the stored collation information table 10, and transmitting it to the connected admission management device. When the registration of the verification information is completed, each fingerprint reader transmits a completion notification to the connected admission management device.

In FIG. 1, six admission management devices (200A to 200F) and six fingerprint readers (300A to 300F) are illustrated. This is a part of the configuration of the admission management system 1000. The numbers of the entrance management device and the fingerprint reader are not limited to the example shown in FIG.
Hereinafter, the configuration of the center server 100, each entrance management device, and each fingerprint reader will be described in more detail. However, the configuration of each entrance management device is the same, and the configuration of each fingerprint reader is the same. The admission management device 200A and the fingerprint reader 300A will be described as an example.

<Center server>
A functional configuration of the center server 100 will be described.
FIG. 2 is a block diagram illustrating a functional configuration of a main part of the center server 100.
The center server 100 includes a memory and a processor. As shown in the figure, the center server 100 includes an input unit 101, a user interface unit 102, a verification information storage unit 103, a configuration information storage unit 104, a history information storage unit 105, a communication. An interface unit 106 and an execution control unit 107 are provided. Note that the function of the execution control unit 107 is realized by the above-described processor executing a program stored in the above-described memory.

Here, the input unit 101 is an input device such as a keyboard, and has a function of transmitting an input signal corresponding to a key pressed by the user to the user interface unit 102. In particular, an administrator of the entrance management system 1000 or the like (Hereinafter simply referred to as “administrator” or the like) is used when instructing to transmit verification information to each entrance management device.
The user interface unit 102 has a function of displaying characters, images, and the like on a display (not shown) according to the content of the user operation transmitted from the input unit 101 and transmitting the content of the user operation to the execution control unit 107. Have.

The collation information storage unit 103 is a collation information table 10 that associates employee IDs and fingerprint data of persons who plan to enter each area (for example, employees who work in the area) (see FIG. 4A). Is a memory area for storing. The contents of the verification information table 10 will be described in detail later.
The configuration information storage unit 104 is a memory area for storing a configuration information table 30 (see FIG. 4B) that is a list of each entrance management device and each fingerprint reader included in the entrance management system 1000. The contents of the configuration information table 30 will be described in detail later.

The history information storage unit 105 is a memory area for storing a history information table 70 (see FIG. 4C) in which history information indicating the result of authentication by each entrance management device is registered. The contents of the history information table 70 will be described in detail later.
The communication interface unit 106 has a function of transmitting / receiving data to / from each entrance management apparatus via the LAN 1. Specifically, in response to an instruction from the execution control unit 107, the verification information is transmitted to each entrance management device, and the history information transmitted from each entrance management device is registered in the history information table 70 of the history information storage unit 105. To do.

The execution control unit 107 receives the collation information (the contents of the collation information table 10 stored in the collation information storage unit 103) in response to the collation information transmission instruction received via the user interface unit 102. It has the function to transmit to each entrance management apparatus via the communication interface part 106.
More specifically, a plurality of threads that transmit the verification information to different admission management devices for each thread are generated, and executed (pseudo parallel processing) while switching the threads to which one processor is assigned. That is, the execution control unit 107 functions as a so-called multi-thread OS (Operating System).

The verification information is actually transmitted by dividing the content of the verification information table 10 into packets. Further, in the present embodiment, a case will be described as an example in which each thread determines to which entry management device each thread transmits the verification information. The processing contents of each thread including this determination method will be described in detail later (see FIG. 7).
<Admission management device>
FIG. 3 is a block diagram showing a functional configuration of main parts of the entrance management device 200A and the fingerprint reader 300A.

First, the functional configuration of the entrance management apparatus 200A will be described.
The admission management device 200A includes a memory and a processor, and includes a communication control unit 201, an authentication information storage unit 202, a timekeeping unit 203, a key control unit 204, and an authentication unit 205 in terms of functions. Each function of the communication control unit 201, the key control unit 204, and the authentication unit 205 is realized by the above-described processor executing a program stored in the above-described memory.

  Here, the communication control unit 201 includes a communication interface corresponding to each of the LAN 1 and the cable 2A, transmits / receives data to / from the center server 100 via the LAN 1, and transmits / receives data to / from the fingerprint reader 300A via the cable 2A. It has a function to send and receive. Specifically, the verification information received from the center server 100 is transferred to the fingerprint reader 300A, and the employee ID received from the fingerprint reader 300A and the information indicating the fingerprint reader 300A (hereinafter referred to as “reader ID”) are authenticated. The completion notification received from the fingerprint reader 300 </ b> A is transferred to the center server 100 together with the management apparatus ID of the own apparatus, and the history information transmitted from the authentication unit 205 is transmitted to the center server 100.

The authentication information storage unit 202 is a memory for storing an authentication information table 80 (see FIG. 4D) in which employee IDs of prospective visitors to each area are associated with areas permitted to enter. It is an area. The contents of the authentication information table 80 will be described in detail later.
The timer unit 203 is a so-called clock and has a function of measuring the current date and time.
The key control unit 204 has a function of controlling an electronic lock that locks and unlocks the door on which the fingerprint reader 300 </ b> A is installed in accordance with an instruction from the authentication unit 205.

  Based on the employee ID and reader ID transmitted from the communication control unit 201 and the authentication information table 80 stored in the authentication information storage unit 202, the authentication unit 205 opens the door where the fingerprint reader 300A is installed. It has a function of determining (authenticating) whether or not to unlock, and transmitting history information (including authentication date / time, employee ID, reader ID, and authentication result) to the center server 100 via the communication control unit 201. In addition, the authentication unit 205 has a function of instructing the key control unit 204 to unlock the electronic key when it is determined to unlock.

<Fingerprint reader>
Next, the functional configuration of the fingerprint reader 300A will be described with reference to FIG.
The fingerprint reader 300A includes a memory and a processor, and includes a communication interface unit 301, a verification information storage unit 302, an update unit 303, a reading unit 304, and a verification unit 305 in terms of functions. Each function of the update unit 303 and the collation unit 305 is realized by the above-described processor executing a program stored in the above-described memory.

  Here, the communication interface unit 301 has a function of transmitting / receiving data to / from the entrance management apparatus 200A via the cable 2A. Specifically, the verification information received from the admission management device 200A is transmitted to the update unit 303, and a completion notification transmitted from the update unit 303 to the effect that storage of the verification information has been completed is transmitted to the admission management device 200A. . In addition, the employee ID and reader ID transmitted from the verification unit 305 are transmitted to the entrance management apparatus 200A.

The verification information storage unit 302 is a flash memory and has a function of storing the verification information table 10.
The update unit 303 registers the verification information transmitted from the communication interface unit 301 in the verification information table 10 of the verification information storage unit 302. When the registration is completed, the update unit 303 enters the entrance management device 200A via the communication interface unit 301. It has a function of transmitting completion information.

The reading unit 304 has a function of reading a fingerprint image of a visitor who intends to enter the corresponding area from the door where the reader is installed, and transmitting the fingerprint data to the verification unit 305.
The collation unit 305 collates the fingerprint data transmitted from the reading unit 304 with the collation information table 10 stored in the collation information storage unit 302 to identify the employee ID of the visitor, and identifies the identified employee ID In addition, the reader ID stored in advance is transmitted to the entrance management device 200A via the communication interface unit 301.

If fingerprint data that matches the transmitted fingerprint data is not registered in the verification information table 10 as a result of verification between the fingerprint data transmitted from the reading unit 304 and the verification information table 10, that fact is indicated. Is notified to the visitors by a buzzer or LED (not shown).
<Data>
Next, data used in the admission management system 1000 will be described.

<Information table for verification>
The verification information table 10 stored in the verification information storage unit 103 of the center server 100 and the verification information storage unit 302 of the fingerprint reader 300A will be described.
FIG. 4A is a diagram illustrating a data configuration and a content example of the verification information table 10.
As shown in the figure, the collation information table 10 stores an employee ID 11 and fingerprint data 12 in association with each person scheduled to enter each area, and is read by the fingerprint reader 300A from the visitors. This is referred to when the employee ID of this person is specified in comparison with the fingerprint image.

Here, the employee ID 11 is an identification number for identifying the corresponding prospective visitor, and is a number that does not overlap with other prospective visitors. The fingerprint data 12 is image data of a fingerprint of a corresponding prospective visitor.
This figure shows that, for example, the fingerprint data 12 of the prospective visitor whose employee ID 11 is “1000001” is “fingerprint data 1”.

  The registration and update of new data in the collation information table 10 stored in the collation information storage unit 103 of the center server 100 is performed by an area read from a fingerprint reader (not shown) connected to the center server 100. This is performed based on an operation for registration or update including image data of a fingerprint of a person who is scheduled to enter and an employee ID of the person from the input unit 101 by an administrator or the like. In addition, deletion of data registered in the verification information table 10 stored in the verification information storage unit 103 is performed based on an operation for deletion from the input unit 101 by an administrator or the like.

In addition, changes (registration, update, deletion) to the collation information table 10 stored in the collation information storage unit 103 are performed on the basis of a collation information transmission instruction from the input unit 101 by an administrator or the like. This is reflected in the verification information table 10 stored in the verification information storage unit 302 of the fingerprint reader.
Using this collation information table 10, the collation unit 305 of each fingerprint reader processes as follows. That is, when a record including fingerprint image data that matches the fingerprint image data transmitted from the reading unit 304 is registered in the verification information table 10, the verification unit 305 includes an employee ID included in the record. And the reader ID of the own reader are transmitted to the entrance management apparatus connected via the communication interface unit 301.

<Configuration information table>
The configuration information table 30 stored in the configuration information storage unit 104 of the center server 100 will be described.
FIG. 4B is a diagram illustrating a data configuration and a content example of the configuration information table 30.
As shown in the figure, the configuration information table 30 stores a management device ID 31, a reader ID 32, and a transmission flag 33 in association with each admission management device, and the execution control unit 107 stores verification information. It is referred to when transmitting to each entrance management device.

Here, the management device ID 31 is an identification number for identifying each entrance management device, and is a number that does not overlap with other entrance management devices. In this example, different numbers are assigned to the admission management devices 200A to 200F so that each number is a serial number from 1.
The reader ID 32 is an identification number of a fingerprint reader connected to the corresponding entrance management device, and is a number that does not overlap with other fingerprint readers. In this example, different numbers are assigned to the fingerprint readers 300 </ b> A to 300 </ b> F so that each number is a serial number from 101.

The transmission flag 33 is information indicating the transmission status of the verification information to the corresponding admission management device. In this example, “0” is not transmitted, “1” is being transmitted, and “2” is transmitted.
In the figure, for example, a fingerprint reader (fingerprint reader 300A) whose reader ID 32 is “101” is connected to an entrance management device (admission management device 200A) whose management device ID 31 is “1”, and a transmission flag 33 indicates “2”, that is, transmission of the verification information to the entrance management apparatus 200A is completed.

For example, a fingerprint reader (fingerprint reader 300B) whose reader ID 32 is “102” is connected to an entrance management device (admission management device 200B) whose management device ID 31 is “2”, and the transmission flag 33 is “1”, that is, indicating that the verification information is being transmitted to the admission management device 200B.
For example, a fingerprint reader (fingerprint reader 300C) with a reader ID 32 of “103” is connected to an entrance management device (admission management device 200C) with a management device ID 31 of “3”, and the transmission flag 33 is “0”, that is, the verification information is not yet transmitted to the entrance management device 200C.

Note that registration, update, and deletion of registered data in the configuration information table 30 are performed based on operations from the input unit 101 of the center server 100 by an administrator or the like.
<History information table>
The history information table 70 stored in the history information storage unit 105 of the center server 100 will be described.

FIG. 4C is a diagram showing a data configuration and example contents of the history information table 70.
The history information table 70 is a table in which the authentication history received from each admission management device is registered. As shown in the figure, for each admission authentication, the date / time 71, employee ID 72, reader ID 73, and result 74 are associated. I remember it.
Here, the date and time 71 is the date and time when authentication is performed, and the employee ID 72 is the identification number of the person who is the subject of the authentication.

The reader ID 73 is an identification number of a fingerprint reader installed on a door of an area to be authenticated as to whether or not to permit entry, and matches the reader ID 32 in any one of the configuration information table 30.
The result 74 is information indicating an authentication result indicating whether or not admission is permitted. In this example, “1” is set when admission is permitted, and “0” is set when admission is not permitted.

In the figure, for example, the employee ID 72 of the person who is the subject of authentication whose date and time 71 is “2008/12/1 8:25” is “1000002”, the reader ID 73 is “103”, and the result 74 is “1” is shown. That is, this person indicates that entry into the area corresponding to the door where the fingerprint reader 300C is installed is permitted.
The generation of the history information table 70 and the deletion of registered data are performed based on an operation from the input unit 101 of the center server 100 by an administrator or the like, and the registration of new data in the history information table 70 is as follows. This is performed when history information is received from each entrance management device.

<Authentication information table>
The authentication information table 80 stored in the authentication information storage unit 202 of the entrance management apparatus 200A will be described.
FIG. 4D is a diagram showing a data configuration and example contents of the authentication information table 80.
As shown in the figure, the authentication information table 80 stores an employee ID 81 and a reader ID 82 in association with each person scheduled to enter each area, and is referred to when the authentication unit 205 performs authentication. The

  Here, the employee ID 81 is identification information for identifying a corresponding prospective visitor, and matches one of the employee IDs in the verification information table 10. The reader ID 82 is an identification number indicating a fingerprint reader installed at a door of an area where entry by the corresponding prospective visitor is permitted, and corresponds to any one of the reader IDs in the configuration information table 30. .

In the figure, for example, a person whose employee ID 81 is “1000001” is permitted to enter the area corresponding to the door where the fingerprint readers (300A and 300B) whose reader IDs 82 are “101” and “102” are installed. It shows that.
Using this authentication information table 80, the authentication unit 205 of each entrance management apparatus performs authentication as follows. In other words, when a record including the employee ID and the reader ID transmitted from the communication control unit 201 is registered in the authentication information table 80, the authentication unit 205 has a fingerprint reader indicated by the reader ID installed. It is determined that the door is unlocked. If the corresponding record is not registered, it is determined that the door is not unlocked.

Note that the generation of the authentication information table 80, the registration and update of new data in the authentication information table 80, and the deletion of the registered data are performed by the administrator or the like from the keyboard or the like (not shown) of each entrance management device. Performed based on the operation.
<Packet>
Since the center server 100 divides and transmits the verification information (contents of the verification information table 10) into each packet when transmitting to each admission management device, the configuration of this packet will be described below.

FIG. 5 is a diagram illustrating a data configuration of each packet for transmitting the verification information.
Each packet includes a transmission source IP address 91, a management device ID 92, a packet count 93, and verification data 94.
Here, the transmission source IP address 91 is the IP address of the center server 100, the management device ID 92 is the identification number of the admission management device that is the destination of each packet, and one of the management device IDs in the configuration information table 30 Is consistent with

The packet number 93 is information indicating the number of all packets when the verification information is divided and transmitted.
The collation data 94 is a part of data for collation information (each record of the collation information table 10) to be transmitted in each packet. In the figure, the first record to the third record of the collation information table 10 are shown. The above is illustrated as collation information A to C.

<Thread state transition>
Hereinafter, the state transition of each thread will be described.
FIG. 6 is a state transition diagram of each thread.
As shown in the figure, each thread has an executable state ST1, an execution state ST2, and a standby state ST3.

Here, the executable state ST1 is a state that can be executed as soon as a processor is assigned. When the execution control unit 107 receives a collation information transmission instruction from the user interface unit 102, the execution control unit 107 generates a thread and sets the thread state to the executable state ST1.
Here, every time a thread is generated, the execution control unit 107 generates a number (hereinafter referred to as “thread number”, which is an integer) that is different from other threads 0 to (number of threads to be generated−1). Assign to that thread and specify the total number of threads to be created. That is, for example, when three threads are generated, “0”, “1”, and “2” are assigned to each thread, and the total number of threads “3” is designated.

The execution state ST2 is a state in which a processor is actually allocated and is being executed.
The execution control unit 107 assigns a processor to one thread in the executable state ST1, and makes a transition to the execution state ST2. In addition, when there is no entrance management device (hereinafter referred to as “target device”) that is a transmission target of the thread in the execution state ST2, the execution control unit 107 extinguishes the thread. The method for determining the presence / absence of the target device will be described in detail in the description of processing contents of each thread below.

  The standby state ST3 is a state in which transmission of verification information to the target device is completed and reception of a completion notification from the admission management device is awaited. When the thread in the execution state ST2 completes the transmission of the verification information, the execution control unit 107 deallocates the processor to the thread, makes a transition to the standby state ST3, and transfers it to another thread in the executable state ST1. Assign a processor to it.

In addition, when the execution control unit 107 receives a completion notification from the admission management device to which the thread has transmitted the verification information, the execution control unit 107 changes the thread from the standby state ST3 to the executable state ST1. Transition.
<Thread processing>
Hereinafter, the process of transmitting the verification information by each thread will be described.

FIG. 7 is a flowchart showing a process for transmitting verification information by each thread.
The thread assigned the processor by the execution control unit 107 and transitioned to the execution state ST2 refers to the configuration information table 30 stored in the configuration information storage unit 104, and the admission management device (transmission target of the own thread) ( It is determined whether or not there is a target device (step S11).

  More specifically, the threads are managed in order from the one with the smallest management device ID corresponding to the entrance management device whose transmission flag of the configuration information table 30 is “0” (that is, the verification information is not transmitted). It is determined whether or not the remainder obtained by dividing the ID by the total number of threads specified by the execution control unit 107 matches the thread number assigned to the own thread. If they match, it is determined that there is a target device.

  If it is determined in step S11 that there is a target device (step S11: YES), the thread updates the transmission flag of the configuration information table 30 for the target device to “1” (that is, during transmission) ( In step S12), the verification information is divided into packets of the format shown in FIG. 5 and transmitted to the target apparatus via the communication interface unit 106 (step S13).

When the transmission of all packets is completed, the thread waits for reception of a completion notification addressed to its own thread (step S14).
Specifically, the thread notifies the device driver of the identification code indicating the completion notification and the management device ID sent together with the completion notification that the thread waits for reception, and the management device ID notified to the device driver. When a completion notification sent is received, a corresponding flag is set and an instruction is given to notify (interrupt to OS).

When the notification of the management device ID and the like by the thread is completed, the execution control unit 107 cancels the assignment of the processor to the thread in the execution state ST2, shifts to the standby state ST3, and sets the predetermined flag described above. (When an interrupt occurs), this thread is first shifted to the executable state ST1.
When the processor is assigned again by the execution control unit 107 and transitioned to the execution state ST2, this thread updates the transmission flag of the configuration information table 30 for the target device to “2” (that is, transmission completion) (step S1). S15) The process is performed again from step S11.

If it is determined in step S11 that there is no target device (step S11: NO), the thread terminates the verification information transmission process and is extinguished by the execution control unit 107.
Actually, registration of verification information in the fingerprint reader may not be completed due to the occurrence of some error, and a completion notification may not be received no matter how long it waits in step S14 described above. Therefore, for example, when the admission management device or the fingerprint reader detects that the verification information needs to be retransmitted, an error notification is transmitted from the admission management device instead of the completion notification.

  In this case, the device driver notifies the management device ID that is sent together with the error notification, and the execution control unit 107 sends the corresponding thread (the thread that sent the verification information to the admission management device indicated by the notified management device ID). ) Is transferred to the executable state ST1 and the thread to which the processor is assigned again by the execution control unit 107 and changed to the execution state ST2 is re-executed from step S13 (not shown in FIG. 7). Process).

  In addition, if the entrance management device and the fingerprint reader cannot detect an error, the above error notification is not transmitted, so that when each thread completes transmission of all packets in step S13, a timer (not shown) is set. When this timer is started and a predetermined time is counted, a timer interrupt may be generated to perform the above-described retransmission process, or the transmission of the verification information to the corresponding admission management device may be abandoned. You may make it transmit the information for collation to an entrance management apparatus.

<Specific example>
The overall operation of the entrance management system 1000 will be specifically described with reference to FIG.
FIG. 8 is a sequence diagram for explaining the flow of processing until the verification information transmitted from the center server 100 is registered in the verification information table 10 of each fingerprint reader.
In this example, it is assumed that three threads are generated by the execution control unit 107, and TH1 to TH3 in the figure indicate these three threads.

  Hereinafter, the execution control unit 107 assigns “1” to the thread TH1, “2” to the thread TH2, “0” to the thread TH3, and the total thread number “3” as the thread number. Shall be specified. Also, it is assumed that the transmission flags 33 in the configuration information table 30 shown in FIG. 4B are all “0” (untransmitted) when the following processing is started.

<First transmission by thread TH1>
First, when the execution control unit 107 transitions the thread TH1 generated and in the executable state ST1 to the execution state ST2, the thread TH1 sets the entrance management device 200A whose management device ID 31 in the configuration information table 30 is “1”. As a target device, the transmission flag 33 corresponding to the management device ID 31 “1” in the configuration information table 30 is updated to “1”, and then the verification information is divided into packets and transmitted via the communication interface unit 106. (Step S20).

Specifically, the target device is determined as follows. That is, the remainder “1” obtained by dividing the management apparatus ID “1” associated with the transmission flag “0” by the designated total number of threads “3” is the thread number “1” assigned to the own thread. Since they match, the admission management device 200A is determined as the target device.
When the transmission of all packets is completed, the thread TH1 is shifted to the standby state ST3 by the execution control unit 107.

The communication control unit 201 of the entrance management apparatus 200A receives each packet transmitted from the center server 100 and transfers it to the connected fingerprint reader 300A (step S21).
The communication interface unit 301 of the fingerprint reader 300A transmits each packet transferred from the entrance management apparatus 200A to the update unit 303, and the update unit 303 transmits the verification data 94 included in each packet to the verification information storage unit 302. Are registered in the collation information table 10 stored in.

When the matching data 94 included in all the packets is registered in the matching information table 10, the updating unit 303 transmits a completion notification to the connected entrance management device 200A via the communication interface unit 301 (step S22). .
More specifically, the update unit 303 counts the number of times that the matching data 94 included in the packet transferred from the admission management device 200A is registered in the matching information table 10, and this count is included in the packet. When the packet count 93 is matched, a completion notification is transmitted.

The communication control unit 201 of the entrance management apparatus 200A transfers the completion notification received from the fingerprint reader 300A to the center server 100 together with the management apparatus ID of the own apparatus (step S23).
The communication interface unit 106 of the center server 100 receives this completion notification and notifies the execution control unit 107. The execution control unit 107 first transitions the thread TH1 in the standby state ST3 to the executable state ST1, and again performs the processor. To the execution state ST2, the thread TH1 that is again in the execution state ST2 sets the transmission flag 33 of the configuration information table 30 corresponding to the management device ID included in the received completion notification to “2”. Update.

<First transmission by thread TH2>
As described above, when the process of step S20 is completed, the thread TH1 is transitioned to the standby state ST3 by the execution control unit 107. Instead of this thread TH1, the execution control unit 107 generates and executes the executable state ST1. Thread TH2 in the transition to the execution state ST2.

  Thereafter, the processing is basically the same as that of the above-described thread TH1, and the thread TH2 transmits a packet to the entrance management apparatus 200B (step S30), and the entrance management apparatus 200B prints the received packet as a fingerprint. The data is transferred to the reader 300B (step S31). The fingerprint reader 300B registers the received packet verification data 94 in the verification information table 10, and upon completion, transmits a completion notification to the admission management device 200B (step S32), and the admission management device 200B receives it. The completion notification is transferred to the center server 100 together with the management apparatus ID of the own apparatus (step S33).

<First transmission by thread TH3>
In the first transmission by the thread TH2, when the processing of step S30 is completed, the thread TH2 is shifted to the standby state ST3 by the execution control unit 107, and the execution control unit 107 generates the thread TH2 instead of the thread TH2. Then, the thread TH3 in the executable state ST1 is shifted to the execution state ST2.

Thereafter, the target device to which the thread TH3 transmits verification information is the admission management device 200C, and the above-described thread TH2 except that the verification data 94 of each packet is registered in the verification information table 10 of the fingerprint reader 300C. Since steps S40 to S43 are processed in the same manner as described above, detailed description thereof is omitted.
<Second transmission by thread TH1>
When the process of step S23 described above is completed, the thread TH1 in the execution state ST2 continues to perform the process of step S24. Thereafter, the target device to which the thread TH1 transmits verification information is the admission management device 200D, and the first transmission described above except that the verification data 94 of each packet is registered in the verification information table 10 of the fingerprint reader 300D. Since it is the same as the processing, detailed description is omitted.

<Discussion>
Hereinafter, in the admission management system 1000, the time until the storage of the verification information in each fingerprint reader is completed and the storage of the verification information in each fingerprint reader by the conventional method (sequential processing method) is completed. Compare the time.
As described with reference to a specific example in FIG. 8, the center server 100 of the admission management system 1000, when the thread TH1 completes the transmission of the verification information to the admission management device 200A, the thread TH2 continues to the admission management device 200B. The transmission of the verification information to the admission management device 200B is started without waiting for the completion notification from the fingerprint reader 300A, such as starting the transmission of the verification information to.

As a result, as shown in the figure, the time until the storage of the collation information in the three fingerprint readers 300A to 300C is T1.
FIG. 9 is a diagram for explaining the time until the storage of the verification information in the three fingerprint readers A to C by the conventional method is completed.
As shown in the figure, conventionally, when a server first transmits verification information to the fingerprint reader A via the management apparatus A, the fingerprint reader A completes storage of the verification information and receives a completion notification. Then, the processing is sequentially performed such that the data is transmitted to the fingerprint reader B via the management apparatus B.

As a result, the time until the storage of the collation information in the three fingerprint readers A to C is T2.
Comparing both times (T1, T2), it can be seen that T1 <T2, and the admission management system 1000 can shorten the time until the storage of the verification information in each fingerprint reader is completed.

<< Modification 1 >>
<Overview>
In the first embodiment, the management device ID of each entrance management device has been described as being assigned so as to be a serial number from 1 (see the configuration information table 30 in FIG. 4B).
However, in the operation stage, the number of entrance management devices included in the entrance management system may increase or decrease. When the management device ID is assigned so as to be a sequential number from 1, it is necessary to reassign the management device ID every time the number of entrance management devices decreases. In addition, there is a case where it is desired to assign a management device ID with a skip number in preparation for the future increase in the number of entrance management devices.

Therefore, in the following, a description will be given of a modified example in which an arbitrary identification number is assigned as the management device ID.
The center server according to the first modification differs from the center server 100 according to the first embodiment in that the configuration information table 40 is stored instead of the configuration information table 30, and the processing of each thread is slightly different. The description will focus on the changes from the first embodiment.

<Configuration information table>
The configuration information table 40 stored in the configuration information storage unit 104 of the center server according to Modification 1 will be described.
FIG. 10 is a diagram illustrating a data configuration and a content example of the configuration information table 40.
As shown in the figure, the configuration information table 40 stores a management device ID 41, a reader ID 42, and a transmission flag 33 in association with each entrance management device, and the management device ID 41 and the reader ID 42 store the configuration information. Different from the table 30.

Specifically, the management device ID 41 and the reader ID 42 are assigned with an arbitrary number that is not a serial number and is not duplicated as an identification number for identifying each entrance management device and each fingerprint reader. The management device ID 31 and the reader ID 32 are different.
<Thread processing>
The processing of each thread according to Modification 1 is slightly different from the processing of each thread according to Embodiment 1 shown in the flowchart of FIG.

Specifically, whether each thread according to the first modification matches the transmission flag corresponding to “0” (that is, the verification information is not transmitted) in order from the smallest management device ID in the configuration information table 40. If it matches, it is determined that there is a target device.
In the first embodiment, the execution control unit 107 of the center server 100 assigns a thread number and designates the total number of threads when generating each thread. Is unnecessary.

In this way, even if an arbitrary identification number is assigned to the management device ID of each entrance management device, each thread can execute the next execution state ST2 when transmission of verification information to one entrance management device is completed. Since the verification information is transmitted to the untransmitted admission management device when the transition to is made, the same effect as in the first embodiment is obtained.
Further, for example, even when the time required for registration of verification information differs for each fingerprint reader, in the method of the first embodiment, the target device is allocated to each thread so that the total number of target devices is almost equal. become. However, in the method of the first modification, the thread that has transmitted the verification information to the admission management device connected to the fingerprint reader that takes a short time to register the verification information transmits the verification information to more admission management devices. Will do. Therefore, in the case as described above, compared with the admission management system 1000 according to the first embodiment, it is possible to further shorten the time required for storing the verification information in each fingerprint reader.

<< Modification 2 >>
<Overview>
The first embodiment has been described on the assumption that each admission management device related to the information registered in the configuration information table 30 can receive the verification information transmitted by the center server 100.
However, at the operation stage, the entrance management device related to the information registered in the configuration information table 30 breaks down, or information about the entrance management device that has not yet been installed is to be registered in the configuration information table 30 in advance. In some cases. Since such an entrance management apparatus is in a state where communication is not possible, even if the verification information is transmitted, an error occurs and waste occurs.

Therefore, hereinafter, a description will be given of a modified example in which information indicating the presence / absence of each entrance management device is added to the configuration information table 30.
The admission management system according to the second modification is not particularly illustrated and described, but instead of the center server 100 of the admission management system 1000 according to the first embodiment, a center is added to the presence confirmation function of each admission management device. Instead of the server 110 and the admission management devices 200A to 200F of the admission management system 1000, there are provided admission management devices 210A to 210F to which a function for responding to the presence / absence confirmation from the center server 110 is added.

Hereinafter, the difference from the admission management system 1000 according to Embodiment 1 will be mainly described.
In addition, since the admission management apparatuses 210A to 210F have the same configuration, the admission management apparatus 210A will be described below as an example.
<Configuration>
<Center server>
FIG. 11 is a block diagram illustrating a functional configuration of a main part of the center server 110 according to the second modification.

As with the center server 100 according to the first embodiment, the center server 110 includes a memory and a processor. In terms of functions, the center server 110 includes an existence confirmation unit 111 in addition to the components of the center server 100 as shown in FIG. Prepare. Note that the function of the presence / absence confirmation unit 111 is realized by the above-described processor executing a control program stored in the above-described memory.
Here, the presence / absence confirmation unit 111 has a function of confirming the presence / absence of each entrance management device. Specifically, the presence / absence check is performed via the communication interface unit 106 for each entrance management device indicated by the management device ID 31 in the configuration information table 50 (see FIG. 13) according to the second modification stored in the configuration information storage unit 104. Packet (hereinafter referred to as “request packet”, including the management device ID of the admission management device as the destination), and whether or not a response packet to the request packet has been received is reflected in the configuration information table 50 It has a function. When a response packet for the request packet is not received within a predetermined time after transmitting the request packet, it is determined that a response bucket is not received.

<Admission management device>
FIG. 12 is a block diagram illustrating a functional configuration of a main part of an admission management device 210A according to the second modification.
The admission management device 210A includes a memory and a processor, as in the admission management device 200A according to the first embodiment, and in terms of function, as shown in FIG. Prepare. Note that the function of the response unit 211 is realized by the above-described processor executing a control program stored in the above-described memory.

Here, when the response unit 211 receives the request packet (request packet including the management device ID of the own device) transmitted from the center server 110 via the communication control unit 201, the response unit 211 receives the request packet addressed to the own device. It has a function of transmitting a response packet including an ID to the center server 110 via the communication control unit 201.
<Configuration information table>
The configuration information table 50 stored in the configuration information storage unit 104 of the center server 110 will be described.

FIG. 13 is a diagram illustrating a data configuration and a content example of the configuration information table 50.
As shown in the figure, the configuration information table 50 stores a management device ID 31, a reader ID 32, a reception result 51, and a transmission flag 33 in association with each admission management device. It differs from the configuration information table 30 in that it is included.
The management device ID 31 shows an example in which different numbers are assigned to the entrance management devices 210A to 210F so that the numbers are serial numbers starting from 1.

Here, the reception result 51 is information indicating the reception status of the response packet with respect to the request packet transmitted to the corresponding admission management device. In this example, “0” is set for unreceived and “1” is set for received.
In the figure, for example, a fingerprint reader (fingerprint reader 300A) whose reader ID 32 is “101” is connected to an entrance management device (admission management device 210A) whose management device ID 31 is “1”, and the reception result 51 indicates “1”, that is, a response packet is received from the admission management device 210A, and the transmission flag 33 is “2”, that is, transmission of the verification information to the admission management device 210A is completed. It shows that.

<Thread processing>
The processing of each thread according to the modification 2 is slightly different from the processing of each thread according to the first embodiment shown in the flowchart of FIG.
Specifically, each thread according to the modified example 2 has an entry management device in which the transmission flag 33 of the configuration information table 50 is “0” (that is, the verification information is not transmitted). In order from the smallest management device ID, it is determined whether or not the corresponding reception result 51 matches “1” (that is, the response packet is received), and if they match, it is determined that there is a target device. The assignment of the thread number to each thread and the designation of the total number of threads are not necessary as in the first modification.

  As a result, the same effect as that of the first modification is obtained, and verification information is not transmitted to an entrance management device that has not received a response packet, that is, an entrance management device that can be determined to be unable to communicate due to a failure or not installed. Further, it is possible to shorten the time until the storage of the collation information to each of the fingerprint readers is completed more effectively without trying to send useless collation information.

<< Embodiment 2 >>
<Overview>
In the first embodiment, the fingerprint readers 300A to 300F that identify the visitors based on the verification information including fingerprint data have been described as an example of the reader device in the entrance management system according to the present invention.

In the second embodiment, not only the fingerprint reader but also the collation information table 20 including identification information (hereinafter referred to as “card ID”) recorded on each IC card possessed by the prospective visitor (FIG. 15A). An example of an entrance management system having a configuration that also includes a card reader that identifies a visitor based on the reference) will be described focusing on changes from the first embodiment.
<Configuration>
FIG. 14 is a system configuration diagram of an admission management system 2000 according to the second embodiment.

As shown in the figure, the admission management system 2000 includes a center server 120 instead of the center server 100 in the admission management system 1000 according to the first embodiment, and card readers 300G and 300H instead of the fingerprint readers 300E and 300F. It is comprised including.
Here, the center server 120 further stores the verification information table 20 in the verification information storage unit 103 of the center server 100 according to the first embodiment, and stores the verification information table 20 in the configuration information storage unit 104 of the center server 100. Instead, it differs from the center server 100 in that the configuration information table 60 is stored. Also, as will be described later, the processing of each thread is slightly different.

Each card reader (300G, 300H) has a function of specifying a visitor using a card ID recorded on an IC card, and is slightly different from the functional configuration of each fingerprint reader.
Specifically, the collation information storage unit of each card reader stores a collation information table 20 instead of the collation information table 10, and the update unit collates the collation information transmitted from the communication interface unit. It differs from each fingerprint reader in that it is registered in the verification information table 20 of the information storage unit.

Further, the reading unit reads the card ID from the IC card possessed by the visitor, and the verification unit uses the card ID transmitted from the reading unit and the verification information table 20 stored in the verification information storage unit. It differs from each fingerprint reader in that the employee ID of the visitor is specified by collation.
<Data>
<Information table for verification>
The verification information table 20 stored in the verification information storage unit 103 of the center server 120 and the verification information storage unit of each card reader will be described.

FIG. 15A is a diagram illustrating a data configuration and a content example of the collation information table 20.
As shown in the figure, the verification information table 20 stores an employee ID 11 and a card ID 21 in association with each prospective visitor, and the card ID 21 is different from the verification information table 10.
Specifically, the card ID 21 is identification information of the IC card recorded on the IC card of the prospective visitor, and is character string data that does not overlap with other card IDs.

This figure shows, for example, that the card ID 21 of the IC card of the prospective admission person whose employee ID 11 is “1000001” is “2y3B9... T948C7”.
It should be noted that new data registration, update, and deletion of registered data in the collation information table 20 stored in the collation information storage unit 103 of the center server 120 are performed from the input unit 101 by an administrator or the like. These changes are made in the collation information table 20 stored in the collation information storage unit of each card reader based on a collation information transmission instruction from the input unit 101 by an administrator or the like. Will be reflected.

  This collation information (the contents of the collation information table 20) includes a card ID, and generally, when compared with the same number (number of records), collation information including fingerprint data (collation information) The size becomes smaller than the contents of the table 10. Therefore, as compared with the case where the verification information including fingerprint data is stored, the time until the registration of the verification information in the verification information storage unit of each card reader is shortened.

  Further, the collation unit of each card reader performs the following process using the collation information table 20. That is, when a record including the card ID stored in the IC card of the visitor transmitted from the reading unit is registered in the verification information table 20, the verification unit includes the employee ID included in the record. The reader ID of the reader is transmitted to the admission management device connected via the communication interface unit.

<Configuration information table>
The configuration information table 60 stored in the configuration information storage unit 104 of the center server 120 will be described.
FIG. 15B is a diagram illustrating a data configuration and a content example of the configuration information table 60.
As shown in the figure, the configuration information table 60 stores a management device ID 31, a reader ID 32, a type 61, and a transmission flag 33 in association with each entry management device, and includes the type 61. Thus, the configuration information table 30 is different.

The reader ID 32 shows an example in which numbers 101 to 104 are assigned to the fingerprint readers 300A to 300D, and numbers 105 and 106 are assigned to the card readers 300G and 300H, respectively.
Here, the type 61 is information indicating the type of verification information used by the reader connected to the corresponding entrance management device to identify the visitors. In this example, “1” is used when collation information including fingerprint data (that is, collation information table 10) is used, and “2” is used when collation information including card ID (that is, collation information table 20) is used. Yes.

  In the drawing, for example, a reader (fingerprint reader 300A) with a reader ID 32 of “101” is connected to an entrance management device (admission management device 200A) with a management device ID 31 of “1”. “1”, that is, indicates that the verification information table 10 is used, and the transmission flag 33 indicates “2”, that is, indicates that transmission of the verification information to the admission management device 200A has been completed. .

  Further, for example, a reader (card reader 300G) with a reader ID 32 of “105” is connected to an entrance management device (admission management device 200E) with a management device ID 31 of “5”, and the type 61 is “2”. ", That is, the use of the collation information table 20, and the transmission flag 33 is" 0 ", that is, the collation information is not yet transmitted to the admission management device 200E.

<Thread processing>
The processing of each thread according to the second embodiment is slightly different from the processing of each thread according to the first embodiment shown in the flowchart of FIG. 7 in step S11 and step S13.
Here, the execution control unit of the center server 120 uses a collation information table 10 instead of the thread number assignment and the designation of the number of all threads described in the first embodiment when generating each thread. Type number indicating whether the verification information is to be transmitted to the admission management device connected to the reader or the admission management device connected to the reader using the verification information table 20 (the former is “1” and the latter is “2”) Assign).

For example, one thread A for transmitting the verification information to the admission management device connected by the reader using the verification information table 20 is generated, and the verification information is sent to the admission management device connected by the reader using the verification information table 10. When two threads B and C to be transmitted are generated, the type number “2” is assigned to the thread A, and the type number “1” is assigned to the threads B and C.
Under such a premise, each thread according to the second embodiment processes as follows instead of the process of step S11 of each thread according to the first embodiment.

That is, for the admission management devices whose transmission flag 33 in the configuration information table 60 is “0” (that is, the verification information has not been transmitted), the corresponding types in order from the smallest management device ID in the corresponding configuration information table 60. 61 determines whether or not it matches the type number designated by the execution control unit. If they match, it is determined that there is a target device.
Also, each thread according to the second embodiment transmits the type of collation information indicated by the type number assigned to the own thread to the target device in the process of step S13 of each thread according to the first embodiment. Thus, the processing in step S13 is slightly different.

<Specific example>
The overall operation of the entrance management system 2000 will be specifically described with reference to FIG.
FIG. 16 is a sequence diagram for explaining the flow of processing until the verification information transmitted from the center server 120 is registered in the verification information table of each fingerprint reader and each card reader.

  In the figure, TH1 to TH3 indicate three threads generated by the execution control unit of the center server 120. Hereinafter, the execution control unit sets the thread TH1 to the type number “2” and the threads TH2 and TH3. The type number “1” is designated. Further, it is assumed that the transmission flags 33 in the configuration information table 60 shown in FIG. 15B are all “0” (untransmitted) when the following processing is started.

<First transmission by thread TH1>
First, when the execution control unit transitions the thread TH1 generated and in the executable state ST1 to the execution state ST2, the thread TH1 is associated with the transmission flag “0” and the type “2” in the configuration information table 50. The entry management device 200E indicated by the smallest management device ID “5” is the target device, the transmission flag 33 of the entrance management device 200E is updated to “1”, and the type number assigned by the execution control unit is Since it is “2”, the verification information including the card ID (the content of the verification information table 20) is divided into packets and transmitted through the communication interface unit (step S50).

Since the processing of the following steps S51 to S53 is basically the same as the processing of steps S21 to S23 of the first embodiment, description thereof will be omitted.
<First transmission by thread TH2>
When the process of step S50 is completed, the thread TH1 is shifted to the standby state ST3 by the execution control unit, and instead of the thread TH1, the execution control unit generates the thread TH2 that is generated and in the executable state ST1 in the execution state ST2. , The thread TH2 uses the entrance management device 200A indicated by the minimum management device ID “1” associated with the transmission flag “0” and the type “1” in the configuration information table 50 as the target device, and enters the entrance. Since the type number assigned to the execution control unit is “1” after updating the transmission flag 33 of the management apparatus 200A to “1”, the collation information including the fingerprint data (the contents of the collation information table 10) ) Are divided into packets and transmitted via the communication interface unit (step S60).

Since the processes in steps S61 to S63 below are the same as the processes in steps S31 to S33 in the first embodiment, the description thereof is omitted.
<First transmission by thread TH3>
In the first transmission by the thread TH2, when the process of step S60 is completed, the thread TH2 is shifted to the standby state ST3 by the execution control unit, and the execution control unit generates and executes the thread TH2 instead of the thread TH2. The thread TH3 in the possible state ST1 is transitioned to the execution state ST2.

Hereinafter, since steps S70 to S73 are processed in the same manner as in the case of the thread TH2 except that the target device to which the thread TH3 transmits the verification information is the entrance management device 200B, detailed description is omitted.
<Second transmission by thread TH1>
When the process of step S53 described above is completed, the thread TH1 in the execution state ST2 continues to perform the process of step S54. Hereinafter, the thread TH1 is the same as the first transmission process of the thread TH1 except that the target device to which the verification information is transmitted is the admission management device 200F, and thus detailed description is omitted.

<Discussion>
Hereinafter, the time until the storage of the verification information in each card reader in the admission management system 2000 is completed, and the time until the storage of the verification information in each card reader in the method of the first embodiment is completed. Compare
As described using a specific example in FIG. 16, the center server 120 of the admission management system 2000 uses the admission management device to which a reader using the collation information table 10 is connected and the collation information table 20 for each thread. The collation information is transmitted by assigning to which of the admission management devices to which the reader is connected the collation information is to be transmitted.

  In the example of the figure, although the management device IDs of the entrance management devices 200E and 200F to which the card readers are connected are relatively large numbers, as a result, priority is given to the transmission of verification information to these entrance management devices. The time from when the center server 120 starts transmitting the verification information to when the storage of the verification information in the two card readers 300G and 300H is completed is t1.

FIG. 17 is a diagram for explaining the time until the storage of the verification information in each card reader by the method of the first embodiment is completed.
As shown in the figure, in this example, according to the management device IDs of the entrance management devices 200E and 200F to which each card reader is connected, transmission of verification information to these entrance management devices is postponed, and the center server The time from when 100 starts transmitting the verification information until the storage of the verification information to the two card readers 300G and 300H is completed is t2.

When both times (t1, t2) are compared, t1 <t2.
The method described in the second embodiment can be said to be particularly effective in the following environment, for example.
In other words, in the case where there are a plurality of doors for entering one wide management target area (room), a card reader is installed in one door, and a fingerprint reader is installed in another door As described in the second embodiment, if each thread transmits the verification information, the verification information is stored in the card reader even when the verification information is not yet stored in the fingerprint reader. Cases such as completion may occur.

As a result, since it is possible to enter the management target area from the door where the card reader is installed, it is possible to improve the convenience of those who need to enter the management target area.
<Supplement>
The admission management system according to the present invention has been described above based on each embodiment. However, the admission management system can be modified as follows, and the present invention can be applied to the admission management system as described in the above-described embodiment. Of course, it is not limited.

(1) In the second modification, the center server 110 transmits a request packet to each admission management device as to whether or not each admission management device can communicate, that is, whether or not verification information can be received. The method of determining whether or not a response packet to the transmitted request packet has been received has been described as an example, but the following modifications are also conceivable.
That is, for example, each admission management device transmits history information to the center server each time authentication is performed, so it is conceivable to use presence / absence of reception of this history information. Specifically, every time the center server receives history information from each admission management device, the center server updates the reception result 51 of the corresponding admission management device in the configuration information table 50 to “1”, and the admission management device. , Start counting (reset and start) the elapsed time since the history information was received. For each admission management device, the center server updates the reception result 51 of the corresponding admission management device in the configuration information table 50 to “0” every time the elapsed time from the reception of the history information times a predetermined time. In this way, it is possible to determine whether or not each entrance management apparatus can communicate without transmitting a request packet.

  Further, the presence / absence of reception of history information and the presence / absence of reception of a response packet may be combined. That is, when receiving history information from a certain admission management device or receiving a response packet, the reception result 51 of the corresponding admission management device in the configuration information table 50 is updated to “1” and timing is started. The reception result 51 may be updated to “0” when a predetermined time has elapsed. Thereby, it can be determined more accurately whether each entrance management apparatus can communicate.

  (2) In each embodiment and each modification, it has been described that each thread determines a target device and divides verification information into packets, and each thread (hereinafter, “each transmission thread”). ) Performs only the process of transmitting the packet, and a control thread different from these determines the transmission target of each transmission thread, and the packet obtained by dividing the verification information to be transmitted by each transmission thread. Alternatively, it may be delivered to each transmission thread.

  (3) In the second embodiment, the example of the admission management system 2000 having a configuration including not only the fingerprint reader but also the card reader has been described. However, each thread has priority over the admission management device connected to the card reader. When the verification information is transmitted and transmission to all the entrance management devices connected to the card reader is completed, each thread may transmit the verification information to the entrance management device connected to the fingerprint reader. As a result, the storage of the verification information in the card reader that takes a relatively short time until the storage of the verification information is completed can be completed before the storage of the verification information in the fingerprint reader. In the environment described in the discussion, it can contribute to improving the convenience of visitors.

(4) In each embodiment and each modification, the configuration in which one reader is connected to each entrance management device has been described. However, a configuration in which a plurality of readers are connected to each entrance management device may be employed.
In this case, each entrance management device needs to store information indicating the correspondence between each reader connected to the entrance management device and the electronic lock in order to control the electronic lock.
In addition, each admission management device, based on this information, transfers verification information to the reader,
Each reader includes the reader ID of its own device in the completion notification and transmits it to the connected admission management device, and the admission management device transfers the received completion notification to the center server.

At this time, the admission management device may transmit one completion notification (including the management device ID of the own device) to the center server when receiving completion notifications from all readers connected to the own device. .
Furthermore, the readers connected to each entrance management device may be the same type or different types. That is, for example, one or more fingerprint readers are connected to the entrance management apparatus A, one or more card readers are connected to the entrance management apparatus B, and one or more fingerprint readers are connected to the entrance management apparatus C. And one or more card readers may be connected.

  In this case, the center server and each admission management device store information indicating the type of each reader, and the center server verifies each admission management device according to the type of reader connected to the admission management device. Information needs to be sent. The method for determining the target device of each thread at this time may be the method described in each embodiment and each modification, or may be the following method.

  The execution control unit connects the fingerprint reader and the card reader with one or more threads A that are transmitted to the entrance management device to which only the fingerprint reader is connected, one or more threads B that are transmitted to the entrance management device to which only the card reader is connected, and One or more threads C to be transmitted to the admission management device. Thread A sends verification information including fingerprint data to the target device (admission management device A in the above example), and thread B transmits verification information including card ID to the target device (admission management device B in the above example). Thread C transmits the verification information including the fingerprint data and the verification information including the card ID to the target device (the admission management device C in the above example).

(5) In each embodiment and each modified example, it has been described that each thread is extinguished by the execution control unit when there is no target device. However, in the flowchart shown in FIG. The execution control unit may be extinguished and regenerated as necessary.
(6) In each embodiment and each modification, it has been described that the authentication information storage unit of each admission management device stores the authentication information table 80 in advance. May be transmitted to each admission management device together or separately when the verification information is transmitted to.

(7) In each embodiment and each modification, a fingerprint reader and a card reader have been described as examples of the reader device in the admission management system according to the present invention. However, any information can be used as long as it can read information for identifying an individual. For example, it may be a reader that reads biological information such as a voiceprint, an iris, and a vein.
(8) The admission management system 2000 according to the second embodiment may be modified as described in each modification.

(9) In the second modification, the center server 110 transmits a request packet to each admission management device and operates based on the configuration information table 50 reflecting the reception result of the response packet to the request packet. Although it has been described that the verification information is transmitted to the management apparatus, the following modification may be made.
That is, an operation flag is provided in place of the reception result 51 of the configuration information table 50, and the administrator sets the operation flag for the operating management apparatus to “1” (indicating that it is in operation). The operation flag for the operation management device is set to “0” (indicating that it is not in operation) in advance, and based on the configuration information table according to this modification, the verification information is sent to the operating admission management device. May be transmitted.

  (10) The server execution control means in the admission management system according to the present invention corresponds to the execution control unit of the center server in the admission management system according to each embodiment and each modification, and the server transmission status storage means, management The apparatus information storage unit and the type storage unit correspond to the configuration information storage unit 104 of the center server according to each embodiment and each modification, and the update unit includes the existence confirmation unit 111 of the center server 110 according to the modification 2. The communication means of the server corresponds to the existence confirmation unit 111 and the communication interface unit 106 of the center server 110 according to the second modification.

The receiving means and transfer control means of the management device in the admission management system according to the present invention correspond to the communication control unit 201 of the admission management device in the admission management system according to each embodiment and each modification. The response means corresponds to the response unit 211 of the entrance management device according to the second modification.
The reader device in the admission management system according to the present invention corresponds to a fingerprint reader and a card reader in the admission management system according to each embodiment and each modification.

1 is a system configuration diagram of an entrance management system 1000. FIG. 3 is a block diagram showing a functional configuration of a main part of the center server 100. FIG. It is a block diagram which shows the function structure of each principal part of the entrance management apparatus 200A and the fingerprint reader 300A. It is a figure which shows each data structure and the example of content of the information table 10 for collation, the structure information table 30, the log | history information table 70, and the information table 80 for authentication. It is a figure which shows the data structure of each packet for transmitting the information for collation. It is a state transition diagram of each thread. It is a flowchart which shows the transmission process of the information for collation by each thread | sled. It is a sequence diagram for demonstrating the flow of a process until the information for collation transmitted from the center server 100 is registered into the collation information table 10 of each fingerprint reader. It is a figure for demonstrating the time until the memory | storage of the information for collation to three fingerprint readers A-C by the conventional method is completed. It is a figure which shows the data structure and content example of the structure information table 40. FIG. It is a block diagram which shows the function structure of the principal part of the center server 110 which concerns on the modification 2. FIG. It is a block diagram which shows the function structure of the principal part of the entrance management apparatus 210A which concerns on the modification 2. FIG. It is a figure which shows the data structure and content example of the structure information table 50. FIG. 6 is a system configuration diagram of an admission management system 2000 according to Embodiment 2. FIG. It is a figure which shows the data structure and content example of each of the information table 20 for collation, and the structure information table 60. FIG. It is a sequence diagram for demonstrating the flow of a process until the information for collation transmitted from the center server 120 is registered into the information table for collation of each fingerprint reader and each card reader. FIG. 6 is a diagram for explaining a time until storage of verification information in each card reader in the method according to the first embodiment is completed.

Explanation of symbols

1 LAN
2A to 2F Cable 100, 110, 120 Center server 101 Input unit 102 User interface unit 103 Verification information storage unit 104 Configuration information storage unit 105 History information storage unit 106 Communication interface unit 107 Execution control unit 111 Existence confirmation unit 200A to 200F, 210A Admission management device 201 Communication control unit 202 Authentication information storage unit 203 Timekeeping unit 204 Key control unit 205 Authentication unit 211 Response unit 300A to 300F Fingerprint reader 300G, 300H Card reader 301 Communication interface unit 302 Verification information storage unit 303 Update unit 304 Reading unit 305 Verification unit 1000, 2000 Admission management system

Claims (7)

A plurality of reader devices that read visitor information and collate with stored verification information to identify visitors, and a plurality of reader devices that authenticate the visitors identified by each reader device and lock and unlock the door An admission management system including a management device and a server for transmitting verification information to each reader device via each management device,
Each management device
Receiving means for receiving verification information from the server;
Transfer control for causing one or more reader devices associated in advance to transfer and store the verification information received by the receiving unit in the reader device, and to send a completion notification to the server when the reader device has been stored. Means and
The server
After sending verification information to a different management device for each thread and executing a plurality of threads that perform processing in accordance with the completion notification corresponding to the transmission in parallel, An admission management system comprising execution control means for controlling the thread to transition to a waiting state until a completion notification corresponding to transmission is received. The total number of threads executed by the execution control means is less than the total number of management devices,
The server
Transmission status storage means for storing transmission status information in which each management device is associated with one different number and information indicating whether or not verification information has been transmitted to the management device,
Each thread refers to the management device associated with the smallest number among the management devices that do not transmit the verification information with reference to the transmission status information when the execution of the thread is started. The admission management system according to claim 1, wherein: The total number of threads executed by the execution control means is less than the total number of management devices,
The server
A transmission that stores transmission status information in which each management device is associated with a different number so that each number is continuous, and information indicating whether or not verification information has been transmitted to the management device. A situation storage means,
Each thread is the remainder of dividing the associated number by the total number of threads among the management devices that do not transmit the verification information with reference to the transmission status information when execution of the thread is started, The admission management system according to claim 1, further comprising: transmitting verification information to a management device that is determined according to a value set in advance in the own thread. The server
A management device information storage unit for storing management device information for identifying a management device in operation among the management devices,
The admission management system according to claim 1, wherein each thread refers to the management device information when the execution of the thread is started and transmits the verification information only to the operating management device. . 5. The admission management system according to claim 4, further comprising: an update unit configured to update the management device information as a management device operating when the server receives data from the management device. Each management device further comprises response means for transmitting a response signal when receiving a request signal from the server,
The server further includes:
A communication means for transmitting a request signal to each management device and receiving a response signal to the request signal;
The said update means updates the said management apparatus information by making the said management apparatus into an operating management apparatus, if the response signal with respect to the request signal transmitted to the said management apparatus is received about each management apparatus. The admission management system described. The verification information includes information about each visitor, and the verification information includes two types of information: medium information for identifying the visitor and biometric information of the visitor.
The server further includes, for each management device, a type storage unit that stores information indicating a type of verification information used for verification by a reader device corresponding to the management device,
Based on the information stored in the type storage unit, each thread sends verification information to a management device associated with a reader device that performs verification using one type of verification information preset for the thread itself. The admission management system according to claim 2, wherein the admission management system is transmitted.

Images