Traffic management system, traffic management method, program, and traffic control device

Abstract

To provide a passage management system, a passage management method, a program, a passage management device, and a passage control device that can prevent an erroneous determination when determining whether or not to permit passage using face authentication.SOLUTION: A passage management system of an embodiment includes a determination unit. The determination unit acquires a first determination result of, based on a picked-up image of a face of a passerby picked up using a camera provided along a passageway, determining whether or not the passerby is a registrant, a second determination result of, based on efficacy information indicating efficacy that the registrant has, determining whether or not passage of the passageway is possible with the efficacy that the registrant has, and a third determination result of, based on information acquired by a wireless reader unit provided along the passageway and identification information on an auxiliary ticket issued in advance for the registrant, determining whether or not the passerby holds the auxiliary ticket, and determines whether or not to permit passing of the passerby based on the first determination result, the second determination result, and the third determination result having been acquired.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] An embodiment of the present invention relates to a traffic management system, a traffic management method, a program, a traffic management device, and a traffic control device. [Background technology]

[0002] There is known a facility that performs face authentication processing based on a facial image of a visitor who is about to enter the facility, and when the visitor is authenticated by the face authentication processing, allows the visitor to enter the facility using the authority of the authenticated registered person. However, if the visitor is mistakenly recognized as a different person by the face authentication processing, there is a risk that the visitor may enter the facility using the authority of the different person. For this reason, there are cases where an unauthorized visitor is allowed to enter, or an authorized visitor is allowed to enter the facility using the authority of the different person. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2017-224186 A Summary of the Invention [Problem to be solved by the invention]

[0004] The problem that the present invention aims to solve is to provide a traffic management system, a traffic management method, a program, a traffic management device, and a traffic control device that can prevent erroneous judgments when determining whether or not a person can pass using facial recognition. [Means for solving the problem]

[0005] The passage management system of the embodiment has a determination unit, which obtains a first determination result of determining whether or not the pedestrian is a registered person based on an image of the face of the pedestrian captured by a camera installed along the passage, a second determination result of determining whether or not the pedestrian is allowed to pass through the passage with the validity held by the pedestrian based on validity information indicating the validity held by the pedestrian, and a third determination result of determining whether or not the pedestrian has an auxiliary ticket based on information obtained by a wireless reader unit installed along the passage and identification information of the auxiliary ticket issued in advance to the pedestrian, and determines whether or not to permit the pedestrian to pass through based on the obtained first, second, and third determination results, and outputs the determined result to the passage control device. [Brief description of the drawings]

[0006] [Figure 1] 1 is a diagram showing an example of an overall system 1 including a traffic management system according to an embodiment. [Diagram 2] FIG. 2 is a diagram for explaining an overview of the process at the time of ticket issuance in the overall system 1 of the embodiment. [Diagram 3] FIG. 2 is a diagram for explaining an overview of a process performed when passing through the entire system 1 according to the embodiment. [Figure 4] FIG. [Diagram 5] FIG. 2 is a top view of the automatic ticket gate 200. [Figure 6] FIG. 2 is a configuration diagram of an automatic ticket gate 200 with a focus on a control unit 220. [Figure 7] FIG. 3 is a diagram showing the configuration of a face search server 300. [Figure 8] FIG. 13 is a diagram showing an example of the contents of a registration information DB table 351. [Figure 9] FIG. 4 is a diagram showing the configuration of a ticket judgment server 400. [Figure 10] FIG. 13 is a diagram showing an example of the contents of a ticket DB table 451. [Figure 11] FIG. 11 is a sequence diagram showing an example of a process performed when issuing a ticket in the passage management system. [Figure 12]FIG. 11 is a sequence diagram showing an example of a process (part 1) at the time of passage in the passage management system. [Figure 13] FIG. 11 is a sequence diagram showing an example of a process (part 2) at the time of passage in the passage management system. [Figure 14] FIG. 11 is a sequence diagram showing an example of a process (part 3) at the time of passage in the passage management system. [Figure 15] FIG. 11 is a sequence diagram showing an example of a process (part 4) at the time of passage in the passage management system. [Figure 16] FIG. 1 is a diagram showing an example of a traffic management system according to an embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0007] Hereinafter, a traffic management system, a traffic management method, a program, a traffic management device, and a traffic control device according to embodiments will be described with reference to the drawings.

[0008] 1 is a diagram showing an example of an overall system 1 including a passage management system of an embodiment. The overall system 1 includes, for example, one or more ticket issuing machines 100, one or more automatic ticket gates 200, a face search server 300, and a ticket judgment server 400. Below, an example of the passage management system of this embodiment configured with the automatic ticket gates 200, the face search server 300, and the ticket judgment server 400 will be described.

[0009] One or more ticket issuing machines 100 and one or more automated ticket gates 200 are connected to a face search server 300 via a network NW. The face search server 300 is connected to a ticket judgment server 400 via the network NW. The network NW includes, for example, the Internet, a wide area network (WAN), a local area network (LAN), a provider device, a wireless base station, etc. The ticket issuing machine 100 and the automated ticket gate 200 may be directly connected to the ticket judgment server 400 via the network NW.

[0010] FIG. 2 is a diagram for explaining an overview of the process at the time of ticket issuing in the overall system 1 of the embodiment.

[0011] The ticket issuing machine 100 is installed, for example, outside the ticket gates of railway facilities, and issues digital tickets for using the railway facilities. A digital ticket is a ticket that is different from a ticket in which necessary information is written onto a magnetic ticket, and is a virtual ticket in which passability is determined using ticket validity information managed by a server. However, the present invention is not limited to this, and the ticket issuing machine 100 may issue various digital tickets for admission to facilities such as exhibitions, fairs, amusement parks, movie theaters, etc.

[0012] The automated ticket gate 200 is installed, for example, at the entrance or exit of a railway facility, and allows or prohibits a user from passing through using a digital ticket. The automated ticket gate 200 is an example of a traffic control device. The traffic control device is not limited to this, and may be a device installed at the entrance of a facility such as an exhibition, fair, amusement park, movie theater, etc., and determines whether or not to permit entry to these facilities. In this case, the ticket issuing machine 100 may be installed at the entrance of these facilities.

[0013] For example, the ticket issuing machine 100 executes a registration process to register a face in advance for use in the automatic ticket gate 200 according to an operation by a user. The face registration process includes, for example, a process of capturing an image of a user's face to acquire face image data of the user, a process of calculating face feature amount data (hereinafter, referred to as first face feature amount data) from the acquired face image data, and a process of transmitting the calculated first face feature amount data to the face search server 300. The face feature amount data is data related to face feature amount. The face registration process is not limited to this, and may include a process of accepting various information (attribute information such as the name, sex, and age of the registrant, a payment method for the fare of the digital ticket, a credit card number, a management number for managing the charged electronic money, etc.) and transmitting it to the face search server 300. In addition, in this embodiment, an example in which the ticket issuing machine 100 calculates the first face feature amount data will be described, but the present invention is not limited to this, and the ticket issuing machine 100 may transmit face image data to the face search server 300, and the face search server 300 may calculate the first face feature amount data.

