Software Device Binding via Constellation Identifier
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for binding software to a device often rely on hardware or operating system-specific information, which can raise privacy concerns and are not effective for applications executed in web browsers that lack access to underlying resources, and are prone to security breaches when user authentication information and security questions are stolen.
Innovation Solution
A method that derives a unique identifier from a constellation of device-specific elements accessible without security or privacy concerns, using statistical methods and preprocessing of user data such as facial characteristics, to bind software to a device without requiring access to hardware or operating system resources, replacing traditional HTTP cookie-based machine binding mechanisms.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If hardware identification methods (RFID tags, device serial numbers) are used to bind software to a device, then device binding reliability is improved, but privacy concerns arise and web browser applications cannot access the information
Solution Approach 1:
The patent introduces an intermediary binding identifier that mediates between the software application and the device. Instead of directly accessing hardware identifiers (which causes privacy concerns), the system creates an intermediate binding record stored in the operating system's protected storage. This intermediary contains a binding identifier that links the software to the device without exposing or requiring direct access to hardware serial numbers or RFID tags, thus resolving the privacy concern while maintaining binding reliability.
2Reliability
If hardware-specific binding methods are used, then software binding security is improved, but platform dependency increases and web browser applications cannot access underlying hardware resources
Solution Approach 1:
The patent implements a universal binding mechanism that works across different operating systems and application types. The binding identifier and protected storage approach is platform-agnostic, allowing the same binding methodology to be used whether the software runs as a native application, a web browser application, or on mobile devices. The system accesses device-specific information through standardized operating system interfaces rather than direct hardware access, enabling cross-platform compatibility while maintaining security.
3Ease of operation
If traditional cookie-based binding mechanisms are used, then ease of operation is improved, but security against theft of authentication information deteriorates
Solution Approach 1:
The patent replaces persistent, easily stolen cookies with a more secure binding mechanism. Instead of relying on vulnerable HTTP cookies that can be intercepted and reused, the system creates binding identifiers stored in protected operating system storage areas. These binding identifiers are designed to be difficult to extract and reuse, effectively making them 'disposable' in the sense that if compromised, the binding can be invalidated and regenerated without affecting the core authentication security. This maintains ease of operation while dramatically improving security.
Data Source
Figure 1
Figure 2~3
Figure 4~5
AI summary
A method of binding a software to a device is disclosed. Accordingly, during a setup of the software in the device, a unique identifier is derived from contents stored in the device and the derived unique identifier is encrypted. The derived unique identifier is then stored in a configuration of the software. During a next invocation of the software in the device, a new unique identifier is derived from the contents stored in the device. The newly derived unique identifier is then matched with the stored unique identifier. The execution of the software is terminated if the matching fails.