JP2001266202A - Gate management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a gate management system which can shorten the collating time on the side of a gate device and lighten the load on a line and the load on a server side by decreasing the number of request inquiries for identification information made by gate devices to a management server. SOLUTION: In the gate management system, feature information for identification is inputted for collation information downloaded from the management server managing a gate device to the gate device together with identification information, the gate device obtains the collation information by using the identification information as a key and compares the feature information with the collation information to open a gate, thereby allowing the person to pass. The gate device obtains information on the time when the person oneself passes through the gate and sends it out to the management server together with the identification information. The management server manages passage time information corresponding to the identification information and downloads the collation information on the person to the gate device together with the identification information before the gate passage time of the person that the passage time indicates.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to a gate management system, and more particularly, to a system including a gate device and a gate management server, in which a collation time on a gate device side can be shortened, and a plurality of gate devices can be transmitted to a gate management server. The present invention relates to a gate management system capable of reducing a line load and a server-side load by reducing the amount of a request inquiry of personal identification information performed on the gate control system.

[0002]

2. Description of the Related Art Conventionally, as one of the gate management systems, an entrance / exit management system for controlling entrance and exit by controlling opening and closing of a gate or a door with an IC card or various cards is known. In this type of system, when entering or entering a room, the user is allowed to enter and enter by checking the card with a gate device, and when leaving and leaving the office, he / she is free to enter and exit, but also manages the time to leave and exit by comparing the card. There is also a system. This type of conventional gate management system (entrance / exit management system) includes (1) a method in which collation data of all persons is stored in a gate device and collated by a gate device. A method in which a personal inquiry is made to a management server such as a server or a traffic management server, and data for verification of the person is downloaded and verified by a gate device. (3) Personal information is transmitted to the management server, verified by the management server, and the result is gated. There is a method to notify the device and open the gate.

[0003] In recent gate management systems, in order to improve the reliability of collation, fingerprint collation is performed by using an input user ID as a key and a face identification part is used instead of collation using a one-dimensional code such as an IC card. Feature point matching based on feature information such as feature point matching is performed, and the matching data is usually recorded as vector data such as two-dimensional image data, and has a large capacity of several hundred bytes to 1 Mbyte. .

[0004]

In feature point collation using two-dimensional vector data, the method of the above (1) is as follows.
Since the collation data of all persons is stored, the collation time is short without querying the management server, but the total number of persons who can be registered is determined by the capacity of the authentication information database in the gate device which can register collation data. However, there is a disadvantage that it is limited to it. Similarly, the above (2)
Is not limited by the capacity of the authentication information database of the gate device, the collation time is short if the number of gate devices is small and the management server is fast, but if the number of gate devices or gates is large, the matching When a plurality of persons pass through the gate, there is a problem that the load is high and the matching time is long. Similarly, in the method of (3), the collation processing of (2) is performed by the management server, so that the collation processing is not affected by the performance of the gate device, and the collation time is short if the performance of the management server is high. When a plurality of persons pass through the gate, the load becomes higher than in the case of (2), and there is a problem that the matching time becomes longer. SUMMARY OF THE INVENTION An object of the present invention is to solve such a problem of the prior art, and can shorten the collation time on the gate device side, and can make a request inquiry of personal identification information performed from a plurality of gate devices to the management server. It is an object of the present invention to provide a gate management system capable of reducing a line load and a server-side load by reducing the amount of data.

[0005]

