WO2021206162A1 - 情報処理サーバ、情報処理システム、判定装置、及び方法 - Google Patents

情報処理サーバ、情報処理システム、判定装置、及び方法 Download PDF

Info

Publication number
WO2021206162A1
WO2021206162A1 PCT/JP2021/015002 JP2021015002W WO2021206162A1 WO 2021206162 A1 WO2021206162 A1 WO 2021206162A1 JP 2021015002 W JP2021015002 W JP 2021015002W WO 2021206162 A1 WO2021206162 A1 WO 2021206162A1
Authority
WO
WIPO (PCT)
Prior art keywords
ticket
feature amount
data
identification information
amount data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/JP2021/015002
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
圭史 伊藤
裕紀 宮西
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Playground Co Ltd
Original Assignee
Playground Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Playground Co Ltd filed Critical Playground Co Ltd
Priority to EP21783705.3A priority Critical patent/EP4134854A4/en
Publication of WO2021206162A1 publication Critical patent/WO2021206162A1/ja
Priority to US17/961,144 priority patent/US12230086B2/en
Anticipated expiration legal-status Critical
Priority to US19/013,095 priority patent/US20250148851A1/en
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C9/00—Individual registration on entry or exit
    • G07C9/20—Individual registration on entry or exit involving the use of a pass
    • G07C9/22—Individual registration on entry or exit involving the use of a pass in combination with an identity check of the pass holder
    • G07C9/25—Individual registration on entry or exit involving the use of a pass in combination with an identity check of the pass holder using biometric data, e.g. fingerprints, iris scans or voice recognition
    • G07C9/26—Individual registration on entry or exit involving the use of a pass in combination with an identity check of the pass holder using biometric data, e.g. fingerprints, iris scans or voice recognition using a biometric sensor integrated in the pass
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31—User authentication
    • G06F21/32—User authentication using biometric data, e.g. fingerprints, iris scans or voiceprints
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31—User authentication
    • G06F21/33—User authentication using certificates
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/02—Reservations, e.g. for tickets, services or events
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/12—Payment architectures specially adapted for electronic shopping systems
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification
    • G06Q20/4014—Identity check for transactions
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G06Q30/0601—Electronic shopping [e-shopping]
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06V—IMAGE OR VIDEO RECOGNITION OR UNDERSTANDING
    • G06V40/00—Recognition of biometric, human-related or animal-related patterns in image or video data
    • G06V40/10—Human or animal bodies, e.g. vehicle occupants or pedestrians; Body parts, e.g. hands
    • G06V40/16—Human faces, e.g. facial parts, sketches or expressions
    • G06V40/168—Feature extraction; Face representation
    • G06V40/171—Local features and components; Facial parts ; Occluding parts, e.g. glasses; Geometrical relationships
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06V—IMAGE OR VIDEO RECOGNITION OR UNDERSTANDING
    • G06V40/00—Recognition of biometric, human-related or animal-related patterns in image or video data
    • G06V40/10—Human or animal bodies, e.g. vehicle occupants or pedestrians; Body parts, e.g. hands
    • G06V40/16—Human faces, e.g. facial parts, sketches or expressions
    • G06V40/172—Classification, e.g. identification
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06V—IMAGE OR VIDEO RECOGNITION OR UNDERSTANDING
    • G06V40/00—Recognition of biometric, human-related or animal-related patterns in image or video data
    • G06V40/40—Spoof detection, e.g. liveness detection
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C9/00—Individual registration on entry or exit
    • G07C9/20—Individual registration on entry or exit involving the use of a pass
    • G07C9/27—Individual registration on entry or exit involving the use of a pass with central registration
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07F—COIN-FREED OR LIKE APPARATUS
    • G07F17/00—Coin-freed apparatus for hiring articles; Coin-freed facilities or services
    • G07F17/42—Coin-freed apparatus for hiring articles; Coin-freed facilities or services for ticket printing or like apparatus, e.g. apparatus for dispensing of printed paper tickets or payment cards
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0407—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the identity of one or more communicating identities is hidden
    • H04L63/0421—Anonymous communication, i.e. the party's identifiers are hidden from the other party or parties, e.g. using an anonymizer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0861—Network architectures or network communication protocols for network security for authentication of entities using biometrical features, e.g. fingerprint, retina-scan

