Information Processing Apparatus, Information Processing Method, and Program

Abstract

To promote the use of biometric authentication in a procedure related to passenger boarding.SOLUTION: According to the present invention, an information processing device includes an acquisition part for acquiring information about a terminal which acquires registered biometric information of a passenger to be used for biometric authentication in a procedure related to boarding of the passenger in an airport, and an output part for outputting the number of registrations of the registered biometric information in each category corresponding to the terminal.SELECTED DRAWING: Figure 23

Description

Technical Field

[0001] The present invention relates to an information processing apparatus, an information processing method, and a program.

Background Art

[0002] Patent Document 1 discloses a ticketless boarding system that uses biometric information such as a face image as a boarding pass and performs procedures by biometric authentication at a plurality of procedure areas (security inspection area, departure inspection area, boarding gate, etc.) without presenting a ticket medium.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] As exemplified in Patent Document 1, at current airports, passengers freely choose either a method using biometric authentication or a conventional method of having a terminal device read a recording medium such as a boarding pass, and perform procedures related to boarding an aircraft. However, in order to improve the throughput within the airport, it is required to further promote the use of biometric authentication by passengers.

[0005] Therefore, in view of the above problems, an object of the present invention is to provide an information processing apparatus, an information processing method, and a program that can promote the use of biometric authentication in procedures related to passenger boarding.

Means for Solving the Problems

[0006] According to one aspect of the present invention, An acquisition unit that acquires information regarding a terminal that has acquired the registered biometric information of a passenger used for biometric authentication in procedures related to boarding of passengers at an airport, and an output unit that outputs the number of registrations of the registered biometric information for each type of the terminal. , the acquisition unit acquires the attribute information of the passenger corresponding to the registered biometric information, and the output unit outputs the number of registrations for each piece of the attribute information. An information processing apparatus is provided.

[0007] According to another aspect of the present invention, a computer includes a step of acquiring information regarding a terminal that has acquired the registered biometric information of a passenger used for biometric authentication in procedures related to boarding of passengers at an airport, and a step of the computer outputting the number of registrations of the registered biometric information for each type of the terminal. Well, in the step of acquisition, the computer acquires the attribute information of the passenger corresponding to the registered biometric information, and in the step of output, the computer outputs the number of registrations for each piece of the attribute information. An information processing method is provided.

[0008] According to still another aspect of the present invention, a computer is caused to execute a step of acquiring information regarding a terminal that has acquired the registered biometric information of a passenger used for biometric authentication in procedures related to boarding of passengers at an airport, and a step of outputting the number of registrations of the registered biometric information for each type of the terminal. In the step of acquisition, the attribute information of the passenger corresponding to the registered biometric information is acquired, and in the step of output, the number of registrations for each piece of the attribute information is output. A program is provided.

Advantages of the Invention

[0009] According to the present invention, it is possible to provide an information processing apparatus, an information processing method, and a program that can promote the use of biometric authentication in procedures related to boarding of passengers.

Brief Description of the Drawings

[0010]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Figure 25

Figure 26

Figure 27

Figure 28

Figure 29

Figure 30

Embodiments for Carrying Out the Invention

[0011] Hereinafter, exemplary embodiments of the present invention will be described with reference to the drawings. In the drawings, the same elements or corresponding elements are denoted by the same reference numerals, and the description thereof may be omitted or simplified.

[0012] <First Embodiment> FIG. 1 is a block diagram showing an example of the overall configuration of the information processing system 1 in the present embodiment. The information processing system 1 is a computer system that manages and supports operations related to the immigration and customs inspection procedures of a user (hereinafter also referred to as a "passenger") U at Airport A. The information processing system 1 is operated, for example, by a public agency such as an immigration and customs administration or a contractor commissioned by such an agency. The reservation system 2 is a computer system provided in an airline company, different from the information processing system 1. The reservation system 2 includes a reservation information database 3 that manages boarding reservation information. In FIG. 1, for convenience of explanation, only one reservation system 2 is shown, but the reservation system 2 is provided in each of a plurality of airline companies.

[0013] In the information processing system 1 of the present embodiment, a check-in terminal 20, an automatic baggage deposit machine 30, a security inspection device 40, an automated gate device 50, and a boarding gate device 60 are respectively connected to a common management server 10 via a network NW1.

[0014] Similarly, for the reservation system 2 of each airline company, a check-in terminal 20, an automatic baggage deposit machine 30, a security inspection device 40, an automated gate device 50, and a boarding gate device 60 are respectively connected to a server (not shown) via a network NW2. The business terminals 22 (32, 42, 52, 62) used by the staff members S1 to S5 are respectively connected to the management server 10 via the network NW1 and to the server of the reservation system 2 via the network NW2. Note that the business terminals 22 (32, 42, 52, 62) may be connected to the networks NW1 and NW2 via an access point (not shown).

[0015] Networks NW1 and NW2 are composed of a LAN (Local Area Network), WAN (Wide Area Network), mobile communication network, etc. that include the in-airport communication network of Airport A. The connection method is not limited to a wired method and may also be a wireless method. Networks NW1 and NW2 are different networks. That is, in this embodiment, it is assumed that the information processing system 1 is not directly connected to the reservation system 2.

[0016] The management server 10 is provided, for example, in a facility such as an airport company that operates Airport A. Note that the management server 10 may be a cloud server instead of a server installed in a facility where actual operations are performed. Also, the management server 10 does not necessarily have to be a single server and may be configured as a server group including a plurality of servers.

[0017] As shown in FIG. 1, the departure inspection procedures at Airport A are sequentially performed at five touch points P1 to P5. Hereinafter, the relationship between each device and touch points P1 to P5 will be described.

[0018] The check-in terminal 20 is installed at the check-in lobby within Airport A (hereinafter referred to as "touch point P1"). The check-in terminal 20 is a self-service terminal for the user U to perform the check-in procedure by himself / herself. Also, the business terminal 22 is installed at the manned counter in the check-in lobby. The staff member S1 uses the business terminal 22 to perform the check-in procedure for the user U. The check-in procedure is a procedure for registering information for identifying the user U who is scheduled to board the aircraft. After the user U completes the procedure at touch point P1, the user U moves to the baggage counter or the security inspection area.

[0019] The automated baggage deposit machine 30 is installed at the baggage counter within Airport A (hereinafter referred to as "touchpoint P2"). The automated baggage deposit machine 30 is a self-service terminal for the user U to operate on their own to perform the procedure of depositing baggage that is not to be carried onto the aircraft (baggage deposit procedure). Also, the business terminal 32 is installed at the manned baggage counter. The staff member S3 uses the business terminal 32 to carry out the baggage deposit procedure for the user U. After the user U completes the procedure at touchpoint P2, the user moves to the security inspection area. Note that if the user U does not deposit any baggage, the procedure at touchpoint P2 is omitted.

[0020] The security inspection device 40 is installed at the security inspection area within Airport A (hereinafter referred to as "touchpoint P3"). The security inspection device 40 is a device for checking whether the user U is carrying any metals that could be dangerous items using a metal detector. Note that in this embodiment, the term "security inspection device" is used to include not only the metal detector, but also an X-ray inspection device for checking for the presence of dangerous items in carry-on baggage, etc. using X-rays, and a terminal device of a Passenger Reconciliation System (PRS) for determining whether the user U can pass through at the entrance of the security inspection area. The user U who has completed the check-in procedure and the automated baggage deposit procedure undergoes the security inspection procedure by the security inspection device 40 at the security inspection area. After the user U completes the procedure at touchpoint P3, the user moves to the immigration inspection area.

[0021] The automated gate device 50 is installed at the immigration inspection area within Airport A (hereinafter referred to as "touchpoint P4"). The automated gate device 50 is a device for automatically performing the immigration inspection procedure for the user U. Also, the business terminal 52 is installed at the manned counter in the immigration inspection area. The staff member S4 uses the business terminal 52 to carry out the immigration inspection procedure for the user U. After the user U completes the procedure at touchpoint P4, the user moves to the departure area where duty-free shops and boarding gates are provided.

[0022] The boarding gate device 60 is an access control device installed for each boarding gate in the departure area (hereinafter referred to as "touchpoint P5"). The boarding gate device 60 confirms that the user U is a passenger of an aircraft that can be boarded from the boarding gate. Also, the service terminal 62 is installed at the manned counter of the boarding gate. The staff member S5 uses the service terminal 62 to perform the boarding procedures for the user U to board the aircraft. After the user U completes the procedures at the touchpoint P5, the user boards the aircraft and departs the country.