SUMMARY OF THE INVENTION A feature of the gate management system of the present invention for achieving the above object is to identify a person with respect to verification information downloaded to a gate device from a management server that manages the gate device. A gate management system that inputs characteristic information for identity verification together with the information, the gate device obtains collation information using the identification information as a key, collates the characteristic information with the collation information, opens the gate, and permits the passage of people. , The gate device acquires the time information of the person passing through the gate and sends it to the management server together with the identification information. The management server manages the passage time information corresponding to the identification information of the person, and Prior to the person's gate passing time indicated by the time, the person's verification information is downloaded to the gate device together with the identification information. Further, as a more specific feature of the present invention, personal information (personal identification information and personal characteristic information) is input to an input device, and the gate device inquires collation information for the personal information to a gate management server, and performs gate management. The server downloads the matching vector data of the person by referring to the pass-permission database, and the gate device compares the matching vector data (matching information) with the characteristic information of the person and opens the gate when the person is recognized as the person. Then, the gate device notifies the gate management server that the traffic has been permitted, records the information of the traffic time at that time in the traffic record database, and, based on the history of the traffic time information in the database, the person can use the gate device (or the gate device). Which gate of the device) and which time of day the vehicle is often passed are detected and registered in the traffic permission database. The authentication data of the person (the vector data for matching and the data of the time zone) is downloaded in advance from the database of the traffic permission before the traffic time zone expected to pass through is reached. Is for collating personal information (personal characteristic information) without making an inquiry to the gate management server. At this time, the gate device first stores the matching vector data corresponding to the personal information (personal characteristic information) in a database (personal authentication database) in which the matching vector data is stored corresponding to the identification information of the person in the gate device. ), And if not, inquires the gate management server to download the personal information (personal characteristic information). In addition, the downloaded collation vector data deletes data corresponding to the collation vector data already stored in the gate device, the data having the oldest traffic time zone or the data having passed the valid traffic time zone. And then register. Further, the number of times of travel in the same time zone is added and managed as authentication data, and a person who frequently travels in the same time zone is registered with priority.

[0006]

DESCRIPTION OF THE PREFERRED EMBODIMENTS In the present invention, as described above, collation information, for example, collation vector data, is downloaded to a gate device before a traffic time zone in which a person is expected to pass. Therefore, most of the collation processing when the person passes through the gate can be executed only by the gate device, and the collation time can be shortened. In addition, since the collation processing can be mostly performed only by the gate device, it is less likely that a plurality of gates simultaneously query the server for the personal information. as a result,
Line load and server load can be reduced.
Further, the collation information (collation vector data) may be downloaded by the number of persons who need collation in the traffic time zone, so that the capacity of the collation information in the gate device can be reduced.

[0007]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described below in detail with reference to the drawings. FIG. 1 is a block diagram of a company entry system to which the gate management system of the present invention is applied. 1, a gate management system 21 is configured by connecting a gate management server 10 and a plurality of gate devices 1, 1... Via a LAN or a line L. Gate device 1
Is composed of an input device 2 for inputting personal information, a gate 3, and a data processing terminal device 4. Data processing terminal 4
Is provided with a personal authentication database 49 for storing personal information collation vector data downloaded in advance from the gate management server 10, performs personal collation, and opens the gate 3 when the collation is matched. Gate 3 does not open if there is a mismatch. The data processing terminal device 4 is an MPU 4
1, memory 42, interface 43, communication control circuit 4
4, a timer 45, a display 46 and the like are mutually connected via a bus 47.

An external storage device 48 such as a hard disk, the input device 2 and the gate 3 are connected to the interface 43.
9 is stored. The memory 42 has a personal authentication program 42 as a processing program to be executed by the MPU 41.
a, an authentication data registration program 42b, an unnecessary data deletion program 42c, and the like are stored, and a work area 42d is provided. In addition, the gate management server 10
1 and memory 12, interface 13, communication control circuit 1
4, a monitoring timer 15, a display 16 and the like are mutually connected via a bus 17. Interface 1
3 is connected to an external storage device 18 such as a hard disk, and stores a traffic record database 19 for recording data indicating that a specific individual has passed the gate 3 of the gate device 1 and authentication data for permitting the gate traffic. A recorded traffic permission database 20 is provided. The memory 12 stores, as processing programs executed by the MPU 11, an authentication data transfer program 12a, a traffic recording processing program 12b, a preceding download program 12c at predetermined time intervals, a gate information generation program 12d, and the like. Is provided.