Definitions

  • the present invention relates to an information processing server, an information processing system, a determination device, a method, and the like.
  • Patent Document 1 information indicating the ticket holder's own face or the feature amount of his / her face is recorded as legitimate holder information, and the face of a person who is trying to enter at the entrance is photographed. , It is disclosed to confirm whether or not the person who is trying to enter is a legitimate holder by face recognition that matches the holder's own face or the feature amount of his / her face recorded on the ticket.
  • a face image or a face is used as face information of a legitimate holder (user).
  • the feature amount is recorded on the ticket.
  • Face images and facial features are user's own personal information, but if these are recorded in a ticket, personal information may be unintentionally passed on to a third party, so protection and security of personal information It was sometimes regarded as a problem from the viewpoint of. On the other hand, there is a problem that a ticket that does not include personal information may be easily resold.
  • the present invention has been made to solve such a problem, and provides an information processing server or the like capable of preventing unauthorized use of a ticket while reducing the risk of leakage of biometric information of a user who uses the ticket.
  • the main purpose is that.
  • the information processing server is An information processing server for managing tickets Judge the validity of the use of the feature amount data that can be acquired from the biological information and is created in advance, the feature amount identification information that can identify the feature amount data associated with the feature amount data, and the ticket.
  • a server storage unit that stores the same predetermined data as the predetermined data stored in the determination device for Including the server control unit
  • the server control unit Determine the ticket identification information that can identify the ticket for the ticket for which the application for issuance is accepted, or acquire the ticket identification information assigned to the ticket in advance.
  • Feature data is determined from the biometric information of the user who uses the entered ticket, and the feature amount data is determined.
  • the determined feature amount data is compared with the feature amount data stored in the server storage unit, the feature amount data having a predetermined similarity is determined, and the feature amount identification information associated with the feature amount data is obtained.
  • Decide, and Check data is calculated by performing a predetermined calculation based on at least one of the determined or acquired ticket identification information and the determined feature amount identification information, and the predetermined data, and the calculated check data and the check data
  • a code attached to the ticket is generated based on the determined or acquired ticket identification information and the determined feature amount identification information, and ticket data for outputting the ticket with the generated code is generated. It is characterized in that it is configured as follows.
  • the information processing server is An information processing server for managing tickets Server storage that stores the same predetermined data as the feature data that can be acquired from the biometric information and is stored in advance in the feature data and the determination device for determining the validity of the ticket use.
  • Department and Including the server control unit The server control unit Determine the ticket identification information that can identify the ticket for the ticket for which the application for issuance is accepted, or acquire the ticket identification information assigned to the ticket in advance.
  • Feature data is determined from the biometric information of the user who uses the entered ticket, and the feature amount data is determined.
  • the determined feature amount data is compared with the feature amount data stored in the server storage unit to determine the feature amount data having a predetermined similarity, and the feature amount data is determined.
  • Check data is calculated by performing a predetermined calculation based on at least one of the determined or acquired ticket identification information and the determined feature amount data, and the predetermined data, and the calculated check data and the said Generate a code attached to the ticket based on the determined or acquired ticket identification information and the determined feature amount data, and generate ticket data for outputting the ticket with the generated code. It is characterized by being composed.
  • the server control unit compares the determined feature amount data with the feature amount data stored in the server storage unit, and determines a plurality of feature amount data having a predetermined similarity.
  • the feature amount data stored in the server storage unit is feature amount data acquired from biometric information of a non-existent person or an unspecified real person, and is feature amount data created in advance.
  • the feature amount data stored in the server storage unit is face feature amount data indicating a feature amount corresponding to a point, line, or surface of a face feature that can be acquired based on a face image.
  • the feature amount data stored in the server storage unit is processed feature amount data generated based on the feature amount data.
  • the server control unit transfers the determined feature amount data and the processed feature amount stored in the server storage unit.
  • the processed feature data generated based on the feature data having a predetermined similarity is determined by comparing with the feature data on which the data is based.
  • the server control unit is configured to transmit ticket data for outputting a ticket to which the generated code is attached to a client terminal capable of communicating with the information processing server via a network.
  • the information processing system An information processing system including the information processing server and the determination device.
  • the determination device is A determination device storage unit that stores the predetermined data, the same feature amount data as the feature amount data and the feature amount identification information stored in the server storage unit, and the feature amount identification information associated with the feature amount data, and a determination device storage unit.
  • the determination device control unit Obtain ticket identification information, feature identification information, and check data from the code attached to the ticket, Obtain the biometric information of the user who presents the ticket, Based on the feature amount data and the feature amount identification information stored in association with each other in the determination device storage unit, the feature amount data determined from the acquired biological information and the acquired feature amount identification information satisfy a predetermined criterion.
  • the check data calculated by performing the predetermined calculation based on at least one of the acquired ticket identification information and the acquired feature amount identification information, and the predetermined data, and the acquired check data It is characterized in that it is configured to determine whether or not they match.
  • the predetermined criteria are From the feature amount data determined from the acquired biometric information and the feature amount data associated with the acquired feature amount identification information in the determination device storage unit having a predetermined similarity, and from the acquired biometric information.
  • the determined feature amount data is compared with the feature amount data stored in the determination device storage unit, the feature amount data having a predetermined similarity is determined, and the feature amount identification information associated with the feature amount data is obtained. Determined, and the determined feature amount identification information includes the acquired feature amount identification information. At least one of them.
  • the information processing system An information processing system including the information processing server and the determination device.
  • the determination device is A determination device storage unit that stores the same feature amount data as the predetermined data and the feature amount data stored in the server storage unit, and a determination device storage unit. Including the judgment device control unit
  • the determination device control unit Obtain ticket identification information, feature data, and check data from the code attached to the ticket, Obtain the biometric information of the user who presents the ticket, It is determined whether or not the feature amount data determined from the acquired biometric information and the acquired feature amount data have a predetermined degree of similarity, and
  • the determination device is It is a judgment device for judging the legitimacy of using a ticket.
  • Predetermined data that is the same as predetermined data stored in an information processing server that can generate ticket data for outputting a ticket, and feature amount data that can be acquired from biometric information stored in the information processing server.
  • Judgment device storage that stores the same feature amount data as the feature amount identification information that can identify the feature amount data and the feature amount data associated with the feature amount data, and the feature amount identification information associated with the feature amount data.
  • the ticket performs a predetermined calculation based on at least one of the ticket identification information that can identify the ticket assigned to the ticket and the feature amount identification information determined based on the biometric information of the user who uses the ticket, and the predetermined data.
  • a code generated based on the check data calculated by the above, the ticket identification information, and the feature amount identification information is attached.
  • the determination device control unit Obtain ticket identification information, feature identification information, and check data from the code attached to the ticket, Obtain the biometric information of the user who presents the ticket, Based on the feature amount data and the feature amount identification information stored in association with each other in the determination device storage unit, the feature amount data determined from the acquired biological information and the acquired feature amount identification information satisfy a predetermined criterion.
  • the check data calculated by performing the predetermined calculation based on at least one of the acquired ticket identification information and the acquired feature amount identification information, and the predetermined data, and the acquired check data It is characterized in that it is configured to determine whether or not they match.
  • the determination device is It is a judgment device for judging the legitimacy of using a ticket.
  • Predetermined data that is the same as predetermined data stored in an information processing server that can generate ticket data for outputting a ticket, and feature amount data that can be acquired from biometric information stored in the information processing server.
  • Judgment device storage unit that stores the same feature amount data as the feature amount data Including the judgment device control unit
  • the ticket is to perform a predetermined calculation based on at least one of the feature amount data determined based on the ticket identification information that can identify the ticket assigned to the ticket and the biometric information of the user who uses the ticket, and the predetermined data.
  • a code generated based on the check data calculated by the above, the ticket identification information, and the feature amount data is attached.
  • the determination device control unit Obtain ticket identification information, feature data, and check data from the code attached to the ticket, Obtain the biometric information of the user who presents the ticket, It is determined whether or not the feature amount data stored in the determination device storage unit and the feature amount data determined from the acquired biometric information satisfy a predetermined criterion, and The check data calculated by performing the predetermined calculation based on at least one of the acquired ticket identification information and the acquired feature amount data and the predetermined data matches the acquired check data. It is characterized in that it is configured to determine whether or not to do so.
  • the method of one embodiment of the present invention A method of managing tickets, run by a computer,
  • the method is a feature amount data indicating a feature amount that can be acquired from biological information, and is a feature amount data created in advance, a feature amount identification information that can identify the feature amount data associated with the feature amount data, and a ticket.
  • a database that stores the same predetermined data as the predetermined data stored in the determination device for determining the validity of the use of the data is used.
  • the determined feature amount data is compared with the feature amount data stored in the database, the feature amount data having a predetermined similarity is determined, and the feature amount identification information associated with the feature amount data is determined.
  • Steps and Check data is calculated by performing a predetermined calculation based on at least one of the determined or acquired ticket identification information and the determined feature amount identification information, and the predetermined data, and the calculated check data and the check data
  • a code attached to the ticket is generated based on the determined or acquired ticket identification information and the determined feature amount identification information, and ticket data for outputting the ticket with the generated code is generated.
  • Steps and It is characterized by including.
  • the method of one embodiment of the present invention A method of managing tickets, run by a computer, The method is the same as the feature amount data indicating the feature amount that can be acquired from the biological information, the feature amount data created in advance, and the predetermined data stored in the determination device for determining the validity of the use of the ticket. It uses a database that stores the specified data of The step of determining the ticket identification information that can identify the ticket for the ticket for which the application for issuance is accepted or acquiring the ticket identification information assigned to the ticket in advance, and Steps to determine feature data from the biometric information of the user who uses the entered ticket, A step of comparing the determined feature amount data with the feature amount data stored in the database to determine feature amount data having a predetermined similarity.
  • Check data is calculated by performing a predetermined calculation based on at least one of the determined or acquired ticket identification information and the determined feature amount data, and the predetermined data, and the calculated check data and the said A step of generating a code attached to a ticket based on the determined or acquired ticket identification information and the determined feature amount data, and generating ticket data for outputting the ticket with the generated code. , It is characterized by including.
  • the method of one embodiment of the present invention A method of determining the legitimacy of using a ticket, executed by a computer.
  • the same predetermined data as the predetermined data stored in the information processing server capable of generating the ticket data for outputting the ticket, and the feature amount data that can be acquired from the biometric information stored in the information processing server are used.
  • the ticket uses a database that The ticket performs a predetermined calculation based on at least one of the ticket identification information that can identify the ticket assigned to the ticket and the feature amount identification information determined based on the biometric information of the user who uses the ticket, and the predetermined data.
  • a code generated based on the check data calculated by the above, the determined ticket identification information, and the determined feature amount identification information is attached.
  • Steps to determine The check data calculated by performing the predetermined calculation based on at least one of the acquired ticket identification information and the acquired feature amount identification information, and the predetermined data, and the acquired check data Steps to determine if they match and It is characterized by including.
  • the method of one embodiment of the present invention A method of determining the legitimacy of using a ticket, executed by a computer.
  • the same predetermined data as the predetermined data stored in the information processing server capable of generating the ticket data for outputting the ticket, and the feature amount data that can be acquired from the biometric information stored in the information processing server are used. It uses a database that stores the same feature amount data as the feature amount data created in advance.
  • the ticket is to perform a predetermined calculation based on at least one of the feature amount data determined based on the ticket identification information that can identify the ticket assigned to the ticket and the biometric information of the user who uses the ticket, and the predetermined data.
  • a code generated based on the check data calculated by the above, the determined ticket identification information, and the determined feature amount data is attached.
  • Steps to acquire ticket identification information, feature data, and check data from the code attached to the ticket Steps to get biometric information of the user presenting the ticket,
  • the check data calculated by performing the predetermined calculation based on at least one of the acquired ticket identification information and the acquired feature amount data and the predetermined data matches the acquired check data. Steps to determine whether or not to do It is characterized by including.
  • the program of one embodiment of the present invention is characterized in that a computer is made to execute each step of the method described above.
  • the present invention it is possible to prevent unauthorized use of the ticket while reducing the risk of leakage of biometric information of the user who uses the ticket.
  • a main embodiment of the present invention is an information processing server 1, a determination device 2, or an information processing system 10 including these.
  • the same reference numerals indicate the same or corresponding parts unless otherwise specified, and unnecessarily detailed description may be omitted.
  • the data structure and database structure in the database described in the embodiment of the present invention are examples, and are not limited thereto.
  • the ticket is an admission ticket required for admission to a predetermined event such as a concert or a sports match. Tickets include electronic tickets and paper tickets.
  • the ticket described in the embodiment of the present invention can include a coupon or a ticket other than the admission ticket described above as long as it does not deviate from the gist of the invention, and can be used with any medium having a property value. You can also do it.
  • FIG. 1 is an overall configuration diagram of the information processing system 10 according to the first embodiment of the present invention.
  • the information processing system 10 includes an information processing server 1, a determination device 2, a client terminal 3, and a ticket sales server 4.
  • the information processing server 1 is a device for managing information related to tickets.
  • the determination device 2 is installed at the entrance of the event venue to determine the legitimacy of using the ticket. To determine the legitimacy of using a ticket is whether the combination of the presented ticket and the user who uses the ticket is valid, that is, whether the user who uses the ticket is the legitimate holder of the ticket. Includes determining whether or not.
  • Determining the legitimacy of using a ticket also includes determining the legitimacy of the ticket itself (for example, the ticket is not a counterfeit ticket).
  • the determination device 2 is embodied as a device for ticket inspection and collation at the time of admission, or is embodied as a part of the device.
  • the information processing server 1 and the determination device 2 are connected to the network 5 and can communicate with each other.
  • the information processing server 1, the client terminal 3, and the ticket sales server 4 are connected to the network 6 and can communicate with each other.
  • FIG. 1 shows that the determination device 2 is configured so as not to communicate with or cannot communicate with the client terminal 3 and the ticket sales server 4, so that the determination device 2 is connected to the information processing server 1 via a network 5 different from these.
  • the determination device 2 may be connected to the information processing server 1 via the same network as the client terminal 3 and the ticket sales server 4.
  • networks 5 and 6 are the Internet.
  • the determination device 2 may be installed at the venue of the event and can communicate with the information processing server 1 before determining the validity of the ticket use, and when determining the validity of the ticket use, the determination device 2 is used. 2 does not have to be connected to the information processing server 1 via the network 5.
  • the information processing system 10 since the client terminal 3 and the ticket sales server 4 can be known devices, the information processing system 10 does not have to include the client terminal 3 and the ticket sales server 4.
  • FIG. 2 is a block diagram showing a hardware configuration of the information processing server 1 according to the first embodiment of the present invention.
  • the information processing server 1 has the same configuration as a general server.
  • the information processing server 1 includes a processor 11, an input device 12, a display device 13, a storage device 14, and a communication device 15. Each of these components is connected by a bus 16. It is assumed that an interface is interposed between the bus 16 and each component device as needed.
  • the information processing server 1 may be composed of a plurality of computers.
  • the processor 11 controls the operation of the information processing server 1, and is, for example, a CPU.
  • the processor 11 an electronic circuit such as an MPU may be used.
  • the processor 11 executes various processes by reading and executing a program or data stored in the storage device 14.
  • the input device 12 is a user interface that receives input from the user to the information processing server 1, and is, for example, a touch panel, a touch pad, a mouse, or a keyboard.
  • the display device (display) 13 displays an application screen or the like to the user of the information processing server 1 under the control of the processor 11.
  • the storage device 14 includes a main storage device and an auxiliary storage device.
  • the main storage device is a semiconductor memory such as RAM.
  • the RAM is a volatile storage medium capable of reading and writing information at high speed, and is used as a storage area and a work area when the processor 11 processes information.
  • the auxiliary storage device stores various programs and data used by the processor 11 when executing each program.
  • the auxiliary storage device is, for example, a hard disk device, but may be any non-volatile storage or non-volatile memory as long as it can store information, and may be removable.
  • the communication device 15 is a wireless LAN module capable of exchanging data with another computer such as a user terminal or a server via a network.
  • the communication device 15 can be another wireless communication device such as a Bluetooth (registered trademark) module, or can be a wired communication device such as an Ethernet (registered trademark) module or a USB interface.
  • FIG. 3 is a block diagram showing a hardware configuration of the client terminal 3 according to the first embodiment of the present invention.
  • the client terminal 3 is a computer installed in a ticket store or the like, or a computer, tablet terminal, or smartphone owned by a user who uses the ticket.
  • the client terminal 3 includes a processor 51, an input device 52, a display device 53, a storage device 54, and a communication device 55. Each of these components is connected by a bus 56. It is assumed that an interface is interposed between the bus 56 and each component device as needed.
  • Each element of the processor 51, the input device 52, the display device 53, the storage device 54, and the communication device 55 corresponds to the processor 11, the input device 12, the display device 13, the storage device 14, and the communication device 15, respectively. Since it has the same configuration, the description thereof will be omitted.
  • a web browser is installed on the client terminal 3. A user can browse a web page using a web browser or send data to a web server using an input form on the web page.
  • FIG. 4 is a block diagram showing a hardware configuration of the ticket sales server 4 according to the first embodiment of the present invention.
  • the ticket sales server 4 has the same configuration as a general server.
  • the ticket sales server 4 includes a processor 61, an input device 62, a display device 63, a storage device 64, and a communication device 65. Each of these components is connected by a bus 66. It is assumed that an interface is interposed between the bus 66 and each component device as needed.
  • Each element of the processor 61, the input device 62, the display device 63, the storage device 64, and the communication device 65 corresponds to the processor 11, the input device 12, the display device 13, the storage device 14, and the communication device 15, respectively. Since it has the same configuration, the description thereof will be omitted.
  • the ticket sales server 4 may be composed of a plurality of computers.
  • FIG. 5 is an example of a functional block diagram of the information processing server 1 according to the first embodiment of the present invention.
  • the information processing server 1 includes a server control unit 21 and a server storage unit 22.
  • these functions are realized by the program being executed by the processor 11 or by the storage device 14.
  • the program to be executed is a program stored in the storage device 14 or received via the communication device 15.
  • another part may have a part or all of one part (function).
  • these functions may be realized by hardware by configuring an electronic circuit or the like for realizing a part or all of each function.
  • the server control unit 21 manages information related to tickets and generates data necessary for ticketing.
  • the information processing server 1 can function as a web server, and the server control unit 21 can be provided with a function of performing processing such as generation and transmission of a web page.
  • the information processing server 1 can also function as an application server, and the server control unit 21 can be provided with a function of performing connection control to a database, transaction processing, and the like.
  • the server storage unit 22 has a function of storing programs, data, and the like.
  • the function of the server storage unit 22 is realized by the storage device 14.
  • the server storage unit 22 can store data for providing a web page, for example, an HTML document, an image, a program for an application server function, and the like.
  • the server storage unit 22 has a database function.
  • the database function is realized when the storage device 14 stores data (for example, a table) or a program for various databases and the program is executed.
  • the server storage unit 22 stores the event table 24, the ticket book table 25, the feature amount table 26, and the ticket table 27.
  • the event table 24 includes event IDs and event information including information such as event names, dates, and venues as data items. Data items correspond to columns.
  • the event table 24 may also include, as a data item, an impresario ID for associating with an impresario table that stores information about the impresario.
  • the primary key of the event table 24 is an event ID, and the event ID is an example of event identification information that can identify an event.
  • the ticket book table 25 includes a ticket book ID and an event ID as data items.
  • the primary key of the ticket book table 25 is the ticket book ID.
  • the feature amount table 26 includes a feature amount ID and facial feature amount data that can be acquired based on a face image.
  • the primary key of the feature amount table 26 is the feature amount ID
  • the feature amount ID is one example of the feature amount identification information capable of identifying the face feature amount data.
  • the ticket table 27 includes a ticket ID, a ticket book ID, detailed ticket information including information such as seats and amounts of tickets, and a feature amount ID as data items.
  • the primary key of the ticket table 27 is a ticket ID, which is an example of ticket identification information that can identify a ticket.
  • the ticket ID, the feature amount ID, and the event ID are numerical data. However, these IDs may be other data that can be treated as numerical data.
  • the server storage unit 22 may store the impresario table including the impresario ID and the impresario information including information such as contract details as data items.
  • the ticket ID of the ticket issued in one event is associated with the event ID of the one event.
  • the ticket ID is associated with the event ID by associating the ticket ID and the ticket book ID with the ticket table 27 and associating the ticket book ID with the event ID at the ticket book table 25.
  • the facial feature amount data is feature amount data indicating a feature amount corresponding to a point, line, or surface of a face feature extracted or acquired from a face image by a known feature amount extraction method.
  • the facial feature amount data is acquired by executing a program of a known software library on the facial image, and is represented by a multidimensional vector.
  • FIG. 6 is an example of the feature amount table 26.
  • the facial feature amount data is data showing numerical information of a 128-dimensional vector (128-dimensional array structure) acquired by using a known facial feature amount extraction program, 128. It is the data in which each of the numerical values of each dimension of the dimension vector is arranged as it is.
  • the facial feature amount extraction program is stored in the server storage unit 22 (storage device 14).
  • the facial feature extraction program may be a trained model.
  • the face image may be two-dimensional data or three-dimensional data including a three-dimensional shape.
  • the facial feature data stored in the feature table 26 is facial feature data acquired from a face image of a non-existent person or an unspecified real person, and is created in advance using the above-mentioned facial feature extraction program.
  • the feature amount table 26 stores a plurality of (for example, 5,000) facial feature amount data acquired from the face images of a plurality of (for example, 5,000) non-existent persons or unspecified real persons prepared in advance. In this way, the feature amount table 26 stores each of the face feature amount data corresponding to each of the face images of the non-existent person or the unspecified real person, but corresponds to the face image of the user who uses the ticket. It does not store facial feature data.
  • the server storage unit 22 stores the ticket ID, the face feature amount data created in advance, the feature amount ID associated with the face feature amount data, and the event ID stored in the determination device 2. And the same event ID as.
  • the server control unit 21 has a function of creating a ticket management web page (ticket management website) for each ticket ID.
  • the ticket management web page includes a screen for registering a face image and a screen for displaying ticket data for outputting a ticket.
  • Ticket data can also be said to be data for displaying the face of the ticket.
  • the ticket sales server 4 is a known server device or server system operated by the ticket sales source.
  • the ticket sales server 4 functions as a web server, and performs processing such as generation and transmission of a web page such as a ticket sales site (ticket sales page) in response to a request from the client terminal 3.
  • the ticket sales server 4 can also function as an application server, and can perform connection control to a database related to ticket sales processing, transaction processing, and the like.
  • the storage device 64 can store data for providing a web page, for example, an HTML document, an image, a program for an application server function, and the like.
  • the ticket sales server 4 includes a ticket sales database that stores ticket information related to tickets managed by the ticket seller and ticket inventory information indicating whether or not each ticket has been purchased.
  • the ticket information stored in the ticket sales database is, for example, event information including the date and place of the event, detailed ticket information including seat type or specific seat number and amount information, and the like for selling tickets. Contains the required information.
  • the user operates the client terminal 3 and performs ticket selection, purchase application for the selected ticket, payment processing, etc. via the ticket sales site.
  • the ticket sales server 4 receives the order information including the ticket information and the user information for which the purchase application has been accepted from the client terminal 3.
  • the ticket information included in the order information is, for example, event information including the date and place of the event, detailed ticket information including seat type or specific seat number and amount information, and is necessary for specifying the ticket. Contains information.
  • the user information included in the order information is the e-mail address of the user whose input is received by the client terminal 3 via the ticket sales site.
  • the e-mail address can be a telephone number, an SNS, an ID of a chat tool, or the like.
  • the order information is created for each order received from the client terminal 3 and transmitted to the ticket sales server 4.
  • FIG. 7 is a flowchart showing the operation of the information processing server 1 according to the first embodiment of the present invention.
  • step 101 the client terminal 3 accepts the input of the ticket purchase application via the ticket sales site.
  • the client terminal 3 transmits the ticket information including the ticket information and the user information regarding the ticket for which the purchase application has been accepted to the ticket sales server 4 via the ticket sales site.
  • the ticket information for which the purchase application has been accepted is the ticket information for one or more tickets.
  • step 102 the ticket sales server 4 receives the order information from the client terminal 3 to accept the application for purchasing the ticket from the client terminal 3 and update the ticket sales database.
  • the ticket sales server 4 transmits the order information to the information processing server 1 for each received order information.
  • the ticket sales server 4 and the information processing server 1 can synchronize the data between the servers. This synchronization between servers may be performed on a regular basis.
  • the information processing server 1 receives order information from the ticket sales server 4 and accepts an application for purchasing a ticket.
  • the server control unit 21 determines the ticket ID for the ticket for which the purchase application has been accepted. Specifically, the server control unit 21 determines the ticket book ID and the ticket ID associated with the ticket specified by the received order information. In one example, determining a ticket ID for a ticket for which a purchase application has been accepted is to create a new ticket ID in response to the ticket purchase application and assign it to the ticket for which the application has been accepted. In one example, determining the ticket ID for the ticket for which the purchase application has been accepted is to assign the ticket ID created in advance in the ticket table 27 to the ticket for which the ticket purchase application has been accepted. The above example also applies to the ticket book ID.
  • the server control unit 21 determines an event ID corresponding to the event information included in the received ticket information, associates it with the ticket book ID, and stores it in the ticket book table 25.
  • the server control unit 21 stores the ticket book ID determined for the same order information as the ticket ID in the ticket table 27 in association with the ticket ID. For example, when the ticket information received from the ticket sales server 4 is ticket information related to a plurality of tickets (A tickets), the server control unit 21 determines one ticket book ID and A ticket IDs. In one example, the server control unit 21 stores the detailed ticket information among the received ticket information in the ticket table 27 in association with the ticket ID.
  • the event ID of the event is created, and the created event ID and the event information associated with the event ID are stored in the event table 24.
  • the event ID determined in step 104 is the same as the event ID stored in the determination device 2 for which the validity of the use of the ticket to which the ticket ID associated with the event ID is assigned is determined.
  • the information processing server 1 may share an event ID with the ticket sales server 4. In this case, the ticket information received by the information processing server 1 from the ticket sales server 4 includes the event ID.
  • the order information received by the information processing server 1 does not have to be the same as the order information received from the client terminal 3 by the ticket sales server 4 as long as it includes ticket information and user information.
  • step 105 the server control unit 21 transmits the address (URL) of the ticket management web page associated with the ticket ID to the user's e-mail address included in the user information included in the received order information.
  • the server control unit 21 transmits the address of one ticket management web page for one ticket ID.
  • step 106 the client terminal 3 accesses the URL received from the information processing server 1 and displays the ticket management web page.
  • the ticket management web page displays a screen asking the user to input a face image.
  • the client terminal 3 receives the input of the face image from the user via the ticket management web page and transmits it to the information processing server 1.
  • the face feature amount data is determined from the face image of the user who uses the input ticket.
  • the server control unit 21 determines the face feature amount data from the received face image by using the face feature amount extraction program stored in the server storage unit 22.
  • the server control unit 21 determines the face feature amount data by calculating the face feature amount data from the received face image or acquiring the face feature amount data from the received face image.
  • step 108 the server control unit 21 compares the face feature amount data determined in step 107 with the face feature amount data stored in the feature amount table 26, and compares the face feature amount data stored in the feature amount table 26 with the face feature amount data stored in the feature amount table 26.
  • the facial feature amount data having a predetermined degree of similarity among them is determined.
  • the server control unit 21 compares each of the facial feature data stored in the feature table 26 with respect to the facial feature data determined in step 107, and compares each of the facial feature data stored in the feature table 26 with each other. Is calculated.
  • the server control unit 21 compares each of the predetermined facial feature data among the facial feature data stored in the feature table 26 with the facial feature data determined in step 107.
  • the server control unit 21 determines the feature amount ID associated with the determined face feature amount data. In one example, the server control unit 21 stores the feature amount ID determined in association with the ticket ID in the ticket table 27. In the present embodiment, for convenience of explanation, the server control unit 21 determines the face feature amount data of one of the face feature amount data stored in the feature amount table 26. In order to reduce the amount of information processing calculation, the face feature amount data determined by the server control unit 21 in step 107 and the face feature amount data stored in the feature amount table 26 may have the same data structure. can. This also applies to other embodiments.
  • the face feature amount data is data indicating numerical information of a 128-dimensional vector, and the similarity corresponds to the Euclidean distance of the two face feature amount data to be compared.
  • the server control unit 21 determines whether or not the Euclidean distance between the two facial feature amount data to be compared is equal to or less than a predetermined value. That is, the server control unit 21 uses the feature amount table 26 to display the face feature amount data in which the Euclidean distance between the face feature amount data determined in step 107 and the face feature amount data stored in the feature amount table 26 is equal to or less than a predetermined value. Determined from the facial feature data stored by.
  • the server control unit 21 determines arbitrary facial feature amount data in which the Euclidean distance is equal to or less than a predetermined value. Alternatively, in one example, the server control unit 21 determines the facial feature amount data having the smallest Euclidean distance.
  • step 109 the server control unit 21 performs a predetermined calculation based on the ticket ID determined in step 104, the feature amount ID determined in step 108, and the event ID determined in step 104, thereby performing check data. Is calculated.
  • the server control unit 21 generates a code attached to the ticket based on the ticket ID determined in step 104, the feature amount ID determined in step 108, and the calculated check data.
  • the server control unit 21 generates ticket data for outputting a ticket to which the generated code is attached.
  • the predetermined calculation is realized by the check data calculation program, and the server control unit 21 calculates the check data by using the check data calculation program.
  • the check data calculation program calculates the sum of the ticket ID determined in step 104, the feature amount ID determined in step 108, and the event ID determined in step 104, and the last digit or the last two digits thereof are calculated. Calculate the digits as check data.
  • the check data calculation program inputs the ticket ID determined in step 104, the feature amount ID determined in step 108, and the event ID determined in step 104 into a predetermined function, and outputs the output value. Calculated as check data.
  • a given function is a one-way function.
  • the check data is one or more digit numerical data.
  • the check data is a check digit.
  • the check data calculation program is stored in the server storage unit 22.
  • the code generated by the server control unit 21 is a QR code (registered trademark) that stores data corresponding to each of the ticket ID, the feature amount ID, and the check data. For example, each of the data is stored at a predetermined position in the data area of the QR code®.
  • the code generated by the server control unit 21 may be a one-dimensional code or a two-dimensional code other than the QR code (registered trademark).
  • the information processing server 1 transmits the ticket data generated in step 109 to the client terminal 3 via the ticket management web page, and the client terminal 3 receives the ticket data. In one example, the information processing server 1 transmits the generated ticket data to the user's e-mail address as the address of a web page on which the generated ticket data can be downloaded.
  • the client terminal 3 outputs a ticket with the code generated in step 109 based on the received ticket data.
  • the client terminal 3 displays the ticket with the code generated in step 109 on the display device 53 as an electronic ticket based on the received ticket data.
  • the client terminal 3 outputs a paper ticket with the code generated in step 109 from a printer communicably connected to the client terminal 3 based on the received ticket data.
  • the client terminal 3 displays the image as it is, and when the ticket data is processed data or encrypted data, the client terminal 3 outputs a ticket using the corresponding application.
  • the client terminal 3 that accepts the purchase application, the client terminal 3 that accepts the input of the face image, and the client terminal 3 that receives the ticket data may be the same terminal or different terminals depending on the usage mode. Can also be configured to be usable.
  • the server control unit 21 can accept changes of the user who uses the ticket via the ticket management web page after generating the ticket data in step 109.
  • the user operates the client terminal 3 to access the ticket management web page associated with the ID of the ticket, and the user of the user You need to enter a face image.
  • the server control unit 21 can accept the input of the face image of the user who uses the ticket, for example, via the ticket management web page linked to the ticket ID of the transferred ticket.
  • the server control unit 21 executes the processes of steps 107 to 109 and generates new ticket data.
  • FIG. 8 is a diagram showing an example of a paper-based ticket output based on the ticket data.
  • the event information 71 such as the event name, date, and venue, and the QR code (registered trademark) 72 generated by the server control unit 21 are printed on the paper ticket. ..
  • the electronic ticket also includes the event information 71 and the QR code (registered trademark) 72 in the same manner as the paper ticket.
  • the information processing server 1 when the face image of the user who uses the ticket is input and the information processing server 1 can acquire the face image, the information processing server 1 is configured so that this flowchart does not include steps 105 and 106. be able to. In the present embodiment, the information processing server 1 only needs to receive the order information regarding the ticket for which the purchase application has been received, and the flowchart can be configured not to include steps 101 to 103.
  • FIG. 9 is a block diagram showing a hardware configuration of the determination device 2 according to the first embodiment of the present invention.
  • the determination device 2 includes a processor 31, an input device 32, a display device 33, a photographing device 34, a storage device 35, and a communication device 36. Each of these components is connected by a bus 37. It is assumed that an interface is interposed between the bus 37 and each component device as needed.
  • the determination device 2 is a tablet terminal such as an iPad (registered trademark).
  • the determination device 2 is not limited to the tablet terminal.
  • the determination device 2 may be configured to include a main body unit having the main functions of the determination device 2 and a photographing device 34 communicatively connected to the main body unit.
  • the processor 31 controls the operation of the information processing server 1, and is, for example, a CPU.
  • the processor 31 an electronic circuit such as an MPU may be used.
  • the processor 31 executes various processes by reading and executing a program or data stored in the storage device 35.
  • the input device 32 is a user interface that receives input from the user to the information processing server 1.
  • the display device (display) 33 displays an application screen or the like to the user of the information processing server 1 under the control of the processor 31.
  • the determination device 2 includes a touch panel 38 as an input device 32, the touch panel 38 also functions as a display device 33, and the input device 32 and the display device 33 are integrated.
  • the photographing device (imaging device) 34 captures (imaging) a still image or moving image in real space, and stores the captured image or moving image data in the storage device 35.
  • the photographing device 34 is a camera composed of, for example, an image sensor.
  • the storage device 35 includes a main storage device and an auxiliary storage device.
  • the main storage device is a semiconductor memory such as RAM.
  • the RAM is a volatile storage medium capable of reading and writing information at high speed, and is used as a storage area and a work area when the processor 31 processes information.
  • the auxiliary storage device stores various programs and data used by the processor 31 when executing each program.
  • the auxiliary storage device is, for example, a hard disk device, but may be any non-volatile storage or non-volatile memory as long as it can store information, and may be removable.
  • the communication device 36 is a wireless LAN module capable of exchanging data with another computer such as a user terminal or a server via a network.
  • the communication device 36 can be another wireless communication device such as a Bluetooth (registered trademark) module, or can be a wired communication device such as an Ethernet (registered trademark) module or a USB interface. Since the determination device 2 may be configured to receive data from the information processing server 1 when determining the legitimacy of using the ticket, the determination device 2 does not have to include the communication device 36. ..
  • FIG. 10 is an example of a functional block diagram of the determination device 2 according to the first embodiment of the present invention.
  • the determination device 2 includes a determination device control unit 41 and a determination device storage unit 42.
  • these functions are realized by the program being executed by the processor 31 or by the storage device 35.
  • the program to be executed is a program stored in the storage device 35 or received via the communication device 15.
  • another part may have a part or all of one part (function).
  • these functions may be realized by hardware by configuring an electronic circuit or the like for realizing a part or all of each function.
  • the determination device storage unit 42 has a database function.
  • the database function is realized when the storage device 35 stores data (for example, a table) or a program for various databases and the program is executed.
  • the determination device control unit 41 determines the legitimacy of using the ticket, for example, whether or not the combination of the presented ticket and the user who uses the ticket is valid.
  • the determination device storage unit 42 has a function of storing programs, data, and the like. The function of the determination device storage unit 42 is realized by the storage device 35.
  • the determination device storage unit 42 stores the feature amount table 46, which is the same feature amount table as the feature amount table 26 stored in the server storage unit 22.
  • the feature amount table 46 is stored before the determination device 2 is installed at the venue of the event and determines the validity of the use of the ticket.
  • FIG. 11 is a flowchart showing the operation of the determination device 2 according to the first embodiment of the present invention.
  • the determination device 2 is installed at the entrance of the event venue so that the photographing device 34 can photograph the ticket and the face of the user who uses the ticket when the user who uses the ticket enters the venue of the event.
  • the determination device storage unit 42 stores the event ID of the installed target event.
  • the determination device control unit 41 operates the photographing device 34 to photograph the ticket and the user presenting the ticket, acquire the face image of the user, and obtain the ticket ID and the feature amount from the code attached to the ticket. Acquire the ID and check data.
  • the determination device control unit 41 captures the code attached to the user's face and the ticket
  • the determination device control unit 41 displays the captured image on the display device 33, and the user uses the ticket in a predetermined area. Display to guide the face and ticket to move.
  • a program for acquiring data included in the code is installed in the determination device 2, so that the function of the determination device control unit 41 is realized.
  • step 202 the determination device control unit 41 determines the face feature amount data from the acquired user's face image by using the same face feature amount extraction program as the face feature amount extraction program stored in the server storage unit 22. ..
  • the facial feature amount extraction program is stored in the determination device storage unit 42.
  • step 203 the determination device control unit 41 determines the feature amount ID acquired in step 201 and the face feature determined in step 202 based on the feature amount ID and the face feature amount data associated and stored in the feature amount table 46. It is determined whether or not the quantity data meets a predetermined criterion.
  • determining whether or not a predetermined criterion is satisfied is a facial feature amount in which the facial feature amount data determined in step 202 and the feature amount ID acquired in step 201 are associated with each other in the feature amount table 46. It is to determine whether or not the data has a predetermined degree of similarity. In this case, satisfying a predetermined criterion means having the predetermined similarity. In one example, determining whether or not the predetermined criteria are satisfied is determined by comparing the facial feature amount data determined in step 202 with the facial feature amount data stored in the feature amount table 46.
  • facial feature data having a predetermined degree of similarity is determined, and the feature ID associated with the facial feature data is determined (acquired), and the determined feature ID is It is to determine whether or not the feature amount ID acquired in step 201 is included.
  • satisfying a predetermined criterion is to include the feature amount ID.
  • determining whether or not a predetermined criterion is satisfied is determining whether or not both of the above two examples are satisfied.
  • satisfying a predetermined criterion means having the predetermined similarity and including the feature ID.
  • the predetermined similarity in step 203 is preferably the same standard as the predetermined similarity in the process of step 108 of the server control unit 21.
  • step 203 If it is determined in step 203 that the predetermined criteria are satisfied, the process of this flowchart proceeds to step 204, and if it is determined in step 203 that the predetermined criteria are not satisfied, the process of this flowchart proceeds to step 206.
  • the determination device control unit 41 performs a predetermined calculation based on the ticket ID and the feature amount ID acquired in step 201 and the event ID stored in the determination device storage unit 42 to obtain check data. calculate.
  • the determination device control unit 41 determines whether or not the calculated check data and the check data acquired in step 201 match.
  • the predetermined calculation is the same as the calculation performed when the server control unit 21 calculates the check data in step 109.
  • the determination device storage unit 42 stores the same check data calculation program as the check data calculation program stored in the storage device 14.
  • the predetermined calculation is realized by the check data calculation program stored in the determination device storage unit 42, and the determination device control unit 41 calculates the check data using the check data calculation program. The same applies to the above in other embodiments.
  • step 204 the process of this flowchart proceeds to step 205, and if it is determined that they do not match in step 204, the process of this flowchart proceeds to step 206.
  • step 205 the determination device control unit 41 determines that the combination of the presented ticket and the user who uses the ticket is a correct combination and is a legitimate use.
  • step 206 the determination device control unit 41 determines that the combination of the presented ticket and the user who uses the ticket is an incorrect combination and is an illegal use.
  • a gate device is installed at the entrance of the event venue, and the determination device control unit 41 is configured to send a signal to the gate device to open or keep the gate open when it is determined to be a legitimate user. Will be done.
  • the determination device control unit 41 is configured to send a signal to the gate device to close or keep the gate closed when it is determined that the user is an unauthorized user. If it is determined that the user is an unauthorized user, the determination device control unit 41 may be configured to output an alarm.
  • the information processing server 1 stores the feature amount table 26 including the feature amount ID and the face feature amount data associated with the feature amount ID.
  • the information processing server 1 determines the face feature amount data from the face image of the user who uses the ticket, and stores the feature amount ID associated with the face feature amount data having a predetermined similarity with the face feature amount data.
  • the information processing server 1 stores the same event ID as the event ID stored in the determination device 2.
  • the information processing server 1 calculates check data by performing a predetermined calculation on a ticket for which a purchase application has been received, based on a determined or acquired ticket ID, a determined feature amount ID, and an event ID to be stored.
  • the information processing server 1 generates a code based on the calculated check data, the determined ticket ID, and the determined feature amount ID, and generates ticket data for outputting the ticket with the generated code. ..
  • the information processing server 1 can create ticket data for generating a ticket for which the validity of use is determined by the determination device 2 in the information processing system 10. can.
  • the determination device 2 stores the feature amount table 46 and the event ID of the target event before determining the validity of the use of the ticket, and also stores the same face feature amount extraction program as that stored in the information processing server 1. And the check data calculation program is stored.
  • the determination device 2 acquires the ticket ID, the feature amount ID, and the check data from the code attached to the ticket, and acquires the face image of the user.
  • the determination device 2 determines the face feature amount data from the acquired face image by using the face feature amount extraction program.
  • the determination device 2 uses the feature amount table 46 to determine whether or not the determined face feature amount and the feature amount ID acquired from the code satisfy a predetermined criterion.
  • the determination device 2 calculates the check data using the check data calculation program based on the acquired ticket ID and feature amount ID and the event ID stored in advance, and matches the acquired check data. Judge whether or not. With such a configuration, in the present embodiment, the determination device 2 can determine the validity of the use of the ticket generated by the information processing server 1 in the information processing system 10.
  • the information processing server 1 stores information (feature amount ID) related to biometric information similar to the biometric information of the user without storing the biometric information (face image) of the user who uses the ticket.
  • the ticket stores (retains) the feature amount ID via the code, but does not store the biometric information of the user who uses the ticket.
  • the determination device 2 does not store the biometric information or the feature amount ID of the user who uses the ticket.
  • the determination device 2 by configuring the determination device 2 to determine whether or not it satisfies a predetermined criterion, it is possible to determine with a certain accuracy whether or not the user presenting the ticket is a legitimate user of the ticket. Become.
  • the feature ID obtained from the code attached to the ticket is not directly linked to the face image of the user who uses the ticket, but the face has a predetermined degree of similarity to the face image for which input has been received in advance from the user. It is linked to the feature amount data via the feature amount table 26. Therefore, it can be said that the feature amount ID associated with the ticket is associated with a face image similar to the user's face image.
  • the configuration for performing such a determination in the present embodiment, it is possible to detect unauthorized use of the ticket based on biometric information with a certain accuracy, and it is possible to prevent resale.
  • the face image of the user who uses the ticket is assigned one of 10,000 types of face feature amount data.
  • the accuracy of determining whether or not the user presenting the ticket is a legitimate user of the ticket corresponds to the quantity of face feature amount data stored in the feature amount table 26. For example, the larger the amount of face feature amount data stored in the feature amount table 26, the higher the determination accuracy.
  • the event ID is stored only in the information processing server 1 and the determination device 2, and the ticket does not store (hold) the event ID. It is difficult to obtain the value of the event ID from the check data stored in the ticket via the code. Therefore, it is difficult to forge the code attached to the ticket. With such a configuration, in the present embodiment, it is possible to prevent forgery of the ticket.
  • the determination device 2 can be completely taken offline. Conventionally, the determination device determines the combination of the ticket and the user while communicating with other devices, and determines whether or not the attendee at the event venue is a legitimate holder of the ticket. However, at the venue of the event where the judgment device is installed, the communication environment may not be good, and the judgment device may not operate normally. In the present embodiment, the determination device 2 stores the feature amount table 46, the event ID of the target event, the face feature amount extraction program, and the check data calculation program, but the user's biological information (face). The feature amount ID determined based on the image) is not stored.
  • the information processing server 1 updates the biometric information (face image) of the user who uses the ticket and generates new ticket data.
  • the determination device 2 there is no necessary processing in the determination device 2.
  • the user who uses the ticket can display it on the screen of his / her own terminal (client terminal 3) and use it as an electronic ticket, or print out a paper ticket and use it. can.
  • client terminal 3 the user who uses the ticket
  • client terminal 3 can display it on the screen of his / her own terminal (client terminal 3) and use it as an electronic ticket, or print out a paper ticket and use it.
  • client terminal 3 the user who uses the ticket can display it on the screen of his / her own terminal (client terminal 3) and use it as an electronic ticket, or print out a paper ticket and use it.
  • client terminal 3 the user who uses the ticket can display it on the screen of his / her own terminal (client terminal 3) and use it as an electronic ticket, or print out a paper ticket and use it.
  • client terminal 3 the user who uses the ticket can display it on the screen of his / her own terminal (client terminal 3) and use it as an electronic ticket, or print out a paper ticket and use it.
  • client terminal 3 the user who uses the ticket can
  • the code attached to the ticket includes a feature amount ID which is identification information rather than face feature amount data having a relatively large amount of information.
  • the feature amount ID is not used.
  • the ticket table 27 stores face feature amount data in association with the ticket ID instead of the feature amount ID.
  • the feature amount table 26 and the feature amount table 46 store the same facial feature amount data as in the first embodiment, but do not have to have the feature amount ID.
  • the face feature amount data does not have to be stored in the form of the feature amount tables 26 and 46.
  • FIG. 12 is a flowchart showing the operation of the information processing server 1 according to the second embodiment of the present invention.
  • Steps 301 to 307 are the same processes as steps 101 to 107 of the first embodiment.
  • the server control unit 21 compares the face feature amount data determined in step 307 with the face feature amount data stored in the feature amount table 26, and compares the face feature amount data stored in the feature amount table 26 with the face feature amount data stored in the feature amount table 26.
  • the facial feature amount data having a predetermined degree of similarity among them is determined.
  • the determination of the facial feature amount data in step 308 is the same process as the determination of the facial feature amount data in step 108 of the first embodiment.
  • the server control unit 21 stores the determined facial feature amount data in the ticket table 27 in association with the ticket ID.
  • step 309 the server control unit 21 performs a predetermined calculation based on the ticket ID determined in step 304, the face feature amount data determined in step 308, and the event ID determined in step 304 for checking. Calculate the data.
  • the server control unit 21 generates a code attached to the ticket based on the ticket ID determined in step 304, the face feature amount data determined in step 308, and the calculated check data.
  • the server control unit 21 generates ticket data for outputting a ticket to which the generated code is attached.
  • the predetermined calculation in the second embodiment is the same as the predetermined calculation in the first embodiment except that the face feature amount data is used instead of the feature amount ID described in the first embodiment.
  • the face feature amount data has a larger amount of information than the feature amount ID, the data of the default part of the face feature amount data may be used instead of the face feature amount data.
  • step 201 the determination device control unit 41 operates the photographing device 34 to photograph the ticket and the user presenting the ticket, acquire the user's face image, and obtain the ticket ID and face feature from the code attached to the ticket. Acquire quantity data and check data.
  • step 203 the determination device control unit 41 determines whether or not the face feature amount data acquired in step 201 and the face feature amount data determined in step 202 have a predetermined degree of similarity.
  • the predetermined similarity is preferably the same standard as the predetermined similarity in the process of step 308 of the server control unit 21.
  • step 204 the determination device control unit 41 performs a predetermined calculation based on the ticket ID and the face feature amount data acquired in step 201 and the event ID stored in the determination device storage unit 42, thereby performing check data. Is calculated. The determination device control unit 41 determines whether or not the calculated check data and the check data acquired in step 201 match.
  • the predetermined operation is the same process as the operation performed when the server control unit 21 calculates the check data.
  • the code attached to the ticket contains facial feature amount data having a larger amount of information than the code in the first embodiment, so it is difficult to perform smoother processing.
  • the same effects as those of the first embodiment can be obtained.
  • the server storage unit 22 further stores the user table 28 (not shown).
  • the user table 28 includes a user ID and linked user identification information which is user identification information in another system as data items.
  • the primary key of the user table 28 is a user ID
  • the user ID is an example of user identification information that can identify a user.
  • the server storage unit 22 may or may not store the ticket book table 25.
  • the server storage unit 22 does not store the ticket book table 25.
  • the event ID is stored in the ticket table 27 in association with the ticket ID.
  • the ticket sales server 4 further has a member database.
  • the member database is a database that stores member information of members of the ticket sales site.
  • Member information includes contact information such as member ID, password, name, and e-mail address.
  • the member ID is unique identification information for identifying a member who has registered to use the ticket sales site.
  • the password is a password used to authenticate the member.
  • the member ID and password of the member information are used for the member authentication.
  • the user needs to log in after registering as a member.
  • the linked user identification information is a member ID.
  • the ticket sales server 4 accepts the input of the face image from the user who has registered as a member, associates it with the member ID, and stores it in the member database.
  • the server control unit 21 has a function of creating a ticket management web page linked with a ticket sales site.
  • the ticket management web page links with the ticket sales site in association with the user ID or the linked user identification information (member ID), and displays the web page for each user ID. That is, the ticket management web page displays a web page corresponding to the user ID of each logged-in user.
  • the logged-in ticket sales site generates a link for accessing the ticket management web page, and the server control unit 21 uses the user ID by accessing from the ticket sales site via the link. Display the ticket management web page while logged in.
  • the logged-in ticket sales site may indicate to the user who purchased the ticket that it is necessary to input a face image in order to make the ticket available.
  • the information processing server 1 is configured to be able to transmit ticket data to the client terminal 3 via a ticket management web page.
  • FIG. 13 is a flowchart showing the operation of the information processing server 1 according to the third embodiment of the present invention.
  • the operation of the information processing system 10 including the operations of the server control unit 21 and the server storage unit 22 will be described with reference to this flowchart.
  • Steps 401 to 403 and 406 to 408 are the same processes as steps 101 to 103 and 107 to 109 of the first embodiment, respectively.
  • the user information included in the order information transmitted by the ticket sales server 4 to the information processing server 1 includes the member ID.
  • the server control unit 21 determines the ticket ID for the ticket for which the purchase application has been accepted.
  • the server control unit 21 determines an event ID corresponding to the event information included in the received ticket information, associates it with the ticket ID, and stores it in the ticket table 27.
  • the server control unit 21 determines a user ID to be associated with the ticket ID, associates the member ID of the received user information with the user ID, and stores it in the user table 28.
  • the user ID determined by the server control unit 21 is the user ID associated with the member ID in the user table 28.
  • step 405 the server control unit 21 acquires the face image associated with the member ID from the ticket sales server 4.
  • the server control unit 21 associates the feature amount ID with the user ID and stores it in the user table 28.
  • the server control unit 21 may store the feature amount ID in the ticket table 27 in association with the ticket ID.
  • step 405 when the ticket sales server 4 does not store the face image or cannot acquire the face image, the server control unit 21 displays a screen asking the user to input the face image on the ticket management web page.
  • the server control unit 21 accepts the input of the face image from the user via the ticket management web page.
  • the server control unit 21 displays the ticket management web page associated with the user ID or the member ID, and the face feature amount determined from the face image of the user who has received the input once. Data can be linked to the user ID. As a result, the next time a ticket is purchased on the same ticket sales site, it is not necessary to input a new face image, so that it is possible to promote the use by a wide range of users. This also applies to the second example.
  • the information processing server 1 and the ticket sales server 4 have a social login function that allows users to log in with an account of a social network service (SNS). The user needs to log in using the SNS account to purchase the ticket.
  • SNS social network service
  • the linked user identification information in the second example is an SNS account ID such as an e-mail address.
  • the user information included in the order information transmitted by the ticket sales server 4 to the information processing server 1 includes the SNS account ID.
  • it is the SNS account ID that the server control unit 21 stores in the user table 28 in association with the user ID.
  • the face image acquired by the server control unit 21 is a face image such as a profile image associated with the SNS account ID from the SNS web page.
  • the feature amount ID is not used.
  • the ticket table 27 stores face feature amount data in association with the ticket ID instead of the feature amount ID.
  • the feature amount table 26 and the feature amount table 46 store the same facial feature amount data as in the first embodiment, but do not have to have the feature amount ID.
  • the face feature amount data does not have to be stored in the form of the feature amount tables 26 and 46.
  • FIG. 14 is a flowchart showing the operation of the information processing server 1 according to the fourth embodiment of the present invention.
  • the operation of the information processing system 10 including the operations of the server control unit 21 and the server storage unit 22 will be described with reference to this flowchart.
  • Steps 501 to 506 are the same processes as 401 to 406 of the third embodiment, and steps 507 to 508 are the same processes as 308 to 309 of the second embodiment.
  • a program that realizes the functions of the embodiment of the present invention described above and the information processing shown in the flowchart, or a computer-readable storage medium that stores the program can also be used. Further, in another embodiment, it is also possible to use a method for realizing the functions of the embodiment of the present invention described above and the information processing shown in the flowchart.
  • the server may be a server capable of supplying the computer with a program that realizes the functions of the embodiment of the present invention described above and the information processing shown in the flowchart. Further, in another embodiment, it can be a virtual machine that realizes the functions of the embodiment of the present invention described above and the information processing shown in the flowchart.
  • the information processing server 1 is realized by a cloud (cloud server).
  • the information processing server 1 executes a predetermined process with respect to the ticket for which the purchase application has been received and generates ticket data.
  • the ticket purchase application according to the embodiment of the present invention. Can apply for the issuance of tickets other than purchase.
  • the facial feature amount data is an example of the feature amount data that can be acquired from biological information.
  • the feature amount data that can be acquired from the biological information can be palm print data or voice print data.
  • the feature amount table 26 does not store the face feature amount data, and the feature amount table 26 includes the feature amount ID and the voice feature amount data that can be acquired based on the voice.
  • the voice feature amount data is stored in association with the feature amount ID.
  • the voice feature data is feature data extracted or acquired from voice data by a known voice feature extraction method, for example, a known voice feature extraction program.
  • the voice feature data stored in the feature table 26 is voice feature data acquired from the voice of a non-existent person or an unspecified real person, and is acquired by using the above-mentioned voice collection extraction program. ..
  • the feature amount table 26 does not store the voice feature amount data corresponding to the voice data of the user who uses the ticket.
  • the determination device 2 and the client terminal 3 include a voice input device such as a microphone.
  • the client terminal 3 receives the voice input from the user and transmits it to the information processing server 1 via the ticket management web page that displays the screen for requesting the user to input the voice.
  • the server control unit 21 determines the voice feature data from the received voice data by using the voice feature extraction program stored in the server storage unit 22.
  • the determination device control unit 41 operates the photographing device 34 to photograph the ticket, and acquires the ticket ID, the feature amount ID, and the check data from the code attached to the ticket. Further, in step 201, the determination device control unit 41 operates the voice input device and acquires the voice data of the user who uses the ticket.
  • the determination device control unit 41 determines the voice feature amount data from the acquired user voice data by using the same voice feature amount extraction program as the voice feature amount extraction program stored in the server storage unit 22. do. The same applies to the modifications of the other embodiments.
  • the face feature amount data stored in the feature amount table 26 is a plurality of face feature amount data calculated by a predetermined calculation program.
  • the face feature amount data stored in the feature amount table 26 is not the face feature amount data acquired from the face image of a non-existent person or an unspecified real person.
  • the voiceprint data stored in the feature amount table 26 is a plurality of voiceprint data calculated by a predetermined calculation program.
  • the determination device 2 further includes a code reading device (not shown) for reading the code attached to the ticket.
  • the determination device 2 includes a main body unit having the main functions of the determination device 2 and a code reading device communicably connected to the main body unit.
  • the determination device control unit 41 operates the photographing device 34 to acquire the user's face image, and also operates the code reading device to operate the code reading device to obtain the ticket ID and the feature from the code attached to the ticket. Acquire the quantity ID or facial feature quantity data and the check data.
  • the information processing server 1 includes the function of the ticket sales server 4 and provides the client terminal 3 with a service for purchasing a ticket via the ticket sales site.
  • the processes of the information processing server 1 and the ticket sales server 4 described in the first to fourth embodiments are the processes in the information processing server 1.
  • the place where the determination device 2 is installed is not the venue of the event but a store or the like.
  • the server control unit 21 acquires the ticket ID assigned to the ticket in advance, instead of determining the ticket ID for the ticket for which the purchase application has been accepted.
  • the ticket sales server 4 determines the ticket ID.
  • the order information transmitted by the ticket sales server 4 to the information processing server 1 in step 103 includes the ticket ID determined by the ticket sales server 4.
  • the server control unit 21 acquires the ticket ID from the received order information.
  • the server control unit 21 performs a predetermined calculation based on the ticket ID acquired in step 104, the feature amount ID determined in step 108, and the event ID determined in step 104, thereby performing check data. Is calculated.
  • the server control unit 21 generates a code attached to the ticket based on the ticket ID acquired in step 104, the feature amount ID determined in step 108, and the calculated check data.
  • the server control unit 21 generates a code attached to the ticket based on the ticket ID acquired in step 104, the feature amount ID determined in step 108, and the calculated check data.
  • the ticket sales server 4 transmits the ticket information or the order information to the information processing server 1 for each received order information. do.
  • the ticket ID is assigned to the ticket specified by the received ticket information or the order information.
  • the server control unit 21 transmits the address (URL) of the ticket management web page associated with the assigned ticket ID to the ticket sales server 4.
  • the ticket sales server 4 transmits the address (URL) of the ticket management web page associated with the ticket ID to the user's e-mail address.
  • the server control unit 21 and the ticket sales server 4 execute the above processing instead of steps 104 to 105 in the first embodiment and the second embodiment. Since the server control unit 21 does not transmit the information to the user's e-mail address, the information processing server 1 does not have to receive the user information in step 103.
  • the ticket sales server 4 further includes a member database.
  • the member database is the same as that described in the third embodiment, and the member information includes an e-mail address.
  • the e-mail address can be a telephone number, an SNS, an ID of a chat tool, or the like.
  • the user information included in the order information is information such as an e-mail address included in the member information.
  • the ticket sales server 4 further includes a member database.
  • the membership database is similar to that described in the third embodiment.
  • the server control unit 21 has a function of creating a ticket management web page linked with the ticket sales site.
  • the server control unit 21 does not have to send the address of the ticket management web page associated with the ticket ID to the user's email address including the received order information.
  • the logged-in ticket sales site indicates to the user who purchased the ticket that a face image must be entered in order to make the ticket available, and a link for accessing the ticket management web page.
  • the server control unit 21 can display the ticket management web page by accessing from the ticket sales site via the link, and can accept the input of the face image from the user via the client terminal 3.
  • the server control unit 21 displays a ticket management web page linked to the member ID in response to an access from the logged-in ticket sales site, and a face image from the user who has received the input once. Can be linked to the page.
  • the client terminal 3 communicates with the ticket sales server 4 and the information processing server 1, and is similar to the ticket sales site and the ticket management web page.
  • a dedicated application that can provide the services of (hereinafter referred to as "dedicated application") is installed.
  • the client terminal 3 is a smartphone.
  • the dedicated application is associated with at least one of the member ID stored in the ticket sales server 4 and the user ID stored in the information processing server 1.
  • the client terminal 3 accepts the input of the ticket purchase application via the dedicated application.
  • the client terminal 3 transmits the ticket information including the ticket information and the user information regarding the ticket for which the purchase application has been accepted to the ticket sales server 4 via the dedicated application.
  • the user information here may include an ID associated with the dedicated application.
  • the server control unit 21 requests the client terminal 3 to input the face image to the client terminal 3 via the dedicated application. Display the screen.
  • the server control unit 21 accepts the input of the face image from the user via the dedicated application.
  • the information processing server 1 transmits the ticket data generated in step 408 to the client terminal 3 via the dedicated application, and the client terminal 3 acquires the ticket data.
  • the server control unit 21 can accept a change of a user who uses a ticket via a dedicated application after generating ticket data in step 408.
  • the dedicated application may include a face feature amount extraction program and may be configured so that face feature amount data can be determined from the face image.
  • the server control unit 21 inputs the face image to the user to the client terminal 3 via the dedicated application. Display the desired screen.
  • the dedicated application receives the input of the face image
  • the dedicated application determines the face feature amount data from the face image and transmits the determined face feature amount data to the information processing server 1.
  • the server control unit 21 does not have to execute the process of step 406. The same applies to the modified example of the fourth embodiment.
  • the ticket management web page is configured to be directly accessible by entering a user ID and password without going through a ticket sales site. NS.
  • the user information included in the order information is an ID or code that can identify the client terminal 3, such as an IP address or a MAC address.
  • the server storage unit 22 does not include the ticket book table 25 and the ticket book ID.
  • the ticket table 27 includes a ticket ID, an event ID, ticket detailed information, and a feature amount ID as data items, and the ticket ID and the event ID are associated with each other via the ticket table 27.
  • the server control unit 21 does not determine the ticket book ID. The server control unit 21 determines an event ID corresponding to the event information included in the received ticket information, associates it with the ticket ID, and stores it in the ticket table 27. The same applies to the above in other embodiments.
  • the server storage unit 22 does not have to store the event table 24 and stores predetermined data not limited to the event ID.
  • the predetermined data can be data for identifying an event, or can be data for identifying a system administrator.
  • predetermined data is stored in the ticket table 27 in association with the ticket ID.
  • the predetermined data is numerical data.
  • the same predetermined data as the predetermined data stored in the server storage unit 22 is stored in the determination device 2.
  • the same predetermined data as the predetermined data stored in the server storage unit 22 in association with the ticket ID of the ticket is stored in the determination device 2 for determining the validity of the use of the ticket. ..
  • the same event ID is stored in the information processing server 1 and the determination device 2, but the information processing server 1 and the determination device 2 are the same as in this modification.
  • the embodiment of the present invention may be realized by storing predetermined data.
  • the predetermined operation of the server control unit 21 in step 109 includes at least one of the ticket ID determined in step 104 and the feature amount ID determined in step 108, and the step. It is performed based on the event ID determined in 104.
  • the predetermined calculation in step 204 is performed based on at least one of the ticket ID and the feature amount ID acquired in step 201 and the event ID stored in the determination device storage unit 42. ..
  • it is desirable that the predetermined calculation is performed by using the ticket ID, the feature amount ID, and the event ID. Even when either one is not used, the embodiment of the present invention may be feasible. The same applies to the third embodiment.
  • the server control unit 21 receives at least one of the ticket ID determined in step 304 and the facial feature amount data determined in step 308.
  • Check data is calculated by performing a predetermined calculation based on the event ID determined in step 304.
  • the predetermined calculation in step 204 is performed based on at least one of the ticket ID and the face feature amount data acquired in step 201 and the event ID stored in the determination device storage unit 42. Will be. The same applies to the fourth embodiment.
  • the server control unit 21 determines a plurality of face feature amount data instead of determining one face feature amount data among the face feature amount data stored in the feature amount table 26. To determine. For example, in step 108, the server control unit 21 determines a plurality of face feature amount data having a predetermined similarity among the face feature amount data stored in the feature amount table 26. In this case, the feature amount ID used by the server control unit 21 in step 109 is also a plurality of feature amount IDs. The same applies to the above in other embodiments.
  • the face feature amount data stored in the feature amount table 26 is processed feature amount data generated based on the face feature amount data.
  • the processed feature amount data is for the face feature amount data which is the feature amount data extracted or acquired by using the face feature amount extraction program stored in the server storage unit 22 for the face image.
  • Data obtained by performing a predetermined encryption process is obtained by performing a predetermined decoding process on the processed feature amount data.
  • the server storage unit 22 and the determination device storage unit 42 store an encryption program that performs a predetermined encryption process and a decryption program that performs a predetermined decryption process.
  • the predetermined encryption process can be a processing process other than the encryption process.
  • the predetermined decoding process can be a process of restoring the processed data.
  • step 108 the server control unit 21 compares the face feature amount data determined in step 107 with the face feature amount data that is the basis of the processed feature amount data stored in the feature amount table 26, and compares the feature amount table.
  • the processed feature amount data generated based on the face feature amount data having a predetermined similarity among the face feature amount data which is the basis of the processed feature amount data stored in 26 is determined.
  • the server control unit 21 decodes the processed feature amount data and acquires the face feature amount data when performing the comparison process.
  • the server control unit 21 determines the face feature amount data, and determines the processed feature amount data obtained by encrypting the determined face feature amount data.
  • the determined processed feature amount data is stored in the feature amount table 26.
  • the feature amount table 26 does not store the face feature amount data as it is, so that the risk related to the biometric information of the user who uses the ticket can be further reduced.
  • the determination device control unit 41 decodes the processed feature amount data associated with the feature amount ID in the feature amount table 46, and the feature amount ID acquired in step 201 and the face feature determined in step 202. It is determined whether or not the quantity data meets a predetermined criterion. The same applies to the third embodiment.
  • step 308 the server control unit 21 compares the face feature amount data determined in step 307 with the face feature amount data that is the basis of the processed feature amount data stored in the feature amount table 26, and compares the feature amount table.
  • the processed feature amount data generated based on the face feature amount data having a predetermined similarity among the face feature amount data which is the basis of the processed feature amount data stored in 26 is determined.
  • step 309 the server control unit 21 checks by performing a predetermined calculation based on the ticket ID determined in step 304, the processed feature amount data determined in step 308, and the event ID determined in step 304. Calculate the data for.
  • the server control unit 21 generates a code attached to the ticket based on the ticket ID determined in step 304, the processed feature amount data determined in step 308, and the calculated check data.
  • the determination device control unit 41 determines whether or not the face feature amount data that is the basis of the processed feature amount data acquired in step 201 and the face feature amount data determined in step 202 have a predetermined degree of similarity. Is determined.
  • the facial feature amount data is stored in a data structure or data format different from that shown in FIG.
  • the face feature amount data is data showing numerical information of a vector of another dimension other than the 128-dimensional vector.
  • the face feature amount data is data showing numerical information of a 256-dimensional vector.
  • the facial feature amount data is not limited to these as long as it is data acquired by using a known facial feature amount extraction program. Further, in the calculation of the similarity performed by the server control unit 21, a value corresponding to the Euclidean distance of the two facial feature amount data can be used, or another known method can be used.
  • the determination device storage unit 42 further includes a used ticket table for determining whether or not the presented ticket is unused.
  • the used ticket table includes a ticket ID and status information indicating either unused or used as a data table, and the ticket ID is the primary key.
  • the determination device control unit 41 determines, for example, whether or not the ticket ID acquired from the code acquired in step 201 has been used before step 203.
  • the status information associated with the ticket ID in the ticket used table is updated to used, and the process proceeds to step 203.
  • This flowchart proceeds to step 206 when the ticket ID has been used.
  • the process of determining whether or not the ticket ID has been used may be executed at any time between steps 202 and 205.
  • the server control unit 21 is configured to generate a code by writing data to an RF tag.
  • a modified example of the first embodiment will be described below with respect to this modified example.
  • the server control unit 21 writes data corresponding to each of the ticket ID, the feature amount ID, and the check data in the RF tag.
  • a user who uses a ticket can acquire an RF tag in which data is written by mail or the like.
  • the RF tag can also be another non-contact IC card. The same applies to the modifications of the other embodiments.
  • the processing or operation can be freely performed in a certain step as long as there is no contradiction in the processing or operation such as using data that should not be available in that step. Can be changed. Further, each of the examples described above is an example for explaining the present invention, and the present invention is not limited to these examples. The present invention can be carried out in various forms as long as it does not deviate from the gist thereof.
  • Information processing server 2 Judgment device 3 Client terminal 4 Ticket sales server 5, 6 Network 10 Information processing system 11, 31, 51, 52 Processor 12, 32, 52, 62 Input device 13, 33, 53, 63 Display device 14, 35, 54, 64 Storage devices 15, 36, 55, 65 Communication devices 16, 37, 56, 66 Bus 21 Server control unit 22 Server storage unit 24 Event table 25 Ticket book table 26, 46 Feature table 27 Ticket table 28 User Table 34 Imaging device 41 Judgment device control unit 42 Judgment device storage unit 71 Event information 72 QR code (registered trademark)

