License Dependency Rule System for Auxiliary Software Activation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional license managers and product activation procedures are inadequate in supporting auxiliary software applications and components, leading to increased complexity and cost in software delivery, as they do not provide independent licensing and activation mechanisms for these components.
Innovation Solution
Implementing a license dependency rule system that evaluates the installation and activation status of primary software applications to enable the use of auxiliary software applications, allowing for flexible specification of required primary applications and reducing the need for separate licensing of auxiliary components.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If each auxiliary software component is given an independent serial number or product key and subjected to the same activation procedure as primary software products, then each auxiliary component can be independently licensed and controlled, but the overall complexity of the licensing and software activation process increases
Solution Approach 1:
The patent merges the licensing control of auxiliary software components with the primary software application by using a shared license module. Instead of treating each auxiliary component as a separate licensable entity, the system combines them under the umbrella of the primary application's license, thereby maintaining licensing control while reducing process complexity
Solution Approach 2:
The shared license module serves multiple functions: it manages licensing for the primary software application and simultaneously handles licensing verification for multiple auxiliary software components. This multi-functionality eliminates the need for separate licensing procedures for each component, reducing overall complexity while maintaining control
2Ease of operation
If conventional license managers are used that are designed to operate only with certain primary software applications, then the licensing process is straightforward for primary applications, but auxiliary software applications or components are not supported
Solution Approach 1:
The license manager is enhanced to serve multiple purposes: it continues to manage licensing for primary software applications while simultaneously providing support for auxiliary software applications and components. This universal approach allows a single license manager to handle diverse software types without requiring separate licensing systems
Solution Approach 2:
The shared license module acts as an intermediary between the primary software application and auxiliary components. It mediates the licensing relationship by verifying the primary application's license status and using that verification to control access to auxiliary components, thereby enabling support for auxiliary software without complicating the primary licensing process
Data Source
AI summary
Methods and systems for enabling a software application that does not have independent licensing information are described. Consistent with some embodiments, a first software application is associated with a license dependency rule that indicates one or more other software applications that must be installed and activated in order for the first software application to be fully executed and used on the target computer system. A license manager module evaluates the license dependency rule, for example, by making remote license calls to verify the license status of the software applications identified in the license dependency rule.