Persistent Enterprise License Generation for Autonomous Software Operation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing software licensing methods for enterprises require continuous communication with the license server, leading to potential license abuse and service denial during network outages, and lack flexibility in managing licensing parameters across different levels.
Innovation Solution
Implementing customer-configurable enterprise-wide licensing techniques that allow for the generation of persistent licenses, enabling features and capacities to be allocated and managed independently within the enterprise network, with hierarchical relationships between system and enterprise records, and using PKI certificates for security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If continuous communication with the license server is required, then license control and security are improved, but service availability and autonomy deteriorate during network outages
Solution Approach 1:
The system performs preliminary actions by generating and distributing persistent licenses to software instances before network outages occur. These licenses contain all necessary authorization information locally, enabling software instances to continue operating autonomously without real-time server communication, thus maintaining service availability while preserving license control.
Solution Approach 2:
The patent implements local quality by enabling each software instance to possess its own persistent license with embedded authorization data. This localizes the license verification capability within each instance, eliminating the need for continuous centralized verification and ensuring operation independence during network disruptions while maintaining security through cryptographic verification.
2Productivity
If persistent licenses are generated for autonomous operation, then service continuity is improved during outages, but risk of license abuse increases
Solution Approach 1:
The system creates secure copies of license authorization data within each software instance through persistent licenses. These copies contain cryptographic signatures and unique identifiers that replicate the server's authorization capability locally, enabling autonomous verification while preventing abuse through unforgeable digital signatures and instance-specific binding.
Solution Approach 2:
The patent implements disposable license mechanisms where persistent licenses can be invalidated and replaced without requiring complex revocation infrastructure. Each license is tied to specific software instances and can be rendered obsolete through license renewal cycles or server-side invalidation, providing security against abuse while maintaining service continuity during operational periods.
3Adaptability or versatility
If hierarchical licensing management is implemented, then flexibility in managing licensing parameters is improved, but system complexity increases
Solution Approach 1:
The patent segments licensing management into hierarchical levels (enterprise-level and instance-level parameters), allowing different aspects of license control to be managed independently. Enterprise-level parameters govern overall capacity and allocation, while instance-level parameters control specific software instance authorization, reducing complexity through clear separation of concerns while providing comprehensive flexibility.
Solution Approach 2:
The system adds a hierarchical dimension to license management, organizing licensing parameters across multiple levels (enterprise, pool, instance) rather than a single flat structure. This dimensional organization enables flexible control at each level while the hierarchical relationships automatically manage complexity through structured delegation and aggregation of authorization rights.
Data Source
AI summary
An enterprise licensing system is provided that includes a licensing agent 172 operable to (a) provide a customer with a first set of enterprise licensable features and/or capacities and a second set of non-enterprise licensable features and/or capacities, with the enterprise licensable features and/or capacities, but not non-enterprise licensable features and/or capacities, being allocable freely by the customer among first and second computational components; (b) receive a first allocation of the members of the first set between the first and second computational components; and (c) generate first and second licenses reflecting the first allocation. The first license is for the first computational component and the second license is for the second computational component.