Landscapes

  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Computer Security & Cryptography (AREA)
  • Health & Medical Sciences (AREA)
  • Oral & Maxillofacial Surgery (AREA)
  • Accounting & Taxation (AREA)
  • Human Computer Interaction (AREA)
  • General Health & Medical Sciences (AREA)
  • Multimedia (AREA)
  • Computer Hardware Design (AREA)
  • General Engineering & Computer Science (AREA)
  • Finance (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Software Systems (AREA)
  • Computer Vision & Pattern Recognition (AREA)
  • Development Economics (AREA)
  • Computing Systems (AREA)
  • Economics (AREA)
  • Tourism & Hospitality (AREA)
  • Marketing (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Biomedical Technology (AREA)
  • Quality & Reliability (AREA)
  • Operations Research (AREA)
  • Human Resources & Organizations (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Collating Specific Patterns (AREA)
PCT/JP2021/015002 2020-04-09 2021-04-09 情報処理サーバ、情報処理システム、判定装置、及び方法 Ceased WO2021206162A1 (ja)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP21783705.3A EP4134854A4 (en) 2020-04-09 2021-04-09 INFORMATION PROCESSING SERVER, INFORMATION PROCESSING SYSTEM, DETERMINATION APPARATUS AND METHOD
US17/961,144 US12230086B2 (en) 2020-04-09 2022-10-06 Information processing server, information processing system, determination device, and method
US19/013,095 US20250148851A1 (en) 2020-04-09 2025-01-08 Information processing server, information processing system, determination device, and method

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2020070365A JP7129443B2 (ja) 2020-04-09 2020-04-09 情報処理サーバ、情報処理システム、判定装置、及び方法
JP2020-070365 2020-04-09

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/961,144 Continuation US12230086B2 (en) 2020-04-09 2022-10-06 Information processing server, information processing system, determination device, and method

Publications (1)

Publication Number Publication Date
WO2021206162A1 true WO2021206162A1 (ja) 2021-10-14

Family

ID=78024025

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2021/015002 Ceased WO2021206162A1 (ja) 2020-04-09 2021-04-09 情報処理サーバ、情報処理システム、判定装置、及び方法

Country Status (4)

Country Link
US (2) US12230086B2 (enExample)
EP (1) EP4134854A4 (enExample)
JP (4) JP7129443B2 (enExample)
WO (1) WO2021206162A1 (enExample)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2017117301A (ja) * 2015-12-25 2017-06-29 サイレックス・テクノロジー株式会社 チケット発行システム
JP6163239B1 (ja) 2016-07-27 2017-07-12 株式会社テイパーズ 認証システム

Family Cites Families (60)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1998050875A2 (en) * 1997-05-09 1998-11-12 Gte Government Systems Corporation Biometric certificates
US6202151B1 (en) * 1997-05-09 2001-03-13 Gte Service Corporation System and method for authenticating electronic transactions using biometric certificates
TW338865B (en) * 1997-06-03 1998-08-21 Philips Eloctronics N V Authentication system
US6513118B1 (en) * 1998-01-27 2003-01-28 Canon Kabushiki Kaisha Electronic watermarking method, electronic information distribution system, image filing apparatus and storage medium therefor
US7035428B1 (en) * 1999-04-23 2006-04-25 The Escher Group, Ltd. Workpiece authentication based upon one or more workpiece images
US7188080B1 (en) * 2000-05-12 2007-03-06 Walker Digital, Llc Systems and methods wherin a buyer purchases products in a plurality of product categories
US7114080B2 (en) * 2000-12-14 2006-09-26 Matsushita Electric Industrial Co., Ltd. Architecture for secure remote access and transmission using a generalized password scheme with biometric features
US20060046842A1 (en) * 2001-08-10 2006-03-02 Igt Ticket redemption using encrypted biometric data
AU2003234699A1 (en) * 2002-04-09 2003-10-27 The Escher Group, Ltd. System and method for authentication of a workpiece using three dimensional shape recovery
US10489449B2 (en) * 2002-05-23 2019-11-26 Gula Consulting Limited Liability Company Computer accepting voice input and/or generating audible output
JP2004078686A (ja) 2002-08-20 2004-03-11 Toshiba Corp 個人認証装置、個人認証方法、通行制御装置および通行制御方法
JP4340860B2 (ja) 2003-09-03 2009-10-07 日本電気株式会社 顔照合システム
JP2006113763A (ja) * 2004-10-14 2006-04-27 Dainippon Printing Co Ltd 入場管理システム
US8700910B2 (en) * 2005-05-31 2014-04-15 Semiconductor Energy Laboratory Co., Ltd. Communication system and authentication card
EP1972091A1 (en) * 2005-08-03 2008-09-24 Intercomputer Corporation System and method for user identification and authentication
JP4736744B2 (ja) * 2005-11-24 2011-07-27 株式会社日立製作所 処理装置、補助情報生成装置、端末装置、認証装置及び生体認証システム
JP4762805B2 (ja) * 2006-06-29 2011-08-31 富士通株式会社 生体認証方法及び生体認証システム
JP4914691B2 (ja) * 2006-10-31 2012-04-11 富士フイルム株式会社 ネットワークコミュニケーション装置、システム、方法およびプログラム
US9298902B2 (en) * 2009-02-12 2016-03-29 International Business Machines Corporation System, method and program product for recording creation of a cancelable biometric reference template in a biometric event journal record
EP2407908A4 (en) * 2009-03-13 2014-03-19 Fujitsu Ltd PERSONAL AUTHENTICATION SYSTEM AND PERSONAL AUTHENTICATION PROCEDURE
EP2418603B1 (en) * 2009-04-09 2018-10-17 Fujitsu Limited Fingerprint authentication server device, fingerprint authentication client device, and fingerprint authentication method
US8121993B2 (en) * 2009-10-28 2012-02-21 Oracle America, Inc. Data sharing and recovery within a network of untrusted storage devices using data object fingerprinting
CN102054182A (zh) * 2009-11-06 2011-05-11 山东新北洋信息技术股份有限公司 一种制票方法及制票装置
DE102009055947A1 (de) * 2009-11-30 2011-06-01 Christoph Busch Authentisierte Übertragung von Daten
EP2348449A3 (en) * 2009-12-18 2013-07-10 CompuGroup Medical AG A computer implemented method for performing cloud computing on data being stored pseudonymously in a database
US10579995B2 (en) * 2010-03-30 2020-03-03 Visa International Service Association Event access with data field encryption for validation and access control
US20130238903A1 (en) * 2010-07-09 2013-09-12 Takeshi Mizunuma Service provision method
US12020178B2 (en) * 2011-03-04 2024-06-25 Digital Consolidation, Inc. Method and apparatus for information representation, exchange, validation, and utilization through digital consolidation
US8870084B2 (en) * 2011-09-13 2014-10-28 Sca Promotions Method and system for the generation and validation of personal identification numbers
BR102012030476A2 (pt) * 2011-12-09 2015-10-06 Visa Int Service Ass método, meio de armazenamento legível em computador, e, sistema
TWI566564B (zh) * 2012-04-25 2017-01-11 Samton International Development Technology Co Ltd Virtual reality authentication circuit, system and electronic consumption method
US20220384027A1 (en) * 2012-10-09 2022-12-01 Kc Holdings I Tracking and rewarding health and fitness activities using blockchain technology
US9158909B2 (en) * 2014-03-04 2015-10-13 Amazon Technologies, Inc. Authentication of virtual machine images using digital certificates
US9519278B2 (en) * 2014-06-09 2016-12-13 Richard J. Petrocy Modularized self-addressing apparatus and method
AU2015311866B2 (en) * 2014-09-03 2018-06-07 Nant Holdings Ip, Llc Synthetic genomic variant-based secure transaction devices, systems and methods
US9361742B2 (en) * 2014-10-28 2016-06-07 Joze Pececnik Highly secure combination lock system
US10275587B2 (en) * 2015-05-14 2019-04-30 Alclear, Llc Biometric ticketing
US11531737B1 (en) * 2015-07-30 2022-12-20 The Government of the United States of America, as represented by the Secretary of Homeland Security Biometric identity disambiguation
US10523441B2 (en) * 2015-12-15 2019-12-31 Visa International Service Association Authentication of access request of a device and protecting confidential information
US10587609B2 (en) * 2016-03-04 2020-03-10 ShoCard, Inc. Method and system for authenticated login using static or dynamic codes
US11212105B2 (en) * 2017-03-23 2021-12-28 Moovel North America, Llc Systems and methods of providing and validating digital tickets
US11212100B2 (en) * 2017-03-23 2021-12-28 Moovel North America, Llc Systems and methods of providing and electronically validating tickets and tokens
GB2546459B (en) * 2017-05-10 2018-02-28 Tomlinson Martin Data verification
CN107491965B (zh) * 2017-07-31 2020-07-10 阿里巴巴集团控股有限公司 一种生物特征库的建立方法和装置
JP6518351B1 (ja) * 2018-01-23 2019-05-22 株式会社ロココ チケッティング管理システム及びプログラム
PH12018502218A1 (en) * 2018-01-23 2019-07-15 Rococo Co Ltd Ticketing management system and program
JP6746103B2 (ja) * 2018-03-23 2020-08-26 カシオ計算機株式会社 認証方法、認証システム、携帯情報機器及びプログラム
US20190340350A1 (en) * 2018-05-02 2019-11-07 Kolumbo Holdings Limited Verification system
US20200184430A1 (en) * 2018-08-01 2020-06-11 Mallservice Inc. Electronic ticket management system, electronic ticket management method and electronic ticket management program
TWI739086B (zh) * 2019-04-10 2021-09-11 歐生全科技股份有限公司 可攜式認證裝置與裝置內自行登錄認證資料的方法
EP3979215A4 (en) * 2019-05-30 2023-06-07 Playground Co., Ltd. TICKET ISSUING SYSTEM, TICKET VERIFICATION DEVICE AND PROGRAM
US11824851B2 (en) * 2019-09-11 2023-11-21 Jumio Corporation Identification document database
AU2019466472A1 (en) * 2019-09-19 2022-05-12 Yellowheart Llc Systems and methods for commerce in a distributed system with blockchain protocols and smart contracts
KR20220081980A (ko) * 2019-10-17 2022-06-16 소니그룹주식회사 정보 처리 시스템, 정보 처리 방법, 프로그램, 유저 인터페이스
US11854348B2 (en) * 2019-11-21 2023-12-26 Igt System and method for lottery and skill games
US11321554B2 (en) * 2020-01-30 2022-05-03 Universal City Studios Llc Efficient management of facial recognition systems and methods in multiple areas
MX2022009621A (es) * 2020-02-07 2022-11-07 Veridas Digital Authentication Solutions S L Firmas electronicas.
US12237937B2 (en) * 2020-02-27 2025-02-25 Nec Corporation Server device, conference assistance system, and conference assistance method
US12488073B2 (en) * 2020-02-28 2025-12-02 Nec Corporation Locker system, locker management system, and locker management method
US20230344815A1 (en) * 2022-04-26 2023-10-26 Citrix Systems, Inc. End-point instance indexing and owner pop selection in gateway service ticketing

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2017117301A (ja) * 2015-12-25 2017-06-29 サイレックス・テクノロジー株式会社 チケット発行システム
JP6163239B1 (ja) 2016-07-27 2017-07-12 株式会社テイパーズ 認証システム

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4134854A4

Also Published As

Publication number Publication date
US20230030754A1 (en) 2023-02-02
JP7129443B2 (ja) 2022-09-01
US12230086B2 (en) 2025-02-18
EP4134854A4 (en) 2023-09-20
JP2022169673A (ja) 2022-11-09
EP4134854A1 (en) 2023-02-15
JP7359917B2 (ja) 2023-10-11
JP2023175880A (ja) 2023-12-12
JP2021168010A (ja) 2021-10-21
JP2024164186A (ja) 2024-11-26
JP7546130B2 (ja) 2024-09-05
US20250148851A1 (en) 2025-05-08

Similar Documents

Publication Publication Date Title
CN110741369B (zh) 使用电子身份进行安全生物统计认证
US8582829B2 (en) Online identity verification
JP7090008B2 (ja) 本人確認支援装置および本人確認支援方法
US20120032782A1 (en) System for restricted biometric access for a secure global online and electronic environment
JP2021519488A (ja) ブロックチェーン内でコード及びイメージを用いるためのシステム及び方法
US12254720B2 (en) Ticket issuing system, and ticket checking apparatus
JP2012003648A (ja) 生体認証システムにおける、生体情報の登録方法、テンプレートの利用申請の方法、および、認証方法
JP7171504B2 (ja) 個人情報管理サーバ、個人情報管理方法及び個人情報管理システム
JP2017117301A (ja) チケット発行システム
US12079322B2 (en) Authentication system and authentication method
JP2023109134A (ja) 本人確認情報の管理方法
JP6828311B2 (ja) 情報処理システム、情報処理装置及びプログラム
JP7359917B2 (ja) 情報処理サーバ、情報処理システム、判定装置、及び方法
KR20240160589A (ko) 신원 확인 및 관련 플랫폼
EP4117328A1 (en) Authentication system, authentication method, and program
JP2004295507A (ja) 携帯機器を用いた身分証明方法，システム及びプログラム
JP2018151764A (ja) 情報処理装置、情報処理方法及びプログラム
JP2002324050A (ja) 個人認証用データ提供システム及び方法
KR20170118382A (ko) 실명확인증표를 전자적으로 관리하는 장치 및 방법
JP5072322B2 (ja) 本人証明システム及び本人証明方法
JP7589863B2 (ja) サーバ装置、システム、サーバ装置の制御方法及びプログラム
TWI906543B (zh) 去中心化零信任身份核實認證系統與方法
JP7740609B1 (ja) サーバ装置、端末、サーバ装置の制御方法及びプログラム
KR20100005951A (ko) 쿠키를 이용한 맞춤형 광고 제공 방법 및 시스템과 이를위한 기록매체
JP2022025977A (ja) 認証システム、及び認証方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21783705

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2021783705

Country of ref document: EP

Effective date: 20221109