[0014] In addition, the ticket issuing machine 100 executes, in accordance with operations by a user, a digital ticket issuing process for issuing a specified digital ticket to a registered user whose face has been registered, and a supplementary ticket issuing process for issuing a supplementary ticket 500 linked to the digital ticket.

[0015] The digital ticket issuance process includes a process for accepting purchase conditions from a user, a process for settling the fare for the digital ticket based on the accepted purchase conditions, a process for registering validity information of the digital ticket after settlement has been completed in the ticket judgment server 400, a process for generating unique identification information (hereinafter referred to as a ticket ID) that identifies each digital ticket and registering it in the ticket judgment server 400. The purchase conditions include, for example, the type of ticket to be purchased, the section for which the ticket is to be used, the period for which the ticket is to be used, the amount of the ticket fare, etc.

[0016] The supplementary ticket issuance process includes a process for physically issuing the supplementary ticket 500 linked to the digital ticket, and a process for generating unique identification information (hereinafter referred to as the supplementary ticket ID) that identifies each supplementary ticket 500 and registering it in the face search server 300.

[0017] The supplementary ticket 500 is composed of, for example, an RFID (radio frequency identifier) ​​tag, and a unique EPC (Electronic Product Code) is stored in the RFID. The EPC is an example of identification information that identifies each supplementary ticket 500. The supplementary ticket 500 performs short-range (several centimeters to several meters depending on the frequency band) wireless communication using an electromagnetic field, radio waves, etc. For example, the supplementary ticket 500 uses UHF (Ultra High Frequency), which is radio waves with a frequency of 300 MHz to 3 GHz.

[0018] The auxiliary ticket 500 operates in a mode in which wireless communication is started when, for example, an EPC embedded in an RFID tag is specified and an instruction to start wireless communication is issued. In other words, the auxiliary ticket 500 that employs this mode does not execute wireless communication if the EPC embedded in its own RFID tag is different from the specified EPC.

[0019] Without being limited thereto, the auxiliary ticket 500 may read out the auxiliary ticket ID embedded in the RFID tag and transmit it by wireless communication when it enters the communication area of ​​the wireless reader for short-distance wireless communication. Furthermore, the auxiliary ticket 500 is not limited to an RFID tag, and may be any non-contact medium that can be captured within a range of several meters, and may be a non-contact IC card that exchanges information by wireless communication, or a terminal capable of short-distance wireless communication (for example, a smartphone, a tablet terminal, etc.).

[0020] In addition, the ticket issuing machine 100 associates the information obtained by the face registration process, the information obtained by the digital ticket issuance process, and the information obtained by the supplementary ticket issuance process with each other, and transmits them to the face search server 300.

[0021] The face search server 300 registers, from among the information received from the ticket issuing machine 100, information necessary for face search processing by the face search server 300 in its own database. For example, the face search server 300 registers the first facial feature amount data received from the ticket issuing machine 100 in its own database. The face search server 300 may also generate identification information (hereinafter, referred to as a registrant ID) for identifying the registrant who registered the first facial feature amount data, and register the first facial feature amount data in its own database in association with the registrant ID. The registrant ID may be generated in the ticket issuing machine 100 and transmitted from the ticket issuing machine 100 together with the first facial feature amount data.

[0022] The face search server 300 also transmits to the ticket validation server 400 information in which the registrant ID generated in the registration process is associated with information required for the ticket validation process among the information received from the ticket issuing machine 100 .

[0023] The ticket judgment server 400 registers in its own database the information received from the face search server 300. For example, the ticket judgment server 400 receives information indicating the purchase conditions of the digital ticket, information indicating that the payment for the digital ticket has been completed, a ticket ID, etc. from the ticket issuing machine 100, and registers them in its own database.

[0024] FIG. 3 is a diagram for explaining an overview of the process at the time of passage in the overall system 1 of the embodiment.

[0025] The automated ticket gate 200, for example, uses a camera provided therein to capture an image of the face of a pedestrian entering a station (or exiting a station), and calculates facial feature amount data (hereinafter, referred to as second facial feature amount data) from the facial image data of the pedestrian. The automated ticket gate 200 transmits information in which the calculated second facial feature amount data is associated with entry information relating to entry (or exit information relating to exit), to the face search server 300. The entry information includes, for example, information indicating the entry station and information indicating the entry date and time. The exit information includes, for example, information indicating the exit station and information indicating the exit date and time.

[0026] The face search server 300 executes a face recognition process to determine whether or not a passerby is a registered person based on a comparison result of the second face feature amount data received from the automated ticket gate 200 and the registered first face feature amount data, and a search process to search for a ticket ID or a supplementary ticket ID associated with the authenticated registered person based on the result of the face recognition process. The face recognition process and the search process are collectively referred to as a face search process. The face search server 300 transmits information indicating the recognition result of the face recognition process and the search result of the search process to the ticket determination server 400.

[0027] When the face search server 300 authenticates that a passerby is a registrant, the passenger ticket judgment server 400 executes a process (hereinafter referred to as a passenger ticket judgment process) to determine whether or not the registrant's validity allows passage through the passage of the automated ticket gate 200, based on the validity information indicating the validity held by the registrant. In the passenger ticket judgment process, for example, the passenger ticket judgment server 400 refers to the validity information registered in advance, and determines whether or not the registrant's validity allows passage, based on the passenger ticket ID and the entry information (or exit information) received from the face search server 300.

[0028] When the face authentication process of the face search server 300 determines that the passer is a registered person and the ticket determination process of the ticket determination server 400 determines that the passer can pass with the validity of the ticket, the automatic ticket gate 200 executes the supplementary ticket confirmation process. The supplementary ticket confirmation process is a process for determining whether or not the supplementary ticket 500 owned by the passer matches the supplementary ticket 500 issued to the registered person when the digital ticket is issued. For example, the automatic ticket gate 200 executes the supplementary ticket confirmation process by collating the supplementary ticket ID stored in the RFID tag of the supplementary ticket 500 owned by the passer with the supplementary ticket ID registered in the face search server 300 in advance. When it is determined that the supplementary ticket 500 owned by the passer matches the supplementary ticket 500 issued to the registered person, the automatic ticket gate 200 determines, as a comprehensive determination result, that the passer is allowed to pass.

[0029] In this way, even if the face recognition process determines that a pedestrian is a registered person and the ticket determination process determines that the pedestrian can pass through with the validity of the ticket, the automatic ticket gate 200 can not allow the pedestrian to pass if the supplementary ticket 500 held by the pedestrian does not match the supplementary ticket 500 issued to the pedestrian. Therefore, even if the pedestrian is mistakenly recognized as a different person by the face recognition process, it is possible to prevent a situation in which the pedestrian is mistakenly allowed to pass.