When a person passes through the gate, first, identification information (hereinafter referred to as a user ID) of the person is input to the input device 2 by a card, key input, or the like, and the person is identified by his / her characteristic information (fingerprint feature point or face information). As an input of two-dimensional image data such as feature points of a specific portion, for example, a predetermined finger is touched on a fingerprint reading device (not shown). Gate device 1
Authentication program 42 stored in the memory 42
“a” is called from the main program when the user ID is input to the input device 2 and executed by the MPU 11. When this is executed, the MPU 11
Reads, for example, two-dimensional image data such as a fingerprint feature point from a fingerprint reader as personal identification input data, and refers to the personal authentication database 49 to search for the same user ID using the user ID as a key. Then, collation vector data corresponding to the fingerprint feature point is obtained, and it is determined whether or not the data matches input data, for example, personal identification input data such as a fingerprint. When the collation vector data obtained as a result of the determination matches the personal identification input data indicating a personal characteristic point such as a fingerprint, a signal for opening the gate 3 is transmitted to open the gate for a certain period. Furthermore, when they match,
Data indicating the passage time (units to minutes) together with the user ID is transmitted to the gate management server 10 together with the passage record request command, with the gate device address of the gate device 1 added. When the gate device 1 has a plurality of gates, the gate number through which the person with the user ID has passed is also transmitted at this time. When the user ID is not in the personal authentication database 49, the authentication data registration program 42b is called to send a download request to the gate management server 10 side to obtain personal information. The gate is not opened when the personal information (personal authentication data) is not downloaded.

The authentication data registration program 42b is called by the personal authentication program 42a and executed by the MPU 11 when the user ID input from the input device 2 is not recorded in the personal authentication database 49. When this is executed, a transfer request (download request) of personal information (authentication data) is made with the user ID input to the gate management server 10 as data and the address of its own gate device 1 as a transfer destination address. Then, the downloaded personal information data is registered in the personal authentication database 49. Also, for example, when a periodical download of personal identification information (specific pre-selected authentication data group) from the gate management server 10 at intervals of 15 minutes is received, the authentication data registration program 4
2b is called and executed by the MPU 11. Thus, the contents of the personal authentication database 49 are sequentially updated to the downloaded data. Furthermore, when the storage capacity of the personal authentication database 49 is full when downloaded, the program calls the unnecessary data erasing program 42c to erase the authentication data having a high probability of not requiring collation from the current time. Thereafter, the personal identification information (specific authentication data group previously selected) downloaded and registered in the personal authentication database 49 is stored.

As shown in FIG. 2, the structure of each authentication data in the personal identification information is, as personal information, a user ID data column 49a, a collation vector data column 49b, a passage time zone / passage number column 49c, There are columns 49c for the passage time zone / number of passages, and so on. User ID data field 49
The data stored in a is a user ID (identification information) such as a personal identification number input by an individual from the input device 2, and the data stored in the collation vector data field 49b is a two-dimensional image obtained from a fingerprint or the like. This is vector data indicating a feature point such as data. In this example, a fingerprint feature pattern of about 500 kbytes is recorded. The plurality of traffic time zones / traffic count columns 49c are stored in three-minute intervals, for example, from 7:00 to 7:02:59. This is the number of times the person has passed through the gate during the time period and correspondingly, for example, during the period of one week by 7:02:59. Then, in the personal authentication database 49, such authentication data (personal information for personal confirmation) is stored as a group corresponding to the gate number, for example, for 30 persons. Here, 30 persons is a number slightly larger than the maximum number of passers in the time section described later. For example, in the case of a 8:00 curfew, the maximum number is from 7:57 to 7:59, and if there are 25 people, 5 people are added to the number, and the number becomes 30. In addition,
When one gate device 1 has only one gate, management for each gate number is unnecessary.

The unnecessary data deletion program 42c is called by the authentication data registration program 42b and
11, when this is executed, the personal data unnecessary as authentication data is deleted by referring to the information on the individual travel time zone and the data on the number of times of travel in accordance with the current time. The method of the deletion will be described later.

Next, the gate management server 10 will be described. The authentication data transfer program 12a stored in the memory 12 of the gate management server 10 transmits a request for transfer of personal information (personal authentication data) from the gate device 1. When there is a traffic recording request from the gate device 1 When an interrupt signal indicating the switching time of the traffic time zone is received from the monitoring timer 15 The MPU 11 executes predetermined processing described below under the above three conditions. . When there is a transfer request for personal information from the gate device 1, the MPU 11 executes the authentication data transfer program 12a. By executing this program, M
The PU 11 searches the passage permission database 20 and sends the matching vector data 203a shown in FIG. 4 corresponding to the user ID sent from the gate device 1 to the gate device 1 having the requested address. When a traffic recording request (traffic recording request command) is received from the gate device 1, the traffic recording processing program 12b is called to cause the MPU 11 to execute it.

