Client-Server Binding via Best-Fit IP Lists

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing client-server network systems face challenges in maintaining constant connectivity, especially for clients with limited computational and storage resources, due to the inefficiencies of the Internet Distributed Name Service (DNS) and the need for dynamic server binding, which can lead to sub-optimal resource allocation and prolonged propagation of IP address changes.

Innovation Solution

A method where a client maintains a set of 'best-fit' server IP addresses, ordered by criteria such as routing distance and server loading, allowing dynamic binding with a server without relying on DNS, using extensions of existing network protocols like SIP and STUN to minimize overhead and resource requirements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If DNS is used for client-server binding, then name resolution is provided, but computational and storage resources are consumed and binding changes propagate slowly

Engineering Contradiction:
Improveclient-server binding reliabilityVSAvoidDNS system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the essential function of DNS (providing server IP addresses to clients) and removes the complex distributed name server infrastructure. Instead of using DNS, the system directly provides clients with lists of server IP addresses through simplified protocols, eliminating the need for clients to implement full DNS functionality while maintaining the core binding capability.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces a simplified intermediary mechanism where servers directly communicate their IP addresses to clients through protocol extensions (SIP, STUN, TURN). This intermediary approach replaces the complex DNS hierarchy with direct server-to-client information provision, reducing both computational overhead and propagation delays.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If multiple servers are deployed for redundancy, then failure points are reduced, but resource allocation becomes sub-optimal and management complexity increases

Engineering Contradiction:
Improveserver availabilityVSAvoidresource allocation efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements dynamic binding where clients can switch between multiple servers based on current conditions. The system provides clients with lists of alternative server IP addresses and enables dynamic re-binding when servers fail or performance degrades. This dynamic approach optimizes resource allocation by allowing flexible redistribution of client connections across available servers.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system incorporates feedback mechanisms where clients monitor server connectivity and performance, and automatically switch to alternative servers when needed. This feedback-driven approach ensures optimal resource utilization by redirecting traffic away from failed or overloaded servers to healthy alternatives, maintaining both reliability and efficiency.

Inventive Principle:
Principle #23Feedback

3Speed

If DNS caching with TTL is used, then name resolution speed is improved, but IP address changes propagate slowly and resource consumption increases

Engineering Contradiction:
Improvename resolution speedVSAvoidIP address change propagation time
Core Design Contradiction:
SpeedVSLoss of time

Solution Approach 1:

The patent provides clients with pre-configured lists of server IP addresses through protocol extensions during initial connection establishment. This preliminary provision of binding information eliminates the need for repeated DNS lookups and caching operations, enabling immediate switching to alternative servers when needed while reducing overall computational and storage resource consumption.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8606874B2System and method of binding a client to a server
Publication Date: 2013.12.10 UPLAND SOFTWARE INC
  • US8606874B2 patent drawing
  • US8606874B2 patent drawing
  • US8606874B2 patent drawing

AI summary

Systems and methods to bind a client with a server are provided. A particular method includes establishing a connection between a server and a client. A list of best-fit server IP addresses is received at the client via the connection. A determination is made whether the server is identified in the list of best-fit server IP addresses. When the server is not identified in the list of best-fit server IP addresses, the connection to the server is terminated.