Software Licensing Enforcement via Two-Phase HUID Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing software licensing schemes for electronic devices face challenges such as high costs and delays during production due to the need for hardware unique IDs (HUIDs), and errors can occur when generating licenses for multiple devices, especially when devices are not connected to a server.
Innovation Solution
A two-phase software licensing process where a default software license is embedded during production without requiring a HUID, and a renewal phase where a single license can be generated for multiple devices using collected HUIDs, with encryption and signature verification for security, allowing devices to operate for a predetermined duration before renewal.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a hardware unique ID (HUID) is used to enforce software licensing during production, then licensing security is improved, but manufacturing cost and time increase
Solution Approach 1:
The licensing process is segmented into two distinct phases: a production phase using a default license without HUID verification for rapid manufacturing, and a post-deployment phase where HUID-based license renewal occurs. This segmentation allows the system to achieve both fast production and secure licensing by separating these conflicting requirements into different time periods and operational contexts.
2Manufacturing precision
If a hardware unique ID (HUID) is used to generate licenses for each device, then licensing accuracy is improved, but human error increases due to manual processing of multiple devices
Solution Approach 1:
The system enables self-service licensing where devices automatically perform HUID verification and license renewal operations without requiring manual human intervention. The electronic device itself participates in the license validation process by providing its HUID and verifying the license signature, eliminating the need for operators to manually match HUIDs with license files and reducing human error.
3Reliability
If real-time clock (RTC) and network connectivity are required for license validation, then licensing reliability is improved, but device complexity and operational constraints increase
Solution Approach 1:
The license file is prepared in advance with all necessary validation information embedded within it, including the license signature and expiration date. This preliminary action allows the device to perform complete license validation using only the current date comparison, eliminating the need for real-time clock synchronization or network connectivity during validation operations.
Data Source
AI summary
This disclosure describes a software licensing process that can be divided into two phases: 1) during production of electronic devices and 2) a renewal phase during operations after the electronic devices are deployed. In the first phase, a default software license goes out along with the firmware when the electronic devices are manufactured. The default software license does not need a hardware unique ID (HUID) and can be part of the firmware file, which makes it easy for manufacturing personnel. The second phase is the renewal phase. Before or after expiration of the software license, a customer can collect and send the HUIDs of the electronic devices to the licensor, e.g., manufacturer, and the licensor can generate a single software license for multiple devices.