The traffic recording processing program 12b is an MPU 1
1, the data area 190 corresponding to the gate device address in the traffic record database 19
, Each data block 191 (see FIG. 3) is searched using the user ID as a key, and the gate number in the column 193 recorded following the matching user ID column in the corresponding column 192 is checked and the vehicle is passed. The recorded times (in minutes) are sequentially recorded in the traveling time column 194. The number of recorded passage times is, for example, about 10 to 15 in one week, and when it exceeds this, old data is deleted and updated to new data. When the gate number is not recorded in the column 193, the current gate number is recorded. When the gate number and the gate number recorded in the column 193 are different, a gate number column and a passage time column are added, and a gate number and a passage time are recorded respectively. When only one gate is provided in one gate device 1,
The gate number column 193 is unnecessary. When the processing of the traffic recording processing program 12b is completed, the MPU 11 next calls and executes the gate information generation program 12d.

The gate information generating program 12d executes the MPU after the processing of the traffic recording processing program 12b is completed.
11 to generate the latest gate information. This may be performed periodically. For regular calls,
For example, it may be called after the preceding download processing is performed by interruption of the monitoring timer 15 every 10 minutes. By executing this program, the MPU 11 refers to the passage time in the passage recording database 19 and reads the gate information 2 in the gate information area 206 of the passage permission database 20.
05 is generated and updated. Traffic permission database 20
FIG. 4 shows a data block of one user ID, as shown in FIG. 4, which has a traffic permission data area 200 provided corresponding to the gate device address. In an authentication data recording block 201 in which collation vector data is recorded for each user ID, a matching user ID column 20 is used with the user ID as a key.
Search the data of No. 2. When there is a request for personal information, the matching vector data 203a of the matching vector data area 203 of the matching user ID is read and transferred to the gate device 1 corresponding to the gate device address. At the time of the preceding download, the comparison vector data in the comparison vector data area 203 and the gate information 205 in the gate information column 204 are transferred.

