Module History-Based Software Licensing Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In multi-processor network element systems with automatic software distribution to customer-replaceable cards, existing license mechanisms struggle to enforce usage agreements due to administrative burdens and communication overheads, especially when cards are field-replaceable and compatibility is hard to maintain.
Innovation Solution
A program controller that manages software for customer-replaceable modules by using a stored history of use to enforce licensing agreements, allowing for automatic authorization, upgrading, and inventory management, reducing the need for supplier intervention and enabling different service levels based on module capabilities and reliability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If hardware fingerprinting and centralized license management are used, then software licensing control is improved, but administrative burden and communication overhead increase significantly
Solution Approach 1:
The patent segments the licensing management function by distributing license information storage to individual modules rather than centralizing it. Each module maintains its own license data locally, eliminating the need for continuous communication with a central authority and reducing administrative overhead while maintaining licensing control.
Solution Approach 2:
The patent implements preliminary action by embedding license information directly into the module during manufacturing. This pre-configured license data allows modules to autonomously verify their licensing status without requiring real-time communication or administrative intervention, thus reducing time loss while maintaining control.
2Reliability
If centralized license management is implemented, then licensing enforcement is improved, but device complexity and communication requirements increase
Solution Approach 1:
The patent applies self-service by enabling modules to autonomously verify their own licensing status using locally stored license information. This eliminates the need for complex centralized management systems and inter-component communication infrastructure, reducing device complexity while maintaining effective licensing enforcement.
Solution Approach 2:
The patent extracts the license information from the centralized system and embeds it directly into the module. This extraction removes the dependency on complex communication systems and centralized management infrastructure, simplifying the overall system while preserving licensing enforcement capability.
3Adaptability or versatility
If modules are made field-replaceable, then adaptability and ease of maintenance are improved, but license compatibility and service consistency become difficult to maintain
Solution Approach 1:
The patent uses preliminary action by pre-configuring each module with its specific license information during manufacturing. This ensures that when modules are field-replaced, their licensing status is already determined and stored locally, maintaining service consistency and compatibility without requiring complex verification procedures.
Solution Approach 2:
The patent segments the licensing information by assigning it to individual modules rather than managing it centrally. This allows each module to independently verify its licensing status, ensuring service consistency even when modules are field-replaced, while maintaining the adaptability of the modular system.
Data Source
AI summary
A program controller is arranged to automatically authorize or configure or upgrade a program for a customer replaceable card of a system, the controller being arranged to manage the program automatically, according to a licence agreement, and according to a stored history of use of the hardware module. A supplier can track customer changes and enforce more easily different conditions for authorizing the program on, different modules from different sources, having different levels of capability. There can be less interaction with the supplier to get specific authorizations. The history can be stored on the module. It can be used to ease inventory tracking and generate billing information.