License Management for Resident Applications
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing license management systems, particularly the floating license system, face issues when applied to resident-type applications, as licenses are consumed even if the application's functions are not in use, leading to depletion and preventing other users from accessing the application. Additionally, these systems degrade UI display response by constantly confirming license availability.
Innovation Solution
A client apparatus with determination units to differentiate between node-locked and floating license systems, initializing the user interface accordingly to enable or disable license-required functions based on license availability, optimizing UI display and preventing unnecessary license consumption.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a floating license system is applied to a resident-type application, then the application can be activated, but licenses are consumed even when functions are not in use, leading to license depletion
Solution Approach 1:
The patent implements dynamic license management by distinguishing between resident mode and execution mode. In resident mode, the application does not consume licenses, but in execution mode when functions are actually used, licenses are acquired dynamically. This dynamic switching resolves the contradiction by making license consumption contingent on actual function usage rather than continuous occupation.
Solution Approach 2:
The patent changes the license acquisition parameter based on the operational state of the application. When the application is merely activated (resident mode), no license is acquired. When functions are actually executed (execution mode), license acquisition is triggered. This parameter change approach allows the same application to behave differently regarding license consumption based on its operational state.
2Reliability
If license confirmation is executed every time the operation menu is displayed, then license availability is accurately verified, but UI display response is degraded
Solution Approach 1:
The patent performs preliminary license acquisition in execution mode before functions are actually executed. By acquiring the license in advance when the execution mode is entered, the system ensures license availability is verified without repeatedly checking during subsequent UI operations. This preliminary action maintains reliability while avoiding continuous verification overhead.
Solution Approach 2:
The patent extracts the license confirmation process from the UI display flow. Instead of confirming licenses every time the menu is displayed, the license confirmation is separated into a distinct execution mode entry point. This extraction allows UI operations to proceed without repeated license checks, maintaining response speed while ensuring license verification occurs at appropriate moments.
3Reliability
If a node-locked license system is applied to an application with restricted functions, then license validity is confirmed at activation, but UI functions are displayed in disabled state reducing user experience
Solution Approach 1:
The patent implements dynamic UI state management based on license acquisition status. When in execution mode and a license is successfully acquired, previously disabled functions become enabled in the UI. This dynamic adjustment allows the interface to transition from a restricted state at activation to a fully functional state when licensing is confirmed, improving user experience while maintaining validation reliability.
Data Source
AI summary
A client apparatus determines whether a license system of an application is a node-locked system or a floating system when the application is activated. The client apparatus further determines whether a node-locked license is acquired if it is determined that the license system of the application is the node-locked system. The client apparatus initializes a user interface to display a license-required function in an enabled state if the node-locked license of the node-locked system is acquired or the license system is the floating system. The client apparatus initializes a user interface to display the license-required function in a disabled state if the node-locked license of the node-locked system is not acquired.