The gate information column 204 contains gate information 205
(Gate number / last updated date column 205a and travel time zone / number of passes 205b... (If the number of travel time zones is plural, plural numbers) are recorded. When the gate numbers are different, gate information areas (ID1 to IDn) 206 are provided and stored in each of them. This gate information column 204
Is a data link with the user ID column 202 as shown by the dotted line and is integrated. The travel time of the travel record database 19 is a travel time up to the minute, but the travel time zone is time information indicating a travel time zone corresponding to each time segmented at 3-minute intervals. As the last update date in the gate number / last update date field 205a, the date when the gate information was updated and registered is recorded. M
The PU 11 executes the gate information generation program 12 d at the time of traffic recording or periodically, and executes the user ID from the data corresponding to the user ID recorded in the traffic recording database 19.
For each D, the data of the traffic time zone and the traffic frequency is generated, searched and generated as the gate information 205 corresponding to the gate number, and the gate information column 204 of the traffic permission database 20 is generated.
Each time the gate number is different, a gate information ID is added and recorded as ID1 to IDn. It should be noted that the traffic time zone is determined from the traffic time of a certain user ID as to which traffic time zone it is in, based on where the time zone is divided into three-minute intervals, and enters the same traffic time zone. The number of passing times can be obtained by counting the number of passing times.

The preceding download program 12c is executed by the MPU 11 when receiving from the monitoring timer 15 an interrupt signal indicating the switching time of the traffic time zone. The execution of this program causes the MPU 11 to, here, for example, monitor the interrupt signal every 10 minutes by the monitoring timer 15.
Occurs, the authentication data in the passage time zone for the gate device 1 from the current time to 15 minutes ahead is retrieved and read from the passage permission database 20, and is sent to the gate device 1 as download data in advance. Here, if the data 15 minutes ahead is downloaded every 10 minutes, more data can be sent than the time to send periodically, so that there is no break in the data. 15 minutes from 5 minutes before
If the data is up to the minute, the authentication data can have a margin of 5 minutes, so that may be used.

By the way, in the traffic permission database 20, the user ID (user name is also acceptable) and the collation vector data 203a are necessary for the collation processing in the gate device 1, so they are collected as data in advance and registered in this. deep. Also, the gate information 205 refers to the traffic record database 19 as described above, and refers to the specific traffic time zone in which the person passes through the gate of the gate device having the gate device address and the number of times during this traffic time zone. Whether or not a person has passed is created based on the time of passage. As can be understood from the above description, the user authentication database 49 stores the user ID
And the vector data for comparison, the time of passage, and the number of times of passage. When a person tries to pass the gate, the information is obtained before the actual matching processing is started (15 minutes before in this embodiment). It is downloaded from the passage permission database 20 of the gate management server 10.

The overall flow of the gate management process of the gate device 1 will be described below with reference to FIG. When a person tries to pass through the gate, the person inputs personal information from the personal information input device 2. As the personal information at this time, a user ID and information (for example, a fingerprint) that can identify the user are input as two-dimensional personal characteristic information (step 101). The gate device 1 searches for data corresponding to the input user ID in the personal authentication database 49 (step 102). If there is no matching vector data (NO condition in step 103), the gate device 1 performs authentication data special recording processing. (Step 200) Inquires the gate management server 10 with the user ID and requests transfer of the personal information (authentication data). Upon receiving the transfer request, the gate management server 10 searches the MPU 11 by executing the authentication data transfer program 12a with reference to the pass-through permission database 20 corresponding to the user ID, and there is authentication data of the user ID. Sometimes, it is read and downloaded to the gate device 1. As a result, is there data in step 104? YE in the judgment of
It becomes S. The processing flow of the authentication data registration processing is as follows.
As shown in FIG. 6, this will be described later.

When the YES condition is satisfied in step 103 or step 104, or when the authentication data is downloaded, the collation vector data is read from the authentication data and collated with the input two-dimensional feature information (step 105). ). Step 1
When the NO condition is reached in 04, the process is terminated without opening the gate (step 105a). When data is downloaded to the personal authentication database 49,
When the database is fully registered (when the data storage area is full of data), the unnecessary data erasing program 42c is called to delete the authentication data having a high probability of not requiring verification from the current time and then downloading the data. The recorded data is recorded in a database (see FIG. 6, described later). The gate device 1 collates the input two-dimensional feature information (feature point information such as a fingerprint that can be identified as the principal) with the collation vector data in the principal authentication database 49 (step 106), and is recognized as the principal. At this time (when the YES condition is satisfied in step 106), the gate 3 is opened (step 107) to allow a person to pass through the gate. At this time, as a traffic recording process, the gate device 1 notifies the gate management server 10 that traffic is permitted in the form of three data of a gate device address, a user ID, and a traffic time, and transmits a traffic recording request. (Step 10
8) The gate management server 10 receives these data and records the passage time in the passage record database 19. In addition,
This will be described with reference to the flowchart of FIG.

FIG. 6 is a flowchart of the authentication data registration process in the gate device 1. First, it is determined whether there is a periodical download of preceding data from the gate management server 10 (step 201). Where NO
Then, a transfer request for the authentication data (identity information) of the identity of the user ID input as the identification information is sent to the gate management server 10 to inquire the identity information (step 202). Next, it is determined whether or not there is a response to the download of the personal information (step 203).
If there is no response from the gate management server 10 for a certain period of time, "no data" is set in the return code (step 204a), and the process proceeds to step 104 in FIG. As a result, the NO condition is satisfied in step 104.
On the other hand, if the result of determination in step 203 is YES,
It is determined whether the storage area of the personal identification database 49 is full (step 204). Here, when the YES condition is satisfied and the condition is full, it is determined whether or not there is data other than the current traffic time zone (step 205).
If YES, the oldest travel time zone data is deleted (step 206).

