DNS Hosting Service Policy-Based Traffic Routing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current DNS hosting services in cloud computing environments offer limited control to customers over how end-users are routed to applications, with existing controls being specific and inefficient, lacking flexibility and scalability.

Innovation Solution

A DNS hosting service that allows customers to manage network traffic routing based on multiple criteria, including end-user and application metrics, using a policy-based model with customizable templates and real-time visualization, enabling flexible routing decisions and optimization of traffic flow across geographic regions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If existing DNS control mechanisms are used, then basic domain name translation is provided, but customer control over traffic routing is limited and inefficient

Engineering Contradiction:
Improvecustomer control over traffic routingVSAvoidrouting control mechanism
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system segments routing control into separate policy templates that can be independently configured and combined. Each template handles specific routing criteria (geographic, load-based, cost-based), allowing customers to build complex routing decisions from modular components without overwhelming complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The DNS service provides universal routing control by implementing multiple routing criteria within a single system. The same DNS infrastructure handles geographic routing, load balancing, cost optimization, and custom policies, eliminating the need for separate specialized systems for each function.

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

2Adaptability or versatility

If specific single-function control is implemented, then basic routing is possible, but flexibility and scalability are reduced

Engineering Contradiction:
Improverouting flexibilityVSAvoidrouting decision efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The system merges multiple routing criteria and decision-making capabilities into a unified DNS service. By combining geographic routing, load balancing, cost optimization, and custom policies within a single infrastructure, the system achieves both flexibility across multiple criteria and efficiency through consolidated processing.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The routing system is dynamic, allowing real-time adjustments based on changing conditions. Policies can be modified, templates can be combined in new ways, and routing decisions can adapt to current network conditions without requiring system redesign, providing both flexibility and efficient decision-making.

Inventive Principle:
Principle #15Dynamics

3Adaptability or versatility

If multiple routing criteria are supported, then comprehensive traffic management is achieved, but system complexity increases

Engineering Contradiction:
Improvemulti-criteria routing capabilityVSAvoidpolicy evaluation system
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

Complex multi-criteria routing is segmented into separate policy templates, each handling one or more specific criteria. The system evaluates these templates in a structured sequence, breaking down the complexity of evaluating multiple criteria simultaneously into manageable steps through template hierarchy and combination rules.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9967232B1Network traffic management system using customer policy settings
Publication Date: 2018.05.08 AMAZON TECH INC
  • US9967232B1 patent drawing
  • US9967232B1 patent drawing
  • US9967232B1 patent drawing

AI summary

A service is described that makes it easy and cost-effective to configure network traffic flowing to multiple endpoints. Enterprises and developers can easily manage the way that end-users are routed to applications running in different geographic regions. Customers can route traffic based on multiple criteria in a customer policy. Customers can manage large-scale, multi-region applications, increase application availability, and minimize latency to end-users. The service can consider the state of end-users, such as their geography, their network, and their latency to different geographic regions. The service can also consider the state of the customer's applications, such as the load on the application, the application's health, the cost of using that application (e.g., resource costs), resource states (e.g., disk throughput), resource location, customer-provided endpoint cost parameters, etc.