Validator Device for Ticket Systems Using Local Authentication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In ticket systems with open architectures, the reliability of inspection results is compromised due to delays in user data record transmission and unreliable communication connections, leading to false negative results when inspecting user identification elements.
Innovation Solution
A validator device with a short-range interface for receiving inspection identifiers, an authentication module for checking authenticity, and a key module for providing a communication data set to establish a secure connection with the inspection device, eliminating the need for a connection to the remote computing device and simplifying key management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the inspection device downloads user data records from the remote central computing device via cellular connection, then the inspection device can access user data for comparison, but communication delays and unreliable connections cause false negative inspection results
Solution Approach 1:
The validator device acts as an intermediary between the inspection device and the remote central computing device. Instead of the inspection device directly downloading data from the remote server via potentially unreliable cellular connections, the validator device receives inspection identifiers from the inspection device and returns the corresponding user data records locally, eliminating the need for the inspection device to establish direct communication with the remote server.
Solution Approach 2:
The validator device stores user data records locally in advance, making them immediately available for inspection comparisons. This preliminary storage of data eliminates the need for real-time data downloads during inspection, thereby removing transmission delays and ensuring that inspection results are based on current, accurate data without timing issues.
2Ease of operation
If the inspection device establishes direct connection to remote computing device, then data access is possible, but system complexity and key management become more difficult
Solution Approach 1:
The complex communication infrastructure and key management responsibilities are extracted from the inspection device and relocated to the validator device. The inspection device only needs simple local communication capabilities to interact with the validator device, while the validator device handles all complex interactions with the remote central computing device, including secure key management and data retrieval.
3Adaptability or versatility
If open media are used as user identification elements, then system flexibility is improved, but inspection becomes more difficult since validation devices cannot write back to identification elements
Solution Approach 1:
The system implements a feedback mechanism where the inspection device presents an inspection identifier to the validator device, and the validator device responds by providing the corresponding user data record. This feedback loop allows the inspection system to verify user identification elements using open media without requiring write capabilities, as the validator device supplies the reference data needed for comparison.
Data Source
Figure 1
Figure 2~3
Figure 4~6
AI summary
The invention relates to a validator device (104, 204, 304) for a ticketing system (100, 200), comprising at least one first near-field interface (106, 206, 306) configured to receive at least one inspection identifier stored in an inspection element (442), at least one authentication module (326) configured to verify the authenticity of the received inspection identifier, and at least one key module (332) configured to provide a communication data set for a second near-field interface (324) upon a positive authentication result, such that the communication data set can be received by the inspection element (442, 642) via the first near-field interface (106, 206, 306) and/or a further interface of the validator device (104, 204, 304).