Virtualized Host ID Key Sharing for License Continuity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In virtual environments, software license authentication becomes problematic due to changing host IDs during virtual machine upgrades, leading to software inoperability and significant administrative burdens, as existing systems rely on consistent MAC addresses and physical device access which are not applicable to virtual machines.

Innovation Solution

A method is introduced to share host access keys between virtual machines, allowing a pre-upgraded VM to authorize a post-upgraded VM, and enabling a primary license server to authorize a redundant server using a handshake mechanism to ensure continuous access to resources by copying and verifying host keys and licenses.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a virtual machine is upgraded, then the system performance and capabilities are improved, but the host ID changes causing license verification to fail

Engineering Contradiction:
Improvesoftware operabilityVSAvoidhost ID consistency
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system separates the host ID into two components: a stable virtual machine identifier (stored in the license file) and a dynamic hardware identifier. This segmentation allows the license verification to rely on the stable component while permitting hardware changes during upgrades.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The license file is generated in advance with the virtual machine's identifier before any upgrades occur. This preliminary licensing establishes a persistent authorization that survives subsequent host ID changes, eliminating the need for re-licensing after upgrades.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If MAC address authentication is used, then physical device security is improved, but virtual machine licensing becomes problematic due to hardware changes

Engineering Contradiction:
Improveauthentication securityVSAvoidvirtual environment compatibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces a virtual machine identifier as an intermediary between the physical hardware and the licensing system. This intermediary decouples the authentication mechanism from physical hardware characteristics, allowing secure licensing in virtualized environments where MAC addresses and hardware configurations may change.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Measurement precision

If license files are maintained with current host IDs, then authorization accuracy is improved, but administrative burden increases substantially

Engineering Contradiction:
Improvelicense verification accuracyVSAvoidlicense management complexity
Core Design Contradiction:
Measurement precisionVSEase of operation

Solution Approach 1:

The system creates a copy of the virtual machine's identifying information and embeds it in the license file during the licensing process. This copied identifier remains static in the license file even when the actual host ID changes, eliminating the need for manual license updates while maintaining verification accuracy.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS11038860B2Virtualized host ID key sharing
Publication Date: 2021.06.15 EXTREME NETWORKS INC
  • US11038860B2 patent drawing
  • US11038860B2 patent drawing

AI summary

In virtualized environments a method of determining authorization to a resource cannot use a hardware specific identifier, such as a MAC address. As a result upgrading a virtual host may cause licenses associated with that host to be invalid, even though the upgraded virtual host should be authorized. Authentication methods and systems are disclosed such that a key may be shared with a second host along with a license file and, provided at least the second host has a key associated with its system identifier and a key associated with a license file, access to a licensed resource may be authorized.