Information processing server, information processing system, determination apparatus, and method
Patent Information
- Application Number
- JP2024144154
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-08-26
- Publication Date
- 2024-12-06
- Estimated Expiration
- 2040-04-09
AI Technical Summary
Conventional facial recognition methods for ticket validation risk exposing personal biometric information and are vulnerable to unauthorized resale due to the inclusion of user facial data on tickets.
An information processing system that uses feature data derived from biometric information, stored on a server, to generate a code attached to tickets, ensuring that only authorized users with similar facial features can validate ticket usage, while keeping personal biometric information secure.
Prevents unauthorized ticket use and reduces the risk of biometric information leakage by using feature data instead of direct facial images, maintaining security and accuracy in ticket validation.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to an information processing server, an information processing system, a determination device, a method, and the like. [Background technology]
[0002] Conventionally, there is a method for preventing illegal resale by using biometric information of a user who uses a ticket. For example, Patent Document 1 discloses a method for recording information indicating the ticket holder's own face or facial features as information on the legitimate holder, photographing the face of a person who is about to enter at the entrance, and verifying whether the person is a legitimate holder or not by face recognition that compares the photograph with the holder's own face or facial features recorded on the ticket. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] Patent No. 6163239 Summary of the Invention [Problem to be solved by the invention]
[0004] In conventional methods for verifying the user of a ticket using face recognition, including the method disclosed in Patent Document 1, a facial image and facial features are recorded on the ticket as the facial information of the legitimate holder (user). Since the facial image and facial features are personal information of the user, recording them on the ticket has been problematic from the standpoint of personal information protection and security, since there is a possibility that the personal information may be unintentionally passed on to a third party. On the other hand, there is a problem in that tickets that do not contain personal information may be easily resold.
[0005] The present invention has been made to solve such problems, and its main objective is to provide an information processing server etc. that can prevent fraudulent use of tickets while reducing the risk of leakage of biometric information of users using tickets. [Means for solving the problem]
[0006] The information processing server according to one embodiment of the present invention includes: An information processing server for managing tickets, a server storage unit that stores pre-created feature data that can be obtained from biometric information, feature identification information that can identify feature data associated with the feature data, and predetermined data that is the same as predetermined data stored in a determination device for determining the validity of ticket use; A server control unit; The server control unit determining ticket identification information capable of identifying the ticket for which the application for issuance has been accepted, or acquiring ticket identification information previously assigned to the ticket; determining feature data from biometric information of a user who uses the entered ticket; comparing the determined feature data with feature data stored in the server storage unit to determine feature data having a predetermined similarity and to determine feature identification information associated with the feature data; and The system is configured to calculate check data by performing a predetermined calculation based on at least one of the determined or acquired ticket identification information and the determined feature identification information and the specified data, generate a code to be affixed to the ticket based on the calculated check data, the determined or acquired ticket identification information, and the determined feature identification information, and generate ticket data for outputting a ticket affixed with the generated code.
[0007] The information processing server according to one embodiment of the present invention includes: An information processing server for managing tickets, a server storage unit that stores feature amount data that can be obtained from biometric information and that has been created in advance, and predetermined data that is the same as predetermined data stored in a determination device for determining the validity of the use of a ticket; A server control unit; The server control unit determining ticket identification information capable of identifying the ticket for which the application for issuance has been accepted, or acquiring ticket identification information previously assigned to the ticket; determining feature data from biometric information of a user who uses the entered ticket; comparing the determined feature data with feature data stored in the server storage unit to determine feature data having a predetermined similarity; and The system is configured to calculate check data by performing a predetermined calculation based on at least one of the determined or acquired ticket identification information and the determined feature data, and the specified data, generate a code to be affixed to the ticket based on the calculated check data, the determined or acquired ticket identification information, and the determined feature data, and generate ticket data for outputting a ticket affixed with the generated code.
[0008] In addition, as one embodiment of the present invention, The server control unit compares the determined feature amount data with feature amount data stored in the server storage unit, and determines a plurality of feature amount data having a predetermined degree of similarity.
[0009] In addition, as one embodiment of the present invention, The feature data stored in the server storage unit is feature data obtained from biometric information of a non-existent person or an unspecified existing person, and is previously created feature data.
[0010] In addition, as one embodiment of the present invention, The feature amount data stored in the server storage unit is face feature amount data indicating feature amounts corresponding to points, lines, or surfaces of facial features that can be obtained based on a face image.
[0011] In addition, as one embodiment of the present invention, the feature amount data stored in the server storage unit is processed feature amount data generated based on the feature amount data, Instead of comparing the determined feature data with the feature data stored in the server memory unit, the server control unit compares the determined feature data with the feature data that is the basis of the processed feature data stored in the server memory unit, and determines processed feature data generated based on feature data having a predetermined degree of similarity.
[0012] In addition, as one embodiment of the present invention, The server control unit is configured to transmit ticket data for outputting a ticket with the generated code attached to a client terminal capable of communicating with the information processing server via a network.
[0013] An information processing system according to an embodiment of the present invention includes: An information processing system including the information processing server and the determination device, The determination device includes: a determination device storage unit that stores the predetermined data, as well as feature data identical to the feature data and feature identification information stored in the server storage unit and feature identification information associated with the feature data; A determination device control unit, The determination device control unit Acquire ticket identification information, feature identification information, and check data from the code attached to the ticket, Acquire biometric information of the user who presents the ticket; determining whether or not the feature amount data determined from the acquired biometric information and the acquired feature amount identification information satisfy a predetermined criterion based on the feature amount data and the feature amount identification information stored in the determination device storage unit in an associated manner; and The present invention is characterized in that it is configured to determine whether or not the check data calculated by performing the specified calculation based on at least one of the acquired ticket identification information and the acquired feature identification information and the specified data matches the acquired check data.
[0014] In addition, as one embodiment of the present invention, The predetermined criteria are: 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 have a predetermined similarity; and comparing feature data determined from the acquired biometric information with feature data stored in the determination device storage unit to determine feature data having a predetermined similarity and to determine feature identification information associated with the feature data, the determined feature identification information including the acquired feature identification information; At least one of the following.
[0015] An information processing system according to an embodiment of the present invention includes: An information processing system including the information processing server and the determination device, The determination device includes: a determination device storage unit that stores the predetermined data and feature amount data identical to the feature amount data stored in the server storage unit; A determination device control unit, The determination device control unit Acquire ticket identification information, feature data, and check data from the code attached to the ticket, Acquire biometric information of the user who presents the ticket; determining whether feature data determined from the acquired biometric information has a predetermined similarity with the acquired feature data; and The device is configured to determine whether or not the check data calculated by performing the specified calculation based on at least one of the acquired ticket identification information and the acquired feature data and the specified data matches the acquired check data.
[0016] The determination device according to an embodiment of the present invention comprises: A determination device for determining the validity of a ticket use, comprising: a determination device storage unit that stores predetermined data identical to predetermined data stored in an information processing server capable of generating ticket data for outputting a ticket, feature data obtainable from biometric information stored in the information processing server, the feature data being created in advance and the feature data identical to feature identification information capable of identifying the feature data associated with the feature data, and the feature identification information associated with the feature data; A determination device control unit, The ticket is provided with at least one of ticket identification information that is assigned to the ticket and that can identify the ticket and feature identification information that is determined based on biometric information of a user who uses the ticket, and check data calculated by performing a predetermined calculation based on the predetermined data, and a code that is generated based on the ticket identification information and the feature identification information, The determination device control unit Acquire ticket identification information, feature identification information, and check data from the code attached to the ticket, Acquire biometric information of the user who presents the ticket; determining whether or not the feature amount data determined from the acquired biometric information and the acquired feature amount identification information satisfy a predetermined criterion based on the feature amount data and the feature amount identification information stored in the determination device storage unit in an associated manner; and The present invention is characterized in that it is configured to determine whether or not the check data calculated by performing the specified calculation based on at least one of the acquired ticket identification information and the acquired feature identification information and the specified data matches the acquired check data.
[0017] The determination device according to an embodiment of the present invention comprises: A determination device for determining the validity of a ticket use, comprising: a determination device storage unit that stores predetermined data identical to predetermined data stored in an information processing server capable of generating ticket data for outputting a ticket, and feature amount data that can be obtained from biometric information stored in the information processing server and is identical to previously created feature amount data; A determination device control unit, The ticket is provided with at least one of ticket identification information that can identify the ticket and that is assigned to the ticket, and feature data that is determined based on biometric information of a user who uses the ticket, and check data that is calculated by performing a predetermined calculation based on the predetermined data, and a code that is generated based on the ticket identification information and the feature data, The determination device control unit Acquire ticket identification information, feature data, and check data from the code attached to the ticket, Acquire biometric information of the user who presents the ticket; determining whether 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 device is configured to determine whether or not the check data calculated by performing the specified calculation based on at least one of the acquired ticket identification information and the acquired feature data and the specified data matches the acquired check data.
[0018] The method of one embodiment of the present invention comprises: 1. A computer-implemented method for managing tickets, comprising: The method uses a database that stores pre-created feature amount data indicating feature amounts obtainable from biometric information, feature amount identification information capable of identifying feature amount data associated with the feature amount data, and predetermined data identical to predetermined data stored in a determination device for determining the validity of ticket use, determining ticket identification information capable of identifying a ticket for which an application for issuance has been accepted, or acquiring ticket identification information previously assigned to the ticket; determining feature data from biometric information of a user who uses the input ticket; a step of comparing the determined feature data with feature data stored in the database to determine feature data having a predetermined similarity and determining feature identification information associated with the feature data; a step of calculating check data 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, generating a code to be affixed to the ticket based on the calculated check data, the determined or acquired ticket identification information, and the determined feature amount identification information, and generating ticket data for outputting a ticket affixed with the generated code; The present invention is characterized by comprising:
[0019] The method of one embodiment of the present invention comprises: 1. A computer-implemented method for managing tickets, comprising: The method uses a database that stores pre-created feature amount data indicating feature amounts obtainable from biometric information and predetermined data identical to predetermined data stored in a determination device for determining the validity of ticket use, determining ticket identification information capable of identifying a ticket for which an application for issuance has been accepted, or acquiring ticket identification information previously assigned to the ticket; determining feature data from biometric information of a user who uses the input ticket; comparing the determined feature data with feature data stored in the database to determine feature data having a predetermined similarity; a step of calculating check data by performing a predetermined calculation based on at least one of the determined or acquired ticket identification information and the determined feature data, and the predetermined data, generating a code to be affixed to the ticket based on the calculated check data, the determined or acquired ticket identification information, and the determined feature data, and generating ticket data for outputting a ticket affixed with the generated code; The present invention is characterized by comprising:
[0020] The method of one embodiment of the present invention comprises: 1. A computer implemented method for determining validity of a ticket redemption, comprising: the method uses a database that stores predetermined data identical to predetermined data stored in an information processing server capable of generating ticket data for outputting a ticket, feature data obtainable from biometric information stored in the information processing server, the feature data being generated in advance, and feature identification information identical to feature data associated with the feature data and capable of identifying the feature data, and feature identification information associated with the feature data; The ticket is provided with at least one of ticket identification information capable of identifying the ticket assigned to the ticket and feature identification information determined based on biometric information of a user who uses the ticket, and check data calculated by performing a predetermined calculation based on the predetermined data, and a code generated based on the determined ticket identification information and the determined feature identification information, acquiring ticket identification information, feature identification information, and check data from a code attached to the ticket; acquiring biometric information of a user presenting the ticket; determining whether or not the feature amount data determined from the acquired biometric information and the acquired feature amount identification information satisfy a predetermined criterion based on the feature amount data and the feature amount identification information stored in the database in an associated manner; a step of determining whether or not 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 matches the acquired check data; The present invention is characterized by comprising:
[0021] The method of one embodiment of the present invention comprises: 1. A computer implemented method for determining validity of a ticket redemption, comprising: the method uses a database that stores predetermined data identical to predetermined data stored in an information processing server capable of generating ticket data for outputting a ticket, and feature amount data that can be obtained from biometric information stored in the information processing server and is identical to previously created feature amount data; The ticket is provided with at least one of ticket identification information that is assigned to the ticket and that can identify the ticket and feature data that is determined based on biometric information of a user who uses the ticket, and check data calculated by performing a predetermined calculation based on the predetermined data, and a code that is generated based on the determined ticket identification information and the determined feature data, acquiring ticket identification information, feature data, and check data from a code attached to the ticket; acquiring biometric information of a user presenting the ticket; determining whether the feature amount data stored in the database and the feature amount data determined from the acquired biometric information satisfy a predetermined criterion; a step of determining whether or not 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; The present invention is characterized by comprising:
[0022] A program according to one embodiment of the present invention is characterized in that it causes a computer to execute each step of the method described above. Effect of the Invention
[0023] According to the present invention, it is possible to prevent unauthorized use of a ticket while reducing the risk of leakage of biometric information of a user who uses the ticket. [Brief description of the drawings]
[0024] [Figure 1] 1 is an overall configuration diagram of an information processing system according to a first embodiment of the present invention. [Diagram 2] 2 is a block diagram showing a hardware configuration of an information processing server according to the first embodiment of the present invention; FIG. [Diagram 3] 2 is a block diagram showing a hardware configuration of a client terminal according to the first embodiment of the present invention. FIG. [Figure 4] 2 is a block diagram showing a hardware configuration of a ticket sales server according to the first embodiment of the present invention. FIG. [Diagram 5] FIG. 2 is an example of a functional block diagram of an information processing server according to the first embodiment of the present invention. [Figure 6] 4 is an example of a feature amount table according to the embodiment of the present invention. [Figure 7] 5 is a flowchart showing an operation of the information processing server according to the first exemplary embodiment of the present invention. [Figure 8] FIG. 11 is a diagram showing an example of a paper ticket output based on ticket data. [Figure 9] 1 is a block diagram showing a hardware configuration of a determination device according to a first embodiment of the present invention. [Figure 10] 1 is an example of a functional block diagram of a determination device according to a first embodiment of the present invention. [Figure 11] 4 is a flowchart showing the operation of the determination device according to the first embodiment of the present invention. [Figure 12] 10 is a flowchart showing an operation of the information processing server according to the second exemplary embodiment of the present invention. [Figure 13] 13 is a flowchart showing an operation of the information processing server according to the third exemplary embodiment of the present invention. [Figure 14] 13 is a flowchart showing an operation of the information processing server according to the fourth exemplary embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0025] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. The 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 in each drawing indicate the same or equivalent parts unless otherwise specified, and unnecessary detailed explanations may be omitted. The data structures and database structures in the databases described in the embodiments of the present invention are merely examples, and the present invention is not limited to these.
[0026] In an embodiment of the present invention, a ticket is an admission ticket required to enter a specific event such as a concert or a sporting event. The ticket includes an electronic ticket and a paper ticket. The ticket described in the embodiment of the present invention may include a coupon or a ticket other than the admission ticket described above without departing from the gist of the invention, and may be any medium having financial value.
[0027] [First embodiment] [Information Processing System] FIG. 1 is an overall configuration diagram of an information processing system 10 according to a first embodiment of the present invention. As shown in FIG. 1, 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 an event venue and determines the legitimacy of ticket use. Determining the legitimacy of ticket use includes determining whether or not a combination of a presented ticket and a user who uses the ticket is legitimate, that is, whether or not a user who uses the ticket is a legitimate holder of the ticket. Determining the legitimacy of ticket use also includes determining the legitimacy of the ticket itself (for example, whether the ticket is not a counterfeit ticket). For example, the determination device 2 is embodied as a device for inspecting and verifying tickets at the time of entry, or is embodied as a part of the device.
[0028] The information processing server 1 and the determination device 2 are connected to a 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 a network 6 and can communicate with each other. FIG. 1 shows that the determination device 2 is configured not to communicate with or cannot communicate with the client terminal 3 and the ticket sales server 4, and is connected to the information processing server 1 via a network 5 different from these. However, 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. For example, the networks 5 and 6 are the Internet. In addition, the determination device 2 may be installed at the event venue and be able to communicate with the information processing server 1 before determining the legitimacy of the ticket use, and when determining the legitimacy of the ticket use, the determination device 2 may not be connected to the information processing server 1 via the network 5. In the embodiment of the present invention, the client terminal 3 and the ticket sales server 4 may be known devices, and therefore the information processing system 10 may not include the client terminal 3 and the ticket sales server 4.
[0029] [Information processing server] 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 a configuration similar to that of 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. These components are connected by a bus 16. Note that an interface is interposed between the bus 16 and each component device as necessary. The information processing server 1 may be composed of multiple computers.
[0030] The processor 11 controls the operation of the information processing server 1 and is, for example, a CPU. Note that an electronic circuit such as an MPU may be used as the processor 11. The processor 11 reads and executes programs and data stored in the storage device 14 to perform various processes.
[0031] The input device 12 is a user interface that accepts input from a 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 application screens and the like to the user of the information processing server 1 under the control of the processor 11.
[0032] The storage device 14 includes a main storage device and an auxiliary storage device. The main storage device is, for example, a semiconductor memory such as a RAM. The RAM is a volatile storage medium that allows high-speed reading and writing of information, and is used as a storage area and a working 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 capable of storing information, and may be removable.
[0033] The communication device 15 is a wireless LAN module capable of transmitting and receiving data to and from other computers such as user terminals or servers via a network. The communication device 15 may be another wireless communication device such as a Bluetooth (registered trademark) module, or may be a wired communication device such as an Ethernet (registered trademark) module or a USB interface.
[0034] FIG. 3 is a block diagram showing a hardware configuration of the client terminal 3 according to the first embodiment of the present invention. For example, 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 a 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. These components are connected by a bus 56. Note that an interface is interposed between the bus 56 and each component device as necessary. The elements of the processor 51, the input device 52, the display device 53, the storage device 54, and the communication device 55 correspond to the above-mentioned processor 11, the input device 12, the display device 13, the storage device 14, and the communication device 15, respectively, and have the same configuration, so that the description will be omitted. In one example, a web browser is installed in the client terminal 3. A user can use the web browser to view web pages and send data to a web server using an input form on a web page.
[0035] 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. These components are connected by a bus 66. Note that an interface is provided between the bus 66 and each component device as necessary. The processor 61, the input device 62, the display device 63, the storage device 64, and the communication device 65 correspond to the above-mentioned processor 11, the input device 12, the display device 13, the storage device 14, and the communication device 15, respectively, and have the same configuration, so that the description thereof will be omitted. The ticket sales server 4 may be configured by a plurality of computers.
[0036] 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. In this embodiment, these functions are realized by a program being executed by the processor 11 or by the storage device 14. For example, the program to be executed is a program stored in the storage device 14 or received via the communication device 15. A function realized by loading a program may be such that one part (function) is partially or entirely possessed by another part. However, these functions may also be realized by hardware by configuring electronic circuits or the like for realizing part or entirely of each function.
[0037] The server control unit 21 manages information related to tickets and generates data necessary for ticket issuance. The information processing server 1 can function as a web server, and the server control unit 21 can have a function for performing processes such as generating and transmitting web pages. The information processing server 1 can also function as an application server, and the server control unit 21 can have a function for controlling connections to databases, processing transactions, and the like.
[0038] The server storage unit 22 has a function of storing programs, data, and the like. This function of the server storage unit 22 is realized by the storage device 14. The server storage unit 22 can store data for providing web pages, such as HTML documents, images, and programs for application server functions. In this embodiment, the server storage unit 22 has a database function. The database function is realized by the storage device 14 storing data (e.g., tables) and programs for various databases and executing the programs.
[0039] The server storage unit 22 stores an event table 24 , a ticket book table 25 , a feature amount table 26 , and a ticket table 27 .
[0040] The event table 24 includes, as data items, an event ID, and event information including information such as the name, date, and location of the event. The data items correspond to columns. The event table 24 can also include, as data items, an exhibitor ID for associating with an exhibitor table that stores information about exhibitors. The primary key of the event table 24 is the event ID, which is an example of event identification information that can identify an event. The ticket book table 25 includes, as data items, a ticket book ID and an event ID. 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 facial image. The primary key of the feature amount table 26 is the feature amount ID, which is an example of feature amount identification information that can identify the facial feature amount data. The ticket table 27 includes, as data items, a ticket ID, a ticket book ID, ticket detail information including information such as the seat and price of the ticket, and a feature amount ID. The primary key of the ticket table 27 is the ticket ID, which is one example of ticket identification information that can identify a ticket. In this embodiment, the ticket ID, feature ID, and 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 a promoter table that includes, as data items, a promoter ID and promoter information that includes information such as contract details.
[0041] Since tickets are issued for each event, the ticket ID of a ticket issued for one event is associated with the event ID of that one event. In this embodiment, the ticket ID and the ticket book ID are associated with each other in the ticket table 27, and the ticket book ID and the event ID are associated with each other in the ticket book table 25, so that the ticket ID is associated with the event ID.
[0042] The facial feature amount data is feature amount data indicating feature amounts corresponding to points, lines, or planes of facial features extracted or acquired from a facial image by a known feature amount extraction method. For example, the facial feature amount data is acquired by executing a program of a known software library on a facial image, and is expressed as a multidimensional vector. FIG. 6 is an example of the feature amount table 26. In one example, as shown in FIG. 6, the facial feature amount data is data indicating numerical information of a 128-dimensional vector (128-dimensional array structure) acquired using a known facial feature amount extraction program, and is data in which the numerical values of each dimension of the 128-dimensional vector are arranged as they are. The facial feature amount extraction program is stored in the server storage unit 22 (storage device 14). The facial feature amount extraction program may be a trained model. The facial image may be two-dimensional data or three-dimensional data including a three-dimensional shape.
[0043] The facial feature data stored in the feature table 26 is facial feature data acquired from facial images of non-existent persons or unspecified existing persons, and is created in advance using the above-mentioned facial feature extraction program. The feature table 26 stores a plurality of (e.g., 5,000) pieces of facial feature data acquired from facial images of a plurality of (e.g., 5,000) non-existent persons or unspecified existing persons that are prepared in advance. In this way, the feature table 26 stores each of the facial feature data corresponding to each of the facial images of non-existent persons or unspecified existing persons, but does not store facial feature data corresponding to the facial image of a user who uses a ticket.
[0044] However, the above-mentioned data structure stored in the server storage unit 22 is just one example. In one preferred example, the server storage unit 22 stores a ticket ID, facial feature amount data created in advance, a feature amount ID associated with the facial feature amount data, and an event ID that is the same as the event ID stored in the determination device 2.
[0045] In this embodiment, the server control unit 21 has a function of creating a ticket management web page (ticket management website) for each ticket ID. In one example, the ticket management web page includes a screen for registering a face image and a screen for displaying ticket data for outputting the ticket. The ticket data can also be said to be data for displaying the face of the ticket.
[0046] The ticket sales server 4 is a known server device or server system operated by a ticket seller. The ticket sales server 4 functions as a web server, and performs processes such as generating and transmitting web pages such as a ticket sales site (ticket sales page) in response to requests from the client terminals 3. The ticket sales server 4 can also function as an application server, and can control connections to databases related to ticket sales processing, perform transaction processing, and the like. The storage device 64 can store data for providing web pages, such as HTML documents, images, and programs for application server functions.
[0047] The ticket sales server 4 includes a ticket sales database that stores ticket information on tickets managed by the ticket seller and ticket inventory information indicating whether each ticket has been purchased. The ticket information stored in the ticket sales database includes information necessary for selling tickets, such as event information including the date and venue of the event, detailed ticket information including the type of seat or specific seat number and price information.
[0048] A user operates the client terminal 3 to select a ticket, apply for purchase of the selected ticket, and process payment via the ticket sales site. The ticket sales server 4 receives order information including the ticket information and user information for which a purchase application has been accepted from the client terminal 3. The ticket information included in the order information includes, for example, event information including the date and venue of the event, detailed ticket information including the type of seat or specific seat number and price information, and includes information necessary to identify the ticket. In this embodiment, the user information included in the order information is the email address of the user whose input has been accepted by the client terminal 3 via the ticket sales site. The email address may be a phone number, an ID for an SNS or a chat tool, or the like. Order information is created for each order accepted from the client terminal 3 and transmitted to the ticket sales server 4.
[0049] FIG. 7 is a flowchart showing the operation of the information processing server 1 according to the first embodiment of the present invention.
[0050] In step 101, the client terminal 3 accepts an input of a ticket purchase application via a ticket sales site. The client terminal 3 transmits order information including ticket information related to the ticket for which the purchase application has been accepted and user information to the ticket sales server 4 via the ticket sales site. The ticket information related to the ticket for which the purchase application has been accepted is ticket information related to one or multiple tickets.
[0051] In step 102, the ticket sales server 4 receives the order information from the client terminal 3, thereby accepting the ticket purchase application from the client terminal 3 and updating the ticket sales database.
[0052] In step 103, the ticket sales server 4 transmits each piece of accepted order information to the information processing server 1. In this way, the ticket sales server 4 transmits the order information to the information processing server 1, whereby the ticket sales server 4 and the information processing server 1 can synchronize data between the servers. This synchronization between the servers may be performed periodically. The information processing server 1 receives the order information from the ticket sales server 4 and accepts applications for purchasing tickets.
[0053] In step 104, the server control unit 21 determines a ticket ID for the ticket for which a purchase application has been accepted. Specifically, the server control unit 21 determines a ticket book ID and a ticket ID to be associated with the ticket identified by the received order information. In one example, determining a ticket ID for a ticket for which a purchase application has been accepted means creating a new ticket ID in response to the ticket purchase application and assigning it to the ticket for which the application has been accepted. In one example, determining a ticket ID for a ticket for which a purchase application has been accepted means assigning a 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.
[0054] The server control unit 21 determines an event ID corresponding to the event information included in the received ticket information, and stores the event ID in the ticket book table 25 in association with the ticket book ID. 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 ticket detail information of the received ticket information in the ticket table 27 in association with the ticket ID.
[0055] Before a ticket for a target event is issued, an event ID for the event is created, and the created event ID and 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 that determines the validity of the use of a ticket to which a ticket ID associated with the event ID is assigned. The information processing server 1 may share the event ID with the ticket sales server 4, and in this case, the ticket information that the information processing server 1 receives from the ticket sales server 4 includes the event ID. Note that the order information received by the information processing server 1 does not have to be the same as the order information received by the ticket sales server 4 from the client terminal 3, as long as it includes ticket information and user information.
[0056] In step 105, the server control unit 21 transmits the address (URL) of the ticket management web page linked to the ticket ID to the user's email address included in the user information contained in the received order information. The server control unit 21 transmits one ticket management web page address for one ticket ID.
[0057] In step 106, the client terminal 3 accesses the URL received from the information processing server 1 and displays a web page for managing the ticket. The web page for managing the ticket displays a screen for requesting the user to input a face image. The client terminal 3 accepts the input of the face image from the user via the web page for managing the ticket and transmits it to the information processing server 1.
[0058] In step 107, facial feature amount data is determined from a facial image of a user who uses the input ticket. In one example, the server control unit 21 determines the facial feature amount data from the received facial image using a facial feature amount extraction program stored in the server storage unit 22. For example, the determination of the facial feature amount data by the server control unit 21 means calculating the facial feature amount data from the received facial image or acquiring the facial feature amount data from the received facial image.
[0059] In step 108, the server control unit 21 compares the facial feature amount data determined in step 107 with the facial feature amount data stored in the feature amount table 26, and determines facial feature amount data having a predetermined similarity among the facial feature amount data stored in the feature amount table 26. In one example, in step 108, the server control unit 21 compares each of the facial feature amount data stored in the feature amount table 26 with the facial feature amount data determined in step 107, and calculates the similarity of each. Alternatively, in one example, the server control unit 21 compares each of the predetermined facial feature amount data among the facial feature amount data stored in the feature amount table 26 with the facial feature amount data determined in step 107, and calculates the similarity of each. The server control unit 21 determines a feature amount ID associated with the determined facial feature amount data. In one example, the server control unit 21 stores the determined feature amount ID in association with the ticket ID in the ticket table 27. In this embodiment, for convenience of explanation, it is assumed that the server control unit 21 determines one of the facial feature amount data stored in the feature amount table 26. In order to reduce the amount of calculation in information processing, the facial feature amount data determined by the server control unit 21 in step 107 and the facial feature amount data stored in the feature amount table 26 can have the same data structure. This also applies to other embodiments.
[0060] In this embodiment, the facial feature amount data is data indicating numerical information of a 128-dimensional vector, and the similarity corresponds to the Euclidean distance between two facial feature amount data to be compared. The server control unit 21 judges 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 determines facial feature amount data, between which the Euclidean distance between the facial feature amount data determined in step 107 and the facial feature amount data stored in the feature amount table 26 is equal to or less than a predetermined value, from the facial feature amount data stored in the feature amount table 26. In one example, the server control unit 21 determines any facial feature amount data whose Euclidean distance is equal to or less than a predetermined value. Alternatively, in one example, the server control unit 21 determines facial feature amount data whose Euclidean distance is the smallest.
[0061] In step 109, the server control unit 21 calculates check data by performing a predetermined calculation based on the ticket ID determined in step 104, the feature ID determined in step 108, and the event ID determined in step 104. The server control unit 21 generates a code to be attached to the ticket based on the ticket ID determined in step 104, the feature 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.
[0062] In this embodiment, the predetermined calculation is realized by a check data calculation program, and the server control unit 21 calculates the check data using the check data calculation program. In one example, 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 calculates the last one or two digits as the check data. In one example, 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 calculates the output value as the check data. For example, the predetermined function is a one-way function. In this way, the check data is calculated by performing a predetermined calculation using multiple values, so it is difficult to obtain the original value from the check data. In one example, the check data is one- or multiple-digit numeric data. In one example, the check data is a check digit. The check data calculation program is stored in the server storage unit 22.
[0063] The code generated by the server control unit 21 is a QR code (registered trademark) that stores data corresponding to the ticket ID, feature amount ID, and check data. For example, each piece of data is stored in a predetermined position in the data area of the QR code (registered trademark). However, 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).
[0064] In one example, the information processing server 1 transmits the ticket data generated in step 109 to the client terminal 3 via a ticket management web page, and the client terminal 3 receives the ticket data. In one example, the information processing server 1 transmits, to the user's email address, the address of a web page from which the generated ticket data can be downloaded.
[0065] The client terminal 3 outputs a ticket to which the code generated in step 109 is attached based on the received ticket data. In one example, the client terminal 3 displays the ticket to which the code generated in step 109 is attached based on the received ticket data as an electronic ticket on the display device 53. In one example, the client terminal 3 outputs a paper ticket to which the code generated in step 109 is attached based on the received ticket data from a printer communicably connected to the client terminal 3. If the ticket data is image data, the client terminal 3 displays the image as is, and if the ticket data is processed data or encrypted data, the client terminal 3 outputs the ticket using a corresponding application. Note that the client terminal 3 that accepts the purchase application, the client terminal 3 that accepts the input of a face image, and the client terminal 3 that receives the ticket data can be the same terminal or can be configured to be different terminals depending on the usage mode.
[0066] In one example, after generating the ticket data in step 109, the server control unit 21 can accept a change in the user who will use the ticket via a ticket management web page. In order for a user to become a legitimate owner of the transferred ticket, the user must operate the client terminal 3 to access a ticket management web page linked to the ID of the ticket and input a facial image of the user. The server control unit 21 can accept input of a facial image of the user who will use the ticket via, for example, a ticket management web page linked to the ticket ID of the transferred ticket. When the server control unit 21 accepts new input of a facial image of the user, it executes the processes of steps 107 to 109 and generates new ticket data.
[0067] Fig. 8 is a diagram showing an example of a paper ticket output based on ticket data. As shown in Fig. 10, event information 71 such as the name, date, and location of the event, and a 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, just like the paper ticket.
[0068] In this embodiment, when a facial image of a user who uses a ticket is input and the information processing server 1 can acquire the facial image, the information processing server 1 can be configured so that this flowchart does not include steps 105 and 106. In this embodiment, it is sufficient for the information processing server 1 to receive order information related to a ticket for which a purchase application has been accepted, and this flowchart can be configured so that it does not include steps 101 to 103.
[0069] [Judgment device] 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. These components are connected by a bus 37. Note that an interface is interposed between the bus 37 and each component device as necessary. In this embodiment, the determination device 2 is a tablet terminal such as an iPad (registered trademark). However, the determination device 2 is not limited to a tablet terminal. For example, the determination device 2 may include a main body having the main functions of the determination device 2 and a photographing device 34 connected to the main body so as to be able to communicate with the main body.
[0070] The processor 31 controls the operation of the information processing server 1, and is, for example, a CPU. Note that an electronic circuit such as an MPU may be used as the processor 31. The processor 31 reads and executes programs and data stored in the storage device 35 to perform various processes.
[0071] The input device 32 is a user interface that accepts input from a user to the information processing server 1. The display device 33 displays application screens and the like to a user of the information processing server 1 under the control of the processor 31. In this embodiment, the determination device 2 includes a touch panel 38 as the input device 32, which also functions as the display device 33, and the input device 32 and the display device 33 are integrated into one structure.
[0072] The photographing device (imaging device) 34 photographs (takes) still images or videos in real space, and stores the photographed image or video data in the storage device 35. The photographing device 34 is, for example, a camera constituted by an image sensor and the like.
[0073] The storage device 35 includes a main storage device and an auxiliary storage device. The main storage device is, for example, a semiconductor memory such as a RAM. The RAM is a volatile storage medium that allows high-speed reading and writing of information, and is used as a storage area and a working 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 capable of storing information, and may be removable.
[0074] The communication device 36 is a wireless LAN module capable of transmitting and receiving data to and from other computers, such as user terminals or servers, via a network. The communication device 36 may be another wireless communication device, such as a Bluetooth (registered trademark) module, or a wired communication device, such as an Ethernet (registered trademark) module or a USB interface. Note that the determination device 2 does not need to include the communication device 36, as long as it is configured to receive data from the information processing server 1 when determining the validity of ticket usage.
[0075] 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. In this embodiment, these functions are realized by the processor 31 executing a program or by the storage device 35. For example, the program to be executed is a program stored in the storage device 35 or received via the communication device 15. A function realized by loading a program may be such that one part (function) is partially or entirely possessed by another part. However, these functions may also be realized by hardware by configuring electronic circuits or the like for realizing part or entirely of each function.
[0076] In this embodiment, the determination device storage unit 42 has a database function. The database function is realized by the storage device 35 storing data (for example, tables) and programs for various databases and executing the programs.
[0077] The determination device control unit 41 determines the validity of ticket usage, for example, whether or not the combination of the presented ticket and the user using the ticket is valid. The determination device storage unit 42 has a function of storing programs, data, and the like. This function of the determination device storage unit 42 is realized by the storage device 35. The determination device storage unit 42 stores a feature table 46 that is the same feature table as the feature table 26 stored in the server storage unit 22. The feature table 46 is stored before the determination device 2 is installed at the event venue and determines the validity of the ticket usage.
[0078] 11 is a flowchart showing the operation of the determination device 2 of the first embodiment of the present invention. The determination device 2 is installed at the entrance of an event venue so that the photographing device 34 can photograph the ticket and the face of the user when the user enters the event venue. The determination device storage unit 42 (storage device 35) stores the event ID of the event for which the determination device 2 is installed.
[0079] In step 201, the determination device control unit 41 operates the photographing device 34 to photograph the ticket and the user presenting the ticket, acquires an image of the user's face, and acquires the ticket ID, feature ID, and check data from the code attached to the ticket. In one example, when photographing the user's face and the code attached to the ticket, the determination device control unit 41 displays the captured image on the display device 33, and displays a display that guides the user to move the face of the user who will use the ticket and the ticket to a predetermined area. In one example, the function of the determination device control unit 41 is realized by installing a program in the determination device 2 that photographs the code and acquires the data contained in the code.
[0080] In step 202, the determination device control unit 41 determines facial feature amount data from the acquired face image of the user by using a facial feature amount extraction program that is the same as the facial 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.
[0081] In step 203, the judgment device control unit 41 judges whether or not the feature ID acquired in step 201 and the facial feature data determined in step 202 satisfy a predetermined criterion, based on the feature ID and facial feature data associated and stored in the feature table 46.
[0082] In one example, determining whether or not a predetermined criterion is satisfied means determining whether or not the facial feature amount data determined in step 202 and the facial feature amount data associated in the feature amount table 46 with the feature amount ID acquired in step 201 have a predetermined similarity. In this case, satisfying the predetermined criterion means having the predetermined similarity. In one example, determining whether or not a predetermined criterion is satisfied means comparing the facial feature amount data determined in step 202 with the facial feature amount data stored in the feature amount table 46 to determine facial feature amount data having a predetermined similarity among the facial feature amount data stored in the feature amount table 46, determining (obtaining) a feature amount ID associated with the facial feature amount data, and determining whether or not the determined feature amount ID includes the feature amount ID acquired in step 201. In this case, satisfying the predetermined criterion means including the feature amount ID. In one example, determining whether or not a predetermined criterion is satisfied means determining whether or not both of the determinations in the above two examples are satisfied. In this case, satisfying the predetermined criterion means having the predetermined similarity and including the feature amount ID. The predetermined similarity in step 203 is preferably the same as the predetermined similarity in the process of step 108 of server control unit 21 .
[0083] If it is determined in step 203 that the predetermined criterion is met, the process of this flowchart proceeds to step 204, and if it is determined in step 203 that the predetermined criterion is not met, the process of this flowchart proceeds to step 206.
[0084] In step 204, the determination device control unit 41 calculates check data by performing a predetermined calculation based on the ticket ID and feature ID acquired in step 201 and the event ID stored in the determination device storage unit 42. The determination device control unit 41 determines whether the calculated check data matches the check data acquired in step 201. The predetermined calculation is the same process as the calculation performed by the server control unit 21 when calculating the check data in step 109. In this embodiment, the determination device storage unit 42 stores a check data calculation program that is the same 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 above is similar to other embodiments.
[0085] If it is determined in step 204 that they match, the process of this flowchart proceeds to step 205, and if it is determined in step 204 that they do not match, the process of this flowchart proceeds to step 206. In step 205, the determination device control unit 41 determines that the combination of the presented ticket and the user using the ticket is a correct combination and is a valid use. In step 206, the determination device control unit 41 determines that the combination of the presented ticket and the user using the ticket is an incorrect combination and is an illegal use. In one example, 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 determines that the user is a valid user. 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 determines that the user is an illegal user. If it determines that the user is an illegal user, the determination device control unit 41 may be configured to output an alarm.
[0086] In this flowchart, the order of steps 203 and 204 may be reversed.
[0087] Next, the effects of the information processing server 1, the determination device 2, and the information processing system 10 according to the first embodiment of the present invention will be described.
[0088] In this embodiment, the information processing server 1 stores a feature table 26 including a feature ID and facial feature data associated with the feature ID. The information processing server 1 determines facial feature data from a face image of a user who uses a ticket, and stores a feature ID associated with the facial feature data having a predetermined similarity to the facial feature data. The information processing server 1 stores an event ID that is the same as the event ID stored in the determination device 2. The information processing server 1 calculates check data for a ticket for which a purchase application has been accepted by performing a predetermined calculation based on the determined or acquired ticket ID, the determined feature ID, and the stored event ID. The information processing server 1 generates a code based on the calculated check data, the determined ticket ID, and the determined feature ID, and generates ticket data for outputting a ticket with the generated code attached. With this configuration, in this embodiment, the information processing server 1 can create ticket data for generating a ticket whose validity of use is determined by the determination device 2 in the information processing system 10.
[0089] Before determining the validity of the use of the ticket, the determination device 2 stores the feature table 46 and the event ID of the target event, and also stores the same facial feature extraction program and check data calculation program as those stored in the information processing server 1. The determination device 2 acquires the ticket ID, feature ID, and check data from the code attached to the ticket, and acquires a face image of the user. The determination device 2 determines facial feature data from the acquired face image using the facial feature extraction program. The determination device 2 determines whether the determined facial feature and the feature ID acquired from the code satisfy a predetermined standard using the feature table 46. The determination device 2 calculates check data using the check data calculation program based on the acquired ticket ID and feature ID, and the event ID stored in advance, and determines whether the check data matches the acquired check data. With this configuration, in this 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.
[0090] As described above, the information processing server 1 does not store the biometric information (facial image) of the user using the ticket, but stores information (feature ID) related to biometric information similar to the biometric information of the user. The ticket stores (holds) the feature ID via a code, but does not store the biometric information of the user using the ticket. The determination device 2 stores neither the biometric information nor the feature ID of the user using the ticket. By configuring the ticket, the information processing server 1, and the determination device 2 in this way so that they do not hold the biometric information of the user, in this embodiment, it is possible to reduce risks related to the biometric information (personal information) of the user using the ticket, for example the risk of leakage of biometric information.
[0091] On the other hand, by configuring the determination device 2 to determine whether a predetermined criterion is satisfied, it becomes possible to determine with a certain degree of accuracy whether a user presenting a ticket is a legitimate user of the ticket. The feature amount ID acquired from the code attached to the ticket is not directly linked to the face image of the user who uses the ticket, but is linked via the feature amount table 26 to face feature amount data having a certain degree of similarity with the face image previously received from the user. Therefore, it can be said that the feature amount ID linked to the ticket is linked to a face image similar to the face image of the user. By configuring the determination device 2 to perform such a determination, in this embodiment, it becomes possible to detect fraudulent use of tickets based on biometric information with a certain degree of accuracy, and to prevent resale.
[0092] For example, if feature table 26 stores 10,000 sets of facial feature data, one of the 10,000 sets of facial feature data is assigned to the facial image of a user using a ticket. The accuracy of determining whether a user presenting a ticket is a legitimate user of the ticket corresponds to the amount of facial feature data stored in feature table 26. For example, the greater the amount of facial feature data stored in feature table 26, the higher the accuracy of the determination.
[0093] Furthermore, in this embodiment, 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 determine 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 this configuration, in this embodiment, it is possible to prevent ticket forgery.
[0094] In this embodiment, the determination device 2 can be made completely offline. Conventionally, the determination device determines the combination of the ticket and the user while communicating with other devices, and judges whether or not the person entering the venue of the event is a legitimate holder of the ticket. However, the venue of the event where the determination device is installed may have a poor communication environment, and the determination device may not operate normally. In this embodiment, the determination device 2 stores the feature table 46, the event ID of the target event, the facial feature extraction program, and the check data calculation program, but does not store the feature ID determined based on the biometric information (facial image) of the user. Therefore, even if the user who uses the ticket transfers the ticket immediately beforehand, the information processing server 1 only needs to update the biometric information (facial image) of the user who uses the ticket and generate new ticket data, and no processing is required in the determination device 2. With this configuration, even if the communication environment of the place where the determination device 2 is installed is poor, for example, even in an offline environment, it is possible to realize the determination by the determination device 2.
[0095] In this embodiment, a user who uses the ticket can display the ticket on the screen of his / her own terminal (client terminal 3) and use it as an electronic ticket, or can print out the paper ticket and use it. By configuring in this way, this embodiment allows a wide range of users to use the ticket because the paper ticket can be used even if the user does not have a terminal such as a smartphone or if a malfunction occurs in the terminal.
[0096] In this embodiment, the code attached to the ticket includes a feature ID, which is identification information, instead of facial feature data, which has a relatively large amount of information. This configuration can reduce the amount of information that the determination device 2 acquires from the code, making it possible to process the code more smoothly.
[0097] The above-described effects and advantages are applicable to other embodiments and examples, unless otherwise specified.
[0098] [Second embodiment] [Information processing server] Next, an information processing server 1 and a determination device 2 according to a second embodiment of the present invention will be described. Below, differences from the first embodiment will be mainly described.
[0099] In the second embodiment, a feature ID is not used. Instead of a feature ID, a ticket table 27 stores facial feature data in association with a ticket ID. The feature tables 26 and 46 store facial feature data similar to those in the first embodiment, but do not need to have a feature ID. In the absence of a feature ID, the facial feature data does not need to be stored in the form of the feature tables 26 and 46.
[0100] FIG. 12 is a flowchart showing the operation of the information processing server 1 according to the second embodiment of the present invention.
[0101] Steps 301 to 307 are similar to steps 101 to 107 in the first embodiment. In step 308, the server control unit 21 compares the facial feature amount data determined in step 307 with the facial feature amount data stored in the feature amount table 26, and determines facial feature amount data having a predetermined similarity among the facial feature amount data stored in the feature amount table 26. The determination of the facial feature amount data in step 308 is similar to the determination of the facial feature amount data in step 108 in 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.
[0102] In step 309, the server control unit 21 calculates check data by performing a predetermined calculation based on the ticket ID determined in step 304, the facial feature amount data determined in step 308, and the event ID determined in step 304. The server control unit 21 generates a code to be attached to the ticket based on the ticket ID determined in step 304, the facial 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.
[0103] The predetermined calculation in the second embodiment is the same as the predetermined calculation in the first embodiment, except that facial feature amount data is used instead of the feature amount ID described in the first embodiment. However, since the facial feature amount data has a larger amount of information than the feature amount ID, a predetermined part of the facial feature amount data may be used instead of the facial feature amount data.
[0104] [Judgment device] Next, a determination device 2 according to a second embodiment of the present invention will be described. Differences from the first embodiment will be mainly described below. The operation of the determination device 2 according to the second embodiment is similar to the flowchart shown in FIG. 11, but the following processing is different from that of the first embodiment.
[0105] In step 201, the determination device control unit 41 operates the photographing device 34 to photograph the ticket and the user presenting the ticket, obtains an image of the user's face, and also obtains the ticket ID, facial feature data, and check data from the code attached to the ticket.
[0106] In step 203, the determination device control unit 41 determines whether or not the facial feature amount data acquired in step 201 and the facial feature amount data determined in step 202 have a predetermined similarity. The predetermined similarity is preferably the same as the predetermined similarity in the process of step 308 of the server control unit 21.
[0107] In step 204, the determination device control unit 41 calculates checking data by performing a predetermined calculation based on the ticket ID and facial feature amount data acquired in step 201 and the event ID stored in the determination device storage unit 42. The determination device control unit 41 determines whether the calculated checking data matches the checking data acquired in step 201. The predetermined calculation is the same process as the calculation performed by the server control unit 21 when calculating the checking data.
[0108] In the second embodiment, the code attached to the ticket contains facial feature data with a larger amount of information than the code in the first embodiment, so it is difficult to perform smoother processing. However, in other respects, the same effects as those of the first embodiment can be obtained.
[0109] [Third embodiment] [Information processing server] Next, an information processing server 1 according to a third embodiment of the present invention will be described. Differences from the first embodiment will be mainly described below. The determination device 2 according to the third embodiment is the same as the determination device 2 according to the first embodiment. First, a first example of the third embodiment will be described.
[0110] The server storage unit 22 further stores a user table 28 (not shown). The user table 28 includes, as data items, a user ID and linked user identification information, which is user identification information in another system. The primary key of the user table 28 is the user ID, which is one example of user identification information capable of identifying a user. As will be described in the modified example, in the embodiment of the present invention, the server storage unit 22 may or may not store the ticket book table 25. For convenience of description, in the third embodiment, it is assumed that the server storage unit 22 does not store the ticket book table 25. In this case, the event ID is stored in the ticket table 27 in association with the ticket ID.
[0111] The ticket sales server 4 further includes a member database. The member database is a database that stores member information of members of the ticket sales site. The member information includes contact information such as a member ID, a password, a name, and an email 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 in the member information are used to authenticate the member. A user can register as a member, log in, log out, and the like on the ticket sales site by operating the client terminal 3. When accepting a member registration from a user, the ticket sales server 4 accepts input of member information, generates member information for the user, and stores it in the member database. When a user purchases a ticket, the user needs to register as a member and then log in. In a first example, the linked user identification information is a member ID. The ticket sales server 4 accepts input of a face image from a user who has registered as a member, and stores the face image in the member database in association with the member ID.
[0112] The server control unit 21 has a function of creating a ticket management web page linked to the ticket sales site. The ticket management web page is linked to the ticket sales site in association with a user ID or linked user identification information (member ID), and displays a 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 for each logged-in user. In one example, the ticket sales site in a logged-in state generates a link for accessing the ticket management web page, and the server control unit 21 displays the ticket management web page in a logged-in state with the user ID by accessing from the ticket sales site via the link. The ticket sales site in a logged-in state may display to the user who has purchased a ticket that a face image needs to be input 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 the ticket management web page.
[0113] 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.
[0114] Steps 401 to 403, 406 to 408 are similar to steps 101 to 103, 107 to 109 in the first embodiment, respectively. However, in step 403, the user information included in the order information sent from the ticket sales server 4 to the information processing server 1 includes a member ID.
[0115] In step 404, server control unit 21 determines a ticket ID for the ticket for which a purchase application has been accepted. Server control unit 21 determines an event ID corresponding to the event information included in the received ticket information, and stores the event ID in ticket table 27 in association with the ticket ID. Server control unit 21 determines a user ID to associate with the ticket ID, and stores the member ID from the received user information in user table 28 in association with the user ID. If a member ID has already been stored in user table 28, the user ID determined by server control unit 21 is the user ID associated with that member ID in user table 28.
[0116] In step 405, the server control unit 21 acquires a face image associated with the member ID from the ticket sales server 4. After determining the feature ID in step 407, the server control unit 21 associates the feature ID with the user ID and stores it in the user table 28. In addition to or instead of storing it in the user table 28, the server control unit 21 may store the feature ID in the ticket table 27 in association with the ticket ID.
[0117] In step 405, if the ticket sales server 4 does not store a facial image or cannot acquire a facial image, the server control unit 21 displays a screen on the ticket management web page requesting the user to input a facial image. The server control unit 21 accepts the input of a facial image from the user via the ticket management web page.
[0118] With the configuration of this embodiment, the server control unit 21 can display a ticket management web page linked to the user ID or member ID, and link the facial feature amount data determined from the face image of the user whose input has been accepted once to the user ID. This makes it possible to promote use by a wide range of users, since the next time a ticket is purchased from the same ticket sales site, there is no need to input a new face image. This is also true in the second example.
[0119] Next, a second example of the third embodiment will be described. The differences from the first example will be mainly described below. In 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 a social network service (SNS) account. When purchasing a ticket, the user needs to log in using the SNS account. The linked user identification information in the second example is an SNS account ID such as an email address.
[0120] In step 403, the user information included in the order information sent by the ticket sales server 4 to the information processing server 1 includes the SNS account ID. In step 404, it is the SNS account ID that the server control unit 21 associates with the user ID and stores in the user table 28. In step 405, 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 webpage.
[0121] [Fourth embodiment] [Information processing server] Next, an information processing server 1 according to a fourth embodiment of the present invention will be described. The following mainly describes the differences from the third embodiment. The determination device 2 according to the fourth embodiment is the same as the determination device 2 according to the second embodiment.
[0122] In the fourth embodiment, a feature ID is not used. Instead of a feature ID, a ticket table 27 stores facial feature data in association with a ticket ID. The feature tables 26 and 46 store facial feature data similar to those in the first embodiment, but do not need to have a feature ID. In the absence of a feature ID, the facial feature data does not need to be stored in the form of the feature tables 26 and 46.
[0123] 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.
[0124] Steps 501 to 506 are similar to the processes 401 to 406 in the third embodiment, and steps 507 to 508 are similar to the processes 308 to 309 in the second embodiment.
[0125] In another embodiment of the present invention, the information processing server 1 may be a program for realizing the functions of the embodiment of the present invention described above and the information processing shown in the flowcharts, or a computer-readable storage medium storing the program. In another embodiment, the information processing server 1 may be a method for realizing the functions of the embodiment of the present invention described above and the information processing shown in the flowcharts. In another embodiment, the information processing server 1 may be a server that can supply a computer with a program for realizing the functions of the embodiment of the present invention described above and the information processing shown in the flowcharts. In another embodiment, the information processing server 1 may be a virtual machine that realizes the functions of the embodiment of the present invention described above and the information processing shown in the flowcharts. For example, in another embodiment of the present invention, the information processing server 1 is realized by a cloud (cloud server).
[0126] In an embodiment of the present invention, the information processing server 1 executes a predetermined process and generates ticket data for a ticket for which a purchase application has been accepted, however, a ticket purchase application in an embodiment of the present invention may also be an application for the issuance of a ticket other than a purchase.
[0127] In an embodiment of the present invention, face feature data is an example of feature data that can be obtained from biometric information. For example, feature data that can be obtained from biometric information can be palm print data or voice print data.
[0128] The following describes modified examples of the embodiment of the present invention. The following mainly describes the differences from the embodiment of the present invention. The modified examples described below can be combined appropriately and applied to any embodiment or modified example of the present invention as long as no contradiction occurs.
[0129] [First Modification] In one modified example of the embodiment of the present invention, the feature table 26 does not store face feature data, but includes a feature ID and voice feature data obtainable based on a voice, and the voice feature data is stored in association with the feature ID. The voice feature data is feature data extracted or obtained from voice data by a known voice feature extraction method, for example, a known voice feature extraction program. For example, the voice feature data stored in the feature table 26 is voice feature data obtained from the voice of a non-existent person or an unspecified existing person, and is obtained using the above-mentioned voice feature extraction program. The feature table 26 does not store voice feature data corresponding to voice data of a user who uses a ticket.
[0130] This modification is a modification of the first embodiment, and will be described below. Differences from the first embodiment will be mainly described. The determination device 2 and the client terminal 3 each include a voice input device such as a microphone.
[0131] In step 106, the client terminal 3 accepts voice input from the user via a ticket management web page that displays a screen that requests the user to input a voice, and transmits the voice input to the information processing server 1. In step 107, the server control unit 21 determines voice feature data from the received voice data using a voice feature extraction program stored in the server storage unit 22. In step 201, the determination device control unit 41 operates the photographing device 34 to photograph the ticket, and acquires the ticket ID, feature ID, and check data from the code attached to the ticket. Furthermore, in step 201, the determination device control unit 41 operates the voice input device to acquire voice data of the user who uses the ticket. In step 202, the determination device control unit 41 determines voice feature data from the acquired user voice data using the same voice feature extraction program as the voice feature extraction program stored in the server storage unit 22. The above is similar to the modified examples of the other embodiments.
[0132] [Second modified example] In one modified example of the embodiment of the present invention, the facial feature data stored in the feature table 26 is a plurality of facial feature data calculated by a predetermined calculation program. In this case, the facial feature data stored in the feature table 26 is not facial feature data acquired from a face image of a non-existent person or an unspecified existing person. The above also applies to the case where the feature table 26 stores biometric information other than facial feature data. For example, in this modified example, the voiceprint data stored in the feature table 26 is a plurality of voiceprint data calculated by a predetermined calculation program.
[0133] [Third modified example] In one modified example of the embodiment of the present invention, the determination device 2 further includes a code reading device (not shown) for reading the code attached to the ticket. For example, the determination device 2 includes a main body having the main functions of the determination device 2, and a code reading device communicably connected to the main body. In this modified example, in step 201, the determination device control unit 41 operates the photographing device 34 to obtain a face image of the user, and operates the code reading device to obtain the ticket ID, the feature amount ID or face feature amount data, and the check data from the code attached to the ticket.
[0134] [Fourth Variation] In one modified example of the embodiment of the present invention, the information processing server 1 includes the functions of the ticket sales server 4 and provides a service for purchasing tickets via a ticket sales site to the client terminal 3. In this embodiment, the processes of the information processing server 1 and the ticket sales server 4 described in the first to fourth embodiments are processed within the information processing server 1.
[0135] [Fifth Variation] In one modified embodiment of the present invention, when the ticket is a coupon, the determination device 2 is installed not at the event venue but at a store or the like.
[0136] [Sixth Variation] In one modification of the embodiment of the present invention, the server control unit 21 acquires a ticket ID that has been assigned to the ticket in advance, instead of determining a ticket ID for the ticket for which a purchase application has been accepted. For example, the ticket sales server 4 determines the ticket ID. This modification is described below as a modification of the first embodiment.
[0137] The order information that the ticket sales server 4 sends to the information processing server 1 in step 103 includes the ticket ID determined by the ticket sales server 4. In step 104, the server control unit 21 acquires the ticket ID from the received order information. In step 109, the server control unit 21 calculates check data by performing a predetermined calculation based on the ticket ID acquired in step 104, the feature ID determined in step 108, and the event ID determined in step 104. The server control unit 21 then generates a code to be attached to the ticket based on the ticket ID acquired in step 104, the feature ID determined in step 108, and the calculated check data. The above also applies to the modified examples of the other embodiments.
[0138] [Seventh Variation] In one modification of the first and second embodiments of the present invention, in step 103, the ticket sales server 4 transmits ticket information or order information to the information processing server 1 for each piece of accepted order information. In step 104, a ticket ID is assigned to the ticket identified by the received ticket information or order information. In step 105, the server control unit 21 transmits to the ticket sales server 4 an address (URL) of a ticket management web page associated with the assigned ticket ID. The ticket sales server 4 transmits the address (URL) of a ticket management web page associated with the ticket ID to the user's email address. In this modification, instead of steps 104 to 105 in the first and second embodiments, the server control unit 21 and the ticket sales server 4 execute the above-mentioned processes. Since the server control unit 21 does not transmit information to the user's email address, the information processing server 1 does not need to receive the user information in step 103.
[0139] [Eighth Modification] In one modification of the first and second embodiments of the present invention, the ticket sales server 4 further includes a member database. The member database is similar to that described in the third embodiment, and the member information includes an email address. The email address may be a telephone number, an ID for an SNS or a chat tool, or the like. In this modification, the user information included in the order information is information such as an email address included in the member information.
[0140] [Ninth Variation] In one modification of the first and second embodiments of the present invention, the ticket sales server 4 further includes a member database. The member database is the same as that described in the third embodiment. The server control unit 21 has a function of creating a ticket management web page linked to the ticket sales site. This modification is a modification of the first embodiment and will be described below.
[0141] In this modification, in step 105, the server control unit 21 may not transmit the address of the ticket management web page linked to the ticket ID to the user's email address included in the received order information. The ticket sales site in a logged-in state displays to the user who has purchased the ticket that a face image needs to be input to make the ticket available, and generates a link for accessing the ticket management web page. The server control unit 21 can display the ticket management web page by access from the ticket sales site via the link, and accept the input of a face image from the user via the client terminal 3. In one example, the server control unit 21 can display the ticket management web page linked to the member ID in response to access from the ticket sales site in a logged-in state, and associate the face image of the user whose input has been accepted with the page. This makes it possible to promote use by a wide range of users, since there is no need to input a new face image when purchasing a ticket at the same ticket sales site next time.
[0142] [Tenth Variation] In one variation of the third and fourth embodiments of the present invention, a dedicated application (hereinafter referred to as a "dedicated app") that communicates with the ticket sales server 4 and the information processing server 1 and can provide services similar to those of a ticket sales site and a ticket management web page is installed on the client terminal 3. In a suitable example of this variation, the client terminal 3 is a smartphone. The dedicated app is linked to 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. A variation of the third embodiment will be described below with regard to this variation.
[0143] In step 401, the client terminal 3 accepts an input of a ticket purchase application via the dedicated app. The client terminal 3 transmits order information including ticket information related to the ticket for which the purchase application has been accepted and user information to the ticket sales server 4 via the dedicated app. The user information here may include an ID linked to the dedicated app. In step 405, if the ticket sales server 4 does not store a facial image or cannot acquire a facial image, the server control unit 21 causes the client terminal 3 to display a screen via the dedicated app that requests the user to input a facial image. The server control unit 21 accepts the input of a facial image from the user via the dedicated app.
[0144] In this modification, 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. For example, after generating the ticket data in step 408, the server control unit 21 can accept a change in the user who uses the ticket via the dedicated application.
[0145] In this modification, the dedicated application may include a facial feature extraction program and be configured to determine facial feature data from a facial image. For example, in step 405, if the ticket sales server 4 does not store a facial image or cannot acquire a facial image, the server control unit 21 causes the client terminal 3 to display a screen requesting the user to input a facial image via the dedicated application. Upon receiving the input of a facial image, the dedicated application determines facial feature data from the facial image and transmits the determined facial feature data to the information processing server 1. In this case, the server control unit 21 does not need to execute the process of step 406. The above is also true in the modification of the fourth embodiment.
[0146] [Eleventh Variation] In one modification of the third and fourth embodiments of the present invention, the ticket management web page is configured so that it can be accessed directly by inputting a user ID and password, without going through the ticket sales site.
[0147] [Twelfth Variation] In one modified embodiment of the present invention, the user information included in the order information is an ID or code capable of identifying the client terminal 3, such as an IP address or a MAC address.
[0148] [13th Variation] In one modified embodiment of the present invention, the server storage unit 22 does not include a ticket book table 25 and a ticket book ID. In this modified embodiment, the ticket table 27 includes, as data items, a ticket ID, an event ID, ticket details information, and a feature ID, and the ticket ID and the event ID are associated via the ticket table 27. In this modified embodiment, for example, in step 104 of the first embodiment, the server control unit 21 does not determine a ticket book ID. The server control unit 21 determines an event ID corresponding to the event information included in the received ticket information, and stores the event ID in the ticket table 27 in association with the ticket ID. The above is similar to other embodiments.
[0149] [Modification 14] In one modified example of the embodiment of the present invention, the server storage unit 22 does not store the event table 24 and the event ID, but stores predetermined data. The predetermined data may be data for identifying an event or data for identifying a system administrator. For example, the predetermined data is stored in the ticket table 27 in association with a ticket ID. For example, the predetermined data is numerical data. In this modified example, the same predetermined data as the predetermined data stored in the server storage unit 22 is stored in the determination device 2. For example, for a target ticket, 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 that determines the validity of the use of the ticket. As described in the embodiment of the present invention, it is desirable that the same event ID is stored in the information processing server 1 and the determination device 2, but there are cases where the embodiment of the present invention can be realized by having the information processing server 1 and the determination device 2 store the same predetermined data as in this modified example.
[0150] [15th Variation] In one modification of the first embodiment of the present invention, the predetermined calculation of the server control unit 21 in step 109 is performed based on at least one of the ticket ID determined in step 104 and the feature ID determined in step 108, and the event ID determined in step 104. In this case, the predetermined calculation of the determination device 2 in step 204 is also performed based on at least one of the ticket ID and the feature ID acquired in step 201, and the event ID stored in the determination device storage unit 42. As described in the embodiment of the present invention, from the viewpoint of robustness, it is desirable to perform the predetermined calculation using the ticket ID, the feature ID, and the event ID, but even if one of the ticket ID and the feature ID is not used, the embodiment of the present invention may be realized in some cases. The above is also true for the third embodiment.
[0151] [Modification 16] Similarly, in the modified example of the second embodiment of the present invention, in step 309, the server control unit 21 calculates check data by performing a predetermined calculation based on at least one of the ticket ID determined in step 304 and the facial feature amount data determined in step 308, and the event ID determined in step 304. In this case, the predetermined calculation in step 204 for the determination device 2 is also performed based on at least one of the ticket ID and the facial feature amount data acquired in step 201, and the event ID stored in the determination device storage unit 42. The above is also the same in the fourth embodiment.
[0152] [17th Variation] In one modified example of the embodiment of the present invention, the server control unit 21 determines a plurality of facial feature amount data instead of determining one facial feature amount data from among the facial feature amount data stored in the feature amount table 26. For example, in step 108, the server control unit 21 determines a plurality of facial feature amount data having a predetermined similarity from among the facial 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 above also applies to other embodiments.
[0153] [Modification 18] In one modified example of the embodiment of the present invention, the facial feature amount data stored in the feature amount table 26 is processed feature amount data generated based on the facial feature amount data. In one example, the processed feature amount data is data obtained by performing a predetermined encryption process on the facial feature amount data, which is feature amount data extracted or acquired from a facial image using a facial feature amount extraction program stored in the server storage unit 22. The facial feature amount data is obtained by performing a predetermined decryption 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. In this case, the predetermined decryption process can be a process of restoring the processed data to its original state.
[0154] This modification is a modification of the first embodiment. In step 108, the server control unit 21 compares the facial feature amount data determined in step 107 with the facial feature amount data stored in the feature amount table 26, which is the basis of the processed feature amount data, and determines the processed feature amount data generated based on the facial feature amount data having a predetermined similarity among the facial feature amount data stored in the feature amount table 26, which is the basis of the processed feature amount data. When performing the comparison process, the server control unit 21 decrypts the processed feature amount data to obtain the facial feature amount data. When determining the processed feature amount data, the server control unit 21 determines the facial feature amount data, and determines the processed feature amount data obtained by encrypting the determined facial feature amount data. The determined processed feature amount data is stored in the feature amount table 26. With this configuration, in this modification, the feature amount table 26 does not store the facial feature amount data as it is, so that it is possible to further reduce the risk regarding the biometric information of the user who uses the ticket. In step 203, the determination device control unit 41 decodes the processed feature data associated with the feature ID in the feature table 46, and determines whether or not the feature ID acquired in step 201 and the face feature data determined in step 202 satisfy a predetermined criterion. The above is the same in the third embodiment.
[0155] As in the above, this modification will be described below as a modification of the second embodiment. In step 308, the server control unit 21 compares the facial feature amount data determined in step 307 with the facial feature amount data on which the processed feature amount data stored in the feature amount table 26 is based, and determines the processed feature amount data generated based on the facial feature amount data having a predetermined similarity among the facial feature amount data on which the processed feature amount data stored in the feature amount table 26 is based. In step 309, the server control unit 21 calculates check data 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. The server control unit 21 generates a code to be 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. In step 203, the determination device control unit 41 determines whether or not the facial feature amount data on which the processed feature amount data acquired in step 201 is based and the facial feature amount data determined in step 202 have a predetermined similarity.
[0156] [Modification 19] In one modification of the embodiment of the present invention, the facial feature amount data is stored in a data structure or data format different from that shown in FIG. 7. In another modification, the facial feature amount data is data indicating numerical information of a dimensional vector other than a 128-dimensional vector. For example, the facial feature amount data is data indicating numerical information of a 256-dimensional vector. The facial feature amount data is not limited to these, as long as it is data obtained using a known facial feature amount extraction program. In addition, the calculation of the similarity performed by the server control unit 21 can use a value corresponding to the Euclidean distance between two facial feature amount data, or can use other known methods.
[0157] [20th Variation] In one modified example of the embodiment of the present invention, 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, as a data table, a ticket ID and status information indicating either unused or used, and the ticket ID is a primary key. In the flowchart shown in FIG. 11, the determination device control unit 41 determines whether or not the ticket ID acquired from the code acquired in step 201 is used, for example, before step 203. If the ticket ID is unused, this flowchart updates the status information associated with the ticket ID in the used ticket table to used, and proceeds to step 203. If the ticket ID is used, this flowchart proceeds to step 206. The process of determining whether or not the ticket ID is used may be executed at any time between steps 202 to 205.
[0158] [21st Variation] In one modified embodiment of the present invention, the server control unit 21 is configured to generate a code by writing data to an RF tag. This modified embodiment will be described below as a modified version of the first embodiment. In step 109, the server control unit 21 writes data corresponding to the ticket ID, the feature ID, and the check data to the RF tag. For example, a user who uses a ticket can obtain the RF tag with the data written therein by mail or the like. The RF tag can also be another non-contact IC card. The above also applies to the modified versions of the other embodiments.
[0159] In the above-described processes or operations, the processes or operations can be freely changed as long as no inconsistencies in the processes or operations occur, such as the use of data that should not yet be available in a certain step. Furthermore, the above-described embodiments are merely examples for explaining the present invention, and the present invention is not limited to these embodiments. The present invention can be embodied in various forms without departing from the gist of the present invention. [Explanation of symbols]
[0160] 1. Information processing server 2 Judgment device 3. Client terminal 4 Ticket sales server 5, 6 Network 10. Information Processing Systems 11, 31, 51, 52 processors 12, 32, 52, 62 input devices 13, 33, 53, 63 Display device 14, 35, 54, 64 storage device 15, 36, 55, 65 Communication equipment 16, 37, 56, 66 Bus 21 Server control unit 22 Server memory unit 24 Event Table 25 Ticket Book Table 26, 46 Feature Table 27 Ticket Table 28 User Table 34 Imaging Equipment 41 Judgment device control section 42 Judgment device storage unit 71 Event Information 72 QR Code (registered trademark)
Claims
1. A program for operating a computer having a processor and a memory, The program causes the processor to: determining first feature data from biometric information of a user; a step of comparing the determined first feature data with a plurality of feature data created in advance, the plurality of feature data not corresponding to biometric information of the user, and determining, from the plurality of feature data, second feature data having a predetermined similarity to the first feature data; A program to execute.
2. The processor, storing the second feature data in association with at least one of identification information of the user and identification information of a ticket related to the user; The program according to claim 1 .
3. The processor, generating ticket data relating to a ticket related to the user based on the second feature data; The program according to claim 1 .
4. The processor, generating data to be stored in an identification medium based on the second feature data; The program according to claim 1 .
5. The processor, generating ticket data relating to a ticket to which the identification medium storing the data is attached; The program according to claim 4, which causes the program to execute the following:
6. An information processing device having a control unit, The control unit: determining first feature data from biometric information of a user; a step of comparing the determined first feature data with a plurality of feature data created in advance, the plurality of feature data not corresponding to biometric information of the user, and determining, from the plurality of feature data, second feature data having a predetermined similarity to the first feature data; An information processing device that executes the above.
7. A method of operating a computer having a processor and a memory, comprising: The processor, determining first feature data from biometric information of a user; a step of comparing the determined first feature data with a plurality of feature data created in advance, the plurality of feature data not corresponding to biometric information of the user, and determining, from the plurality of feature data, second feature data having a predetermined similarity to the first feature data; A method for performing.
8. A means for determining first feature data from biometric information of a user; a means for comparing the determined first feature data with a plurality of feature data created in advance, the plurality of feature data not corresponding to biometric information of the user, and determining, from the plurality of feature data, second feature data having a predetermined similarity to the first feature data; A system comprising:
