Hardware-Based Identity Verification for Trusted Device Detection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing identity verification methods, such as biometric and verification code verification, are costly and pose privacy concerns, especially in high-security applications like payment apps, and are vulnerable to hacking, leading to user resistance and potential privacy breaches.
Innovation Solution
An identity verification method that determines whether a terminal device is a commonly used device by comparing its hardware model parameters with device model distribution information, allowing the system to skip verification for trusted devices and perform verification only when necessary to ensure security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If biometric identity verification is used to ensure security, then security is improved, but user privacy concerns increase and verification costs rise
Solution Approach 1:
The verification system is segmented into two independent parts: device identity verification (using hardware parameters) and user identity verification (using biometric or verification code). The server first verifies the device, and only if the device is trusted does it proceed to user verification. This segmentation allows the system to maintain security while reducing privacy concerns by minimizing unnecessary biometric verification.
Solution Approach 2:
The server performs preliminary device verification by comparing hardware parameters before triggering user identity verification. This preliminary action filters out untrusted devices early, preventing unnecessary biometric verification and reducing both privacy concerns and verification costs for legitimate users.
2Reliability
If verification code identity verification is used to ensure security, then security is improved, but verification costs increase due to SMS expenses
Solution Approach 1:
The server performs preliminary device verification by comparing hardware parameters before triggering verification code sending. This preliminary action filters out untrusted devices early, preventing unnecessary SMS verification and reducing verification costs for legitimate users while maintaining security.
Solution Approach 2:
The system applies verification selectively rather than universally. Only untrusted devices or high-risk operations trigger verification code sending, while trusted devices enjoy streamlined verification. This partial action approach reduces overall verification costs while maintaining adequate security.
3Reliability
If frequent identity verification is performed to ensure security, then security is improved, but user convenience deteriorates and verification frequency increases
Solution Approach 1:
The verification process is segmented into device verification and user verification stages. Device verification using hardware parameters is performed first and can be cached for multiple subsequent operations. This segmentation reduces the frequency of full identity verification, improving user convenience while maintaining security through the initial device trust assessment.
4Measurement precision
If device model distribution information is collected and analyzed, then verification accuracy is improved, but system complexity increases
Solution Approach 1:
The server performs multiple functions using the collected device model distribution information: it identifies commonly used devices, detects abnormal devices, and makes verification decisions. This multi-functionality justifies the data collection and processing complexity by providing comprehensive security and verification optimization.
Data Source
Figure 1~2
Figure 3~4
Figure 5
AI summary
This specification provides an identity verification method and device, and a storage medium. In the method, in response to an identity verification request sent by a terminal device, a verification device obtains a target account of an application corresponding to the identity verification request, a first hardware parameter of the terminal device, and a second hardware parameter corresponding to the target account; and obtains a distribution status of each device model in a device that uses the application; and then the verification device can determine, based on the obtained parameter and distribution status, whether the terminal device is a commonly used device corresponding to the target account; and then indicate, based on a determining result, the terminal device to or not to initiate an identity verification procedure for a user.