Contact List Authentication via Server-Side Hash Comparison
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing user authentication methods rely heavily on identifiers and passwords, or additional devices like OTPs, which may not provide robust secondary authentication mechanisms, especially in scenarios where device changes occur.
Innovation Solution
A system and method that utilizes a contact list stored on an electronic device, where a server compares contact list information from different devices to authenticate users based on a threshold ratio of common contacts, generating hash values and storing relevant information to verify user identity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional identifier and password authentication is used, then the authentication process is simple and fast, but the security and robustness of authentication is insufficient
Solution Approach 1:
The patent introduces contact list information as an intermediary element for authentication. Instead of directly comparing passwords or using complex cryptographic protocols, the system uses the user's contact list as a mediator to verify identity. The contact list serves as a unique profile that reflects the user's social connections, making it difficult for attackers to compromise without access to the user's actual contact network.
Solution Approach 2:
The system performs preliminary actions by storing and indexing contact list information in advance during user registration. The contact lists are pre-processed and stored in the server's database, allowing for rapid comparison during authentication without requiring real-time data collection. This preliminary preparation enables fast authentication while maintaining security.
2Reliability
If contact list information is transmitted and stored for authentication, then additional authentication capability is provided, but data transmission and storage requirements increase
Solution Approach 1:
The patent extracts only the essential elements needed for authentication from the complete contact list. Instead of transmitting and storing entire contact lists with all details, the system extracts key identifiers and comparison-relevant features. This extraction process reduces the volume of data that needs to be transmitted and stored while maintaining the authentication capability.
Solution Approach 2:
The system uses partial contact list information for authentication purposes rather than requiring complete contact list data. By using a subset of contact information that is sufficient for verification, the system reduces data transmission and storage requirements while still providing reliable authentication. The patent compares only the necessary portions of contact lists to determine authentication outcomes.
3Reliability
If contact list comparison is performed for authentication, then user identity verification is enhanced, but processing time and computational resources increase
Solution Approach 1:
The system performs preliminary processing of contact list information during registration, including indexing, hashing, or other pre-computation techniques. This preliminary action prepares the data in advance so that during authentication, the comparison process is significantly accelerated. The pre-processed data structures enable rapid querying and comparison without requiring intensive real-time computation.
Solution Approach 2:
The contact list comparison process is segmented into multiple stages or phases. Instead of comparing entire contact lists in a single operation, the system divides the comparison into smaller, manageable segments that can be processed efficiently. This segmentation allows for optimized processing at each stage, reducing overall authentication time while maintaining verification accuracy.
Data Source
AI summary
A user authentication system and method uses a contact list that may receive contact list information stored in an electronic device from the electronic device over a network. The system is further configured to store, in a database, and manage first contact list information received from a first electronic device of a user through the reception controller in association with an identifier of the user, compare second contact list information received from the first electronic device or a second electronic device to the first contact list information stored in the database in association with the identifier of the user, in response to a service request from the first electronic device or the second electronic device based on the identifier of the user; and determine whether to authenticate the user in response to the service request from the first electronic device or the second electronic device based on the comparison result.