[0023] As shown in FIG. 1, the management server 10 has a token ID information DB 11, a passage history information DB 12, an authentication history information DB 13, and a business information DB 14. Note that the databases possessed by the management server 10 are not limited to these databases.

[0024] FIG. 2 is a diagram showing an example of the information stored in the token ID information DB 11. The token ID information DB 11 has data items of a token ID, a group ID, a feature amount, a registered face image, a token issuance time, a token issuance device name, an invalidation flag, and an invalidation time. The token ID is an identifier that uniquely identifies the ID information. In the present embodiment, the token ID is temporarily issued on the condition that the collation result of the face image of the passport read from the passport at the touchpoint P1 and the face image of the user U possessing the passport matches. Then, when the user U finishes the procedures at the touchpoint P5 (boarding gate), the token ID is invalidated. That is, the token ID is a one-time ID having a validity period (life cycle).

[0025] The group ID is an identifier for grouping ID information. The feature amount is a value extracted from biometric information. For example, when there is a companion or in the case of a group customer, the same group ID is set. The registered face image is the face image registered for the user U. In this embodiment, the term biometric information shall mean a face image and a feature amount extracted from the face image. Note that the biometric information is not limited to a face image and a face feature amount. That is, biometric authentication may be performed using a fingerprint image, a palmprint image, an auricle image, an iris image, etc. as the biometric information of the user U.

[0026] The token issuance time is the time when the management server 10 issues the token ID. The token issuance device name is the device name of the source of the registered face image that triggered the issuance of the token ID. The invalid flag is flag information indicating whether the token ID is valid at the current time. When the token ID is issued, the invalid flag has a value of "1" indicating that the token ID is in a valid state. Also, when a predetermined condition is satisfied, the invalid flag is updated to a value of "0" indicating that the token ID is in an invalid state. The invalidation time is the timestamp when the invalid flag is invalidated.

[0027] FIG. 3 is a diagram showing an example of information stored in the passage history information DB 12. The passage history information DB 12 has data items of a passage history ID, a passage touch point, a passage time, a device name, a business system type, a token ID, a reservation number, and an airline code. The passage history ID is an identifier that uniquely identifies the passage history information. The passage touch point is the name of the touch points P1 to P5 that have been passed through. The passage time is the time stamp when the user U passed through the touch points P1 to P5. The device name is the name of the body of the business terminal used in the procedures at the touch points P1 to P5. The business system type is the type of the business system to which the business terminal belongs. Note that the management server 10 can grasp up to which touch point the user U has completed the procedure by extracting the passage history information in units of token ID. Also, in the present embodiment, the reservation number and the airline code are data items that are recorded instead of the token ID when the procedure at the touch point is performed by reading a recording medium such as a boarding pass. That is, it is assumed that the passage history information is registered in the passage history information DB 12 regardless of whether the procedure at each touch point P1 to P5 is performed by a biometric authentication method or a conventional method of reading a recording medium.

[0028] FIG. 4 is a diagram showing an example of information stored in the authentication history information DB 13. The authentication history information DB 13 has data items such as an authentication history ID, a token ID, an authentication touch point, a device name, a location ID, an authentication score, an authentication processing time, and an authentication result (success / failure of biometric authentication). The authentication history ID is an identifier that uniquely identifies the authentication history information. The authentication touch point is the name of the touch point where the authentication process was executed. The device name is the model name (device information) of the terminal device used for biometric authentication at the touch points P1 to P5. The location ID is an identifier (location information) that uniquely identifies the section where the terminal device was placed at the touch points P1 to P5. Since the authentication history information includes a token ID, passenger attribute information can be obtained from the business information DB 14 described later using the token ID as a key. Also, passenger attribute information (age / gender / member category / nationality, etc.) may be recorded in the authentication history information.

[0029] FIG. 5 is a diagram showing an example of information stored in the business information DB 14. The business information DB 14 has data items such as a token ID, a reservation number, an airline code, a passenger name, a departure location, a destination, a flight number, an operation date, a seat number, a seat class (e.g., first class / business class / economy class), a nationality, a passport number, a surname, a given name, a date of birth, a gender, a member category, the presence or absence of a companion (e.g., infant / toddler / person requiring assistance, etc.), and a companion category. The reservation number is an identifier that uniquely identifies the reservation information for boarding an aircraft. The airline code is an identifier that uniquely identifies an airline company.

[0030] FIG. 6 is a diagram showing an example of information stored in the reservation information DB 3. The reservation information DB 3 has data items such as a reservation number, an airline code, a passenger name, a departure location, a destination, a flight number, an operation date, a seat number, a seat class, a nationality, a passport number, a surname, a given name, a date of birth, a gender, a member category, the presence or absence of a companion, and a companion category.

[0031] In this embodiment, when the terminal device (such as the check-in terminal 20) at each touch point reads the reservation number and airline code from the airline ticket medium presented by the user U, it can inquire about the boarding reservation information based on the reservation number from the reservation system 2 of the airline corresponding to the airline code. Note that the method of inquiring about the boarding reservation information from the reservation system 2 is not limited to this.

[0032] Also, after the token ID information of the user U and the face image are registered in the token ID information DB 11, the boarding reservation information obtained from the reservation information DB 3 is associated with the token ID and registered in the business information DB 14. Thereby, the terminal device at each touch point can obtain the business information including the boarding reservation information from the business information DB 14 using the token ID as a key and can be used for the procedures at each touch point.

[0033] Subsequently, with reference to FIGS. 7 to 13, a hardware configuration example of each device constituting the information processing system 1 will be described. Note that for devices having the same name and only different reference numerals in FIGS. 7 to 13, since they are devices having equivalent functions, detailed descriptions will be omitted in the subsequent drawings.

[0034] FIG. 7 is a block diagram showing an example of the hardware configuration of the management server 10. As shown in the figure, the management server 10 has a CPU (Central Processing Unit) 101, a RAM (Random Access Memory) 102, a storage device 103, and a communication I / F 104. Each device is connected to a bus line 105.

[0035] The CPU 101 is a processor that performs a predetermined operation according to a program stored in the storage device 103 and has a function of controlling each part of the management server 10. The RAM 102 is composed of a volatile storage medium and provides a temporary memory area necessary for the operation of the CPU 101.

[0036] The storage device 103 is composed of a storage medium such as a non-volatile memory or a hard disk drive, and functions as a storage unit. The storage device 103 stores programs executed by the CPU 101, data referred to by the CPU 101 during the execution of the programs, and the like.

[0037] The communication I / F 104 is a communication interface based on standards such as Ethernet (registered trademark), Wi-Fi (registered trademark), 4G, etc., and is a module for communicating with the check-in terminal 20 and the like.

[0038] FIG. 8 is a block diagram showing an example of the hardware configuration of the check-in terminal 20. As shown in the figure, the check-in terminal 20 includes a CPU 201, a RAM 202, a storage device 203, a communication I / F 204, an input device 206, a display device 207, a media reader 208, and a biological information acquisition device 209. Each device is connected to a bus line 205.

[0039] The input device 206 is, for example, a pointing device such as a touch panel or a keyboard. The display device 207 is a liquid crystal display device, an OLED (Organic Light Emitting Diode) display device, etc., and is used for displaying videos, still images, characters, etc. In the check-in terminal 20 of the present embodiment, it is assumed that the input device 206 and the display device 207 are integrally formed as a touch panel.

[0040] The media reader 208 is a device that reads the passport or airline ticket media of the user U and acquires the information recorded on the passport or airline ticket. Examples of the airline ticket media include a paper airline ticket, a mobile terminal that displays a copy of an e-ticket, etc. The media reader 208 is composed of, for example, a code reader, an image scanner, a non-contact IC (Integrated Circuit) reader, an OCR (Optical Character Reader) device, etc., and acquires information from various media held over its reading unit.

[0041] The biological information acquisition device 209 is a device that acquires a face image of the user U as the biological information of the user U. The biological information acquisition device 209 is, for example, a digital camera that photographs the face of the user U standing in front of the check-in terminal 20, and photographs the face of the user U to acquire the face image.

