Dual Secured Connection Load Balancer for Distributed Computing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing legacy processes for creating secure connections in distributed computing often result in inadequate security and inflexibility, particularly in scenarios involving sensitive data like financial transactions.

Innovation Solution

A computing system and method that establish two separate secured connections between a client device and a server, using a load balancer for load balancing and secure communication, with the first connection between the client and load balancer and a second connection between the load balancer and server, employing protocols like SSL or IP filtering for authentication and security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a single secured connection is used between client and server, then device complexity is reduced, but security is compromised

Engineering Contradiction:
ImprovesecurityVSAvoidconnection structure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent divides the communication path into two separate secured connections: one between the client and load balancer, and another between the load balancer and server. This segmentation allows each connection to be independently secured, improving overall security without requiring the client to directly connect to multiple servers

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The load balancer acts as an intermediary component that establishes separate secured connections with both the client and the server. This intermediary approach enables security hardening at the load balancer level while maintaining simplified client-server communication through the load balancer

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If legacy authentication processes are used, then ease of operation is maintained, but security is insufficient

Engineering Contradiction:
ImprovesecurityVSAvoidauthentication process
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent implements preliminary authentication and authorization at the load balancer before requests are forwarded to servers. SSL/TLS certificates are validated and mutual authentication is completed in advance, ensuring security requirements are met before operational transactions begin

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent replaces legacy mechanical authentication processes with modern cryptographic mechanisms including SSL/TLS protocols, digital certificates, and mutual authentication. This substitution maintains ease of operation through automated cryptographic handshakes while significantly improving security

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Adaptability or versatility

If direct client-server connections are used, then connection establishment is simple, but flexibility and failover capability are reduced

Engineering Contradiction:
Improvefailover capabilityVSAvoidconnection management
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The load balancer serves as an intermediary that manages multiple server connections behind a single client-facing connection. This enables seamless failover and load distribution without requiring the client to manage multiple direct connections, maintaining simplicity while improving flexibility

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The load balancer performs multiple functions including establishing secured connections, performing mutual authentication, conducting load balancing, and enabling failover. This multi-functionality provides flexibility and adaptability without requiring separate systems for each function

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

Data Source

PatentUS9032505B1Creating secure connections between distributed computing devices
Publication Date: 2015.05.12 WELLS FARGO BANK NA
  • US9032505B1 patent drawing
  • US9032505B1 patent drawing
  • US9032505B1 patent drawing

AI summary

A computing device includes: a processing unit; and memory encoding instructions that, when executed by the processing unit, cause the processing unit to: receive a request from a client computing device; establish a first secured connection to the client computing device; select a server computing device from a plurality of server computing devices to service the request from the client computing device, selection being made based, at least in part, upon load balancing considerations; establish a second secured connection to the server computing device, the second secured connection being separate from the first secured connection; and allow the client computing device to securely communicate with the server computing device through the first and second secured connections.