Software Usage Auditing via Dynamic Unlock Keys
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current software protection systems are inflexible, failing to differentiate between legitimate and illegitimate software usage, and do not allow users to utilize software on multiple devices as needed, leading to user dissatisfaction and potential piracy.
Innovation Solution
A method for auditing software usage that involves receiving a serial number and device identifier, calculating a copy count, and sending either an unlimited or limited unlock key based on predefined limits, allowing software to run indefinitely or for a specified time period, thereby enabling flexible usage monitoring and control.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a strict copy limit is enforced to prevent piracy, then software protection reliability is improved, but user flexibility and satisfaction deteriorate
Solution Approach 1:
The patent implements dynamic authorization by transitioning from static copy limits to a system that continuously monitors software execution and adapts authorization levels. The authorization authority dynamically adjusts whether to grant or deny authorization based on real-time analysis of usage patterns, allowing the system to be strict when detecting piracy and flexible when confirming legitimate use.
Solution Approach 2:
The system incorporates feedback mechanisms where the authorization authority receives information about software execution and user behavior, then uses this feedback to make informed authorization decisions. This feedback loop enables the system to learn from usage patterns and adjust authorization policies accordingly, balancing protection reliability with user flexibility.
2Ease of operation
If authorization is granted on all devices to improve user convenience, then ease of operation is improved, but software piracy and unauthorized copying increase
Solution Approach 1:
The authorization system continuously receives feedback about software execution and user behavior patterns. By analyzing this feedback data, the system can distinguish between legitimate multi-device usage and piracy activities, granting authorization conveniently for legitimate users while blocking unauthorized copying.
Solution Approach 2:
The patent replaces traditional mechanical copy-protection mechanisms (such as copy-count limits and device-binding) with an intelligent authorization system that uses data analysis and pattern recognition. This substitution allows the system to make nuanced decisions about authorization based on behavioral patterns rather than rigid rules.
3Measurement precision
If copy monitoring is implemented to detect piracy, then measurement precision is improved, but system complexity increases
Solution Approach 1:
The authorization authority serves multiple functions: it authorizes software execution, monitors usage patterns, detects piracy attempts, and adjusts authorization policies. By consolidating these functions into a single universal system, the patent reduces overall complexity compared to having separate systems for each function.
Solution Approach 2:
The system performs self-monitoring and self-adjustment by automatically analyzing usage patterns and making authorization decisions without requiring manual intervention. This self-service capability reduces operational complexity while maintaining high measurement precision for detecting piracy.
Data Source
AI summary
Systems and methods are provided for auditing and selectively restricting software usage based on, for example, software copy counts or execution counts. In one embodiment, the method comprises verifying whether the serial number for a software installed on a computing device corresponds to one of recognized serial numbers, and calculating a copy count (or software execution count) for the serial number. In response to the copy count exceeding a defined upper limit, a limited unlock key may be sent to the device. The limited unlock key may allow the software to be executed on the device for a defined time period, a defined number of executions, and/or with at least one feature of the software disabled.