Virtual Machine Migration With Network Mapping Across Platforms

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Migrating virtual machines between independent distributed computing platforms is challenging due to the need for additional account setup, authentication, and network configuration, which disrupts seamless network connectivity.

Innovation Solution

A distributed computing system with migration agents on each hypervisor that coordinate the migration of virtual machines across platforms, maintaining virtual network parameters and updating physical network associations to ensure seamless connectivity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If virtual machines are migrated between independent distributed computing platforms, then platform flexibility and resource utilization are improved, but network connectivity and system complexity worsen

Engineering Contradiction:
Improveplatform flexibilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a network virtualization layer that acts as an intermediary between virtual machines and physical networks. This layer maintains network parameter mappings and translates communication protocols, enabling seamless migration across independent platforms without requiring complex reconfiguration of network connections or authentication protocols.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The network virtualization layer provides universal network management capabilities that work across different distributed computing platforms. By implementing a standardized interface for network parameter management and translation, the system achieves platform-agnostic virtual machine migration while maintaining network connectivity, reducing the need for platform-specific configuration.

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

2Productivity

If virtual machines are migrated between independent distributed computing platforms, then resource scalability is improved, but network configuration complexity worsens

Engineering Contradiction:
Improveresource scalabilityVSAvoidnetwork configuration complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The network virtualization layer serves as a mediator that abstracts network configuration details from virtual machines. It maintains mappings between virtual network parameters and physical network parameters, automatically translating communication protocols during migration. This eliminates the need for manual network reconfiguration when virtual machines move between independent platforms, enabling seamless scalability.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If virtual machines are migrated between independent distributed computing platforms, then fault tolerance is improved, but authentication complexity worsens

Engineering Contradiction:
Improvefault toleranceVSAvoidauthentication complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The network virtualization layer implements a universal authentication mechanism that works across independent distributed computing platforms. By establishing standardized authentication protocols at the virtualization layer, the system enables seamless migration while maintaining security, eliminating the need for platform-specific authentication configurations and reducing overall authentication complexity.

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

Data Source

PatentUS12632279B2Cross-platform virtual machine migration
Publication Date: 2026.05.19 MICROSOFT TECHNOLOGY LICENSING LLC
  • US12632279B2 patent drawing
  • US12632279B2 patent drawing
  • US12632279B2 patent drawing

AI summary

A distributed computing system including a migration domain having migration agents and virtual machines running on hypervisors, where the hypervisors span multiple independent distributed computing platforms. The migration domain is configured to (1) receive a request to migrate a virtual machine from a source hypervisor to a target hypervisor on a separate, independent distributed computing platform; (2) receive, once the virtual machine is active at the target hypervisor, virtual network parameters that were used by the virtual machine, pre-migration, to connect with a virtual network; and (3) communicate an updated virtual/physical association of the virtual network parameters to one or more other migration agents, enabling the migrated virtual machine to continue connectivity to the virtual network with the same virtual network parameters used at the source hypervisor.