Software License Roaming via User ID Linking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing software licensing systems often restrict software use to a single machine, requiring manual entry of product keys on multiple machines and lacking efficient mechanisms for managing and tracking license rights across devices.
Innovation Solution
Implementing a licensing system that allows roaming of application and feature licenses linked to a user identification, enabling seamless use across multiple machines while tracking and managing license rights to prevent abuse and piracy.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If license rights are restricted to a single computing machine, then software security and piracy prevention are improved, but user convenience and accessibility across multiple devices deteriorate
Solution Approach 1:
The license system is segmented into master license entries stored on the user's account and individual machine-specific license instances. The master license entry contains the user's purchasing information and authorizes multiple machines, while each machine receives a specific license instance that references the master entry. This segmentation allows security to be maintained through centralized control while enabling multi-machine access.
Solution Approach 2:
A licensing server acts as an intermediary between the user's account and multiple computing machines. The server receives requests from machines, verifies them against the user's master license entry, and distributes appropriate license instances. This intermediary enables secure multi-machine licensing by centralizing authorization control while allowing distributed access.
2Reliability
If manual product key entry is required on each machine, then license control and piracy prevention are improved, but time consumption and operational complexity increase
Solution Approach 1:
The system enables self-service licensing where the user's account automatically manages license distribution across their machines. When a user installs software on a new machine and logs in with their credentials, the system automatically retrieves the appropriate license from their account and activates it on the new machine without requiring manual product key entry. This maintains license control through automated verification while eliminating manual entry time.
Solution Approach 2:
License information is preliminarily stored and associated with the user's account during the initial purchase. The master license entry is created in advance and stored on the licensing server. When the user later installs software on multiple machines, the license is already prepared and can be automatically retrieved and activated, eliminating the need for repeated manual entry of product keys.
3Adaptability or versatility
If feature licenses are added to existing applications, then software functionality and user value are improved, but license management complexity increases
Solution Approach 1:
Feature licenses are merged with the existing master license entry structure. Instead of creating separate independent license systems for features, the patent integrates feature licenses into the same master license entry that controls the base application. The master license entry can contain multiple feature license instances, each with its own machine-specific authorization. This merging approach enables enhanced functionality while maintaining a unified, manageable license structure rather than proliferating separate license systems.
Data Source
AI summary
A master license entry that links a software application to a user identification can be made. Application licenses to use the software application can be roamed to multiple computing machines. Feature licenses for added features of the software application can be roamed to those computing machines as well. Multiple overlapping license rights for the software application may be linked to the master license entry. A count of how many license rights for the software application are linked to the master license entry can be maintained. Requests for licenses may be refused if the count of license rights has reached zero.