CDN Edge Cache Scheduling to Reduce Parent-Node Interaction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The frequent interaction between edge nodes and parent layer nodes in a content delivery network (CDN) increases bandwidth consumption and internal costs due to the need for edge nodes to frequently request cache data from the parent layer when it is not available.

Innovation Solution

A scheduling method and apparatus that determines the existence of cache data in edge nodes using address mapping data based on a load balancing strategy, allowing cache data to be sent from target edge nodes where it is stored, reducing interactions between edge and parent layer nodes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If edge nodes frequently request cache data from parent layer nodes, then cache data availability is improved, but bandwidth consumption and internal costs increase

Engineering Contradiction:
Improvecache data availabilityVSAvoidbandwidth consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system performs preliminary actions by pre-fetching cache data from parent layer nodes to edge nodes based on predictive algorithms and historical access patterns. This proactive caching ensures data is available locally before actual user requests occur, eliminating the need for frequent real-time requests to parent nodes and reducing bandwidth consumption while maintaining high data availability

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements local quality by enabling each edge node to independently determine the availability of cache data through local judgment mechanisms. Edge nodes can assess whether required cache data exists in their local storage or nearby edge nodes, reducing the need to frequently query parent layer nodes and thereby decreasing bandwidth consumption while maintaining reliable data access

Inventive Principle:
Principle #3Local quality

2Productivity

If edge nodes frequently interact with parent layer nodes, then cache data is obtained, but interaction overhead and internal consumption cost increase

Engineering Contradiction:
Improvedata retrieval capabilityVSAvoidinteraction overhead
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent introduces intermediary mechanisms between edge nodes and parent layer nodes, including local judgment modules and predictive caching systems. These intermediaries handle data availability checks and pre-fetch operations locally, acting as a buffer that reduces the frequency and overhead of direct interactions with parent layer nodes, thereby maintaining productivity while reducing time loss

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

Edge nodes are empowered with self-service capabilities to independently determine cache data availability and manage their own caching strategies. By autonomously judging data availability and making local caching decisions, edge nodes reduce dependency on parent layer nodes, minimizing interaction overhead and time loss while maintaining effective data retrieval

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12375583B2Scheduling method and apparatus, storage medium and electronic device for content delivery network
Publication Date: 2025.07.29 BEIJING YOUZHUJU NETWORK TECH CO LTD
  • US12375583B2 patent drawing
  • US12375583B2 patent drawing
  • US12375583B2 patent drawing

AI summary

The disclosure relates to a method, apparatus, electronic device and storage medium for scheduling for a content distribution network (CDN). The method includes: in response to an access request, received by an edge node, for a user to access a target website, determining whether target cache data corresponding to the target web site exists in the edge node; in response to absence of the target cache data in the edge node, reading address mapping data according to a load balancing strategy corresponding to the content delivery network; in response to determining that a target historical access network address corresponding to the target website exists in the address mapping data, determining a target edge address corresponding to the target historical access network address; and sending target cache data in the target edge address, corresponding to the target historical access network address to a user equipment through a cache service of the CDN.