Biometric Ticket Security via Feature Extraction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional methods for preventing unauthorized resale of tickets using facial recognition technologies pose risks of personal information leakage and lack effectiveness in preventing unauthorized use.
Innovation Solution
An information processing server and system that manage tickets by creating and storing feature quantity data from biological information, generating a code based on this data and ticket information, and attaching it to the ticket, while ensuring that personal information is not directly stored on the ticket or determination device.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If facial recognition technology is used to prevent unauthorized resale, then ticket security is improved, but personal information leakage risk increases
Solution Approach 1:
The patent extracts only the essential feature quantity data from the user's facial information and stores this extracted data on the ticket, while the complete facial information remains stored securely in the server's database. This extraction approach allows facial recognition functionality to be maintained while minimizing the amount of personal information exposed on the ticket itself.
Solution Approach 2:
The patent introduces a server as an intermediary between the ticket and the complete user facial information. The server stores the full facial information and provides feature quantity data to the ticket upon request, acting as a mediator that prevents direct storage of complete personal information on the ticket while maintaining security functionality.
2Object-affected harmful factors
If no personal information is stored on the ticket, then personal information leakage risk is reduced, but unauthorized resale prevention capability deteriorates
Solution Approach 1:
The patent segments the facial information into two parts: feature quantity data that is stored on the ticket and complete facial information that is stored on the server. This segmentation allows the ticket to contain minimal personal information for security purposes while the server maintains the complete data needed for accurate facial recognition and unauthorized resale prevention.
Solution Approach 2:
The patent performs preliminary extraction of feature quantity data from the user's facial information before issuing the ticket. This preliminary action ensures that the ticket contains the necessary data for security verification without requiring storage of complete personal information, thereby preventing unauthorized resale while minimizing information leakage risk.
3Reliability
If feature quantity data is stored on the ticket, then unauthorized use prevention is improved, but personal information protection deteriorates
Solution Approach 1:
The patent extracts only the necessary feature quantity data from the complete facial information and stores this extracted data on the ticket. By taking out only the essential features needed for recognition rather than the complete facial information, the system achieves unauthorized use prevention while maintaining personal information protection.
Solution Approach 2:
The patent applies local quality by storing different types of data in different locations: feature quantity data is stored on the ticket for local verification, while complete facial information is stored on the server for centralized management. This local quality approach ensures that personal information is protected while still enabling effective unauthorized use prevention where needed.
Data Source
AI summary
An information processing server for managing a ticket, including: a server storage unit storing feature quantity data obtainable from biological information and created in advance, feature quantity identification information associated with the feature quantity data, and prescribed data that is identical to prescribed data stored in a determination device for determining a usage validity of a ticket; and a server control unit determining an item of feature quantity data from a piece of biological information on a user who is to use a ticket, determine a piece of feature quantity identification information based on a comparison between the determined item of feature quantity data and items of feature quantity data stored in the server storage unit, generate a code to be attached to the ticket based on an assigned piece of ticket identification information, the determined piece of feature quantity identification information, and the prescribed data, and generate ticket data.


