Ephemeral Token Validation for Secure Device Identifier Authentication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing client server authentication solutions rely on manual user input for authenticating information, leading to inefficiencies and errors, especially when sensitive information like device-specific data is required, which can waste networking and computing resources and limit self-service interactions.
Innovation Solution
A validation system using ephemeral tokens, generated by user equipment (UE) based on device identifiers like IMEI, which are encrypted and transmitted to a token validation server for authentication, allowing secure and efficient validation without exposing sensitive information over unsecure connections.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If manual user input is used for authentication, then users can provide authenticating information, but it leads to errors and inefficiencies in authentication processes
Solution Approach 1:
The system enables self-service authentication by automatically extracting device identifier information from the user equipment without requiring manual user input. The validation component within the application program automatically obtains and transmits the device identifier to the server, eliminating human error while maintaining ease of operation.
Solution Approach 2:
The patent replaces the mechanical process of manual typing and form-filling with an automated electronic extraction and transmission system. The validation component automatically retrieves the device identifier from the device's memory or hardware and transmits it through the application programming interface, substituting manual mechanical input with automated electronic processes.
2Productivity
If sensitive device-specific information is transmitted over unsecure connections, then authentication can be performed, but security risks increase
Solution Approach 1:
The system extracts and transmits only the specific device identifier information needed for authentication, rather than transmitting all sensitive device-specific data. The server validates the extracted identifier against stored records, minimizing the amount of sensitive information transmitted over the network while maintaining authentication security.
Solution Approach 2:
The server pre-stores valid device identifier records in its database before authentication occurs. During authentication, the system only needs to compare the extracted identifier against these pre-stored values, eliminating the need to transmit or process additional sensitive information and reducing security risks associated with data transmission.
3Measurement precision
If correct device identifier information is not provided on the first attempt, then authentication fails, but networking and computing resources are wasted
Solution Approach 1:
The validation component automatically ensures accurate device identifier extraction and transmission without requiring user intervention or multiple attempts. The system self-corrects potential errors by using the device's official identifier from its hardware or memory, ensuring first-attempt success and eliminating resource waste from failed authentication attempts.
Data Source
AI summary
A validation system includes a user equipment (UE) and a client server. The UE is configured to store a device identifier associated with the UE. In response to a first validation request triggered by an application program of the UE, the UE is configured to encrypt the device identifier to generate an ephemeral token having a token value that is representative of the device identifier, transmit the first validation request including the ephemeral token, receive a first validation response based on the first validation request, and provide the first validation response to the application program. The client server is configured to receive the first validation request, transmit a second validation request, including the ephemeral token, for validation of the ephemeral token, receive a second validation response based on the ephemeral token included in the second validation request, and generate the first validation response based on the second validation response.