[0030] [Automatic ticket gate 200] 4 is a perspective view of the automated ticket gate 200. The automated ticket gate 200 includes a master unit 210 and a slave unit 230. A camera unit 210A is mounted on the upper surface of the slave unit 230. The camera unit 210A includes a camera 211 that captures an image of the face of a passerby.

[0031] 5 is a view of the automatic ticket gate 200 as seen from above. The master unit 210 and the slave unit 230 are housings that form one passageway. For example, the master unit 210 and the slave unit 230 are arranged opposite each other to form a passageway 10 that connects a first area and a second area that are partitioned from each other. For example, the first area is outside the station premises, and the second area is inside the station premises. The master unit 210 and the slave unit 230 are wirelessly connected by LAN communication or short-range communication, or may be connected via a cable.

[0032] The main unit 210 includes, for example, a wireless reader unit 212, an upper display unit 213, a front display unit 214, a door unit 217, passage sensors 219-1 to 219-4, and a control unit 220. Hereinafter, when the passage sensors 219-1 to 219-4 are not to be distinguished from one another, the symbols following the hyphen (-) will be omitted and the sensors will simply be referred to as the passage sensors 219.

[0033] The slave unit 230 includes the above-mentioned camera unit 210A and a door section 218. The camera unit 210A is installed at the end of the slave unit 230 on the second area side, at the end on the exit side of the path a that passes through the passage 10 from the first area to the second area. The door section 218 is provided at a position facing the door section 217.

[0034] Camera 211 includes a solid-state imaging element such as a CCD (Charge Coupled Device) or a CMOS (Complementary Metal Oxide Semiconductor). Camera 211 is provided along passage 10, captures an image of a face of a pedestrian who is about to pass through passage 10 on route a, and transmits the captured image data to control unit 220 via slave 230. For example, camera 211 is provided at a height and angle that captures an image of a predetermined range equivalent to the height of the face of a pedestrian on passage 10 (for example, a range of 140 to 180 [cm] from the ground on passage 10).

[0035] 6 is a configuration diagram of the automated ticket gate 200, focusing on the control unit 220. In addition to the above-mentioned components, the control unit 220 is further connected to a communication unit 240 and a storage unit 250. Note that the illustration of the wireless communication connection between the master unit 210 and the slave unit 230 is simplified.

[0036] The wireless reader unit 212 includes a reader / writer 212A and an encoding / decoding unit 212B. The reader / writer 212A communicates with the RFID tag of the supplementary ticket 500 held over its reader face. The reader / writer 212A includes, for example, an antenna, and transmits the supplementary ticket ID and the like using a predetermined frequency band.

[0037] The encoding / decoding unit 212B encrypts information (e.g., auxiliary ticket ID) instructed by the entrance / exit processing unit 223 and outputs it to the reader / writer 212A, and the reader / writer 212A transmits the information input from the encoding / decoding unit 212B to the auxiliary ticket 500. In addition, the encoding / decoding unit 212B decodes (decodes) the encoded information (e.g., auxiliary ticket ID) read from the RFID tag of the auxiliary ticket 500 by the reader / writer 212A and outputs it to the entrance / exit processing unit 223.

[0038] The top display unit 213 is a display unit installed on the top surface of the master unit 210. The front display unit 214 is a display unit installed on the front surface of the first area side. The door unit 217 performs an opening operation or a closing operation together with the door unit 218. The passage sensors 219 are provided, for example, on the side surface of the master unit 210 on the aisle side. The passage sensors 219 detect users in the aisle 10 formed by the automated ticket gate 200. The passage sensors 219 are realized, for example, by infrared sensors or optical sensors. The passage sensors 219 may detect users in the aisle in cooperation with a passage sensor provided on the opposing slave unit 230.

[0039] The communication unit 240 includes, for example, a communication interface such as a NIC. The communication unit 240 communicates with the face search server 300 via a communication network such as a LAN under the control of the control unit 220. The storage unit 250 is realized by, for example, a random access memory (RAM), a read only memory (ROM), or a hard disk drive (HDD). The storage unit 250 stores a program executed by the processor, and also stores station information 251 including identification information of each station. The station information 251 includes, for example, identification information of the station where the automatic ticket gate 200 is installed.

[0040] The control unit 220 includes, for example, an image processing unit 221, a communication processing unit 222, an entrance / exit processing unit 223, a door control unit 224, and an output control unit 225. Some or all of these functional units are realized by, for example, a processor such as a CPU (Central Processing Unit) executing a program (software) stored in the storage unit 250. In addition, some or all of the functions of these components may be realized by hardware (including circuitry) such as an LSI (Large Scale Integration), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a GPU (Graphics Processing Unit), or may be realized by cooperation between software and hardware. The program may be stored in a storage device such as an HDD (Hard Disk Drive) or a flash memory in advance, or may be stored in a removable storage medium such as a DVD or a CD-ROM, and installed by mounting the storage medium in a drive device.

[0041] The image processing unit 221 executes a predetermined image processing on the captured image captured by the camera 211. For example, the image processing unit 221 calculates second facial feature amount data indicating facial features included in the captured image captured by the camera 211. Note that the predetermined image processing by the image processing unit 221 employs a method similar to the method of calculating the first facial feature amount data.

[0042] The communication processing unit 222 uses the communication unit 240 to transmit the second face feature amount data calculated by the image processing unit 221 to the face search server 300 via the network NW. On the other hand, the communication processing unit 222 uses the communication unit 240 to receive the ticket determination result, the supplementary ticket ID, and the like transmitted from the face search server 300 via the network NW, and outputs them to the entrance / exit processing unit 223.

[0043] The entrance / exit processing unit 223 detects the presence and passing direction of a pedestrian based on the detection result of the passage sensor 219. For example, when the passage sensor 219-1 detects a pedestrian before the other passage sensors, the entrance / exit processing unit 223 determines that there is a pedestrian (enterer) entering the passage 10 from the first area. On the other hand, when the passage sensor 219-4 detects a pedestrian before the other passage sensors, the entrance / exit processing unit 223 determines that there is a pedestrian (enterer) entering the passage 10 from the second area. When an entrant is detected, the entrance / exit processing unit 223 generates entry information. Note that the automated ticket gate 200 does not manage the passage of entrants, so when it determines that there is an entrant, it instructs the output control unit 225 to notify the pedestrian that passage is not possible.

[0044] Furthermore, when the ticket determination result received from the face search server 300 is "ticket validity OK", the entrance / exit processing unit 223 executes a supplementary ticket confirmation process. The entrance / exit processing unit 223 is an example of a supplementary ticket confirmation unit. The supplementary ticket confirmation process is a process for determining whether or not a passerby has a supplementary ticket 500 based on information acquired by the wireless reader unit 212 and the supplementary ticket ID of the supplementary ticket 500 issued in advance to a registered user.

[0045] For example, if the entry / exit processing unit 223 determines, based on information obtained from the RFID tag of the supplementary ticket 500 by the wireless reader unit 212, that the supplementary ticket ID (EPC) of the supplementary ticket 500 held by a passerby matches the supplementary ticket ID (EPC) of a supplementary ticket issued in advance to a registered person, it determines that the passerby is in possession of a supplementary ticket issued in advance to a registered person.