[0042] FIG. 9 is a block diagram showing an example of the hardware configuration of the automatic baggage deposit machine 30. As shown in the figure, the automatic baggage deposit machine 30 includes a CPU 301, a RAM 302, a storage device 303, a communication I / F 304, an input device 306, a display device 307, a media reader 308, a biological information acquisition device 309, a baggage transport device 310, and an output device 311. Each device is connected to a bus line 305.

[0043] When the identity verification of the user U is successful, the baggage transport device 310 transports the baggage to be loaded onto the aircraft on which the user U boards. The baggage transport device 310 transports the baggage placed on the receiving part by the user U and tagged with a baggage tag toward the baggage sorting area.

[0044] The output device 311 is a device that outputs a baggage tag to be attached to the baggage to be deposited. In addition, the output device 311 outputs a baggage exchange certificate necessary for exchanging the baggage after arriving at the destination. Note that the baggage tag and the baggage exchange certificate are associated with at least one of the travel document information and the boarding information.

[0045] FIG. 10 is a block diagram showing an example of the hardware configuration of the security inspection device 40. As shown in the figure, the security inspection device 40 includes a CPU 401, a RAM 402, a storage device 403, a communication I / F 404, an input device 406, a display device 407, a media reader 408, a biological information acquisition device 409, and a metal detector gate 410. Each device is connected to a bus line 405.

[0046] The metal detector gate 410 is a gate-type metal detector, and detects metals carried by the user U passing through the metal detector gate 410.

[0047] FIG. 11 is a block diagram showing an example of the hardware configuration of the automated gate device 50. The automated gate device 50 includes a CPU 501, a RAM 502, a storage device 503, a communication I / F 504, an input device 506, a display device 507, a medium reader 508, a biometric information acquisition device 509, and a gate 511. Each device is connected to a bus line 505. Note that the automated gate device 50 disposed at the immigration inspection site has the same hardware configuration as the automated gate device 50 disposed at the emigration inspection site.

[0048] When the user U successfully passes the identity verification at the automated gate device 50 and passes the emigration inspection, the gate 511 shifts from the closed state that blocks the passage of the user U during standby to the open state that permits the passage of the user U according to the control by the CPU 501. The type of the gate 511 is not particularly limited, and examples thereof include a flap gate in which flaps provided on one or both sides of a passage open and close, a turnstile gate in which three bars rotate, and the like.

[0049] FIG. 12 is a block diagram showing an example of the hardware configuration of the boarding gate device 60. As shown in the figure, the boarding gate device 60 includes a CPU 601, a RAM 602, a storage device 603, a communication I / F 604, an input device 606, a display device 607, a biometric information acquisition device 609, and a gate 611. Each device is connected to a bus line 605.

[0050] FIG. 13 is a block diagram showing an example of the hardware configuration of the business terminals 22, 32, 42, 52, and 62. As shown in the figure, the business terminal 22 includes a CPU 221, a RAM 222, a storage device 223, a communication I / F 224, an input device 226, a display device 227, and a medium reader 228. Each device is connected to a bus line 225. Note that the hardware configurations of the business terminals 32, 42, 52, and 62 are the same as that of the business terminal 22.

[0051] Subsequently, the operations of the devices in the information processing system 1 in the present embodiment will be described with reference to FIGS. 14 to 26.

[0052] [Check-in Procedure] Figure 14 is a sequence diagram showing an example of the processing of the reservation system 2, the check-in terminal 20, and the management server 10. This processing is executed every time the user U performs a check-in procedure using the check-in terminal 20.

[0053] First, the check-in terminal 20 determines whether the user U's passport is held over the reading unit (not shown) of the medium reader 208 (step S101), and waits until the passport is held over (step S101, NO).

[0054] Next, when the check-in terminal 20 determines that the passport is held over the reading unit of the medium reader 208 (step S101, YES), it acquires the user U's passport information from the held passport (step S102). The acquired passport information includes the passport face image of the user U, the identity verification information, the passport number, the information of the country of issue of the passport, and the like.

[0055] Next, the check-in terminal 20 photographs the face of the user U with the biometric information acquisition device 209 (step S103), and transmits the face image, the passport information, the device information of the check-in terminal 20, and the location information to the management server 10 (step S104). It is preferable to display a screen for obtaining the consent of the user U before photographing the face image.

[0056] When the management server 10 receives information from the check-in terminal 20, it collates the face image recorded in the user U's passport (hereinafter referred to as "passport face image") and the face image photographed by the check-in terminal 20 (hereinafter referred to as "target face image") one-to-one (step S105).

[0057] Next, the management server 10 issues an authentication history ID, and registers the authentication history information associating the authentication history ID, the authentication score, the authentication processing time, and the authentication result in the authentication history information DB13 (step S106).

[0058] Next, when the management server 10 determines that the verification result of the passport face image and the target face image is a match (step S107, YES), it issues a token ID (step S108). The token ID is set to a unique value based on, for example, the date and time during processing or a sequence number.

[0059] Next, the management server 10 registers the relationship between the token ID and the registered face image in the token ID information DB11 with the target face image as the registered face image (step S109). Also, the management server 10 updates the authentication history information DB13 to add the token ID to the authentication history of the verified user U (step S110).

[0060] In this embodiment, the reasons for using the face image (target face image) taken locally as the registered face image include that the validity period (life cycle) of the token ID ends within the same day, and the quality (appearance) of the captured image is closer to that of the passport face image than the images taken in subsequent authentication processes. However, instead of the target face image (captured face image), the passport face image may be set as the registered face image (registered biometric information). For example, when the life cycle of the token ID is long (for example, in the airline industry, when a member has a valid token ID for a certain period), it is advisable to set the face image on the passport or driver's license as the registered face image.

[0061] Next, the management server 10 sends the issued token ID and the verification result of the match to the check-in terminal 20 (step S111).

[0062] On the other hand, when the management server 10 determines that the verification result of the passport face image and the target face image is a non-match (step S107, NO), it sends the verification result of the non-match to the check-in terminal 20 (step S112).

[0063] Next, when the check-in terminal 20 determines that it can execute the check-in procedure based on the verification result of the match received from the management server 10 (step S113, YES), the process proceeds to step S114. On the other hand, when the check-in terminal 20 determines that it cannot execute the check-in procedure based on the verification result of the non-match received from the management server 10 (step S113, NO), an error message is notified to the user U (step S115).

[0064] In step S114, the check-in terminal 20 determines whether the airline ticket medium of the user U is held over the reading unit of the medium reader 208. The check-in terminal 20 waits until the airline ticket medium is held over (step S114, NO).

[0065] Next, when the check-in terminal 20 determines that the airline ticket medium is held over the reading unit of the medium reader 208 (step S114, YES), it acquires the recorded data such as the reservation number and airline code from the held airline ticket medium (step S116).

[0066] Next, the check-in terminal 20 transmits the recorded data to the reservation system 2 of the airline corresponding to the airline code (step S117) and requests verification of the recorded data and the boarding reservation information.

[0067] When the reservation system 2 receives the recorded data from the check-in terminal 20, it verifies the recorded data and the boarding reservation information recorded in the reservation information DB3 (step S118) and transmits the verification result to the check-in terminal 20 (step S119).

[0068] Next, when the check-in terminal 20 receives the verification result of the match from the reservation system 2, it executes check-in procedures such as verifying the itinerary and selecting a seat based on the input information of the user U (step S120). If the verification result in the reservation system 2 does not match, the check-in terminal 20 may notify an error without executing the check-in procedure. Then, the check-in terminal 20 transmits the token ID, the business information, and the pass history information indicating the completion of the procedure at the check-in terminal 20 to the management server 10 (step S121). Also, it is assumed that the pass history information includes information such as the passing time of the touch point P1 and the device name of the terminal used for the procedure.

[0069] Next, when the management server 10 receives the information from the check-in terminal 20, it registers the pass history information indicating the relationship between the token ID and the passing information of the touch point P1 in the pass history information DB12 (step S122). Then, the management server 10 registers the business information including the boarding reservation information received from the check-in terminal 20 in the business information DB14 (step S123).

[0070] In this way, in the check-in procedure, the target face image (captured face image) that matches the face image of the travel document obtained from the travel document is registered as the registered face image in the token ID information DB11, and the registered face image is associated with the business information in the business information DB14 by the issued token ID. As a result, at each subsequent touch point, biometric authentication by face matching between the captured face image and the registered face image becomes possible.

