CDN Service Interaction Management via Layered Virtual Machine

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Content delivery networks (CDNs) face challenges in efficiently managing content distribution, caching, and peering policies, leading to suboptimal performance and increased costs due to the complexity of interactions between various services and intermediaries in the network.

Innovation Solution

A framework for content delivery networks that includes a layered virtual machine (LVM) and request collection lattice (RCL) to manage service interactions, caching, and peering policies, enabling efficient content distribution and dynamic configuration of services within the CDN.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If traditional CDN architectures are used to manage content distribution, then basic content delivery is achieved, but service interaction complexity increases and performance deteriorates

Engineering Contradiction:
Improvecontent delivery efficiencyVSAvoidservice interaction complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the CDN system into distinct functional layers: origin servers, edge servers, and client devices. Each layer operates independently with defined interfaces, reducing service interaction complexity while maintaining delivery efficiency. Edge servers cache content locally, eliminating the need for complex real-time coordination between all components.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces DNS-based resolution as an intermediary mechanism that simplifies service interactions. Instead of direct complex peer-to-peer communications between CDN components, all content requests are routed through DNS resolution at edge servers, which act as mediators between clients and origin servers, reducing overall system complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Speed

If content is cached at edge servers to reduce latency, then content delivery speed improves, but cache management complexity increases

Engineering Contradiction:
Improvecontent delivery speedVSAvoidcache management complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The patent implements preliminary content placement at edge servers during off-peak hours based on predictive analytics of content popularity. This preliminary action reduces real-time cache management complexity during peak delivery periods, as frequently accessed content is pre-positioned at edge locations, maintaining high speed while simplifying active cache management.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If multiple peering policies are implemented to optimize content distribution, then content delivery performance improves, but policy management complexity increases

Engineering Contradiction:
Improvecontent distribution efficiencyVSAvoidpeering policy complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements local quality by allowing each edge server to apply simplified peering policies specific to its local context and content type, rather than enforcing complex global policies. This enables efficient content distribution adapted to local conditions while reducing the complexity of centralized policy management.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS10791050B2Geographic location determination in a content delivery framework
Publication Date: 2020.09.29 SANDPIPER CDN LLC
  • US10791050B2 patent drawing
  • US10791050B2 patent drawing
  • US10791050B2 patent drawing

AI summary

A computer-implemented method operable in a content delivery network (CDN), includes receiving a request a service in said CDN; determining a particular classification of an Internet Protocol (IP) address associated with said request, said determining using a first function that maps IP addresses to one or more classifications, said particular classification being one of said one or more classifications; and processing said request based on said particular classification of said IP address associated with said request. A location-specific response to a request may be based on a geographic location associated with said IP address associated with said request.