[0046] More specifically, the entrance / exit processing unit 223 executes a mode of capturing only an RFID that holds an optional auxiliary ticket ID. For example, the entrance / exit processing unit 223 transmits a request signal including the auxiliary ticket ID received from the face search server 300 from the wireless reader unit 212. If an answer signal is received via the wireless reader unit 212 within a predetermined time, the entrance / exit processing unit 223 determines that the RFID that holds the auxiliary ticket ID received from the face search server 300 has been captured.

[0047] Without being limited to this, the entrance / exit processing unit 223 may execute a mode of capturing all RFIDs present within the radio wave range of the wireless reader unit 212. For example, when the entrance / exit processing unit 223 receives an auxiliary ticket ID from the face search server 300, it transmits a request signal from the wireless reader unit 212. When an answer signal is received via the wireless reader unit 212 within a predetermined time, the entrance / exit processing unit 223 determines whether the auxiliary ticket ID included in the received answer signal matches the auxiliary ticket ID received from the face search server 300, and if they match, determines that the RFID holding the auxiliary ticket ID received from the face search server 300 has been captured.

[0048] The entrance / exit processing unit 223 also functions as a decision unit that decides whether or not to permit a pedestrian to pass based on the judgment results of the face authentication processing, the judgment results of the passenger ticket judgment processing, and the judgment results of the supplementary ticket confirmation processing. For example, if the face authentication processing determines that the pedestrian is a registered person, the passenger ticket judgment processing determines that the pedestrian is allowed to pass with the validity of the registered person, and the supplementary ticket confirmation processing determines that the pedestrian is in possession of the supplementary ticket 500, the entrance / exit processing unit 223 determines as a comprehensive judgment result that the pedestrian is permitted to pass.

[0049] For example, if the entrance / exit processing unit 223 determines through the auxiliary ticket confirmation process that the auxiliary ticket 500 held by the passerby is the same as the auxiliary ticket 500 held by the facially authenticated registered user, the entrance / exit processing unit 223 determines as a comprehensive determination result that the passerby is permitted to pass. On the other hand, if the entrance / exit processing unit 223 determines that the auxiliary ticket 500 held by the passerby is not the same as the auxiliary ticket 500 held by the facially authenticated registered user, the entrance / exit processing unit 223 determines as a comprehensive determination result that the passerby is not permitted to pass.

[0050] When the passenger ticket determination result received from the face search server 300 is "passenger ticket invalid", the entrance / exit processing unit 223 does not execute the supplementary ticket confirmation process.

[0051] An example of the auxiliary ticket confirmation process will be described. The entrance / exit processing unit 223 judges whether the auxiliary ticket 500, which stores the auxiliary ticket ID received from the face search server 300 in the RFID tag, is present within the communication area. For example, the entrance / exit processing unit 223 uses the wireless reader unit 212 to transmit the auxiliary ticket ID received from the face search server 300. If the received auxiliary ticket ID matches the auxiliary ticket ID stored in the RFID tag, the auxiliary ticket 500 transmits an answer signal. On the other hand, if the received auxiliary ticket ID does not match the auxiliary ticket ID stored in its own RFID tag, the auxiliary ticket 500 does not transmit an answer signal. If the entrance / exit processing unit 223 receives an answer signal, it judges that the auxiliary ticket 500 owned by the passerby matches the auxiliary ticket 500 owned by the face-authenticated registered user, and determines, as a comprehensive judgment result, that the passerby is permitted to pass. On the other hand, if the answer signal is not received, the entrance / exit processing unit 223 determines, as a comprehensive judgment result, that the passerby is not permitted to pass.

[0052] The door control unit 224 is a restriction mechanism that restricts passage through the passage 10 , and operates the door units 217 and 218 in response to a door control signal output from the entrance / exit processing unit 223 .

[0053] The output control unit 225 generates, for example, an image according to the processing result by the entrance / exit processing unit 223, and displays it on the top display unit 213. The output control unit 225 also generates an image indicating whether or not entry into the passage 10 is possible, and displays it on the front display unit 214.

[0054] [Face Search Server 300] 7 is a configuration diagram of the face search server 300. The face search server 300 includes, for example, a communication unit 310, a control unit 330, and a storage unit 350. The communication unit 310 includes, for example, a communication interface such as a NIC. The communication unit 310 communicates with the ticket issuing machine 100, the automatic ticket gate 200, and the ticket judgment server 400 via the network NW under the control of the control unit 330. The storage unit 350 is realized, for example, by a RAM, a ROM, a HDD, etc. The storage unit 350 stores a program executed by the processor, as well as a registration information DB table 351, etc.

[0055] The control unit 330 includes, for example, a registration unit 331, a face authentication processing unit 332, a search unit 333, and a linking unit 334. Some or all of these functional units are realized by, for example, a processor such as a CPU executing a program (software) stored in the storage unit 350. Some or all of the functions of these components may be realized by hardware (including circuitry) such as an LSI, ASIC, FPGA, or GPU, or may be realized by cooperation between software and hardware. The program may be stored in a storage device such as an HDD or flash memory in advance, or may be stored in a removable storage medium such as a DVD or CD-ROM, and installed by mounting the storage medium in a drive device.

[0056] The registration unit 331 uses the communication unit 310 to store the information received from the ticket issuing machine 100 via the network NW as a part of the registration information DB table 351 in the storage unit 350. The registration unit 331 issues a registrant ID for each registrant, and uses the registrant ID to store the information received from the ticket issuing machine 100 for each registrant.

[0057] 8 is a diagram showing an example of the contents of the registration information DB table 351. The registration information DB table 351 is, for example, a group of information in which a registrant ID is associated with first facial feature amount data, a ticket ID, and a supplementary ticket ID.

[0058] When the face authentication processing unit 332 receives the second face feature amount data indicating the facial feature amount of the passer from the automatic ticket gate 200, the face authentication processing unit 332 refers to the registration information DB table 351 in the storage unit 350 and performs face authentication processing to prove that the passer is a registered person who has been registered in advance. For example, the face authentication processing unit 332 calculates a matching score indicating the degree of similarity between the first face feature amount data of all registered persons registered in the registration information DB table 351 and the second face feature amount data of the passer received from the automatic ticket gate 200 for each registered person, and determines a registered person who is recognized as the same person as the passer based on the calculated matching score. The face authentication processing unit 332 may calculate the feature amount data using any method generally used in face authentication processing.

[0059] The search unit 333 searches the storage unit 350 based on the processing result by the face recognition processing unit 332, and obtains, as a search result, the passenger ticket ID and the supplementary ticket ID associated with the registered person who is recognized as the same person as the passerby by the face recognition processing. Then, the search unit 333 transmits the passenger ticket ID associated with the registered person obtained by the search to the passenger ticket judgment server 400 via the network NW using the communication unit 310.

