Developer Profile-Based License Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing software licensing models often require manual management of license information for each application, leading to inefficiencies and inconsistencies in determining and presenting application states, especially across multiple applications developed by the same entity.

Innovation Solution

Accessing licensing information based on a developer profile allows for centralized management and sharing of license information across applications, enabling consistent presentation and mode determination based on the license state, using a keychain utility to store and retrieve this information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual management of license information is performed for each application, then individual application licensing control is achieved, but management complexity and administrative burden increase

Engineering Contradiction:
Improvelicensing controlVSAvoidmanagement complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges license information management across multiple applications by associating license data with developer profiles. Instead of managing separate license information for each application, the system combines them under a unified developer profile structure, allowing centralized access and consistent licensing control across all applications developed by the same entity.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The developer profile serves as a universal container that can hold license information for multiple different applications. This multi-functional structure allows the same profile to manage licensing across diverse applications, reducing the need for application-specific license management mechanisms.

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

2Adaptability or versatility

If separate license information is stored for each application, then application-specific licensing is maintained, but consistency across applications deteriorates

Engineering Contradiction:
Improveapplication-specific licensingVSAvoidlicensing consistency
Core Design Contradiction:
Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The system merges previously separate license information structures into a unified developer profile. This consolidation ensures that all applications associated with the same developer profile access consistent license information, eliminating inconsistencies while preserving application-specific licensing capabilities through the profile association mechanism.

Inventive Principle:
Principle #5Merging (Combining)

3Productivity

If centralized license information access is implemented, then administrative burden is reduced, but system complexity increases

Engineering Contradiction:
Improvemanagement efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system introduces a keychain utility as an intermediary component that mediates between applications and license information storage. This intermediary handles the complexity of centralized license management automatically, allowing applications to access license information through simple keychain operations without directly managing the complexity of centralized access control.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Ease of operation

If license information is accessed through individual application processes, then application autonomy is maintained, but information sharing efficiency decreases

Engineering Contradiction:
Improveapplication autonomyVSAvoidinformation retrieval time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The keychain utility serves as an intermediary that enables efficient information sharing while preserving application autonomy. Applications can independently access license information through the keychain without direct inter-application communication, maintaining autonomy while benefiting from centralized information availability and reduced retrieval time.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9563752B2License information access based on developer profiles
Publication Date: 2017.02.07 MICROSOFT TECHNOLOGY LICENSING LLC
  • US9563752B2 patent drawing
  • US9563752B2 patent drawing
  • US9563752B2 patent drawing

AI summary

Disclosed herein are systems, methods, and software for facilitating application licensing. In at least one implementation, license information for an application is identified based at least in part on a developer profile associated with the application and a state of a license for the application identified from at least a portion of the license information. Presentation of the application in accordance with the state of the license for the application can then be initiated.