Here, as for the confirmation information data having a high probability that the collation is unnecessary, the data having the oldest valid traffic time zone of the authentication data or the data having passed the valid traffic time zone is deleted by referring to the traffic time zone 49c. After that, the downloaded data is registered in the personal authentication database 49. Also, when the data is fully registered only with the data of the same traffic time zone, or when there is a large number of data of the same traffic time zone to be deleted, the number of traffics in the same traffic time zone is referred to the traffic frequency 49d. The authentication data of a person with few traffics is deleted, and a person with a high traffic frequency is preferentially left. The amount of data to be deleted at this time is an amount that can store the amount of downloaded data. Therefore, after deletion, in step 207, the downloaded personal information (authentication data) is registered in the personal authentication database 49, and “data present” is set as the return code (step 208), and the process proceeds to step 104 in FIG. as a result,
In step 104, the condition becomes YES.

If the NO condition is satisfied in step 204, the data can be stored. Therefore, it is determined whether or not there is already data in the travel time zone from the current time to 15 minutes ahead of the current time corresponding to the user ID. A determination is made (step 205a). If data of the same traffic time zone already exists for the same user ID, the data of the same traffic time zone downloaded for the same user ID is overwritten (step 206a). enter.
On the other hand, if the NO condition is satisfied in step 205, the MPU 41 executes the unnecessary data erasing program 42c. Here, when the deletion is performed according to the deletion rule described in the above section, the MPU 41 performs A small amount of data is deleted (step 206b). Then, the process proceeds to the previous step 207.

Referring to FIG. 7, a description will be given of the traffic recording request processing in step 108 of FIG. 5 performed by the gate device 1. First, the input user ID is acquired (step 301), the current time is acquired, and the acquired time is used as the gate of a specific gate number of the gate device 1 of the person having the user ID (there is no gate number when there is only one gate). )) (Step 302). Then, the address and gate number of its own gate device 1 are obtained (step 30).
3) The respective data such as the gate number, the gate device address, the passage time, and the user ID are transmitted to the gate management server 10 (step 304), and the process returns to the gate management process of FIG.

Next, processing on the gate management server 10 side will be described. FIG. 8 is a flow of an overall process performed by the MPU 11 executing the authentication data transfer program 12a. The MPU 11 executes the authentication data transfer program 12a and enters a request reception waiting loop. The request reception waiting loop first determines whether there is a data request for personal information (authentication data corresponding to the user ID) from each gate device connected via a line or the like (step 401).
If NO, it is next determined whether or not there is a traffic recording request from each gate device (step 402). If the answer is NO, it is determined whether or not it is time to switch the traffic time zone based on whether or not an interrupt signal is received every 10 minutes from the monitoring timer 15 (step 403).
Then, the process returns to the first step 401.

In the request reception waiting loop, if the answer is YES in step 401, the process enters the personal information data response process in FIG. In the principal information data response process, the source gate device address and the user ID are acquired (step 50).
1) The user ID is searched for by referring to the data area of the passage permission database 20 where the gate device address matches (step 502). Then, it is determined whether or not the same user ID exists in the storage area of the device address of the gate device 1 (step 503). Here, if YES, and there is a user ID, the collation vector data, the travel time zone data, and the number of times of travel are obtained from the travel permission database 20 (step 504), and these data are transferred to the personal information data (user ID The authentication data is transmitted to the gate device 1 (step 50).
5). If the determination in step 503 is NO, the fact that there is no personal information is notified to the gate device 1 (step 506). Then, the process proceeds to step 402 in FIG.

If the answer to the request acceptance waiting loop is YES in step 402, the flow enters the traffic recording process of FIG. The traffic recording processing is executed by the MPU 11 by calling the traffic recording processing program 12b when a traffic recording request is issued from the gate device 1. First, the source gate device address is obtained (step 601), and the gate device 1
(Step 602)
The passage time received from the gate device 1 is acquired (step 603), and when there are a plurality of gates, the gate number is further acquired (step 604). (Step 605).

