Time-Based Software Execution Limiting Mechanism
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing software licensing models either expire after a predefined time, limiting usage permanently or require continuous payment, lacking flexibility in time-based usage restrictions tailored to specific intervals or schedules.
Innovation Solution
A user-immutable time-based limiting mechanism that enables or limits software application execution according to pre-defined rules, allowing execution during specific intervals, disabling functionality or preventing launch during others, and enabling again after a set period, based on time-of-day, day-of-week, or day-of-month criteria, with optional external or hardware-enforced enforcement.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional time-limited software licensing is used, then software usage can be restricted to a predefined time period, but the licensing model lacks flexibility and requires user intervention or complex external enforcement
Solution Approach 1:
The licensing mechanism is segmented into distinct time intervals (first time interval for enabled execution, second time interval for limited execution, third time interval for enabled execution). This segmentation allows the software to provide different levels of access during different periods without requiring complex external enforcement, as each interval has clearly defined rules that are automatically applied by the processor.
Solution Approach 2:
The licensing model transitions from static time-limiting (permanent expiration) to dynamic time-based control where the software execution state changes over time. The processor dynamically evaluates the current time against the defined intervals and automatically adjusts whether to enable or limit execution, eliminating the need for user intervention or complex external systems.
2Ease of operation
If software execution is permanently limited after a predefined time, then licensing control is simple, but user flexibility and accessibility are reduced
Solution Approach 1:
The time intervals and execution rules are predetermined and built into the software licensing mechanism before execution. The processor automatically determines whether to enable or limit software execution based on the current time falling within the first, second, or third time interval, eliminating the need for user intervention or complex external enforcement systems.
3Productivity
If continuous payment licensing is required, then revenue stability is improved, but user accessibility and trial flexibility are reduced
Solution Approach 1:
The licensing model employs periodic action by alternating between enabled execution periods (first and third time intervals) and limited execution periods (second time interval). This creates a rhythmic pattern of full access and restricted access that allows users to trial the software during limited intervals while generating revenue, then provides full access during enabled intervals, offering both revenue stability and user flexibility.
Data Source
AI summary
A method of limiting execution of a software application according to a pre-defined time-based rule comprises: whenever the software application is attempted to be launched, enforcing a pre-defined time-based rule (e.g. that is user-immutable) such that: i. whenever the software application is attempted to be launched during a first time interval, the execution of the software application is enabled; ii. whenever the software application is attempted to be launched during a second time interval immediately following the first time interval, the execution of the software application is limited; and iii. whenever the software application is attempted to be launched during a third time interval immediately following the second time interval, the execution of the software application is enabled.