Distributed Server Connection Selection Without Central Controller

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current network technologies rely on central controllers for load balancing and connection management, limiting redundancy and availability since servers must be collocated and lack visibility into server status for remote applications, which restricts intelligent connection routing and maintenance.

Innovation Solution

A distributed system where each server in a group is configured with a unique identifier and posts its status and connection details to a central database, allowing remote clients to access and choose the best server for connections based on available information without a central controller, using a dummy server to aggregate data and provide extrinsic information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a central controller is used for load balancing and connection management, then connection routing is simplified, but system reliability deteriorates due to single point of failure and limited redundancy

Engineering Contradiction:
Improveconnection routingVSAvoidsystem availability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent extracts the central controller function from the system by having servers independently publish their own status and connection information to a distributed database. Each server becomes autonomous in managing its own connectivity, eliminating the single point of failure while maintaining simplified client access through group-based queries.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system segments the central control function across multiple independent servers that each publish their own status information. Instead of one centralized controller, multiple servers distributed throughout the network independently manage their own connection information, providing redundancy and fault tolerance.

Inventive Principle:
Principle #1Segmentation

2Ease of manufacture

If servers are collocated and grouped as a physical unit, then virtualization and redundancy are simplified, but adaptability deteriorates as servers cannot operate in different physical and logical locations

Engineering Contradiction:
Improvevirtualization configurationVSAvoidserver location flexibility
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent introduces dynamic server placement where servers can be located anywhere in the network and assigned to logical groups based on functional requirements rather than physical proximity. The distributed database enables dynamic association of servers with client groups, allowing flexible deployment across different physical and logical locations.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system enables any server to serve multiple logical groups and any client to connect to any server in the network, regardless of physical location. The universal database structure allows servers to be universally accessible and reassigned to different functional groups as needs change.

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

3Device complexity

If remote applications lack server status information, then connection decisions are simplified, but connection efficiency deteriorates as applications cannot intelligently route based on server conditions

Engineering Contradiction:
Improveconnection decision logicVSAvoidconnection efficiency
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The patent implements feedback mechanisms where servers continuously publish their status information (uptime, downtime, impaired state, sunset status) and connection details to the distributed database. Clients query this feedback information to make intelligent connection decisions, enabling efficient routing based on real-time server conditions.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

Servers perform preliminary actions by proactively publishing their status and connection information before clients need to make connection decisions. This advance information availability allows clients to pre-determine optimal routing paths without requiring complex real-time negotiation.

Inventive Principle:
Principle #10Preliminary action

4Ease of manufacture

If maintenance is performed on a server, then server updates can be applied, but connection continuity deteriorates as all existing connections may be disconnected

Engineering Contradiction:
Improveserver maintenanceVSAvoidconnection continuity
Core Design Contradiction:
Ease of manufactureVSDuration of action of stationary object

Solution Approach 1:

The system enables dynamic maintenance operations where servers can be individually taken offline for updates while the distributed database automatically redirects clients to alternative servers in the same logical group. This dynamic reconfiguration maintains connection continuity during maintenance activities.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent provides beforehand cushioning by ensuring multiple servers in each logical group are pre-configured with backup capabilities. When maintenance is needed, the system has already established redundant pathways through the distributed database, cushioning against connection interruptions.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

Data Source

PatentUS12034799B2Systems and methods for automated, controllerless and stateless network connection selection based on distributed server information
Publication Date: 2024.07.09 IP TECHNOLOGY LABS LLC
  • US12034799B2 patent drawing

AI summary

The invention is that of systems and methods for controllerless and distributed network connections to servers on a network by remote clients seeking their services. The invention comprises a central database where servers within a server group identified by a group name may post unique identifiers (UIDs) for retrieval by group clients configured with the group name, which may query the central database for server connection information such as uptime, downtime, and congestion in order to select a server for a preferential connection based on an overall availability profile as determined by the group client. In some embodiments, one server of the group is a “dummy server” that may aggregate and selectively transmit server information from other servers in the group, or other devices, and posts it to the central database for client access. The methods described herein eliminate a separate controller and thereby a single point of failure (SPOF).