Thereafter, the gate information generation program 12
d is executed by the MPU 11 to read the passage time (time in minutes) from the current reference data of the passage record database 19, and obtain the acquired user ID, gate number, and 3
The number of times of traffic entering the current traffic time zone from the current traffic time zone according to the time division of the minute is calculated based on the number of traffic times entering the same traffic time zone, based on the current traffic time zone, for example, from 7:00 to 2 minutes 59 seconds. 7:00 as a traffic time to enter the section until,
A count value n is obtained by counting how many pieces of data at 7:00 and 7:00 are present (step 606). Then, the access permission database 20 is searched, and the gate information column 204 is referred to the block of the storage area using the same user ID of the same gate device address as a key, and the current traffic time zone, for example, from 7:00 to 2 minutes. The section up to 59 seconds is searched (step 607), and it is determined whether or not there is data (step 608). If there is no data, the result is NO. In the information field 204, the gate number, the traffic time zone, and the traffic count (the count value n) are registered as new data as gate information IDi (where i is the next registration number of the already registered gate information).

If there is data in the determination in step 608, the result is YES, and the current date and the gate number / last updated date column 2 in the searched gate information column 204 are set.
05, it is determined whether or not the last update date of the data has exceeded a predetermined time, for example, one week from the current date (step 610). Is updated to the count value n (step 611). Also,
If it has been longer than one week, YE
S, and changes the existing traffic count to 1 (step 6).
12). That is, here, the number of times of traffic in a specific traffic time zone in the period up to one week before the latest is managed, and an initial value of 1 is set for a person who passes the gate more than one week after the last time. Treat it.

If YES in step 403 of FIG. 8, each traffic permission data area 200 of the traffic permission database 20 is sequentially searched to obtain data of the next traffic time zone (step 404), and the searched gate number is obtained. The data is downloaded to the gate device having (when there are a plurality of gates in the gate device) (Step 405), the data is searched until the end of the passage permission database 20, and it is determined whether or not the process is completed (Step 406). ). Where N
When the answer is O, the process returns to step 404, and the next data is searched in the traffic permission database 20. When the search is completed up to the end of the traffic permission database 20, the search data ends, and the answer to step 406 is YES. At this time, since the authentication data necessary for the next time zone has been downloaded to each gate device in advance, the process returns to step 401.

Thus, the gate management server 10
Is registered in the traffic record database 19 upon receiving a notice of a traffic record request from the gate device 1, when the user I is registered for the specific gate device (or for each gate number).
The number of times of passage for each D and for each passage time zone is counted and registered in the storage area of the gate information 204 of the passage permission database 20. In addition, when the number of times of travel in the same travel time zone is already registered, if the final registration time of the number of times of registered travel does not exceed a certain period (for example, one week), whether the count value is registered as described above is determined. Alternatively, the current number of times of travel may be further added to the registered number of times of travel. If the period exceeds a certain period, the number of registered registrations is cleared to 0 and then set to 1. In such a case, the authentication data may be forcibly downloaded. Also, as described above, in the present invention, the gate management server 10 searches the traffic permission database 20 before switching to the next traffic time zone, and checks the authentication data of the next traffic time zone, for example, 15 When there is authentication data up to the minute, the data is pre-downloaded to the gate device 1 of the gate device address having the authentication data together with the gate number. As described above, the gate device 1 may overwrite the preceding download data when data in the same traffic time zone is already registered. As a result, when the person travels during the next traffic time zone, the gate device 1 can check the personal information without making an inquiry to the gate management server.

As described above, the travel time zone can be managed, for example, every minute, as the same as the travel time (minutes). In the case where the management is performed for each gate device, the gate number is not always necessary. In the embodiment, an example of entry is given. However, the present invention is not limited to entry, and it is needless to say that the present invention can be applied to general entrance / exit management including various gate passing devices. Further, in the embodiment, the object of the preceding download is selected a predetermined time ahead of the current time with reference to the passage time zone, but the selection from a point before the predetermined time to a point ahead of the predetermined time may be selected. Further, the time that is a predetermined time ahead of the present time may be different depending on the traffic time zone. For example, depending on the entry / exit state of a person passing through the gate, such as every 15 minutes from 7 am to 8 am, every 30 minutes at 9 am, and 60 minutes after 10 am. The preceding period of the data selection of the preceding download can be made different.

[0033]

According to the present invention, collation information, for example, collation vector data is downloaded to the gate device before the traffic time when the person is expected to pass, so that the person is Most of the collation processing when passing through the gate can be executed only by the gate device, and the collation time can be shortened. In addition, since the collation processing can be mostly performed only by the gate device, it is less likely that a plurality of gates simultaneously query the server for the personal information. As a result, the line load and the server load can be reduced. Further, the collation information (collation vector data) may be downloaded by the number of persons who need collation in the traffic time zone, so that the capacity of the collation information in the gate device can be reduced.

