Content File Recipe Composition for CDN Bandwidth Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Content delivery networks face inefficiencies in bandwidth usage and data retrieval due to the need to repeatedly fetch large amounts of redundant data, leading to potential delays and degraded user experience, especially as digital content sizes increase.

Innovation Solution

Implementing a system where content files are composed using recipes that include instructions to retrieve and reuse similar data, allowing only portions of content data to be stored in a cache, with the remaining data referenced by these recipes, thereby reducing the burden on content delivery nodes and improving network performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If content delivery nodes store complete content files locally, then delivery speed improves, but storage requirements and bandwidth usage increase significantly

Engineering Contradiction:
Improvecontent delivery speedVSAvoidstorage capacity required
Core Design Contradiction:
SpeedVSQuantity of substance

Solution Approach 1:

The patent segments content files into multiple data portions and stores only selected portions at content delivery nodes. Instead of caching complete files, the system divides content into manageable segments and strategically caches only the most frequently accessed or critical segments, reducing storage requirements while maintaining delivery capability for commonly requested content.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a new dimension of data reconstruction by creating composite content through combining multiple data portions from different sources. Content delivery nodes can assemble complete content files by retrieving and combining segments from various content files and sources, transforming the traditional single-file caching approach into a multi-source composition system that reduces overall storage needs.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Reliability

If content delivery nodes retrieve complete content files from content providers, then data accuracy is maintained, but bandwidth consumption and retrieval time increase

Engineering Contradiction:
Improvedata completenessVSAvoidbandwidth consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent extracts and caches only the essential or frequently accessed data portions from complete content files, rather than caching entire files. Content delivery nodes retrieve and store specific segments that are most likely to be needed, reducing bandwidth consumption during both the initial caching phase and subsequent content delivery operations.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent implements partial action by caching only a subset of content data portions rather than complete files. The system retrieves and caches sufficient data portions to enable reconstruction of commonly requested content, using just enough bandwidth to cache essential segments without the excessive bandwidth consumption of caching complete files.

Inventive Principle:
Principle #16Partial or excessive action

3Loss of energy

If delta coding is used to reduce bandwidth usage, then transmission efficiency improves, but user experience degrades when delta size is large

Engineering Contradiction:
Improvebandwidth usageVSAvoiddata delivery delay
Core Design Contradiction:
Loss of energyVSLoss of time

Solution Approach 1:

The patent performs preliminary action by pre-caching data portions at content delivery nodes before user requests arrive. Instead of transmitting large deltas in real-time, the system proactively stores content segments at edge nodes in advance, so that when users request content, the data is already locally available or can be quickly assembled from cached segments, eliminating delivery delays.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent creates local copies of data portions at content delivery nodes rather than relying on delta compression and decomposition. By caching actual content segments at edge locations, the system enables direct local retrieval and composition of content without requiring bandwidth-intensive delta transmission and client-side reconstruction, maintaining both low bandwidth usage and fast delivery.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS9294529B1Reusing data in content files
Publication Date: 2016.03.22 GOOGLE LLC
  • US9294529B1 patent drawing
  • US9294529B1 patent drawing
  • US9294529B1 patent drawing

AI summary

An embodiment for reusing data in content files includes receiving a request for a content file and retrieving a recipe that includes a series of instructions needed to compose the content file. Data identified by the recipe may then be retrieved from a content file server and the requested content file is composed based on the set of instructions in the recipe. In an example, the recipe is processed by a recipe player to compose a content file. In another embodiment, content files are stored in a cache as a series of instructions for generating them from portions of other content files. In this way, performance in a content delivery network may be improved by reusing similar data in content files.