[0071] [Baggage Deposit Procedure] FIG. 15 is a sequence diagram showing an example of the processing of the automatic baggage deposit machine 30 and the management server 10. This processing is executed when the user U who has completed the check-in procedure undergoes a baggage deposit procedure as needed.

[0072] The automatic luggage storage machine 30 always or periodically photographs in front of the device, and determines whether or not a face of the user U standing in front of the automatic luggage storage machine 30 is detected in the photographed image (step S201). The automatic luggage storage machine 30 waits until the face of the user U is detected in the image by the biometric information acquisition device 309 (step S201, NO).

[0073] When the automatic luggage storage machine 30 determines that the face of the user U has been detected by the biometric information acquisition device 309 (step S201, YES), it photographs the face of the user U and acquires the face image of the user U as the target face image (step S202).

[0074] Next, the automatic luggage storage machine 30 transmits the target face image of the user U imaged by the biometric information acquisition device 309, the device information of the automatic luggage storage machine 30, and the location information to the management server 10 together with a collation request (step S203). Thereby, the automatic luggage storage machine 30 requests the management server 10 to collate the target face image of the user U imaged by the biometric information acquisition device 309 and a plurality of registered face images registered in the token ID information DB11 of the management server 10 on a one-to-N basis.

[0075] When the management server 10 receives information such as the target face image and the collation request from the automatic luggage storage machine 30, it collates the face image of the user U (step S204). That is, the management server 10 collates the target face image received from the automatic luggage storage machine 30 and a plurality of registered face images registered in the token ID information DB11 on a one-to-N basis. Note that the registered face image to be the collation target is limited to the image associated with the token ID whose invalid flag value is "1" (valid).

[0076] Next, the management server 10 issues an authentication history ID, and registers authentication history information associating the authentication history ID, device information, location information, authentication score, authentication processing time, and authentication result in the authentication history information DB 13 (step S205). When the collation result in step S204 is a match, since the token ID associated with the registered face image that matches can be specified, the authentication history information also includes the token ID.

[0077] Here, when the management server 10 determines that the collation result is a non-match (step S206, NO), the management server 10 sends the non-match collation result to the automated luggage storage machine 30 (step S209), and the process proceeds to step S210. On the other hand, when the management server 10 determines that the collation result is a match (step S206, YES), the process proceeds to step S207.

[0078] In step S207, the management server 10 uses the token ID associated with the registered face image that matches in the token ID information DB 11 as a key to obtain boarding reservation information such as a reservation number from the business information DB 14. Then, the management server 10 sends the token ID, boarding reservation information, and collation result to the automated luggage storage machine 30 (step S208).

[0079] Next, when the automated luggage storage machine 30 determines that it can execute the procedure based on the collation result (step S210, YES), the process proceeds to step S212.

[0080] On the other hand, when the automated luggage storage machine 30 determines that it cannot execute the procedure based on the collation result (step S210, NO), it notifies the user U of an error message (step S211).

[0081] In step S212, the automated luggage storage machine 30 executes the process of the user U's luggage storage procedure based on the boarding reservation information received from the management server 10.

[0082] Next, the automatic baggage deposit machine 30 transmits to the management server 10 the token ID, the business information, and the passing history information indicating that the baggage deposit procedure of the user U has been completed through face image verification (step S213). Note that the passing history information is assumed to include information such as the passing time at the touch point P2 and the device name of the used terminal.

[0083] When the management server 10 receives information from the automatic baggage deposit machine 30, it registers the passing history information indicating the relationship between the token ID and the passing information of the touch point P2 of the user U in the passing history information DB12 (step S214). Then, the management server 10 registers the business information received from the automatic baggage deposit machine 30 in the business information DB14 as necessary (step S215).

[0084] [Security Inspection Procedure] FIG. 16 is a sequence diagram showing an example of the processing of the security inspection device 40 and the management server 10. This processing is executed when the user U who has completed the check-in procedure or the baggage deposit procedure undergoes the security inspection procedure.

[0085] The security inspection device 40 always or periodically takes a picture in front of the metal detection gate 410 and determines whether the face of the user U standing in front of the metal detection gate 410 is detected in the taken picture (step S301). The security inspection device 40 waits until the face of the user U is detected in the picture by the biometric information acquisition device 409 (step S301, NO).

[0086] When the security inspection device 40 determines that the face of the user U has been detected by the biometric information acquisition device 409 (step S301, YES), it takes a picture of the face of the user U and acquires the face image of the user U as the target face image (step S302).

[0087] Next, the security inspection device 40 transmits the target face image of the user U captured by the biometric information acquisition device 409, the device information of the security inspection device 40, and the location information to the management server 10 together with a collation request (step S303). Thereby, the security inspection device 40 requests the management server 10 to collate the target face image of the user U captured by the biometric information acquisition device 409 and a plurality of registered face images registered in the token ID information DB11 of the management server 10 on a one-to-N basis.

[0088] When the management server 10 receives the target face image and the collation request etc. from the security inspection device 40, it collates the face image of the user U (step S304). That is, the management server 10 collates the target face image received from the security inspection device 40 and a plurality of registered face images registered in the token ID information DB11 on a one-to-N basis. Note that the registered face images to be collated are limited to the images associated with the token ID whose invalid flag value is "1" (valid).

[0089] Next, the management server 10 issues an authentication history ID, and registers authentication history information in which the authentication history ID, device information, location information, authentication score, authentication processing time, and authentication result are associated in the authentication history information DB13 (step S305). Note that when the collation result in step S304 is a collation match, since the token ID associated with the registered face image that matches the collation can be specified, the token ID is also included in the authentication history information.

[0090] Here, when the management server 10 determines that the collation result is a collation mismatch (step S306, NO), the management server 10 transmits the collation result of the collation mismatch to the security inspection device 40 (step S309), and the process proceeds to step S310. On the other hand, when the management server 10 determines that the collation result is a collation match (step S306, YES), the process proceeds to step S307.

[0091] In step S307, the management server 10 acquires boarding reservation information such as a reservation number from the business information DB14 using the token ID associated with the registered face image that matches in the token ID information DB11 as a key. Then, the management server 10 transmits the token ID, the boarding reservation information, and the verification result to the security inspection device 40 (step S308). The process proceeds to step S310.

[0092] Next, when the security inspection device 40 determines that it can execute the procedure based on the verification result (step S310, YES), the process proceeds to step S312.

[0093] On the other hand, when the security inspection device 40 determines that it cannot execute the procedure based on the verification result (step S310, NO), it notifies the user U of an error message (step S311).

[0094] Next, the security inspection device 40 executes the security inspection process for the user U based on the boarding reservation information received from the management server 10 (step S312). In the security inspection process, the CPU 401 controls each part of the security inspection device 40. As a result, the security inspection device 40 detects the metals carried by the user U passing through the metal detection gate 410. The user U who has passed through the metal detection gate 410 heads towards the departure inspection area.

[0095] Next, the security inspection device 40 transmits to the management server 10 the passing history information indicating that the security inspection procedure for the user U has been completed after verifying the token ID, the business information, and the face image. Note that the passing history information is assumed to include information such as the passing time at the touch point P3 and the device name of the terminal used.

[0096] When the management server 10 receives information from the security inspection device 40, it registers the passage history information indicating the relationship between the token ID and the passage information of the touch point P3 of the user U in the passage history information DB12 (step S314). Then, the management server 10 registers the business information received from the security inspection device 40 in the business information DB14 as necessary (step S315).

[0097] [Exit inspection procedure] FIG. 17 is a sequence diagram showing an example of the processing of the automated gate device 50 and the management server 10.

[0098] The user U who has completed the security inspection procedure goes to the exit inspection area and undergoes the exit inspection procedure at the automated gate device 50. The automated gate device 50 and the management server 10 execute the processing shown in FIG. 17 each time a plurality of users U undergo the exit inspection procedure.

[0099] The automated gate device 50 always or periodically captures an image in front of the automated gate device 50 and determines whether a face of the user U standing in front of the automated gate device 50 is detected in the captured image (step S401). The automated gate device 50 waits until the face of the user U is detected in the image by the biometric information acquisition device 509 (step S401, NO).

