Hierarchical License Tree for Software Resource Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional software licensing methods fail to account for overlaps in software resources, leading to inefficient management and potential unauthorized use of software, as they require separate access codes for each software component without considering existing licenses or overlaps.
Innovation Solution
A hierarchical license tree system is implemented, where each node represents a software resource, and the software resource manager maintains license information to determine valid installations based on parent and child node licenses, allowing or restricting access and execution accordingly.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional licensing methods are used with separate access codes for each software component, then each software can be independently licensed and controlled, but the management complexity increases and overlaps are not accounted for
Solution Approach 1:
The patent combines multiple software license management operations into a unified hierarchical license tree structure. Instead of managing separate access codes for each software component independently, the system merges them into a tree where parent nodes represent software bundles or suites and child nodes represent individual components. This consolidation reduces management complexity while maintaining reliable control over software usage and overlaps.
Solution Approach 2:
The hierarchical license tree structure serves multiple functions simultaneously: it tracks licensing status, manages software overlaps, enables bulk licensing for suites, and provides a unified interface for license verification. This multi-functional approach eliminates the need for separate management systems for different software components, reducing overall complexity while maintaining comprehensive control.
2Reliability
If separate access codes are required for each software component, then precise control over each component is achieved, but the need for multiple codes increases operational difficulty
Solution Approach 1:
The patent introduces a hierarchical dimension to license management by organizing access codes into a tree structure with parent and child nodes. Instead of requiring users to manage multiple independent codes at the same level, the system creates a hierarchical relationship where a parent license code can grant access to multiple child software components. This dimensional change simplifies user operations while maintaining precise control over each component's access rights.
3Ease of manufacture
If conventional licensing does not account for software overlaps, then independent licensing is simpler, but unauthorized use of unlicensed software may occur
Solution Approach 1:
The hierarchical license tree system incorporates feedback mechanisms that automatically detect and resolve software licensing overlaps. When software is installed or accessed, the system queries the license tree to verify authorization status, providing real-time feedback on whether the software is properly licensed. This feedback loop prevents unauthorized use of unlicensed software while maintaining a relatively simple licensing structure through the hierarchical organization.
Solution Approach 2:
The patent implements preliminary verification of license authorization before allowing software installation or execution. By querying the hierarchical license tree in advance and confirming valid authorization paths from root to leaf nodes, the system prevents unauthorized use before it occurs. This preliminary action ensures security while maintaining simplicity through the pre-organized hierarchical structure that makes verification efficient.
Data Source
AI summary
According to example configurations as described herein, use of software can be contingent upon whether a hierarchical license tree has a valid license for a software resource associated with a respective node in the tree. For example, an installer can be configured to traverse the hierarchical license tree to identify which, if any, of the software resources as represented by nodes in the tree has a valid license and therefore can be installed for execution on a respective computer system. If a valid license exists for a given node in the tree, the software resource associated with the given node as well as software resources associated with child nodes of the given node can be installed for use on the computer. A software resource manager can be configured to prevent installation, execution, etc., of software resources for nodes above the respective parent node that do not have a corresponding valid license.