Server-Side Hardware License Validation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Software manufacturers face revenue loss due to users installing discounted licenses on hardware not authorized for them, as the licensing entity lacks information about the hardware during activation.

Innovation Solution

Implementing server-side validation of hardware-specific software product licenses by collecting and categorizing computing device information, using hashes to protect personally identifiable data, and assigning licenses based on hardware components, ensuring only authorized hardware can utilize the software.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If discounted licenses are offered to users, then software accessibility and user adoption are improved, but revenue loss occurs when users install discounted licenses on unauthorized hardware

Engineering Contradiction:

Improvesoftware accessibilityVSAvoidrevenue loss

Core Design Contradiction:

Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The system performs preliminary hardware identification and categorization during license activation before the software is fully installed. The licensing entity collects hardware-specific information, categorizes the hardware, and validates whether the hardware is authorized for the discounted license before allowing installation to proceed. This prevents revenue loss by blocking unauthorized installations before they complete.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system establishes a feedback loop where hardware information is continuously monitored and validated against license terms. During activation, the licensing entity receives hardware identifiers, compares them against authorized hardware categories, and provides immediate feedback by either approving or denying license activation. This real-time validation ensures discounted licenses are only activated on authorized hardware.

Inventive Principle:

Principle #23Feedback

2Loss of energy

If hardware-specific validation is implemented, then revenue protection is improved, but system complexity increases due to additional validation requirements

Engineering Contradiction:

Improverevenue protectionVSAvoidsystem complexity

Core Design Contradiction:

Loss of energyVSDevice complexity

Solution Approach 1:

The patent introduces a licensing entity as an intermediary between the software manufacturer and the user's hardware. This intermediary collects hardware identifiers, categorizes the hardware against predefined categories, and validates license eligibility. By centralizing the validation logic in this intermediary layer, the complexity is isolated from both the manufacturer's core system and the user's installation process, making the system easier to manage and update.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The validation system is segmented into distinct functional components: hardware identifier collection, hardware categorization based on predefined categories, license eligibility validation, and activation decision-making. This segmentation allows each component to be independently developed, maintained, and updated, reducing overall system complexity while maintaining comprehensive validation capabilities.

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS8676714B2Hardware specific product license validation

Publication Date: 2014.03.18 MICROSOFT TECHNOLOGY LICENSING LLC

AI summary

Server-side validation of hardware specific software product licenses is described herein.