Secondary Device Authentication via Primary Trust Proxy
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Mobile telecommunications networks face vulnerabilities in user authentication, including shared usernames and passwords across platforms, lack of three-factor authentication, inconsistent multi-layer security, and manual monitoring processes, which can lead to unauthorized access and fraudulent activities.
Innovation Solution
Establishing a trust relationship with a primary mobile device using mechanisms like MAG authorization, IMSI encryption challenges, and self-identified IMSI processes, and extending this trust to secondary devices through authorization codes and access tokens, ensuring only authorized users can access accounts across different devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If traditional username and password authentication is used across multiple platforms, then ease of operation is improved, but security is worsened due to shared credentials and lack of multi-factor authentication
Solution Approach 1:
The authentication system is segmented into multiple independent factors: device trust relationship (established through MAG authorization or IMSI encryption), authorization codes (sent via SMS or email), and access tokens (generated upon successful verification). This segmentation allows each factor to operate independently, providing both convenience and security.
Solution Approach 2:
A server acts as an intermediary between the user's device and the service provider systems. The server establishes trust relationships with devices, generates authorization codes, and issues access tokens. This intermediary layer enables multi-factor authentication without requiring users to manually manage complex security protocols, thus maintaining ease of operation while improving security.
2Reliability
If multi-layer security with three-factor authentication is implemented, then security is improved, but device complexity and ease of operation are worsened due to manual monitoring and inconsistent security layers
Solution Approach 1:
The system enables self-service authentication where the server automatically manages trust relationships, generates authorization codes, and issues access tokens without requiring manual security administration. The primary device automatically establishes trust relationships through MAG authorization or IMSI encryption, and the server handles code generation and verification, eliminating the need for manual security configuration and monitoring.
Solution Approach 2:
The authentication system is designed to be universal and consistent across all service provider networks and platforms. The same trust establishment mechanisms (MAG authorization, IMSI encryption) and token generation processes are applied uniformly regardless of the specific service or network, providing consistent multi-layer security without requiring separate security configurations for different systems.
3Reliability
If device trust relationships are established through MAG authorization or IMSI encryption, then security is improved, but loss of time increases due to authentication processes
Solution Approach 1:
Trust relationships are established preliminarily between the server and the primary device through MAG authorization or IMSI encryption before actual service access is required. Once the trust relationship is established, the server can quickly generate authorization codes and issue access tokens without repeating the full authentication process, significantly reducing authentication time for subsequent access requests.
Solution Approach 2:
The system uses authorization codes as a copy or representation of the trusted device's identity. Instead of requiring the primary device to directly authenticate each access request, the server creates authorization codes that can be transferred to secondary devices. This copying mechanism allows rapid authentication of secondary devices without repeating the time-consuming trust establishment process.
Data Source
AI summary
A method of authenticating a secondary communication device based on authentication of a primary mobile communication device is disclosed. Trust is established with the primary mobile communication device by a device authentication server (DAS). The DAS receives an authorization code request from a secondary application operating on the secondary communication device, and transmits an authorization code to the secondary communication device. The DAS receives the authorization code from a primary application operating on the primary mobile communication device. The DAS authorizes the secondary application based on the trust with the primary mobile communication device and the authorization code from the primary application. The DAS transmits a secondary token to the secondary application at the secondary communication device to allow initialization of a communication session from the secondary application on behalf of the primary mobile communication device.