Content Node TCP Parameter Configuration for Device Characteristics

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Content delivery networks face slowdowns and latency issues due to outdated components, poor caching management, and limitations in end user device capabilities, which affect the efficient transfer of network content from origin servers to end users.

Innovation Solution

Configuring Transmission Control Protocol (TCP) parameters based on the characteristics of end user devices to optimize data transfer speeds and efficiency, using content nodes as intermediary proxy servers to cache and deliver content, and employing a content delivery network with local data storage and management systems to manage content delivery.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If content nodes use default TCP parameters for all devices, then configuration simplicity is maintained, but data transfer efficiency decreases due to mismatched device capabilities

Engineering Contradiction:
Improvedata transfer efficiencyVSAvoidTCP parameter configuration complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent dynamically changes TCP parameters (such as window size, congestion control thresholds, and buffer sizes) based on detected end user device characteristics including device type, network conditions, and performance capabilities. This allows optimization of data transfer efficiency for each device without requiring manual configuration, resolving the contradiction between transfer efficiency and configuration complexity.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The system implements dynamic adaptation of TCP parameters during runtime based on real-time device characteristics and network conditions. The content nodes continuously monitor device performance and adjust TCP settings accordingly, transforming the static configuration approach into a dynamic one that optimizes productivity without increasing operational complexity for users.

Inventive Principle:
Principle #15Dynamics

2Reliability

If content nodes cache all origin server content, then content availability is improved, but storage requirements and memory usage increase significantly

Engineering Contradiction:
Improvecontent availabilityVSAvoidcached content volume
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent implements selective caching where content nodes cache only specific portions of origin server content based on local quality metrics such as popularity, access frequency, and predicted demand. Instead of uniformly caching all content, the system identifies and caches only the most valuable content segments, maintaining content availability for frequently accessed material while minimizing storage requirements for less important content.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system applies partial caching by caching only a subset of available content rather than all content. This partial action approach caches content selectively based on anticipated demand and storage capacity, ensuring adequate content availability for user needs while avoiding the excessive storage consumption that would result from caching complete content sets.

Inventive Principle:
Principle #16Partial or excessive action

3Loss of energy

If content nodes handle all content requests, then origin server load is reduced, but content node processing speed decreases due to request volume

Engineering Contradiction:
Improveorigin server energy consumptionVSAvoidcontent node processing speed
Core Design Contradiction:
Loss of energyVSSpeed

Solution Approach 1:

The patent segments the content delivery workload by dividing requests into different handling paths based on cache status and device characteristics. The content delivery network segments traffic so that cached content is served directly by content nodes while uncached or updated content is retrieved from origin servers, preventing content node overload while maintaining origin server load reduction benefits.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The content delivery network acts as an intermediary layer between origin servers and end user devices, intelligently routing requests based on cache availability and device needs. This intermediary function allows the system to reduce origin server load through caching while managing content node processing capacity through smart request routing and load distribution mechanisms.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP3017613B1Network parameter configuration based on end user device characteristics
Publication Date: 2021.03.24 FASTLY INC
  • EP3017613B1 patent drawingFigure 1
  • EP3017613B1 patent drawingFigure 2
  • EP3017613B1 patent drawingFigure 3

AI summary

Systems, methods, and software for operating a content node are provided herein. In one example, a method of operating a content node is presented. The method includes receiving a characteristic of an end user device, and configuring one or more transmission control protocol (TCP) parameter for communications with the end user device based on at least the characteristic of the end user device. The method also includes transferring the communications using the one or more TCP parameters for delivery to the end user device.