[0100] When the automated gate device 50 determines that the face of the user U has been detected by the biometric information acquisition device 509 (step S401, YES), it captures the face of the user U and acquires the face image of the user U as the target face image (step S402).

[0101] Next, the automated gate device 50 transmits the target face image of the user U captured by the biometric information acquisition device 509, the device information, and the location information of the automated gate device 50 to the management server 10 together with a collation request (step S403). Thereby, the automated gate device 50 requests the management server 10 to collate the target face image of the user U captured by the biometric information acquisition device 509 and a plurality of registered face images registered in the token ID information DB11 of the management server 10 on a one-to-N basis.

[0102] When the management server 10 receives the target face image and the collation request etc. from the automated gate device 50, it collates the face image of the user U (step S404). That is, the management server 10 collates the target face image received from the automated gate device 50 and a plurality of registered face images registered in the token ID information DB11 on a one-to-N basis. Note that the registered face images to be collated are limited to the images associated with the token IDs whose invalid flag value is "1" (valid).

[0103] Next, the management server 10 issues an authentication history ID and registers authentication history information in which the authentication history ID, device information, location information, authentication score, authentication processing time, and authentication result are associated in the authentication history information DB13 (step S405). Note that when the collation result in step S404 is a collation match, since the token ID associated with the registered face image that matches the collation can be specified, the token ID is also included in the authentication history information.

[0104] When the management server 10 determines that the collation result is a collation mismatch (step S406, NO), the management server 10 transmits the collation result of the collation mismatch to the automated gate device 50 (step S409), and the process proceeds to step S410. On the other hand, when the management server 10 determines that the collation result is a collation match (step S406, YES), the process proceeds to step S407.

[0105] In step S407, the management server 10 uses the token ID associated with the registered face image that matches the verification in the token ID information DB11 as a key to obtain boarding reservation information such as a reservation number from the business information DB14. Then, the management server 10 transmits the token ID, the boarding reservation information, and the verification result to the automated gate device 50 (step S408). The process proceeds to step S410.

[0106] Next, when the automated gate device 50 determines that it can execute the procedure based on the verification result (step S410, YES), the process proceeds to step S412. On the other hand, when the automated gate device 50 determines that it cannot execute the procedure based on the verification result (step S410, NO), it notifies the user U of an error message (step S411). For example, a notification screen including a message such as "Please go through the departure review procedure at the manned counter." is displayed on the display device 507.

[0107] Next, the automated gate device 50 executes the departure review procedure for the user U based on the boarding reservation information received from the management server 10 (step S412) and opens the gate 511 (step S413). The user U who has passed through the touch point P4 heads to the departure area where the boarding gate is located.

[0108] Next, the automated gate device 50 transmits to the management server 10 the passing history information indicating that the departure review procedure for the user U has been completed after verifying the token ID, the business information, and the face image (step S414). Note that the passing history information shall include information such as the passing time of the touch point P4 and the device name of the terminal used.

[0109] When the management server 10 receives information from the automated gate device 50, it registers the passing history information indicating the relationship between the token ID and the passing information of the touch point P4 of the user U in the passing history information DB12 (step S415). Then, the management server 10 registers the business information received from the automated gate device 50 in the business information DB14 as necessary (step S416).

[0110] [Boarding Check at Boarding Gate] FIG. 18 is a sequence diagram showing an example of the processing of the boarding gate device 60 and the management server 10. This processing is executed when the user U passes through the boarding gate.

[0111] The boarding gate device 60 always or periodically photographs in front of the device, and determines whether a face of the user U standing in front of the boarding gate device 60 is detected in the photographed image (step S501). The boarding gate device 60 waits until the face of the user U is detected in the image by the biometric information acquisition device 609 (step S501, NO).

[0112] When the boarding gate device 60 determines that the face of the user U has been detected by the biometric information acquisition device 609 (step S501, YES), it photographs the face of the user U and acquires the face image of the user U as the target face image (step S502).

[0113] Next, the boarding gate device 60 transmits the target face image of the user U captured by the biometric information acquisition device 609, the device information of the boarding gate device 60, and the location information to the management server 10 together with a collation request (step S503). Thereby, the boarding gate device 60 requests the management server 10 to collate the target face image of the user U captured by the biometric information acquisition device 609 with a plurality of registered face images registered in the token ID information DB11 of the management server 10 on a one-to-N basis.

[0114] When the management server 10 receives the target face image and the collation request, etc. from the boarding gate device 60, it collates the face image of the user U (step S504). That is, the management server 10 collates the target face image received from the boarding gate device 60 with a plurality of registered face images registered in the token ID information DB11 on a one-to-N basis. Note that the registered face images to be collated are limited to the images associated with the tokens whose invalid flag values are "1" (valid).

[0115] Next, the management server 10 issues an authentication history ID and registers authentication history information associating the authentication history ID, device information, location information, authentication score, authentication processing time, and authentication result in the authentication history information DB 13 (step S505). Note that when the collation result in step S504 is a match, the token ID associated with the registered face image that matches can be specified, so the authentication history information also includes the token ID.

[0116] When the management server 10 determines that the collation result is a mismatch (step S506, NO), the management server 10 sends the collation result of the mismatch to the boarding gate device 60 (step S509), and the process proceeds to step S510. On the other hand, when the management server 10 determines that the collation result is a match (step S506, YES), the process proceeds to step S507.

[0117] In step S507, the management server 10 uses the token ID associated with the registered face image that matches in the token ID information DB 11 as a key to obtain boarding reservation information such as a reservation number from the business information DB 14. Then, the management server 10 sends the token ID, boarding reservation information, and collation result to the boarding gate device 60 (step S508). The process proceeds to step S510.

[0118] Next, when the boarding gate device 60 determines that it can execute the procedure based on the collation result (step S510, YES), the process proceeds to step S512.

[0119] On the other hand, when the boarding gate device 60 determines that it cannot execute the procedure based on the collation result (step S510, NO), it notifies the user U of an error message (step S511). For example, the boarding gate device 60 displays a notification screen including a message such as "Please proceed with the procedure at the manned counter." on the display device 607.

[0120] In step S512, when the boarding gate device 60 receives the boarding reservation information from the reservation system 2, it executes the boarding check of the user U based on the flight number, gate number, boarding start time, etc. included in the boarding reservation information. When the boarding gate device 60 permits boarding, it opens the gate 611 (step S513). The user U who has passed through the touch point P5 boards the aircraft. Note that in step S512, when the boarding gate device 60 determines not to permit boarding, it may notify the user U of an error message without opening the gate 611. For example, when the user U mistakes the gate number of the gate 611 or the current time has not reached the boarding start time, etc., the gate 611 is not opened.

[0121] Next, the boarding gate device 60 transmits to the management server 10 the token ID, the business information, and the passage history information indicating that the boarding of the user U on the aircraft has been completed through the collation of the face images (step S514). Note that the passage history information shall include information such as the passage time of the touch point P5 and the device name of the terminal used.

[0122] When the management server 10 receives information from the boarding gate device 60, it registers the passage history information indicating the relationship between the token ID and the passage information of the touch point P5 of the user U in the passage history information DB12 (step S515). In addition, the management server 10 registers the business information received from the boarding gate device 60 in the business information DB14 as necessary (step S516).

[0123] Then, the management server 10 updates the token ID information DB11 (step S517). Specifically, the management server 10 updates the invalid flag of the token ID information DB11 to an invalid value (“0”). Thereby, the valid period (life cycle) of the token ID expires.

[0124] [Procedures other than biometric authentication] FIG. 19 is a sequence diagram showing an example of the processing of the reservation system 2, the business terminal 22, and the management server 10. This processing is executed when a staff member (S1 to S5) performs procedures using the business terminal 22 or the like. Here, the business terminal 22 disposed at the touch point P1 will be described as an example.

[0125] First, the business terminal 22 determines whether the travel document of the user U is held over the reading unit (not shown) of the medium reader 228 (step S601), and waits until the travel document is held over (step S601, NO).

[0126] Next, when the business terminal 22 determines that the travel document of the user U is held over the reading unit of the medium reader 228 (step S601, YES), the business terminal 22 acquires the travel document information of the user U from the held travel document (step S602). The acquired travel document information includes the travel document face image of the user U, the identity verification information, the travel document number, the information of the country where the travel document was issued, and the like.