[0060] In addition, if the facial recognition process determines that the passerby is not the same person as any of the registered persons, the search unit 333 instructs the collaboration unit 334 to transmit information indicating that the passerby was not recognized as a registered person by the facial recognition process to the automatic ticket gate 200 that transmitted the second facial feature data.

[0061] The cooperation unit 334 transmits and receives information to cooperate with the processing by the face search server 300 and the processing by the passenger ticket judgment server 400. For example, the cooperation unit 334 transmits, using the communication unit 310, information required for the passenger ticket judgment processing among the information received from the ticket issuing machine 100, to the passenger ticket judgment server 400. For example, the cooperation unit 334 transmits information indicating the purchase conditions for the digital passenger ticket, information indicating that the settlement for the digital passenger ticket has been completed, and a passenger ticket ID to the passenger ticket judgment server 400. In addition, the cooperation unit 334 transmits, using the communication unit 310, entrance information (or exit information) received from the automatic ticket gate 200 to the passenger ticket judgment server 400.

[0062] Furthermore, when the face authentication determines that the passerby is a registered person, the cooperation unit 334 transmits information indicating the result of the face authentication process together with the ticket ID to the ticket determination server 400. On the other hand, when the face authentication determines that the passerby is not a registered person, the cooperation unit 334 transmits the result of the face authentication process to the automated ticket gate 200.

[0063] Furthermore, the cooperation unit 334 uses the communication unit 310 to transmit the result of the passenger ticket judgment process received from the passenger ticket judgment server 400 via the network NW to the automated ticket gate 200 via the network NW. For example, if the passenger ticket judgment process determines that the passenger ticket is valid and can pass through, the cooperation unit 334 transmits information indicating the passenger ticket judgment result to the automated ticket gate 200 together with the auxiliary ticket ID (auxiliary ticket ID associated with the registered user ID recognized as the same person) previously read out by the search unit 333. On the other hand, if the passenger ticket judgment process determines that the passenger ticket is not valid and can pass through, the cooperation unit 334 transmits only the information indicating the passenger ticket judgment result to the automated ticket gate 200.

[0064] [Ticket Judgment Server 400] 9 is a configuration diagram of the passenger ticket determination server 400. The passenger ticket determination server 400 includes, for example, a communication unit 410, a control unit 430, and a storage unit 450. The communication unit 410 includes, for example, a communication interface such as a NIC. The communication unit 410 communicates with the face search server 300 via the network NW under the control of the control unit 430. The storage unit 450 is realized, for example, by a RAM, a ROM, a HDD, etc. The storage unit 450 stores the programs executed by the processor, as well as a passenger ticket DB table 451, etc.

[0065] The control unit 430 includes, for example, a registration unit 431, a validity determination unit 432, and an update unit 433. Some or all of these functional units are realized by, for example, a processor such as a CPU executing a program (software) stored in the storage unit 350. Some or all of the functions of these components may be realized by hardware (including circuitry) such as an LSI, ASIC, FPGA, or GPU, or may be realized by a combination of software and hardware. The program may be stored in a storage device such as an HDD or flash memory in advance, or may be stored in a removable storage medium such as a DVD or CD-ROM, and installed by mounting the storage medium in a drive device.

[0066] The registration unit 431 uses the communication unit 410 to store the information received from the face search server 300 via the network NW as a part of the ticket DB table 451 in the storage unit 450. The registration unit 431 stores the information received from the ticket issuing machine 100 for each registrant by using the registrant ID.

[0067] 10 is a diagram showing an example of the contents of the passenger ticket DB table 451. The passenger ticket DB table 451 is a group of information in which, for example, a passenger ticket ID is associated with digital ticket validity information, information indicating whether the digital ticket has been paid for, and information indicating the status of the passenger ticket. The digital ticket validity information is, for example, information indicating the purchase conditions of the digital ticket, and includes, for example, the type of ticket to be purchased, the section for which the ticket can be used, the period for which the ticket can be used, the amount of the ticket fare, etc.

[0068] When the face search server 300 authenticates that the passerby is a registrant, the validity determination unit 432 refers to the passenger ticket DB table 451 and determines whether the registrant's validity allows passage through the passage based on the validity information of the registrant whose face has been authenticated. For example, when the validity determination unit 432 receives a passenger ticket ID from the face search server 300, it determines that the face search server 300 authenticates that the passerby is a registrant, and determines whether the registrant's validity allows passage through the passage based on the validity information associated with the received passenger ticket ID.

[0069] For example, when condition 1 (being within the usage section), condition 2 (being within the usage period), condition 3 (payment has been completed), and condition 4 (not being used), are satisfied, the validity determination unit 432 determines that the registrant is allowed to pass through the passage with the validity that the registrant has. For example, when information indicating the entrance station included in the entrance information received from the face search server 300 is included in the usage section of the passenger ticket included in the validity information, the validity determination unit 432 determines that condition 1 is satisfied. For example, when date and time information included in the entrance information received from the face search server 300 is included in the usage period of the passenger ticket included in the validity information, the validity determination unit 432 determines that condition 2 is satisfied. For example, when information indicating whether or not payment has been completed for the digital passenger ticket associated with the passenger ticket ID received from the face search server 300 in the passenger ticket DB table 451 is information indicating completion of payment, the validity determination unit 432 determines that condition 3 is satisfied. For example, when the information indicating the ticket status associated with the ticket ID received from the face search server 300 in the ticket DB table 451 indicates that the ticket is unused, the validity determination unit 432 determines that condition 4 is met.

[0070] The validity determination unit 432 transmits information indicating the result of the ticket validation process to the face search server 300.

[0071] When the automated ticket gate 200 determines as a comprehensive judgment result that passage is permitted, the update unit 433 writes information to the ticket status in the ticket DB table 451 indicating that the digital ticket has been used (already used).

[0072] <Ticket issuing sequence> 11 is a sequence diagram showing an example of the process when issuing a ticket in the passing management system. First, the ticket issuing machine 100 executes a face registration process (step S1). As described above, the face registration process includes a process of capturing an image of a user's face, a process of calculating first face feature amount data from the captured image data of the user's face, and a process of registering the first face feature amount data in the face search server 300.

[0073] Next, the ticket issuing machine 100 executes the digital ticket issuing process (step S2). As described above, the digital ticket issuing process includes the process of accepting purchase conditions from the user, the process of settling the fare for the digital ticket based on the accepted purchase conditions, the process of registering the validity information of the digital ticket after the settlement has been completed in the ticket judgment server 400, the process of generating a ticket ID and registering it in the ticket judgment server 400, etc.

[0074] Next, the ticket issuing machine 100 executes a supplementary ticket issuing process (step S3). The supplementary ticket issuing process includes a process for physically issuing the supplementary ticket 500 linked to the digital ticket, and a process for generating a supplementary ticket ID and registering it in the face search server 300. The order of the processes in steps S1 to S3 may be reversed.

