Server Self-Configuration via DNS for Scalable Network Services

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing network-based communication systems face challenges in scalability and reliability due to manual configuration of client-server information, which limits their ability to handle increased demand and adapt to changes in server resources.

Innovation Solution

Implementing a network-based server arrangement with automatic self-configuration and reconfiguration of services based on administrative assignments, where multiple servers provide common services and dynamically adjust their configurations in response to client requests and DNS updates, ensuring that only necessary services are active and matching the requested service types.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If manual configuration of client-server information is used, then device complexity is reduced, but scalability and reliability deteriorate

Engineering Contradiction:
Improveconfiguration complexityVSAvoidservice reliability
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The server automatically performs configuration tasks by receiving service type information from the DNS server and autonomously configuring its services accordingly. This self-service mechanism eliminates manual configuration while ensuring reliable service setup, as the server independently adapts its configuration based on received parameters without human intervention.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The DNS server pre-configures service type information and transport parameters before the actual service activation. By preparing configuration data in advance and making it available to clients and servers, the system ensures that when services are activated, they are immediately ready with correct settings, improving both reliability and scalability.

Inventive Principle:
Principle #10Preliminary action

2Device complexity

If manual configuration of client-server information is used, then device complexity is reduced, but scalability deteriorates

Engineering Contradiction:
Improveconfiguration complexityVSAvoidscalability
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

Servers automatically receive service type information from the DNS server and self-configure based on received parameters. This eliminates the need for manual configuration updates when scaling the system, allowing new servers to be automatically integrated by simply registering with the DNS server, thereby enabling seamless scalability.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The DNS server serves multiple functions: it stores service type information, manages transport parameters, provides configuration data to both clients and servers, and enables automatic service activation. This multi-functional approach allows the same infrastructure to support system growth without requiring additional configuration mechanisms.

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

3Adaptability or versatility

If automatic self-configuration is implemented, then scalability is improved, but device complexity increases

Engineering Contradiction:
ImprovescalabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The DNS server acts as an intermediary that centralizes the management of service type information and transport parameters. By mediating between clients and servers, and between service activation and configuration, the DNS server reduces overall system complexity while enabling automatic self-configuration, as all configuration logic is consolidated in one location rather than distributed across multiple components.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If multiple servers provide common services, then reliability is improved, but service configuration complexity increases

Engineering Contradiction:
Improveservice availabilityVSAvoidservice configuration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Each server independently receives service type information from the DNS server and automatically configures itself based on received parameters. This self-service approach allows multiple servers to provide common services with consistent configuration without requiring manual coordination, thereby maintaining reliability while reducing configuration complexity.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The DNS server provides uniform service type information to all servers, ensuring homogeneous configuration across the system. By standardizing the configuration data structure and parameters provided to all servers, the system achieves consistent service delivery across multiple servers without increasing configuration complexity.

Inventive Principle:
Principle #33Homogeneity

Data Source

PatentUS8943180B1Server-based service configuration system and approach
Publication Date: 2015.01.27 8X8 INC
  • US8943180B1 patent drawing
  • US8943180B1 patent drawing
  • US8943180B1 patent drawing

AI summary

Network service providers are managed using a server-side configuration approach. According to an example embodiment of the present invention, a host network location includes two or more servers that automatically reconfigure their services in response to controller service settings corresponding to each server. Each server reads configuration information provided at a controller such as a domain name server (DNS), and in response, starts a network-based service corresponding to the configuration information. For instance, each of the two or more servers may be adapted to provide mail service via simple mail transfer protocol (SMTP) and web service via hyper text transfer protocol (HTTP). In this regard, when a DNS associates a first one of the servers with HTTP services and a second one of the servers with SMTP services, each server reconfigures its services accordingly, e.g., at a selected configuration time after startup or in response to an initiating event.