[0127] Next, the business terminal 22 determines whether the airline ticket medium of the user U is held over the reading unit of the medium reader 228 (step S603). The business terminal 22 waits until the airline ticket medium is held over (step S603, NO).

[0128] Next, when the business terminal 22 determines that the airline ticket medium is held over the reading unit of the medium reader 228 (step S603, YES), the business terminal 22 acquires the recorded data such as the reservation number and the airline code from the held airline ticket medium (step S604).

[0129] Next, the business terminal 22 transmits the recorded data to the reservation system 2 of the airline corresponding to the airline code (step S605), and requests a collation between the recorded data and the boarding reservation information.

[0130] When the reservation system 2 receives the recorded data from the business terminal 22, the reservation system 2 collates the recorded data with the boarding reservation information recorded in the reservation information DB3 (step S606), and transmits the collation result to the business terminal 22 (step S607).

[0131] Next, when the business terminal 22 receives the verification result from the reservation system 2, it determines whether it can execute the procedure at the touch point P1 (step S608). Here, when the business terminal 22 determines that it can execute the procedure (step S608, YES), the process proceeds to step S609. On the other hand, when the business terminal 22 determines that it cannot execute the procedure based on the information received from the management server 10 (step S608, NO), it notifies an error message (step S610).

[0132] In step S609, the business terminal 22 executes a review procedure (check-in procedure) at the touch point P1 based on the input information of the clerk S. The business terminal 22 transmits the reservation number, the business information obtained by the processing in the business terminal 22, and the passing history information indicating the completion of the procedure in the business terminal 22 to the management server 10 (step S611).

[0133] Next, when the management server 10 receives the information from the business terminal 22, it registers the passing history information in the passing history information DB12 (step S612). Then, the management server 10 registers the business information received from the business terminal 22 in the business information DB14 as necessary (step S613).

[0134] [Statistical Analysis Processing] FIG. 20 is a flowchart showing an example of the processing of the management server 10. This processing is executed at a predetermined cycle or when a processing request from the system administrator or the like is input.

[0135] First, when the management server 10 acquires the statistical analysis conditions set by the administrator or the like (step S701), it acquires the passing history information for the specified period from the passing history information DB12 based on the statistical analysis conditions (step S702). Note that when the procedure is performed by reading the recording medium at each touch point P1 to P5, the passing history information not including the token ID is acquired from the passing history information DB12.

[0136] Next, the management server 10 acquires the authentication history information at the time of passing through the touch point from the authentication history information DB 13 using the token ID included in the passing history information (step S703).

[0137] Next, the management server 10 acquires the business information including the attribute information of the user U from the business information DB 14 using the token ID included in the passing history information (step S704).

[0138] Next, the management server 10 executes statistical analysis processing on the passing history information, authentication history information, and business information (attribute information) (step S705). The management server 10 executes statistical processing, for example, by touch point, by attribute of the user U, and by period.

[0139] Then, when the management server 10 acquires the display condition of the statistical analysis result designated by the administrator or the like (step S706), it displays the statistical analysis result on the business terminal 22 or a display terminal (not shown) for display (step S707).

[0140] FIGS. 21 to 26 are diagrams showing an example of a screen output by the management server 10. FIG. 21 shows an analysis menu selection screen for the system administrator to select the analysis result to be displayed. In the central area of the screen, a plurality of analysis menus M1 to M6 and an analysis condition setting button M7 for transitioning to a screen for setting analysis conditions are displayed.

[0141] FIG. 22 is a dashboard screen in which different types of statistical results are collectively displayed in a dashboard format. The dashboard screen shown in FIG. 21 is mainly composed of four areas A1 to A4. Area A1 shows the result of statistically analyzing the authentication accuracy by location.

[0142] Area A1 consists of areas A11 to A14. Area A11 displays the average authentication accuracy, average authentication time, and token ID utilization rate at location (“south of T1, west”). The “token ID utilization rate” is synonymous with the utilization rate of biometric authentication. By adding the number of records of the history information (first history information) of procedures using biometric authentication (i.e., the number of biometric authentication users) N1 and the number of records of the utilization information of procedures by reading the recording medium (i.e., the number of medium users) N2, the total number of passengers N3 can be obtained. Therefore, if the token ID utilization rate is R, it can be calculated as R = N1 / (N1 + N2).

[0143] Area A12 displays the average authentication accuracy for each terminal ID. Area A13 displays the average authentication time for each terminal ID. Area A14 displays the token ID utilization rate for each terminal ID. Note that in A12 to A14, the locations with terminal IDs “#51” to “#54” are “south of T1, west”, and the locations with terminal IDs “#61” to “#64” are “main building of T2”.

[0144] In areas A11, A12, and A13, terminals that do not meet a predetermined threshold may be detected and highlighted. For example, in area A12, a terminal with terminal ID “#52” can be detected as a terminal whose average authentication accuracy is less than 0.96 of the threshold. Also, the processing results of biometric authentication (authentication accuracy, authentication time, and authentication success rate) may be aggregated and output for each location. And when the average authentication accuracy per location (placement location) is less than a predetermined threshold, the information of the corresponding location may be output.

[0145] In area A13, a terminal with terminal ID “#52” can be detected as a terminal whose average authentication time exceeds 1 second of the threshold. Similarly, when displaying the authentication success rate for each terminal in area A1, terminals whose authentication success rate is less than a predetermined threshold can be detected and highlighted.

[0146] Area A2 shows the results of a statistical analysis of the distribution of the number of staying guests by location. Area A2 consists of Area A21 and Area A22. Area A21 shows the number of passing guests in a pie chart. Area A22 shows the assumed number of staying guests in a pie chart.

[0147] Area A3 shows the results of a statistical analysis of the average passing time and throughput of terminals by device. Area A3 consists of Area A31 and Area A32. Area A31 shows the average passing time for each terminal ID in a bar graph. Area A32 shows the throughput for each terminal ID in a bar graph.

[0148] Area A4 shows the results of a statistical analysis of the number of customers by time period. In Area A4, the number of customers is classified by location (T1 South W Satellite 4 / T1 South W Satellite 5 / T2 Main Building / T2 Satellite) before and after the security inspection area (PRS) and at touch point P3. Also, Area A4 consists of Area A41 and A42. Area A41 shows the number of customers by time period at two locations (T1 South W Satellite 4 / T2 Main Building). Also, Area A42 shows the transition data of the number of passengers by time period and location using eight line graphs.

[0149] Figure 23 is a Token ID Registrant Number Transition Screen showing the transition of the number of registrants of Token ID. At the top of the screen, there are buttons B11 for switching the statistical period of the data in years, months, and days, and button B12 for outputting the statistical results as a CSV file. Here, the annual button B11 is selected. Also, in the central part of the screen, the number of registrants in the period from 2018 to 2019 is shown in a bar graph, the number of registrants for each touch point is shown in a line graph, and in a list. Note that although all legends are shown in Figure 23, buttons for selecting touch points can be provided, and only the transition of the number of registrants for the selected touch point can be shown.

[0150] FIG. 24 is a token ID registrant attribute analysis screen that analyzes the number of registrants of token IDs for each attribute of user U. At the upper part of the screen, a button B21 for switching the statistical period of data in units of years, months, and days is displayed. Here, the monthly unit is selected. Also, adjacent to the button B21, a button B22 for switching the display period is displayed. In the central part of the screen, the analysis results by nationality, gender, seat class, airline, and age are respectively displayed by pie charts. Note that not only attribute information but also the results of analysis using boarding information (for example, analysis results by destination) can be displayed.

[0151] FIG. 25 is a utilization rate transition screen by touch point that analyzes the utilization rate of biometric authentication by touch point. At the upper part of the screen, an area selection button B31 for selecting a touch point and a button B32 for switching the statistical period of data in units of years, months, and days are displayed. Here, the monthly unit is selected. Also, adjacent to the button B32, a button B33 for switching the display period is displayed. In the central part of the screen, the number of biometric authentication users (number of users) at each of the four touch points (check-in lobby, baggage drop-off area, security inspection area, and boarding gate) is displayed by a bar graph, and the utilization rate of biometric authentication is displayed by a line graph. As the utilization rate of biometric authentication, for example, the ratio occupied by the number of passengers who actually use biometric authentication among the number of passengers who have registered biometric information for use in the boarding procedure (the number of passengers for whom a token ID has been issued) can be shown. Also, the ratio occupied by the number of passengers who use biometric authentication among the total number of passengers can be shown.

