Mesh Gateway Routing for Secure Cross-Datacenter Communication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing technologies face complexities and costs in establishing secure, efficient cross datacenter communication, particularly in multi-cloud, multi-cluster, and hybrid-cloud environments, due to the need for complex VPN configurations and the risk of subnet overlap without ensuring optimal network routes.

Innovation Solution

Implementing mesh gateways that sniff protocol messages for destination information, determine routing configurations, and use single-hop or multi-hop routes to efficiently connect datacenters, eliminating the need for direct connections and reducing the complexity of VPN setups.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If point-to-point VPN connections are used to connect web-services in different data centers, then secure communication is achieved, but configuration complexity and cost increase significantly

Engineering Contradiction:
Improvesecure communicationVSAvoidconfiguration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system segments the complex mesh of required VPN connections into individual service-level configurations. Each service independently declares its network requirements, and the service mesh infrastructure automatically computes and manages the underlying connection topology, transforming a globally complex configuration problem into locally simple service declarations.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The service mesh infrastructure acts as an intermediary between services and the underlying network infrastructure. It abstracts the complex VPN management away from individual services, providing a higher-level control plane that automatically manages connection establishment, routing, and security policies across the distributed system.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If direct connections between data centers are established for service communication, then communication efficiency improves, but network route optimization becomes complex

Engineering Contradiction:
Improvecommunication efficiencyVSAvoidnetwork route complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system implements dynamic route selection where the service mesh control plane continuously monitors network conditions and automatically adjusts routing decisions. Routes can be optimized based on real-time factors such as network latency, bandwidth availability, and service availability, allowing the system to adapt to changing conditions without manual intervention.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The service mesh incorporates feedback mechanisms where routing decisions are continuously refined based on observed performance metrics. The system collects data on communication patterns, network performance, and service health, using this feedback to automatically optimize route selection and adjust connection strategies for improved efficiency.

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If VPN tunnels are configured between multiple cloud instances, then cross-environment connectivity is achieved, but deployment and management time increase

Engineering Contradiction:
Improvecross-environment connectivityVSAvoiddeployment time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The service mesh performs preliminary actions by pre-configuring connection templates and security policies that can be automatically applied when services are deployed. The infrastructure anticipates connection requirements based on service declarations and pre-establishes the necessary network pathways, eliminating the need for manual VPN configuration at deployment time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system enables self-service deployment where services automatically declare their own network requirements and the service mesh infrastructure automatically satisfies these requirements. Individual services do not need manual configuration for cross-environment connectivity; instead, the system autonomously manages connection establishment based on service-level declarations.

Inventive Principle:
Principle #25Self-service

4Reliability

If manual VPN policy synchronization is performed across multiple locations, then security policies can be enforced, but operational complexity increases

Engineering Contradiction:
Improvesecurity policy enforcementVSAvoidpolicy management ease
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The service mesh implements a universal policy management system where a single source of truth for security policies automatically propagates to all services and environments. The control plane provides multi-functional capabilities including policy authoring, validation, distribution, and enforcement across the entire service mesh, replacing multiple manual synchronization processes with a unified system.

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

Data Source

PatentUS12388742B2Cross datacenter communication using a mesh gateway
Publication Date: 2025.08.12 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US12388742B2 patent drawing
  • US12388742B2 patent drawing
  • US12388742B2 patent drawing

AI summary

A method for cross datacenter service-to-service communication over a shortest network route using mesh gateways. A mesh gateway receives a protocol message from a first service directed to a second service, identifies destination information associated with the second service, recognizes a routing configuration for routing the protocol message, determines a network route based on the routing configuration, and forwards the protocol message to another gateway associated with the second service over the determined network route.