Computing Device Accessory Authentication via Token History

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The increasing prevalence of counterfeit computing device accessories poses challenges 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 registering authentic devices and banning counterfeit ones without relying solely on security chips.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If security chips are used for authentication, then authentication capability is provided, but the system becomes vulnerable to counterfeit devices when chip information is compromised

Engineering Contradiction:
Improveauthentication reliabilityVSAvoidcounterfeit device vulnerability
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

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 stored on the server, thereby resolving the vulnerability where compromised chip information allows counterfeit devices to pass authentication.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If remote server-based authentication is implemented, then authentication reliability is enhanced, but device complexity increases

Engineering Contradiction:
Improveauthentication reliabilityVSAvoidauthentication system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The authentication system is segmented into distinct functional components: device certificates stored on the server, token generation mechanisms, token history tracking, and ban list management. This segmentation allows each component to perform its specific function independently, making the overall complex system more manageable and maintainable while enhancing authentication reliability through distributed verification.

Inventive Principle:
Principle #1Segmentation

3Device complexity

If security chips are relied upon exclusively, then device simplicity is maintained, but counterfeit devices can mimic authentic devices

Engineering Contradiction:
Improvedevice simplicityVSAvoidcounterfeit detection capability
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The system performs preliminary actions by pre-storing legitimate device certificates and token histories on the remote server before authentication occurs. When a device attempts authentication, the server compares presented tokens against the pre-stored token history to detect counterfeit devices. This preliminary preparation enables reliable counterfeit detection without adding complexity to the device itself, as the verification logic resides on the server.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12407512B2Securing a computing device accessory
Publication Date: 2025.09.02 MICROSOFT TECHNOLOGY LICENSING LLC
  • US12407512B2 patent drawing
  • US12407512B2 patent drawing
  • US12407512B2 patent drawing

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.