Content Delivery Node Purge and Coherence Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Content delivery systems face challenges in maintaining synchronized content across multiple nodes due to network latencies, failures, and other events, leading to mismatched revisions and improper content propagation.

Innovation Solution

A method and system where a content delivery node receives a purge instruction, purges the content, and transfers a content request to another node with a revision indicator to ensure coherent content propagation, using a content delivery system with distributed nodes and management systems to handle requests and updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If content is cached in distributed content delivery nodes, then access speed and latency are improved, but content synchronization and coherence across nodes deteriorate due to network latencies and failures

Engineering Contradiction:
Improvecontent access speedVSAvoidcontent synchronization
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The system implements a feedback mechanism where content delivery nodes report their cached content state to a management system, which then distributes appropriate purge instructions to maintain coherence. The management system receives status information from nodes and sends control instructions back to ensure all nodes have consistent content versions.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

A central management system acts as an intermediary between content delivery nodes and origin servers. This intermediary coordinates content purges and updates across the distributed network, managing the complexity of synchronization by centralizing control while allowing distributed caching to continue.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Device complexity

If content delivery nodes autonomously cache and serve content, then system complexity is reduced, but content coherence and version control worsen due to lack of centralized coordination

Engineering Contradiction:
Improvesystem complexityVSAvoidcontent coherence
Core Design Contradiction:
Device complexityVSLoss of information

Solution Approach 1:

The management system serves as an intermediary that maintains content coherence without requiring complex autonomous decision-making at each node. Nodes simply follow purge instructions from the management system, keeping individual node complexity low while ensuring overall system coherence through centralized coordination.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

Content delivery nodes autonomously serve cached content to end users without requiring real-time coordination for each request. This self-service capability reduces system complexity for content delivery operations while the management system handles coherence maintenance separately through purge instructions.

Inventive Principle:
Principle #25Self-service

3Reliability

If purge instructions are distributed to all content delivery nodes, then content coherence is improved, but network traffic and processing overhead increase

Engineering Contradiction:
Improvecontent coherenceVSAvoidnetwork overhead
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system segments the content delivery network into manageable nodes that can be independently controlled. The management system can send purge instructions to specific nodes or groups of nodes rather than broadcasting to all nodes, reducing network overhead while maintaining coherence where needed.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Instead of continuously synchronizing all content across all nodes, the system uses partial action by sending purge instructions only when and where needed. This reduces network traffic and processing overhead compared to continuous full synchronization, while still maintaining content coherence through targeted updates.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS10594778B2Data purge distribution and coherency
Publication Date: 2020.03.17 FASTLY INC
  • US10594778B2 patent drawing
  • US10594778B2 patent drawing
  • US10594778B2 patent drawing

AI summary

Systems, methods, and software for operating a content delivery system are provided herein. In one example, a method includes, in a first content delivery node, receiving a purge instruction to purge first content stored in the first content delivery node and responsively purging the first content. Responsive to purging the first content, the method includes transferring a content request for delivery to a second content delivery node, where the content request comprises a request for second content to replace the first content and a revision indicator of the first content. Responsive to the content request, the method includes receiving the second content for storage in the first content delivery node.