CDN Edge Node Scheduling via Proxy to Bypass DNS Hijacking

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

DNS domain hijacking leads to incorrect IP address returns for CDN edge nodes, causing video service play failures, with over 50% of failures attributed to this issue in existing systems.

Innovation Solution

Implement a scheduling proxy server that determines the target CDN scheduling center and edge node IP addresses based on terminal device IP addresses, bypassing direct DNS resolution, ensuring correct IP address acquisition and integrating authentication processes to enhance content delivery success and play success rates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If DNS domain resolution is used for CDN edge node scheduling, then the scheduling system can resolve domain names to IP addresses, but DNS domain hijacking occurs causing incorrect IP address returns and video service play failures

Engineering Contradiction:
ImproveIP address correctnessVSAvoidDNS domain hijacking
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent introduces a scheduling proxy server as an intermediary between the terminal device and the CDN scheduling center. This proxy server obtains the IP address of the target CDN edge node through HTTP scheduling and directly returns it to the terminal device, bypassing the DNS resolution process entirely. This eliminates the vulnerability to DNS domain hijacking while maintaining the ability to obtain correct IP addresses for CDN edge nodes.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If terminal device directly initiates HTTP scheduling request to CDN scheduling center, then IP address can be obtained, but domain name resolution is still required which is vulnerable to hijacking

Engineering Contradiction:
Improvescheduling accuracyVSAvoidscheduling process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The scheduling proxy server acts as an intermediary that consolidates multiple functions: it receives scheduling requests from terminal devices, performs HTTP scheduling with the CDN scheduling center, and returns the obtained IP addresses to terminal devices. This intermediary approach simplifies the overall scheduling process by centralizing the complex HTTP scheduling operations and eliminating the need for terminal devices to perform separate DNS resolution.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Loss of time

If DNS resolution is performed for scheduling, then domain names can be resolved to IP addresses, but play start delay increases due to additional resolution steps

Engineering Contradiction:
Improveplay start delayVSAvoidcontent delivery efficiency
Core Design Contradiction:
Loss of timeVSProductivity

Solution Approach 1:

The patent extracts the DNS resolution step from the scheduling process by using HTTP scheduling instead. The scheduling proxy server directly communicates with the CDN scheduling center through HTTP requests to obtain IP addresses, completely removing the DNS resolution环节 from the scheduling flow. This extraction eliminates the time delay associated with DNS resolution while maintaining efficient content delivery.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentEP4380109B1Content delivery network CDN edge node scheduling method and device
Publication Date: 2026.02.04 PETAL CLOUD TECH CO LTD
  • EP4380109B1 patent drawingFigure 1A
  • EP4380109B1 patent drawingFigure 1B
  • EP4380109B1 patent drawingFigure 2

AI summary

Embodiments of this application provide a content delivery network CDN edge node scheduling method and a device. The method includes: receiving, by a scheduling proxy server, a first request message from a terminal device, where the first request message includes a first IP address, and the IP address is an IP address of the terminal device; determining, based on the first IP address and configuration information, a target CDN scheduling center corresponding to the first IP address; sending a second request message to the target CDN scheduling center when the target CDN scheduling center supports proxy scheduling setting, where the second request message includes the first IP address, so that the target CDN scheduling center determines a second IP address based on the first IP address, and the IP address is an IP address of a target CDN edge node corresponding to the first IP address; receive the second IP address sent by the target CDN scheduling center; and send a request response message to the terminal device, where the request response message carries the second IP address, so that the terminal device obtains delivery content from the target CDN edge node based on the second IP address In this way, a content obtaining success rate can be increased.