Terminal Electronic Ticket Authentication for Offline Display
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems for managing electronic tickets in terminal devices face challenges when communication with a control center is unavailable due to system failures or maintenance, leading to potential inability to use the electronic tickets.
Innovation Solution
A terminal device with a controlling portion that stores electronic tickets and executes authentication, allowing display of associated tickets even in non-communicable states by utilizing stored authentication information and conditions such as usage start, user association, and geographical validity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the terminal device requires communication with the server for authentication and ticket display, then the security and control of the electronic ticket system is improved, but the availability and usability of the electronic ticket deteriorates when the server is unavailable
Solution Approach 1:
The terminal device performs authentication with the server in advance and stores the authentication result and ticket information locally in the storage portion. When the server is available, the device authenticates the user and saves the ticket data. When the server becomes unavailable, the device can still display the previously authenticated ticket from local storage, eliminating the need for real-time server communication during ticket display.
Solution Approach 2:
The terminal device creates a local copy of the electronic ticket data in its storage portion after successful authentication. This copy contains all necessary ticket information (ticket ID, usage conditions, validity period, etc.) to function independently. The device displays this local copy when the server is unavailable, effectively decoupling the display function from continuous server dependency while maintaining security through initial authentication.
2Measurement precision
If the terminal device continuously checks communication status with the server, then the accuracy of ticket validity verification is improved, but the complexity of the system increases
Solution Approach 1:
Instead of continuously checking server communication status, the terminal device performs authentication only when needed (when the user attempts to use the ticket) and stores the result. The device checks communication status only at authentication moments, not continuously. This partial action approach maintains verification accuracy by authenticating before use while avoiding the complexity of continuous monitoring systems.
Solution Approach 2:
The terminal device uses its own stored authentication results and ticket data to verify and display tickets independently when the server is unavailable. The device serves itself by relying on previously obtained authentication information from local storage, eliminating the need for complex continuous server communication infrastructure while maintaining functional accuracy for valid tickets.
Data Source
AI summary
A terminal device according to this disclosure is a terminal device including a controlling portion, a storage portion, and a communication portion. The controlling portion stores electronic tickets in the storage portion. The controlling portion executes authentication of a user through communication with a server. In a case where the user is authenticated successfully, the controlling portion causes an electronic ticket associated with the user to be displayable from among the electronic tickets stored in the storage portion. In a case where a non-communicable state in which the communication with the server is not performable is established, the controlling portion causes a corresponding electronic ticket to be displayable from among the electronic tickets stored in the storage portion.