City-Level CDN Scheduling via LDNS Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In content delivery networks (CDNs), existing methods for scheduling user access requests based on local domain name systems (LDNS) lead to resource wastage and inefficiencies, particularly when handling large file downloads, due to complex settings and multiple city-level cloud delivery nodes sharing the same LDNS.
Innovation Solution
A method and apparatus that determine the city and city operator corresponding to each access source IP segment, select a preferred cloud delivery node based on historical and real-time network transmission state parameters, and issue a mapping relationship to scheduling agent modules for efficient routing, allowing for real-time detection and modification of faulty nodes to optimize access request scheduling.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If multiple city-level cloud delivery nodes share the same LDNS, then resource sharing is achieved, but scheduling efficiency deteriorates and resource wastage occurs
Solution Approach 1:
The patent segments the provincial LDNS into multiple city-level LDNS instances, each responsible for a specific city. This segmentation allows independent scheduling decisions for each city while maintaining resource sharing across the province, thereby resolving the contradiction between resource sharing and scheduling efficiency.
Solution Approach 2:
The patent implements local quality by allowing each city-level LDNS to have customized scheduling policies and parameters specific to its local conditions (traffic patterns, network status, node capabilities). This enables optimized scheduling for each city while maintaining overall provincial resource sharing.
2Measurement precision
If complex LDNS settings are used for city-level scheduling, then scheduling precision is improved, but system complexity increases
Solution Approach 1:
The patent introduces an intermediary scheduling system that automatically translates high-level scheduling requirements into specific routing decisions. This intermediary layer handles the complexity of city-level scheduling internally, presenting a simplified interface to users while maintaining precise scheduling control.
Solution Approach 2:
The patent implements self-service by enabling the LDNS system to automatically detect network conditions, select optimal nodes, and adjust scheduling parameters without manual intervention. This automation maintains high scheduling precision while reducing the operational complexity for users.
3Measurement precision
If historical network transmission state parameters are used for node selection, then scheduling accuracy is improved, but processing time increases
Solution Approach 1:
The patent applies preliminary action by pre-calculating and storing historical network transmission state parameters for multiple nodes. When a scheduling decision is needed, the system retrieves pre-computed data rather than calculating everything in real-time, thus maintaining high accuracy while reducing processing time.
Solution Approach 2:
The patent uses partial action by selectively using historical data for only the most critical scheduling decisions or for nodes with significant performance variations. Not all nodes require historical analysis, which reduces overall processing time while maintaining accuracy where it matters most.
Data Source
AI summary
An access request scheduling method includes determining a city and a city operator corresponding to an access source IP segment; selecting, from cloud delivery nodes of the city operator, a preferred node of the access source IP segment; determining a mapping relationship between the access source IP segment and an IP of the preferred node; and issuing the mapping relationship to scheduling agent modules of the cloud delivery nodes in a network.