CDN Proxy Routing by Content Attributes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Content delivery networks (CDNs) face challenges in efficiently processing client requests due to insufficient information about content attributes, leading to suboptimal routing of requests to appropriate servers, which can result in inefficient content delivery and increased load on origin servers.

Innovation Solution

A CDN framework that utilizes a proxy to query attribute databases for content attributes, allowing for the selection of appropriate parent CD services to process requests, with generic servers acting as fallbacks when information is lacking, and updating databases with information about content to improve future request routing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a CDN framework queries attribute databases for content attributes to route requests to appropriate servers, then content delivery efficiency is improved, but system complexity increases due to additional database queries and processing steps

Engineering Contradiction:
Improvecontent delivery efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by querying attribute databases and determining content attributes before routing requests. The proxy queries databases for content attributes, determines appropriate parent CD services in advance, and prepares routing decisions before actual content delivery, thereby improving efficiency despite added complexity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The proxy acts as an intermediary between clients and parent CD services. It mediates request routing by querying attribute databases, determining content attributes, and selecting appropriate parent CD services based on this information, thereby improving overall system efficiency while managing complexity through a dedicated intermediate component.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If generic servers are used as fallbacks when content attribute information is lacking, then request processing reliability is improved, but content delivery optimization deteriorates

Engineering Contradiction:
Improverequest processing reliabilityVSAvoidcontent delivery optimization
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system prepares for potential information gaps by having generic servers ready as fallback options. When content attribute information is insufficient or unavailable, the proxy routes requests to generic servers that can handle requests without detailed content knowledge, ensuring reliable processing while accepting reduced optimization for those specific cases.

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

Solution Approach 2:

The system dynamically adjusts routing parameters based on available information. When content attributes are known, it routes to specialized parent CD services for optimized delivery; when attributes are unknown, it changes the routing parameter to use generic servers, thereby maintaining reliability across varying information conditions.

Inventive Principle:
Principle #35Parameter changes

3Measurement precision

If the CDN updates databases with content information over time, then routing precision is improved, but information processing load increases

Engineering Contradiction:
Improverouting precisionVSAvoidinformation processing load
Core Design Contradiction:
Measurement precisionVSUse of energy by moving object

Solution Approach 1:

The system implements feedback by updating attribute databases with content information over time. When parent CD services or origin servers process requests, they provide information about content attributes back to the proxy, which stores this information in databases for future routing decisions, thereby improving precision while distributing the processing load.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The CDN system serves itself by automatically updating its own attribute databases with content information. The proxy and parent CD services work together to collect, store, and utilize content attribute information without requiring external manual intervention, improving routing precision while managing processing loads through automated self-service mechanisms.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20240372932A1Request processing in a content delivery framework
Publication Date: 2024.11.07 SANDPIPER CDN LLC
  • US20240372932A1 patent drawing
  • US20240372932A1 patent drawing
  • US20240372932A1 patent drawing

AI summary

A node in a content delivery network (CDN) receives a request for content and determines information about the request. When sufficient information about the content is determined, the request is assigned to an appropriate CD service to process the request; and when insufficient information about the content is determined, the request is assigned to a generic CD service to process the request. The generic CD service processes the request; and provides updated information about the content to be used for processing future requests. An appropriate CD service processing a request may also provide updated information about the content to be used for processing future requests.