Direct Server Return via Load Balancer Loopback Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional cloud computing platforms fail to support direct IP addressing and direct server return, which are essential for efficient communication between client devices and servers, due to their reliance on virtual private network configurations that prevent direct IP addressing and server return.

Innovation Solution

The implementation of a cloud computing platform with a load balancer and servers configured with public, private, and loopback interfaces, where the load balancer selects a server to process messages and modifies the destination MAC address without altering the IP address, enabling direct server return and allowing multiple client devices to connect to the same server through direct addressability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional virtual private network configurations are used in cloud computing platforms, then application security and reliability are improved, but direct IP addressing and direct server return are prevented

Engineering Contradiction:
Improveapplication securityVSAvoiddirect IP addressing support
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The network interface is segmented into multiple interfaces (public, private, loopback) with distinct functions. The public interface handles direct IP addressing and direct server return traffic, the private interface handles internal cloud communication, and the loopback interface provides local routing. This segmentation allows the system to maintain security through VPN configurations on the private interface while enabling direct addressing capabilities on the public interface.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The loopback interface acts as an intermediary that enables direct server return functionality. When a server needs to respond directly to a client, the loopback interface facilitates the routing of traffic back to the client without requiring traversal through the load balancer, while still maintaining the overall VPN-protected architecture.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Device complexity

If load balancer processes all reply messages, then load distribution is simplified, but round trip reply time increases and message path lengthens

Engineering Contradiction:
Improveload balancing complexityVSAvoidround trip reply time
Core Design Contradiction:
Device complexityVSLoss of time

Solution Approach 1:

The system dynamically determines the reply path based on the type of traffic and server configuration. For standard load-balanced traffic, replies traverse through the load balancer. For direct server return traffic, the path dynamically routes directly from server to client, reducing latency while maintaining simplified load balancing for the majority of traffic.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

Different quality of routing is applied to different traffic types. Direct server return traffic receives optimized local routing that bypasses the load balancer, while other traffic maintains the standard path through the load balancer. This allows time-sensitive traffic to take the faster path without complicating the overall load balancing architecture.

Inventive Principle:
Principle #3Local quality

3Reliability

If servers use private IP addresses only, then network security is improved, but direct addressability for multiple clients is reduced

Engineering Contradiction:
Improvenetwork securityVSAvoiddirect addressability
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The IP addressing is segmented across multiple interfaces. The public interface is assigned a public IP address that enables direct addressability from external clients, while the private interface maintains private IP addressing for internal cloud network security. The loopback interface provides additional routing capabilities. This segmentation allows servers to maintain security through private addressing internally while providing direct addressability externally through the public interface.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8266204B2Direct addressability and direct server return
Publication Date: 2012.09.11 MICROSOFT TECHNOLOGY LICENSING LLC
  • US8266204B2 patent drawing
  • US8266204B2 patent drawing
  • US8266204B2 patent drawing

AI summary

Cloud computing platforms having computer-readable media that perform methods for direct addressability and direct server return are provided. The cloud computing platform includes a load balancer and several servers. The servers are configured with public addresses, private addresses, and an address of the load balancer. The loopback interface of the servers is configured with the address of the load balancer. This allows a server to bypass the load balancer when replying to communication messages. Additionally, the public and private addresses of the servers enable direct addressability in the cloud computing platform. Accordingly, an application executing in the cloud computing platform may connect two or more clients on the same server.