Accessory Authentication Using Remote Token History Checks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The increasing prevalence of counterfeit computing device accessories poses a challenge for legitimate manufacturers, as existing authentication methods relying on security chips can be compromised, leading to counterfeit devices being authenticated and causing security chip shortages.
Innovation Solution
Implementing a remote server-based authentication system that verifies device certificates and tokens through an encrypted communication channel, adding an additional layer of security by maintaining a token history and ban list to identify and ban counterfeit devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If security chips are used for authentication, then device authentication is improved, but the system becomes vulnerable to chip compromise and counterfeit devices
Solution Approach 1:
The patent introduces a remote server as an intermediary authentication authority. Instead of relying solely on security chips embedded in devices, the server acts as a mediator that verifies device certificates and tokens. This intermediary layer detects counterfeit devices by checking token histories and ban lists, thereby reducing vulnerability to chip compromise while maintaining authentication reliability.
Solution Approach 2:
The patent adds a remote authentication dimension to the traditional local chip-based authentication. By implementing server-based verification of device certificates and tokens, the system moves from single-point (chip) authentication to multi-point (chip + server) authentication, enhancing security against counterfeit devices without sacrificing reliability.
2Reliability
If remote server-based authentication is implemented, then authentication security is improved, but system complexity increases
Solution Approach 1:
The patent extracts the complex authentication verification logic from the device level and places it at the remote server level. Devices only need to store and transmit their certificates and tokens, while the server handles the complex verification processes including token history checks and ban list comparisons. This extraction reduces device complexity while maintaining high authentication security.
Solution Approach 2:
The server provides feedback to devices about authentication status through token issuance and ban list notifications. This feedback mechanism simplifies device operations by allowing automatic authentication decisions based on server responses, reducing the computational burden on devices while maintaining secure authentication.
3Reliability
If token history and ban lists are maintained, then counterfeit device identification is improved, but data storage requirements increase
Solution Approach 1:
The patent applies local quality by maintaining different types of data with different storage characteristics. Token histories store authentication records with specific formats optimized for verification, while ban lists maintain compact lists of counterfeit device identifiers. This differentiated storage approach improves counterfeit detection accuracy while minimizing overall data storage requirements compared to uniform storage solutions.
Data Source
AI summary
An online service may use a computing system to authenticate a remote accessory device by establishing an encrypted communication channel with the remote accessory device, the remote accessory device being connected to a host device. Then, using the encrypted communication channel, obtain a device certificate possessed by the remote accessory device. The online service may then receive a first device token from the remote accessory device and determine whether the first device token exists within a token history associated with the device certificate. Based on the first device token existing within the token history, the online service may then determine that the remote accessory device is an authentic device; generate a second device token for the remote accessory device; store the second device token in the token history associated with the device certificate; and send the second device token to the remote accessory device.