Time-Based Authentication Apparatus Resynchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing two-factor authentication methods using mobile phones are unreliable due to text message delivery delays, signal issues, and time synchronization problems, especially when users travel across time zones, leading to scalability and reliability issues.
Innovation Solution
A time-based authentication apparatus that generates and uses composite codes from portable electronic devices, allowing for automatic resynchronization across different time slots, enhancing security and usability by doubling the number of digits in the authentication process without requiring a network connection.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If text messages are used to send passcodes to mobile phones, then authentication can be performed, but delivery delays and signal issues reduce reliability
Solution Approach 1:
The system pre-generates and stores multiple time-based codes in advance within the authentication server, so that when authentication is needed, the codes are already ready and do not require real-time generation or messaging. This eliminates delivery delays as the codes are retrieved rather than sent.
Solution Approach 2:
Instead of sending a single time-based code via text message, the system uses multiple copies of time-based codes that are pre-generated and stored. The authentication process retrieves appropriate codes from these pre-generated copies, ensuring availability without relying on real-time message delivery.
2Speed
If time-based codes are used for authentication, then authentication speed improves, but time synchronization problems arise when users travel across time zones
Solution Approach 1:
The system changes the parameter of time-based code generation by allowing the authentication server to generate codes based on the server's own time rather than relying on the user's device time. This decouples the authentication process from the user's local time zone, as the server generates codes independently and stores them for later retrieval.
Solution Approach 2:
The system incorporates time synchronization feedback by continuously tracking the user's device time versus server time and adjusting the code retrieval process accordingly. When a user travels to a different time zone, the system detects the time discrepancy and retrieves codes that account for this offset, ensuring authentication remains reliable.
3Reliability
If multiple time-based codes are accepted for authentication, then reliability across time zones improves, but system complexity increases
Solution Approach 1:
The system segments the authentication process into distinct phases: pre-generation of time-based codes, storage of these codes, and retrieval during authentication. By separating these functions, the complexity is distributed across different components rather than concentrated in a single complex algorithm, making the system more manageable and maintainable.
Solution Approach 2:
The system performs preliminary generation and storage of multiple time-based codes before authentication is needed. This pre-computation eliminates the need for complex real-time calculations during authentication, as the codes are already prepared and stored. The authentication process simply involves retrieving the appropriate pre-generated codes rather than computing them on-demand.
Data Source
Figure 1A
Figure 1B
Figure 2
AI summary
Time-based authentication apparatus deploys a seed record to user equipment such as a mobile telephone pre-equipped with an app. When a user initiates login access to a protected product or service, using a computing device, they run the app on their mobile equipment which delivers an output such as a QR code (or other local communication such as NFC) containing two time-based codes. The login process on the computing device accepts the output and sends the time-based codes to the authentication apparatus, either together or the second code on request. The authentication apparatus now locates the codes and automatically resynchronises to any time zone across the world plus 1 hour of clock drift (+/- 13 hours UTC).