[0075] Next, the ticket issuing machine 100 transmits the information and results obtained by the processing of steps S1 to S3 to the face search server 300 (step S4). For example, the ticket issuing machine 100 transmits to the face search server 300 the first facial feature amount data, information indicating the purchasing conditions for the digital ticket, information indicating that the payment for the digital ticket has been completed, the ticket ID, the supplementary ticket ID, etc.

[0076] The face search server 300 stores in its own database the information required for face search processing from among the received information (step S5). For example, the face search server 300 stores in its own database the first face feature amount data, the passenger ticket ID, the supplementary ticket ID, etc. Next, the face search server 300 transfers to the passenger ticket judgment server 400 the information required for the passenger ticket judgment processing from among the received information (step S6). For example, the face search server 300 transmits to the passenger ticket judgment server 400 information indicating the purchase conditions of the digital passenger ticket, information indicating that the digital passenger ticket settlement has been completed, the passenger ticket ID, etc. Then, the passenger ticket judgment server 400 stores in its own database the information received from the face search server 300 (step S7).

[0077] <Passing sequence (part 1)> 12 is a sequence diagram showing an example of processing (part 1) at the time of passage in the passage management system. This processing (part 1) is processing for a case in which the face search server 300 judges the passerby to be a registered person by face recognition processing, the ticket judgment server 400 judges that the validity of the registered person allows passage through the passage, and the supplementary ticket held by the passerby is judged to match the supplementary ticket issued when the digital ticket was issued, so that the passerby is permitted to pass through.

[0078] First, a passenger carrying the supplementary ticket 500 advances through the passage 10 to pass through the automatic ticket gate 200. The camera 211 of the automatic ticket gate 200 captures an image of the passenger's face (step S101) and outputs the captured image data to the image processing unit 221 (step S102). The image processing unit 221 calculates second facial feature amount data based on the input captured image data (step S103) and outputs the data to the communication processing unit 222 (step S104). The communication processing unit 222 transmits the second facial feature amount data to the face search server 300 using the communication unit 240 (step S105). In addition, in step S105, the communication processing unit 222 transmits the entrance information (or exit information) generated by the entrance / exit processing unit 223 together with the second facial feature amount data to the face search server 300.

[0079] The face search server 300 executes face recognition processing based on the received second face feature amount data. If the face recognition processing authenticates that the passenger is a registrant, it acquires the passenger ticket ID and auxiliary ticket ID associated with the registrant ID of the registrant whose face has been authenticated (step S106). Next, the face search server 300 transmits the acquired passenger ticket ID to the passenger ticket judgment server 400 (step S107). In step S107, the face search server 300 transmits entrance information (or exit information) to the passenger ticket judgment server 400 together with the passenger ticket ID.

[0080] The passenger ticket judgment server 400 searches for the validity information associated with the received passenger ticket ID (step S108). The passenger ticket judgment server 400 judges whether or not the registrant's validity allows passage through the passage based on the validity information obtained by the search and the entry information (or exit information) received from the face search server 300 (step S109). If it is judged that the registrant's validity allows passage through the passage, the passenger ticket judgment server 400 transmits information indicating the judgment result "passenger ticket valid OK" to the face search server 300 (step S110).

[0081] When information indicating the judgment result “passenger ticket validity OK” is received from the ticket judgment server 400, the face search server 300 transmits the supplementary ticket ID acquired in step S106 and the judgment result by the ticket judgment server 400 “passenger ticket validity OK” to the automatic ticket gate 200 (step S111).

[0082] When the communication processing unit 222 of the automated ticket gate 200 receives the supplementary ticket ID and the judgment result "ticket validity OK" by the ticket judgment server 400 via the communication unit 240, it outputs a supplement request specifying the supplementary ticket ID to the wireless reader unit 212 to request supplementation of the RFID tag of the supplementary ticket 500 (step S112). The wireless reader unit 212 that has received the supplement request starts wireless communication (step S113) and transmits a request signal including the supplementary ticket ID (step S114).

[0083] When the supplementary ticket 500 receives a request signal from the automated ticket gate 200, it compares the supplementary ticket ID included in the request signal with the supplementary ticket ID embedded in its own RFID tag and determines whether they match (step S115). If it is determined that they match, the supplementary ticket 500 transmits an answer signal by wireless signal (step S116).

[0084] Next, the wireless reader unit 212 of the automatic ticket gate 200 judges whether a predetermined time has elapsed since the time when the request signal was transmitted, and stops wireless communication if the predetermined time has elapsed (step S117). If the wireless reader unit 212 receives an answer signal before the predetermined time has elapsed since the time when the request signal was transmitted, it outputs the received answer signal to the entrance / exit processing unit 223 (step S118). If the answer signal is input, the entrance / exit processing unit 223 determines to permit entry (or exit) as a comprehensive judgment result. Then, the entrance / exit processing unit 223 generates a door control signal instructing to open the door units 217 and 218, outputs it to the door control unit 224, and outputs guidance information informing that passage is permitted to the output control unit 225 to display it on the upper surface display unit 213 (step S119).

[0085] By doing this, not only can the facial recognition process determine that a pedestrian is a registered person and the ticket determination process determine that the pedestrian is allowed to pass through the passage with the validity of the registered person, but also, if the supplementary ticket held by the pedestrian does not match the supplementary ticket issued when the digital ticket was issued, the overall determination result is that the pedestrian will not be allowed to pass. Therefore, even if the pedestrian is mistakenly recognized as a different person by the facial recognition process, it is possible to prevent a situation in which the pedestrian is erroneously allowed to pass.

[0086] <Passing sequence (part 2)> 13 is a sequence diagram showing an example of the process (part 2) at the time of passage in the passage management system. This process (part 2) is a process for the case where the face search server 300 determines that the passerby is a registered person by the face recognition process, and the ticket determination server 400 determines that the validity of the registered person allows passage through the passage, but the supplementary ticket held by the passerby does not match the supplementary ticket issued when the digital ticket was issued, and therefore the overall determination result is that passage is not permitted.

[0087] Steps S201 to S214 are the same as steps S101 to S114 described above, and therefore detailed description will be omitted. When the supplementary ticket 500 receives a request signal from the automated ticket gate 200, it compares the supplementary ticket ID included in the request signal with the supplementary ticket ID embedded in its own RFID tag, and determines whether or not the two match (step S215). If it is determined that the two do not match, the supplementary ticket 500 does not transmit an answer signal.

[0088] Next, the wireless reader unit 212 of the automatic ticket gate 200 judges whether a predetermined time has elapsed since the time when the request signal was transmitted, and stops wireless communication if the predetermined time has elapsed (step S217). If the wireless reader unit 212 does not receive an answer signal before the predetermined time has elapsed since the time when the request signal was transmitted, it outputs information indicating that the answer signal was not captured to the entrance / exit processing unit 223 (step S218). If information indicating that the answer signal was not captured is input, the entrance / exit processing unit 223 determines that entry (or exit) is not permitted as a comprehensive judgment result. Then, the entrance / exit processing unit 223 generates a door control signal instructing not to open the door units 217 and 218, outputs it to the door control unit 224, and outputs guidance information informing that passage is not permitted to the output control unit 225 to display on the upper surface display unit 213 (step S219).

