Distributed License Management with Local Caching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing license management systems face challenges in flexibility and operational security, particularly with central licensing, where network load increases due to constant license allocation and re-release, and functionality is restricted if the central license server malfunctions or is unreachable.
Innovation Solution
A distributed license management system where a central entity registers releasable licenses and multiple secondary entities manage and synchronize the allocation and release of licenses, ensuring availability even if the connection to the central entity is limited, with synchronization steps repeated across all secondary entities to maintain accurate records and reduce the need for excessive license storage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a central license server is used to manage licenses dynamically, then license flexibility and network resource utilization are improved, but network load increases due to constant allocation and re-release operations
Solution Approach 1:
The patent applies preliminary action by pre-loading license information from the central server to secondary entities (communication systems) before it is actually needed. The central server sends license data proactively to secondary entities, so when license allocation is needed, the information is already available locally, reducing the need for constant real-time communication and thus reducing network load while maintaining flexibility
Solution Approach 2:
The patent implements local quality by distributing license management functionality from a centralized server to multiple secondary entities (communication systems). Each secondary entity maintains local license information and can make allocation decisions independently based on pre-loaded data, reducing the need for continuous central server communication and thereby reducing overall network load while preserving license flexibility
2Adaptability or versatility
If a central license server is used to manage licenses dynamically, then license flexibility is improved, but operational reliability deteriorates when the server malfunctions or becomes unreachable
Solution Approach 1:
The patent applies segmentation by dividing the centralized license management system into multiple independent secondary entities (communication systems), each capable of autonomous license management. This segmentation ensures that if the central server fails, the distributed secondary entities can continue operating independently with their locally stored license information, thereby maintaining operational reliability while preserving license flexibility
Solution Approach 2:
The patent implements beforehand cushioning by pre-loading and caching license information in secondary entities before central server failure occurs. This preparatory measure creates a buffer that allows the system to continue operating normally even when the central server becomes unavailable, thus protecting against reliability issues while maintaining the flexibility benefits of central化管理
3Loss of time
If licenses are pre-loaded in multiple secondary entities, then reaction time for license allocation is reduced, but the amount of license data that must be stored increases
Solution Approach 1:
The patent applies parameter changes by dynamically adjusting what license information is pre-loaded into secondary entities based on actual usage patterns and system state. Rather than loading all possible license data, the system selectively pre-loads only the relevant subset needed for current operations, thereby reducing storage requirements while maintaining fast reaction times for license allocation
Data Source
Figure 1
Figure 2A~2C
Figure 3A~3C
AI summary
The invention relates to a method for managing licenses. In a first instance (RS), the number of releasable licenses is registered. A second instance (A, B, C) assigns and/or revokes a releasable license registered in the resource to be used (R1A, R1B, R2A, R2B). In a synchronization step, the second instances (A, B, C) repeatedly report the difference between the number of licenses granted for use since a previous synchronization step and the number of licenses released during that time to the first instance (RS). Based on this difference, the number of releasable licenses registered in the first instance (RS) is decreased or increased accordingly. Conversely, the resulting number of releasable licenses is reported from the first instance (RS) to the second instance and registered there as the number of releasable licenses.