[0152] FIG. 26 is a transition screen of the authentication rate (authentication success rate) of biometric authentication for each touch point, which analyzes the authentication rate for each touch point. At the upper part of the screen, an area selection button B41 for selecting a touch point and a button B42 for switching the statistical period of data in units of months, days, and hours are displayed. Here, the monthly unit is selected. Also, a button B43 for switching the display period is displayed next to the button B42. In the central part of the screen, the total number of authentication target persons at the security inspection site is displayed as a bar graph, and the authentication rate of biometric authentication is displayed as a line graph.

[0153] According to the present embodiment, the management server 10 can grasp the usage status of the biometric authentication of the user U from various viewpoints by statistically analyzing the history information (token ID information, passage history information, authentication history information, and business information) registered in the database when the user U performs various procedures for boarding an aircraft at each touch point based on biometric authentication. Thereby, the use of biometric authentication in the procedures at each touch point can be promoted.

[0154] <Second Embodiment> Hereinafter, the information processing system 1 in the present embodiment will be described. Note that the same reference numerals as those given in the drawings of the first embodiment indicate the same objects. The description of the parts common to the first embodiment will be omitted, and the different parts will be described in detail.

[0155] In the present embodiment, the management server 10 creates a learning model based on the token ID information, passage history information, authentication history information, and business information, and is further provided with a function of applying new data to the learning model to perform throughput simulation and propose an optimal layout and number of units, which is different from the first embodiment. That is, in the present embodiment, the CPU 101 of the management server 10 also functions as a learning unit and a prediction unit.

[0156] As an example of the learning method in the management server 10, it is possible to perform learning using a general deep learning framework such as TensorFlow, Caffe2, or PyTorch.

[0157] Figure 27 is a schematic diagram for explaining the neural network used in the learning process in this embodiment. The neural network shown in Figure 27 includes an input layer having a plurality of nodes, an intermediate layer having a plurality of nodes, and an output layer having one node. To each node in the input layer, for example, the number of passengers passing through each touch point during a predetermined period, the number of terminals installed at each touch point during the procedure, the passing time, etc. are input. Each node in the intermediate layer is connected to each node in the input layer. Each element of the input value input to the nodes in the intermediate layer is used for the calculation in each node in the intermediate layer. Each node in the intermediate layer calculates a calculation value, for example, using the input value input from each node in the input layer, a predetermined weighting coefficient, and a predetermined bias value. Each node in the intermediate layer is connected to the output layer respectively, and outputs the calculated calculation value to the node in the output layer. The node in the output layer receives the calculation value from each node in the intermediate layer.

[0158] The node in the output layer calculates the processing time (estimated value) at each touch point using the calculation value input from each node in the intermediate layer, the weighting coefficient, and the bias value. When training the neural network, for example, the error backpropagation method is used. Specifically, the output value when data is input to the input layer is compared with the output value obtained from the teacher data, and the error generated as a result of the comparison is fed back to the intermediate layer. This is repeated until the error falls below a predetermined threshold.

[0159] Through such learning processing, when an arbitrary number of passengers is input to the neural network (learning model), the predicted processing time at each touch point can be output with high accuracy. Note that the learning model created by the learning processing is not limited to the above-described one.

[0160] Figure 28 is a flowchart showing an example of the processing of the management server 10. This processing is executed by a system administrator or the like to grasp the usage status of biometric authentication in the airport.

[0161] First, the management server 10 acquires the installation data of the terminals (step S801), and acquires the transition data of the number of passengers (step S802).

[0162] Next, when the management server 10 performs prediction processing based on the learning model (step S803), it outputs the prediction result (step S804).

[0163] Next, the management server 10 refers to the prediction result and determines whether the predicted residence time of passengers at each touch point exceeds a predetermined threshold (step S805). In this embodiment, the predicted residence time of passengers is regarded as the same as the prediction processing time of the terminal device. Here, when it is determined that the predicted residence time exceeds the predetermined threshold (step S805, YES), the process proceeds to step S806. On the contrary, when it is determined that the predicted residence time does not exceed the predetermined threshold (step S805, NO), the process of FIG. 28 ends.

[0164] In step S806, the installation data with the changed number of installed terminals is applied to the learning model, and the prediction processing based on the learning model is repeatedly executed. For example, while subtracting the number of installed units and inputting it into the learning model, the number of installed units when the predicted residence time corresponding to the number of passengers is within the threshold is obtained.

[0165] Then, the management server 10 displays a proposal screen for proposing the optimal number of installed units and locations (step S807), and ends the process of FIG. 28.

[0166] FIG. 29 is a diagram showing an example of a screen output by the management server 10. FIG. 29 is a proposal screen for proposing the optimal number of installed units of the terminal device for biometric authentication. In the center of the screen, a proposal message based on the analysis process of the management server 10 ("During the period from ○ month ○ day to △ month △ day, it is expected that the number of passengers from country X will increase significantly. Please newly install ** units of check-in terminals in section AA of the check-in lobby.") is displayed. In addition to the display, a map of the corresponding area in the airport can be displayed, and the location where the number of installed units is proposed can be highlighted.

[0167] As described above, according to this embodiment, the management server 10 can create a learning model based on the passenger history information, and can predict the predicted stay time (predicted processing time) of passengers in the airport based on the learning model. In addition, the management server 10 can also propose the number of terminal devices having a biometric authentication function installed at each touch point based on the prediction result.

[0168] <Third Embodiment> FIG. 30 is a block diagram showing an overall configuration example of the information processing apparatus 100 in this embodiment. The information processing apparatus 100 includes an acquisition unit 100A and an output unit 100B. The acquisition unit 100A acquires first history information indicating that procedures related to boarding of passengers in the airport are executed by biometric authentication and second history information indicating that the procedures are executed by reading a medium, respectively. The output unit 100B outputs the usage status of biometric authentication in the procedure based on the first history information and the second history information. According to the information processing apparatus 100 in this embodiment, the use of biometric authentication in procedures related to boarding of passengers can be promoted.

[0169] <Modified Embodiment> As described above, the present invention has been described with reference to the embodiments, but the present invention is not limited to the above-described embodiments. Various modifications understandable by those skilled in the art are possible within the scope not departing from the gist of the present invention in terms of the configuration and details of the present invention. For example, an embodiment in which a part of the configuration of any one of the embodiments is added to another embodiment, or an embodiment in which a part of the configuration of another embodiment is replaced should be understood as an embodiment to which the present invention can be applied.

[0170] In addition, the configuration of the present invention can be applied not only to international flights but also to domestic flights. In the case of domestic flights, in addition to the departure inspection procedures, the one-to-one collation process between the passport face image and the photographed face image may be omitted. In this case, as the registered biometric image, for example, a photographed face image at the time of purchasing a boarding pass can be used. When purchasing a boarding pass or checking in online using a terminal such as a smartphone or a personal computer, if a face image photographed by the terminal is registered, it is also possible to board an aircraft by face authentication at Airport A.

[0171] In the above-described first embodiment, the check-in terminal 20 has been applying for the issuance of a token ID to the management server 10 by reading the passport face image from the passport. However, considering the case of performing the check-in procedure online, it may be possible to apply for the issuance at the automatic baggage deposit machine 30 or the security inspection device 40. That is, the management server 10 acquires the passport face image and the target biometric image from any one of the business terminals that execute the business related to the departure of the user U. Among the series of procedure operations performed at the time of departure, an application for the issuance of a token ID may be made in the first procedure operation performed. In this case, the processing in the automatic baggage deposit machine 30 and the security inspection device 40 may include steps such as acquiring the recording data from the passport and the airline ticket medium, and inquiring the reservation system 2 about the boarding reservation information, similar to the case of FIG. 14.

