Component-Agnostic Licensing Entitlement Service
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The complexity and resource-intensiveness of managing software entitlements across multi-cloud systems, where each new software component type requires customized coding, testing, and integration, leading to increased maintenance efforts.
Innovation Solution
A method and system where an entitlement service on a cloud platform uses a plug-in to store and manage software component data, allowing it to support various component types and feature sets without custom coding, through an entitlement specification service that queries a feature-set plug-in to generate entitlement specifications for enabling feature sets.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the entitlement service handles more component types with customized coding, then the entitlement management capability is improved, but the device complexity and maintenance burden increase
Solution Approach 1:
The patent implements a universal entitlement service that can handle multiple software component types through a common architecture. Instead of creating separate customized services for each component type, the system uses a single entitlement service that dynamically adapts to different component types using configuration data and plug-ins, thereby maintaining versatility while avoiding the complexity of multiple specialized services
Solution Approach 2:
The patent changes the approach from code customization to configuration-based adaptation. By storing component-type-specific information (offerings, feature sets, entitlement rules) as configurable parameters in a database rather than hardcoding them, the system can adapt to new component types by simply adding configuration data without modifying the core service logic, thus reducing service complexity while maintaining adaptability
2Manufacturing precision
If the entitlement service is customized for each new component type, then the entitlement accuracy is improved, but the loss of time and resources for maintenance increases
Solution Approach 1:
The patent performs preliminary configuration by storing all component-type-specific entitlement information (offerings, feature sets, pricing, rules) in a database before runtime. When a new component type needs to be supported, the configuration data is prepared in advance and loaded into the system, allowing the entitlement service to immediately handle the new component type with accurate entitlement calculation without requiring time-consuming customization and testing at deployment
Solution Approach 2:
The patent uses template-based configuration where common entitlement logic and structure are copied across different component types. Instead of creating unique customized code for each component type, the system copies and adapts configuration templates, allowing rapid onboarding of new component types with consistent entitlement accuracy while minimizing maintenance overhead through standardized configurations
Data Source
AI summary
An example method of configuring an entitlement service that manages entitlement of software in a virtualized computing system includes: receiving, at a plug-in of the entitlement service, software component data that specifies a component type and offerings of the component type, the offerings associated with feature sets, the entitlement service executing on a cloud platform in the virtualized computing system; storing, by the plug-in, the software component data in a database; and notifying, by the plug-in, the entitlement service to support entitlement of components of the software having the component type.