[Brief description of the drawings]

FIG. 1 is a block diagram of a company entry system to which a gate management system according to the present invention is applied.

FIG. 2 is an explanatory diagram of a configuration of authentication data in FIG. 1;

FIG. 2 is an explanatory diagram of recorded contents of a traffic record database.

FIG. 4 is an explanatory diagram of recorded contents of an authentication information database.

FIG. 5 is an explanatory diagram of an overall processing flow of gate management of the gate device.

FIG. 6 is an explanatory diagram of a flow of authentication data transfer.

FIG. 7 is an explanatory diagram of a traffic recording process in the gate device.

FIG. 8 is an explanatory diagram of an overall processing flow of the authentication data transfer of the gate management server.

FIG. 9 is an explanatory diagram of a flow of personal information data transfer processing of the gate management server.

FIG. 10 is an explanatory diagram of a traffic recording process of the gate management server.

[Explanation of symbols]

DESCRIPTION OF SYMBOLS 1 ... Gate device, 2 ... Input device, 3 ... Gate, 4 ... Data processing terminal device, 10 ... Gate management server, 11, 42 ... MPU, 12 ... Memory, 12a ... Authentication data transfer program, 12b ... Traffic recording processing program Reference numeral 15: Monitoring timer, 16: Display, 17: Bus, 18, 48: External storage device, 19: Traffic record database, 20: Traffic permission database, 21: Gate management system, 41: MPU, 42: Memory, 42a ... 42b: Unnecessary data erasing program, 42b: Work area, 43: Interface, 44: Communication control circuit, 45: Timer, 46: Display, 47: Bus, 49: Personal authentication database .

──────────────────────────────────────────────────続 き Continued on the front page (51) Int.Cl. ⁷ Identification symbol FI theme coat ゛ (reference) G06K 17/00 G06K 17/00 VF term (reference) 2E250 AA12 BB05 BB25 BB30 BB47 CC11 CC14 DD03 DD07 DD09 EE03 FF18 FF43 FF44 3E038 AA01 BA01 BB05 CA02 CA03 EA02 FA10 GA02 HA05 JA01 JB10 5B058 KA01 KA37 KA38 YA11

Claims (4)

[Claims] An identification server and identification information for personal identification are input to collation information downloaded to a gate device from a management server that manages the gate device, and the gate device uses the identification information as a key. A gate management system that obtains the collation information, collates the feature information with the collation information, opens a gate, and allows a person to pass; the gate device includes: time information when the person passes through the gate; And sends it to the management server together with the identification information, wherein the management server manages the travel time information in accordance with the identification information of the principal, and the gate traffic of the principal indicated by the travel time. A gate management system, wherein the verification information of the principal is downloaded to the gate device together with the identification information before a time. 2. The management server has a traffic time zone database for recording traffic time zones divided according to a predetermined time interval corresponding to the identification information, and the traffic time zone has the identification information. The travel time zone of the time segment in which the time indicated by the travel time information of the principal enters, and the management server refers to the information of the travel time zone of the principal and downloads the information before the gate travel time of the principal. The gate management system according to claim 1. 3. The management server further includes a traffic record database that records traffic time information in correspondence with the identification information, and the traffic record database includes a plurality of traffic time information for one piece of the identification information. Information is recorded, and the traffic time zone database records the traffic time zone and the number of times the traffic time information is included in the traffic time zone as the traffic frequency, and the management server performs verification information along with the identification information of the person. 3. The gate management system according to claim 2, wherein the number of times of travel and the number of times of travel are downloaded. 4. The management server according to claim 1, wherein said management server refers to the data in said traffic time zone, selects said data to be downloaded a predetermined time ahead of a current time, and performs said data periodically. The apparatus has a database that stores the identification information, the collation information, the travel time zone, and the number of times of travel downloaded from the management server, and refers to the collation information by referring to the travel time zone and the number of times of travel. 4. Deleted unnecessary data including the above and store the downloaded data in the database.
Gate management system as described.