Dynamic Parameter Authentication Using Connected Device Metrics
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing authentication methods are vulnerable to issues such as forgotten PINs, injured fingers for fingerprint scanning, and the insecurity of static secure questions, as well as the risks associated with relying on portable devices that can be lost, stolen, or run out of battery.
Innovation Solution
The method involves determining a device for authentication, receiving a parameter value from the device, and authenticating the client based on both the authentication value provided by the client and the parameter value. This approach utilizes connected devices as native token sources, eliminating the need for special software or hardware, and allows for the use of variable parameters to enhance security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a secret code (PIN or password) is used for authentication, then the authentication method is simple and widely applicable, but the user may forget the code or enter it wrong multiple times leading to blocking
Solution Approach 1:
The system changes the authentication parameter from a static secret code to a dynamic parameter value that can be obtained from various connected devices (odometer reading, fuel level, battery level, etc.). This allows the authentication method to remain simple while providing multiple alternative sources for the authentication value, preventing blocking due to forgotten or mistyped codes.
2Reliability
If a fingerprint sensor is used for authentication, then the authentication is secure and convenient, but authentication becomes impossible if the user injures the finger
Solution Approach 1:
The system implements multi-functionality by accepting authentication values from multiple different types of connected devices (vehicle odometer, fuel level indicator, battery level indicator, etc.). This universal approach ensures that if one authentication method is unavailable due to injury or other reasons, alternative methods can be used to maintain authentication security and availability.
3Ease of manufacture
If static secure questions are used as backup authentication, then the setup is simple, but the questions are insecure as answers can be easily guessed or investigated
Solution Approach 1:
The system transitions from static secure questions to dynamic parameter values that change over time (odometer readings, fuel levels, battery levels). These dynamic values are much harder to guess or investigate compared to static answers, while maintaining simple setup through automatic device integration.
4Ease of operation
If a software token (SMS or mobile application) is used for backup authentication, then the authentication method is accessible, but the portable device can be lost, stolen, or run out of battery
Solution Approach 1:
The system creates multiple copies of the authentication capability across different connected devices. Instead of relying on a single mobile device, the authentication function is distributed across various devices (vehicle systems, fuel indicators, battery indicators), ensuring that if one device is lost or fails, authentication remains accessible through other devices.
5Reliability
If a hardware token device is used for backup authentication, then the authentication is more secure, but the device requires specialized hardware that can be broken, lost, or forgotten and requires regular maintenance
Solution Approach 1:
The system eliminates the need for specialized hardware tokens by utilizing the existing multi-functional connected devices that the user already possesses and interacts with regularly (vehicle odometer, fuel system, battery system). This approach maintains strong authentication security while reducing device complexity and eliminating maintenance requirements.
Data Source
Figure 1a
Figure 1b
Figure 1c
AI summary
A method, apparatus, and computer program for authenticating a client is disclosed. The method comprises determining a device to be used for the authentication of the client, receiving a parameter value of the device and an authentication value of the client, and authenticating the client based on the authentication value and the parameter value.