[0172] Furthermore, the types of statistical analysis processing are not limited to those described above. For example, a series of procedures regarding a certain user U may be analyzed. Specifically, history information may be respectively obtained from the passage history information DB12 and the authentication history information DB13 using the token ID of the user U as a key, and a procedure area (touch point) where there is no passage history information or authentication history information may be detected and analyzed. That is, when the user U completes a procedure by reading a recording medium such as a boarding pass at some touch points, a touch point where there is passage history information but no authentication history information can be detected. For example, at the check-in lobby (touch point P1) and the baggage counter (touch point P2), biometric authentication is used, and then at the security inspection area (touch point P3), biometric authentication is not used, and at the departure inspection area (touch point P4) and the boarding gate (touch point P5), biometric authentication is used. This is a case where the authentication history at the touch point P3 is missing. Similarly, when a procedure is performed using the business terminals (22, 32, 42, 52, 62) but the registration process of the passage history information is not executed, a touch point where neither the passage history information nor the authentication history information exists can be detected. By detecting and analyzing such a record missing state, the movement route of the user U can be grasped. As a result, it is also possible to change the layout and the number of terminal devices having a biometric authentication function and promote further use of biometric authentication.

[0173] A program that operates the configuration of the above-described embodiment to realize the functions of the above-described embodiment is recorded on a recording medium, the program recorded on the recording medium is read as code, and a processing method executed by a computer is also included in the scope of each embodiment. That is, a computer-readable recording medium is also included in the scope of each embodiment. In addition, not only the recording medium on which the above-described program is recorded but also the program itself is included in each embodiment.

[0174] As the recording medium, for example, a floppy (registered trademark) disk, a hard disk, an optical disk, a magneto-optical disk, a CD-ROM, a magnetic tape, a non-volatile memory card, etc. can be used. Further, not limited to those that execute processing with only the program recorded on the recording medium, those that operate on the OS and execute processing in cooperation with the functions of other software and expansion boards are also included in the scope of each embodiment.

[0175] Some or all of the above-described embodiments can be described as follows in the appended claims, but are not limited thereto.

[0176] (Appended Claim 1) An acquisition unit that acquires first history information indicating that procedures related to passenger boarding in the airport have been executed by biometric authentication and second history information indicating that the procedures have been executed by reading a medium, respectively; An output unit that outputs the usage status of the biometric authentication in the procedures based on the first history information and the second history information; An information processing apparatus comprising the above.

[0177] (Appended Claim 2) Further comprising an issuing unit that issues a token ID corresponding to the registered biometric information of the passenger used for the biometric authentication, The first history information includes a procedure area where the registered biometric information is registered and the token ID, The output unit outputs the number of registrations of the registered biometric information for each procedure area, The information processing apparatus according to Appended Claim 1.

[0178] (Appended Claim 3) The first history information includes the attribute information of the passenger, The output unit outputs the number of registrations for each attribute information, The information processing apparatus according to Appended Claim 2.

[0179] (Appended Claim 4) The output unit outputs the utilization rate of the biometric authentication in the procedure area based on the ratio of the first history information and the second history information for each of the procedure areas. The information processing apparatus according to appended note 2 or 3.

[0180] (Appended note 5) The output unit detects, based on the token ID, a procedure area among the plurality of procedure areas where there is no first history information about the same passenger. The information processing apparatus according to any one of appended notes 2 to 4.

[0181] (Appended note 6) The first history information includes the terminal ID of the terminal used for the biometric authentication and the processing result of the biometric authentication. The output unit aggregates and outputs the processing results for each terminal ID. The information processing apparatus according to any one of appended notes 1 to 5.

[0182] (Appended note 7) The output unit detects a terminal whose authentication success rate is less than a predetermined threshold based on the processing results for each terminal ID. The information processing apparatus according to appended note 6.

[0183] (Appended note 8) The first history information further includes the location of the terminal within the airport. The output unit aggregates and outputs the processing results for each location. The information processing apparatus according to appended note 6 or 7.

[0184] (Appended note 9) The output unit outputs information on a location where the average authentication accuracy obtained by averaging the authentication accuracy of the biometric authentication for each location is less than a predetermined threshold. The information processing apparatus according to appended note 8.

[0185] (Appended note 10) A prediction unit that outputs a predicted processing time in the procedure based on a learning model that has previously learned the relationship between the number of passengers during a specified period, the number of installed terminals, and the time required for the procedure. The information processing apparatus according to any one of Appendices 6 to 9, further comprising the above.

[0186] (Appendix 11) When the predicted processing time exceeds a predetermined threshold, the prediction unit outputs information prompting a change in the number of installed units. The information processing apparatus according to Appendix 10.

[0187] (Appendix 12) The output unit outputs different types of statistical analysis results based on the first history information and the second history information in a dashboard format. The information processing apparatus according to any one of Appendices 1 to 11.

[0188] (Appendix 13) Steps of respectively obtaining first history information indicating that a procedure related to passenger boarding in an airport has been executed by biometric authentication and second history information indicating that the procedure has been executed by reading a medium; Based on the first history information and the second history information, outputting the usage status of the biometric authentication in the procedure. An information processing method comprising the above.

[0189] (Appendix 14) Causing a computer to Steps of respectively obtaining first history information indicating that a procedure related to passenger boarding in an airport has been executed by biometric authentication and second history information indicating that the procedure has been executed by reading a medium; Based on the first history information and the second history information, outputting the usage status of the biometric authentication in the procedure. A recording medium recording a program for executing the above.

Explanation of Signs

[0190] NW1, NW2 ··· Network 1 ··· Information Processing System 2 ··· Reservation System 3 ··· Reservation Information DB 10 ··· Management Server 11 ··· Token ID Information DB 12 ··· Passage History Information DB 13 ··· Authentication History Information DB 14 ··· Business Information DB 20 ··· Check-in Terminal 30 ··· Automatic Baggage Storage Machine 40 ··· Security Inspection Device 50 ··· Automated Gate Device 60 ··· Boarding Gate Device 22, 32, 42, 52, 62 ··· Business Terminal 100 ··· Information Processing Device 100A ··· Acquisition Unit 100B ··· Output Unit

Claims

1. An acquisition unit that acquires information about a terminal that has acquired the registered biometric information of a passenger used for biometric authentication in procedures related to the boarding of passengers at an airport; An output unit that outputs the number of registrations of the registered biometric information for each type of the terminal; comprising: The acquisition unit acquires the attribute information of the passenger corresponding to the registered biometric information, The output unit outputs the number of registrations for each piece of the attribute information, an information processing apparatus.

2. The acquisition unit acquires a token ID corresponding to the registered biometric information, and refers to a database that stores the attribute information of the passenger and the token ID in association with each other, and acquires the attribute information associated with the acquired token ID, The information processing apparatus according to claim 1.

3. The terminal is a terminal used for the procedure, The acquisition unit acquires history information indicating that the procedure has been executed by the biometric authentication, The output unit outputs the utilization rate of the biometric authentication in the procedure area based on the history information for each procedure area where the terminal is provided, The information processing apparatus according to claim 1 or 2.

4. The output unit detects, based on the token ID, a procedure area in which there is no history information indicating that the procedure has been executed by the biometric authentication for the same passenger among a plurality of procedure areas, The information processing apparatus according to claim 2.

5. The history information includes a terminal ID of the terminal used for the biometric authentication and a processing result of the biometric authentication, The output unit aggregates and outputs the processing results for each terminal ID, The information processing apparatus according to claim 3 or 4.

6. The output unit detects the terminal whose authentication success rate is less than a predetermined threshold based on the processing results for each of the terminal IDs. The information processing apparatus according to claim 5.

7. The output unit outputs different types of statistical analysis results in a dashboard format based on the history information and other history information indicating that the procedure was executed by reading a medium. The information processing apparatus according to claim 3 or 4.

8. A step in which a computer obtains information regarding a terminal that has obtained registered biometric information of a passenger used for biometric authentication in a procedure related to boarding of a passenger at an airport, A step in which the computer outputs the number of registrations of the registered biometric information for each type of the terminal, comprising, In the obtaining step, the computer obtains attribute information of the passenger corresponding to the registered biometric information, In the outputting step, the computer outputs the number of registrations for each of the attribute information, an information processing method.

9. On a computer, A step in which the computer obtains information regarding a terminal that has obtained registered biometric information of a passenger used for biometric authentication in a procedure related to boarding of a passenger at an airport, A step in which the computer outputs the number of registrations of the registered biometric information of the type of the terminal, is made to execute, In the obtaining step, the computer obtains attribute information of the passenger corresponding to the registered biometric information, In the outputting step, the computer outputs the number of registrations for each of the attribute information, a program.

Images