Network Authentication Token Exchange via Local Application Broadcasting
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Users subscribed to multiple services face burdensome authentication processes, requiring repeated entry of identification information each time they access a new service or network.
Innovation Solution
Implementing a system where an application associated with a service provider broadcasts a message to other applications on the user's home network, allowing identification information to be shared and verified by a backend server, thereby eliminating the need for users to manually input login credentials.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If users manually enter identification information for each service, then authentication security is maintained, but user convenience and time efficiency deteriorate
Solution Approach 1:
The system performs preliminary authentication by having users enter their credentials once when initially subscribing to services. The backend server stores this authentication information and uses it for subsequent automatic authentications, eliminating the need for repeated manual entry.
Solution Approach 2:
The backend server acts as an intermediary that stores and manages authentication information. When a user device needs to access a service, the local application communicates with the backend server to obtain authentication tokens, which then facilitate automatic authentication without requiring users to manually enter credentials again.
2Extent of automation
If automatic authentication is implemented, then user convenience improves, but system complexity increases
Solution Approach 1:
The backend server serves as a centralized intermediary that manages authentication information storage and verification. This centralization simplifies the overall system architecture by concentrating complexity in one location rather than distributing it across multiple service applications and user devices.
Solution Approach 2:
The backend server provides universal authentication services for multiple different services and applications. By creating a single authentication system that works across all services, the patent avoids the complexity of implementing separate authentication mechanisms for each individual service.
3Productivity
If identification information is stored locally, then authentication speed increases, but security risks increase
Solution Approach 1:
The backend server acts as a secure intermediary that maintains the master copy of authentication information. Local devices store only authentication tokens that are issued and managed by the backend server, ensuring that sensitive credential data remains protected on the server while enabling fast local authentication through token verification.
Solution Approach 2:
Instead of storing complete authentication credentials locally, the system creates and stores simplified authentication tokens as copies on user devices. These tokens are sufficient for verification purposes but do not contain the full security-sensitive information, which remains stored securely on the backend server.
Data Source
AI summary
In some implementations, a first device may connect to a network, wherein the first device is associated with a first application that is associated with a service provider. The first device may detect that a second device connected to the network is associated with a second application that is associated with the service provider. The first device may receive, from the second device, identification information associated with the second device. The first device may transmit, to a third device associated with the service provider, the identification information associated with the second device. The first device may receive, from the third device, authentication information permitting the first application to operate on the network based on the third device receiving the identification information associated with the second device.