Dynamic Authorization Process Selection for Software Licensing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Software licensing mechanisms face challenges in balancing security and user convenience, particularly in dynamic user behavior patterns where users access software from various locations and platforms, often requiring a trade-off between enforcement and convenience.

Innovation Solution

A system that dynamically selects a preferred authorization process based on conditions such as the environment and installation progress, allowing for flexible licensing enforcement by choosing between keyless and key-based authorization processes to ensure seamless user access while protecting software providers' interests.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a key-based authorization process is used to ensure security, then protection against unauthorized use is improved, but user convenience and access speed deteriorate

Engineering Contradiction:
Improveprotection against unauthorized useVSAvoiduser convenience
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system dynamically selects between key-based and keyless authorization processes based on runtime conditions such as environment type (roaming vs. local), installation progress, and availability of authorization services. This dynamic adaptation allows the system to provide strong security when needed while offering convenient quick access when appropriate, resolving the contradiction between security and user convenience.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes the authorization mode parameter based on detected conditions. When roaming environment is detected or installation is incomplete, it switches to keyless authorization for convenience. When local environment with complete installation is detected, it switches to key-based authorization for security, thus adapting the security level to the operational context.

Inventive Principle:
Principle #35Parameter changes

2Ease of operation

If a keyless authorization process is used to improve user convenience, then access speed and ease of use are improved, but security protection deteriorates

Engineering Contradiction:
Improveaccess speedVSAvoidsecurity protection
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system dynamically adjusts the authorization process based on environmental conditions. Keyless authorization is selectively applied only in roaming environments or during installation, while key-based authorization is used in local environments with complete installations, thus maintaining security where needed while enabling convenience where appropriate.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The authorization mode parameter is changed based on detected conditions such as roaming status and installation progress. The system transitions between keyless and key-based modes to balance security and convenience according to the operational context, applying keyless only when security risks are minimized.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If complex key management paradigms are implemented to enhance security, then protection against unauthorized use is improved, but system complexity increases

Engineering Contradiction:
Improveprotection against unauthorized useVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The authorization system is segmented into multiple independent processes (key-based and keyless) that can be selected based on conditions. This segmentation allows the system to use complex key management only when necessary, while relying on simpler keyless processes in other scenarios, thus reducing overall system complexity while maintaining security where needed.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The authorization system is designed to perform multiple functions through a single unified framework that supports both key-based and keyless processes. This multi-functionality allows the system to adapt to different security requirements without requiring separate dedicated systems, thereby managing complexity while providing robust protection.

Inventive Principle:
Principle #6Universality (Multi-functionality)

4Adaptability or versatility

If licensing mechanisms are made flexible to accommodate changing user behavior patterns, then user convenience is improved, but security protection deteriorates

Engineering Contradiction:
ImproveflexibilityVSAvoidsecurity protection
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The licensing mechanism dynamically adapts its authorization process based on detected environmental conditions such as roaming status, installation progress, and service availability. This dynamic behavior provides flexibility to accommodate various user scenarios while maintaining security through conditional application of key-based processes in appropriate contexts.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes authorization parameters based on operational context. When flexibility is needed (roaming, installation in progress), it switches to keyless mode. When security is prioritized (local environment, complete installation), it switches to key-based mode, thus achieving both flexibility and security through parameter adaptation.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentEP2807596B1Dynamic selection of authorization processes
Publication Date: 2017.12.20 MICROSOFT TECHNOLOGY LICENSING LLC
  • EP2807596B1 patent drawingFigure 1~2
  • EP2807596B1 patent drawingFigure 3
  • EP2807596B1 patent drawingFigure 4~5

AI summary

Systems, methods, and software are disclosed herein for licensing applications using a preferred authorization process dynamically identified based on conditions associated with an initiation of an application. Authorization is then attempted using the preferred authorization process. In some examples, the preferred authorization process is selected from at least a keyless authorization process and a key-based authorization process.