Cloud Migration Gateway for IP Preservation and Multicast Routing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The migration of software applications to a cloud computing platform is complex due to connectivity and security policy dependencies, particularly when preserving the Internet Protocol (IP) address, and the underlying infrastructure of public cloud platforms struggles with multicast traffic.

Innovation Solution

A system and method that utilizes two gateways, one deployed in the on-premises network and another in the public cloud network, to establish a secure communication path and extend a subnet across both networks, allowing for IP address preservation and seamless communication between on-premises and cloud-hosted software components.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If software components are migrated to a public cloud platform with IP address preservation, then connectivity continuity is improved, but the complexity of migration increases due to security policy updates and multicast traffic handling

Engineering Contradiction:
Improveconnectivity continuityVSAvoidmigration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a gateway as an intermediary component deployed in both on-premises and cloud networks. This gateway handles IP address preservation, security policy translation, and multicast traffic routing between the two networks, thereby maintaining connectivity continuity while managing the complexity of migration through a dedicated mediation layer

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The migration system is divided into distinct segments: on-premises network segment, cloud network segment, and gateway segment. Each segment handles specific functions (local traffic, cloud traffic, and translation/routing respectively), which simplifies the overall migration process by isolating complexity into manageable portions

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If manual updates are performed for each migrated application, then customization can be achieved, but human error increases and automation is reduced

Engineering Contradiction:
Improvecustomization capabilityVSAvoidautomation level
Core Design Contradiction:
Adaptability or versatilityVSExtent of automation

Solution Approach 1:

The gateway is configured with security policies and routing rules that automatically adapt to migrated applications. The system performs self-service functions such as automatic policy translation, IP address mapping, and traffic routing without requiring manual intervention for each application, thereby reducing human error while maintaining customization through configurable gateway parameters

Inventive Principle:
Principle #25Self-service

3Ease of manufacture

If IP addresses are assigned differently to migrated applications, then cloud platform security policies are simplified, but connectivity to on-premises applications is lost

Engineering Contradiction:
Improvecloud platform configuration easeVSAvoidapplication connectivity
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The gateway changes network parameters by translating IP addresses, MAC addresses, and security policies between the on-premises and cloud networks. It maintains the original IP addresses for on-premises applications while assigning appropriate addresses to cloud instances, thereby preserving connectivity without compromising cloud security policy simplicity

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS20250141960A1System and method for non-disruptive migration of software components to a public cloud system
Publication Date: 2025.05.01 AVIATRIX SYSTEMS INC
  • US20250141960A1 patent drawing
  • US20250141960A1 patent drawing
  • US20250141960A1 patent drawing

AI summary

A system supporting transferring content between an on-premises network and a public cloud network includes a first cloud computing platform comprising a first software instance having a first IP address, a subnet configured to extend across on-premises network and a public cloud network, a first gateway associated with the on-premises network, a second gateway associate with the public cloud network, a secure communication path between the first and second gateways. The subnet comprises a shared IP address range between the public cloud network and the on-premises network, and the first IP address of the first software instance is the same as an IP address of the first software instance that resided on the on-premises network.