Network Connection History Authentication Mechanism
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional password-based authentication methods are insufficient due to increasing sophistication in security breaches, with no adequate solutions currently available to enhance electronic authentication effectively.
Innovation Solution
A device and method that utilize a network connection history, such as Wi-Fi, Bluetooth, or VPN history, to authenticate a second device by matching connection data from a first device with stored connection histories, allowing access to resources based on the ordering and timing of connections, and evolving with time, potentially using only the most recent history for authentication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If traditional password-based authentication is used, then ease of operation is improved, but security reliability deteriorates due to data center hacks and intercepted transmissions
Solution Approach 1:
The patent replaces the mechanical/password-based authentication system with a network-based authentication system that uses network connection histories. Instead of relying on passwords that can be stolen or intercepted, the system uses the sequence and timing of network connections (Wi-Fi, Bluetooth, cellular, etc.) as a dynamic authentication mechanism. This substitution maintains ease of use while dramatically improving security reliability.
Solution Approach 2:
The patent introduces dynamic authentication by using network connection histories that continuously evolve over time. The authentication criterion changes dynamically based on the sequence of network connections made by a device. Rather than a static password, the system adapts the authentication requirement based on the device's network behavior pattern, making it increasingly secure over time while remaining convenient for legitimate users.
2Reliability
If network connection history is used for authentication, then security reliability is improved, but device complexity increases due to multiple network interfaces and data processing requirements
Solution Approach 1:
The patent achieves universality by using a single authentication mechanism (network connection history comparison) that works across multiple network types (Wi-Fi, Bluetooth, cellular, Ethernet, VPN). The same principle applies regardless of which network interfaces are used, simplifying the overall system architecture while maintaining high security. The server compares connection histories from various network types using a unified approach.
Solution Approach 2:
The patent introduces network connection history as an intermediary element between the device and the authentication server. Instead of the device directly providing authentication credentials, the system uses the network connection history as a mediator that carries authentication information. This intermediary approach simplifies the authentication process by abstracting away the complexity of multiple network interfaces and authentication methods.
3Measurement precision
If multiple network connection histories are stored and compared, then authentication accuracy is improved, but information storage requirements and processing time increase
Solution Approach 1:
The patent applies segmentation by dividing the network connection history into discrete, manageable segments (individual network connections with timestamps and identifiers). Each connection event is recorded as a separate entry in the history log. This segmentation allows the system to store only the necessary connection details rather than entire network states, reducing storage requirements while maintaining authentication accuracy through sequential comparison of these segmented connection records.
Data Source
AI summary
In one aspect, a first device includes at least one processor and storage accessible to the at least one processor. The storage includes instructions executable by the at least one processor to access a first network connection history for a second device different from the first device. The instructions are also executable to determine in a first instance whether to authenticate the second device based on the first network connection history and to authenticate the second device based on a determination to authenticate the second device.