CDN Node URL Refresh Filtering via Local Database Comparison

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional URL refreshing methods in CDNs result in low efficiency due to heavy workload on CDN memory devices, as all to-be-refreshed URLs are deleted across multiple CACHE devices, leading to numerous invalid refresh operations.

Innovation Solution

A method where the CDN node receives a refresh request, compares the URL with a local database to identify only the URLs actually stored, and performs a refresh operation on those URLs, reducing unnecessary refreshes and workload by filtering out URLs not stored locally.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If all to-be-refreshed URLs are deleted in each memory in the CDN, then URL correctness is ensured, but workload of each memory becomes heavy and refreshing efficiency becomes low

Engineering Contradiction:
ImproveURL correctnessVSAvoidrefreshing efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments the URL refreshing process into two distinct phases: a filtering phase where the CDN controller identifies which URLs need refreshing by comparing against a local database, and an execution phase where only those filtered URLs are actually deleted from memories. This segmentation prevents unnecessary refresh operations in each memory while ensuring correct URL updates, thereby resolving the contradiction between reliability and productivity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary filtering action before the actual refresh operation. The CDN controller first compares to-be-refreshed URLs with URLs stored in the local database to identify only the subset that truly needs refreshing. This preliminary action prevents memories from processing irrelevant URLs, reducing workload while maintaining URL correctness.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If URLs are refreshed in multiple CACHE devices, then URL correctness is maintained, but invalid refresh operations increase and workload increases

Engineering Contradiction:
ImproveURL correctnessVSAvoidinvalid refresh operations
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent introduces a CDN controller as an intermediary between the refresh request source and the CACHE devices. The controller receives refresh requests, filters them by comparing against the local database, and only forwards valid URLs to appropriate memories. This intermediary prevents invalid refresh operations from reaching multiple CACHE devices, reducing energy waste while maintaining URL correctness.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent extracts the filtering function from the CACHE devices and centralizes it in the CDN controller. By taking out the decision-making logic about which URLs need refreshing, the system prevents CACHE devices from performing invalid refresh operations. Only extracted and validated URLs are then distributed to memories, eliminating wasteful operations.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS12067069B2URL refreshing method, apparatus and device in CDN, and CDN node
Publication Date: 2024.08.20 BEIJING KINGSOFT CLOUD NETWORK TECH CO LTD
  • US12067069B2 patent drawing
  • US12067069B2 patent drawing
  • US12067069B2 patent drawing

AI summary

A URL refreshing method, apparatus and device in a CDN, and a CDN node, relating to the technical field of data processing, and the technical problem of poor URL refreshing efficiency in a CDN. The method includes: receiving a first refreshing request, the first refreshing request comprising at least one URL to be refreshed; comparing the at least one URL with a URL stored in a local database, the local database storing a URL corresponding to a locally stored source file; and executing a refreshing operation of the URL existing in the database.