[0089] By doing this, if the supplementary ticket held by a pedestrian does not match the supplementary ticket issued when the digital ticket was issued, the pedestrian will not be allowed to pass, and even if the pedestrian is mistakenly recognized as a different person through facial recognition processing, it is possible to prevent a situation in which a pedestrian is mistakenly allowed to pass.

[0090] <Passing sequence (part 3)> 14 is a sequence diagram showing an example of a process (part 3) at the time of passage in the passage management system. This process (part 3) is a process for a case where the passerby is determined to be a non-registered person by the face recognition process of the face search server 300, and therefore is not permitted to pass as a comprehensive determination result.

[0091] Steps S301 to S306 are the same as steps S101 to S106 described above, and therefore detailed description will be omitted. If the face search server 300 is unable to authenticate that the passenger is a registered person through face recognition processing, it transmits information indicating the judgment result "face judgment NG" to the automated ticket gate 200 (step S307). If it receives information indicating the judgment result "face judgment NG", the entrance / exit processing unit 223 determines that the entrance (or exit) is not permitted as a comprehensive judgment result. Then, the entrance / exit processing unit 223 generates a door control signal instructing not to open the door units 217 and 218, outputs the signal to the door control unit 224, and outputs guidance information informing the passenger that passage is not permitted to the output control unit 225 to display on the upper display unit 213 (step S308).

[0092] By doing this, if the face authentication process determines that the passerby is not a registered user, the passenger ticket determination process and the supplementary ticket confirmation process can be omitted, and an overall determination result can be obtained.

[0093] <Passing sequence (part 4)> 15 is a sequence diagram showing an example of the process (part 4) at the time of passage in the passage management system. This process (part 4) is a process for a case where the face search server 300 determines that the passerby is a registered person through the face recognition process, but the ticket determination server 400 determines that the validity of the registered person does not allow passage through the passage, and therefore the overall determination result is that passage is not permitted.

[0094] Steps S401 to S108 are the same as steps S401 to S408 described above, and therefore detailed description will be omitted. The passenger ticket judgment server 400 judges that the validity held by the registrant does not allow passage through the passage, based on the validity information obtained by the search and the entry information (or exit information) received from the face search server 300 (step S409). If it is judged that the validity held by the registrant does not allow passage through the passage, the passenger ticket judgment server 400 transmits information indicating the judgment result "passenger ticket invalid" to the face search server 300 (step S410).

[0095] When receiving information indicating the judgment result "ticket invalid" from the ticket judgment server 400, the face search server 300 transmits the judgment result "ticket invalid" by the ticket judgment server 400 to the automated ticket gate 200 (step S411). Here, the face search server 300 does not transmit the supplementary ticket ID acquired in step S406 to the automated ticket gate 200.

[0096] When the entrance / exit processing unit 223 of the automated ticket gate 200 receives the judgment result "ticket invalid" from the ticket judgment server 400 via the communication unit 240, it determines that entry (or exit) is not permitted as a comprehensive judgment result. Then, the entrance / exit processing unit 223 generates a door control signal instructing not to open the doors 217, 218, outputs it to the door control unit 224, and outputs guidance information informing that passage is not permitted to the upper display unit 213 to the output control unit 225 (step S412).

[0097] By doing this, if the passenger ticket evaluation process determines that the validity of the registered user does not allow passage through the passageway, the supplementary ticket confirmation process can be omitted and a comprehensive evaluation result can be obtained.

[0098] According to the embodiment described above, even if a pedestrian is mistakenly recognized as a different person through face recognition processing, it is possible to prevent a situation in which the pedestrian is mistakenly allowed to pass.

[0099] According to at least one of the embodiments described above, a first judgment result is obtained, which determines whether or not the pedestrian is a registered person based on an image of the pedestrian's face taken by a camera installed along the passage; a second judgment result is obtained, which determines whether or not the pedestrian is able to pass through the passage with the validity held by the pedestrian based on validity information indicating the validity held by the pedestrian; and a third judgment result is obtained, which determines whether or not the pedestrian is in possession of an auxiliary ticket issued in advance to the pedestrian, based on information acquired by a wireless reader unit installed along the passage and identification information of the auxiliary ticket issued in advance to the pedestrian; and a decision unit is provided which decides whether or not to allow the pedestrian to pass based on the first, second, and third judgment results acquired, and outputs the decision to a passage control device, thereby preventing a situation in which a pedestrian is erroneously allowed to pass even if the pedestrian is erroneously recognized as a different person through facial recognition processing.

[0100] Although some embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included in the scope of the invention and its equivalents described in the claims, as well as in the scope and spirit of the invention.

[0101] For example, the face search server 300 and the ticket judgment server 400 may be the same device.

[0102] For example, a part of the processing performed by the automated ticket gate 200 may be implemented in the face search server 300 or the ticket judgment server 400 , and a part of the processing performed by the face search server 300 or the ticket judgment server 400 may be implemented in the automated ticket gate 200 .

[0103] For example, the face search server 300 and the ticket judgment server 400 may execute the supplementary ticket confirmation process and the overall judgment by the automated ticket gate 200, and notify the automated ticket gate 200 of the overall judgment result. Fig. 16 is a diagram showing an example of a passage management system according to an embodiment. The determination unit 600 may be configured to be included in the face search server 300, the ticket judgment server 400, or a separate server connected to the automated ticket gate 200, the face search server 300, and the ticket judgment server 400 via the network NW.

[0104] The determination unit 600 acquires a first judgment result from the face search server 300, acquires a second judgment result from the ticket judgment server 400, and acquires a third judgment result from the automatic ticket gate 200. The first judgment result is a result of face authentication processing, and is a judgment result of judging whether or not the passerby is a registered person based on a captured image of the passerby's face photographed by the camera 211. The second judgment result is a result of ticket judgment processing, and is a judgment result of judging whether or not the passerby is allowed to pass through the passage 10 with the validity held by the registered person based on the validity information indicating the validity held by the registered person. The third judgment result is a result of supplementary ticket confirmation processing, and is a judgment result of judging whether or not the passerby is in possession of the supplementary ticket 500 based on the information acquired by the wireless reader unit 212 and the supplementary ticket ID of the supplementary ticket 500 issued in advance to the registered person.

[0105] The determination unit 600 determines whether or not to permit the pedestrian to pass based on the acquired first, second, and third judgment results, and outputs the determined result to the automated ticket gate 200. In this manner, the overall judgment result can be determined on the server side. The determination unit 600 may be mounted on the automated ticket gate 200.

