Content Steering Server Negotiation for Multi-CDN Load Shifting
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current multi-Content Delivery Network (CDN) systems lack a mechanism for CDNs to communicate their load requirements to the steering server, leading to inefficient load balancing that does not consider the dynamic capacity and performance changes of individual CDNs, resulting in suboptimal utilization and energy inefficiency.
Innovation Solution
Implementing a content steering server that facilitates negotiations between CDNs to dynamically redistribute loads based on internal statistics such as power efficiency, profitability, and operational requirements, allowing CDNs to express their traffic handling preferences and adjust loads strategically.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If the steering server exclusively uses client QoE reports for load balancing decisions, then the system is simple to implement, but it cannot consider CDN capacity and performance changes leading to suboptimal utilization
Solution Approach 1:
The patent implements a feedback mechanism where CDNs periodically report their status information (capacity, performance metrics) to the steering server. This feedback loop enables the steering server to adjust load balancing decisions based on real-time CDN capabilities, resolving the contradiction between simple implementation and optimal utilization by adding targeted feedback channels without fundamentally redesigning the steering architecture.
Solution Approach 2:
The system transitions from static load balancing based on fixed QoE reports to dynamic load balancing that incorporates real-time CDN status updates. The steering server dynamically adjusts routing decisions based on changing CDN capacities and performance conditions, enabling optimal resource allocation while maintaining architectural simplicity through incremental dynamic updates rather than complete system redesign.
2Device complexity
If CDNs cannot update their requirements, then the system structure remains simple, but load balancing cannot meet CDN needs and energy efficiency is reduced
Solution Approach 1:
The steering server acts as an intermediary that enables CDNs to express their load requirements and capacity status without requiring direct peer-to-peer communication between CDNs. This intermediary mechanism allows CDNs to update their requirements through standardized status reports to the steering server, which then incorporates this information into load balancing decisions, achieving energy efficiency improvements while maintaining communication structure simplicity.
3Ease of operation
If the steering server does not consider CDN status updates, then the system is easier to operate, but it cannot optimize for both QoE and CDN capacity leading to suboptimal performance
Solution Approach 1:
The patent segments the load balancing decision-making process into distinct components: QoE-based routing decisions and CDN capacity-based adjustments. The steering server maintains simple QoE report processing while separately incorporating CDN status information, allowing operational simplicity to be preserved while improving reliability through segmented, modular integration of multiple optimization criteria without requiring complete system redesign.
Data Source
AI summary
Techniques for multi-Content Delivery Network (CDN) load balancing are performed at a content steering server in a multi-CDN system, where the multi-CDN system includes a plurality of CDNs serving a plurality of clients. The content steering server receives from a first CDN of the plurality of CDNs a request to switch a first number of clients in the multi-CDN system. In response to receiving the request, the content steering server facilitates negotiations between the first CDN and at least one CDN of the plurality of CDNs, including determining a second number of clients in the multi-CDN system to be switched. Upon successful negotiations, the content steering server triggers the first CDN and the at least one CDN to switch the second number of clients between the first CDN and the at least one CDN.