Server-Based Peer-to-Peer Authentication Without Personal Data
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current communication methods require personal information for user authentication, limiting the ability to provide secure communication services without inputting phone numbers or other personal details, and do not enable peer-to-peer communication effectively.
Innovation Solution
The method involves generating a unique identifier and security key for clients based on device and manufacturing keys, allowing peer-to-peer communication without personal information input, using a server to manage key pairs and authenticate clients, and enabling encrypted packet transmission between clients.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If personal information (phone number, e-mail) is used for user authentication, then user identification and communication service provision is achieved, but the ability to provide secure communication services without personal information input is limited
Solution Approach 1:
The patent uses device identifiers and manufacturing keys as copies or representations of user identity, replacing the need for personal information like phone numbers and e-mails. The server assigns unique identifiers to devices, enabling communication services without requiring users to input their personal information, thus maintaining service accessibility while removing the dependency on personal data.
Solution Approach 2:
The patent substitutes the mechanical/manual process of users inputting personal information with an automated system where the server automatically assigns identifiers and manages authentication. The server receives device information, generates unique identifiers, and handles authentication automatically, replacing the manual personal information entry process with an automated identifier-based system.
2Productivity
If peer-to-peer communication is enabled, then direct communication between clients is achieved, but secure authentication and key management without server involvement is required
Solution Approach 1:
The server acts as an intermediary that manages the complex authentication and key distribution processes. The server receives device information, generates unique identifiers, creates key pairs, and distributes them to clients. This intermediary approach allows peer-to-peer communication to function efficiently while the server handles the complexity of authentication and key management, reducing the burden on individual clients.
3Reliability
If unique identifiers and security keys are generated for each client, then secure peer-to-peer communication is enabled, but the system requires sophisticated key management and authentication mechanisms
Solution Approach 1:
The system implements self-service through automatic identifier assignment and key generation. When a device connects to the server, the server automatically generates a unique identifier and key pair without requiring manual user input or configuration. The server stores these credentials and automatically manages the authentication process, allowing clients to communicate securely without needing to manually manage their own keys or identifiers.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Disclosed is a method for operating a server supporting peer-to-peer communication. One embodiment comprises the steps of: issuing a public key in response to a public key request received from a client and transmitting the public key to the client; receiving a private key from the client and mapping the public key and private key as a key pair; receiving, from the client, a request to generate an identifier comprising one or more items of unique information of the client; generating an identifier corresponding to the client in response to the request to generate an identifier, generating a security key utilizing the unique information, and transmitting the identifier and security key to the client; receiving, from the client, an authentication request comprising the identifier and security key; and authenticating the client in response to the authentication request and transmitting the authentication result to the client.