[0106] Although an example in which the ticket issuing machine 100 physically issues a supplementary ticket has been described, the present invention is not limited to this. The ticket issuing machine 100 may issue a virtual digital supplementary ticket in which a supplementary ticket verification process is performed using the supplementary ticket ID of the supplementary ticket managed in the server. In this case, the ticket issuing machine 100 transmits the supplementary ticket ID to a terminal held by a registrant and causes the supplementary ticket ID to be registered in the face search server 300. Without being limited to this, the ticket issuing machine 100 may receive unique information held by the terminal (for example, a NIC (Network Interface Card) address, a BLE (Bluetooth (registered trademark) Low Energy) UUID (Universally Unique Identifier), etc.) from the terminal, and use the unique information held by the terminal as the supplementary ticket ID. The automatic ticket gate 200 communicates with the terminal via the wireless reader unit 212. If the automatic ticket gate 200 determines, based on information obtained from the terminal by the wireless reader unit 212, that the supplementary ticket ID obtained from the terminal carried by the passerby matches the supplementary ticket ID issued in advance to a registered user and received from the face search server 300, it determines that the passerby is in possession of a supplementary ticket that was issued in advance to a registered user. [Explanation of symbols]

[0107] 100... ticket issuing machine, 200... automatic ticket gate, 210... main machine, 210A... camera unit, 211... camera, 212... wireless reader unit, 213... upper display unit, 214... front display unit, 217... door unit, 218... door unit, 219... passage sensor, 220... control unit, 230... slave machine, 300... face search server, 310... communication unit, 330... control unit, 331... registration unit, 332... face authentication processing unit, 333... search unit, 334... linkage unit, 350... memory unit, 351... registration information DB table, 400... passenger ticket judgment server, 410... communication unit, 430... control unit, 431... registration unit, 432... validity judgment unit, 450... memory unit, 451... passenger ticket DB table, 500... supplementary ticket

Claims

1. an authentication unit that authenticates whether or not a passerby is a registered person based on a captured image of the passerby's face taken by a camera installed along the passage; a validity determination unit that, when the authentication unit has authenticated that the passer is a registered person, determines whether or not the validity held by the registered person allows passage through the passage based on validity information that indicates the validity held by the registered person and that is stored in a passenger ticket DB table; a supplementary ticket confirmation unit which, when the authentication unit authenticates that the passerby is a registered person, determines whether the passerby is in possession of the supplementary ticket based on whether identification information of a supplementary ticket issued in advance and associated with the registered person matches identification information of the supplementary ticket obtained from a non-contact medium carried by the passerby by a wireless reader unit installed along the passage; a decision unit which decides to permit the pedestrian to pass if the authentication unit authenticates that the pedestrian is a registered person, the validity determination unit determines that the pedestrian is permitted to pass through the passage with the validity held by the pedestrian, and the supplementary ticket confirmation unit determines that the pedestrian is in possession of the supplementary ticket, and which decides not to permit the pedestrian to pass if this is not the case, and outputs the decision to a passage control device. Traffic management system.

2. The non-contact medium is an RFID tag in which a unique EPC, which is the identification information, is stored; When it is determined that the EPC of the auxiliary ticket issued in advance matches the EPC of the auxiliary ticket acquired from the RFID tag by the wireless reader unit, the auxiliary ticket confirmation unit determines that the passerby is in possession of the auxiliary ticket. The traffic control system according to claim 1.

3. The non-contact medium is a terminal provided by the passerby, The wireless reader unit communicates with the terminal, The supplementary ticket confirmation unit determines that the passerby is in possession of the supplementary ticket when it is determined that the identification information of the supplementary ticket issued in advance matches the identification information of the supplementary ticket acquired from the terminal by the wireless reader unit. The traffic control system according to claim 1 .

4. When the validity determination unit determines that the registrant is permitted to pass through the passage with the validity that the registrant has, the supplementary ticket confirmation unit determines whether the registrant has the supplementary ticket, The determination unit determines to permit the pedestrian to pass when the supplementary ticket confirmation unit determines that the pedestrian is in possession of the supplementary ticket. The traffic control system according to any one of claims 1 to 3.

5. The computer authenticating whether or not a passerby is a registered person based on a captured image of the passerby's face taken by a camera installed along the passageway; If it is authenticated that the passer is a registered person, it is determined whether or not the validity of the registered person allows passage through the passage based on validity information indicating the validity of the registered person stored in the ticket DB table; If the passerby is authenticated as a registered person, it is determined whether the passerby is in possession of the supplementary ticket based on whether identification information of a supplementary ticket issued in advance and associated with the registered person matches identification information of the supplementary ticket obtained from a non-contact medium carried by the passerby by a wireless reader unit installed along the passageway; If it is authenticated that the pedestrian is a registered person, if it is determined that the pedestrian is permitted to pass through the passage with the validity held by the registered person, and if it is determined that the pedestrian is in possession of the supplementary ticket, it is determined that the pedestrian is not permitted to pass through, and the content of the determination is output to a passage control device. Traffic management method.

6. On the computer, authenticating whether or not a passerby is a registered person based on a captured image of the passerby's face taken by a camera installed along the passageway; if it is authenticated that the passer is a registered person, determining whether or not the validity held by the registered person allows passage through the passage based on validity information that indicates the validity held by the registered person and that is stored in a ticket DB table; When the passerby is authenticated as a registered person, a determination is made as to whether or not the passerby is in possession of the supplementary ticket based on whether or not identification information of a supplementary ticket issued in advance and associated with the registered person matches identification information of the supplementary ticket obtained from a non-contact medium carried by the passerby by a wireless reader unit provided along the passage; If it is authenticated that the pedestrian is a registered person, if it is determined that the pedestrian is permitted to pass through the passage with the validity held by the registered person, and if it is determined that the pedestrian is in possession of the supplementary ticket, it is determined that the pedestrian is not permitted to pass through, and the determined content is output to a passage control device. program.

7. Cameras installed along the corridor, an acquisition unit that acquires from the passage management device a first determination result obtained by an authentication unit of the passage management device authenticating whether or not the pedestrian is a registered person based on an image of the pedestrian's face captured by the camera, and if the authentication unit authenticates the pedestrian as a registered person, a second determination result obtained by a validity determination unit of the passage management device determining whether or not the pedestrian is allowed to pass through the passage with the validity held by the pedestrian based on validity information indicating the validity held by the pedestrian stored in a ticket DB table; A wireless reader unit provided along the passage; a supplementary ticket confirmation unit which, when the authentication unit authenticates that the passerby is a registered person, determines whether the passerby is in possession of the supplementary ticket based on whether identification information of a supplementary ticket issued in advance that is associated with the registered person matches the identification information of the supplementary ticket obtained by the wireless reader unit from a non-contact medium carried by the passerby, and obtains a third determination result; a decision unit which decides to permit the pedestrian to pass if the authentication unit authenticates that the pedestrian is a registered person, the validity determination unit determines that the validity held by the pedestrian allows passage through the passage, and the supplementary ticket confirmation unit determines that the pedestrian is in possession of the supplementary ticket, and decides not to permit the pedestrian to pass if these determinations are not met; A traffic control device comprising:

Images