CDN Latency Measurement via Client-Triggered Resource Requests
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Content providers and CDN service providers face challenges in efficiently managing and measuring latency in resource requests, particularly when handling high volumes of requests from multiple client devices, which can strain computing resources and impact service quality.
Innovation Solution
Implementing a system where CDN service providers measure latency by generating executable code that causes client computing devices to transmit resource requests to different computing devices within their domain, allowing for the collection and processing of performance metric information, including latency data, through embedded resource identifiers and protocol interactions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If CDN service providers maintain multiple computing devices to handle high volume requests, then service capacity and availability are improved, but computing resource strain and operational complexity increase
Solution Approach 1:
The patent segments the CDN infrastructure into multiple distributed computing devices (Points of Presence) geographically dispersed across different locations. Each PoP independently handles requests from nearby clients, dividing the overall system load into manageable segments. This segmentation allows high service capacity through parallel processing while keeping individual device complexity low.
Solution Approach 2:
The patent introduces a new dimension of measurement - latency-based performance metrics - to manage and optimize the CDN network. By measuring and analyzing latency across different PoPs and routing requests accordingly, the system can handle high volumes efficiently without proportionally increasing operational complexity, as decisions are made based on quantitative latency data rather than manual management.
2Adaptability or versatility
If embedded resource identifiers are used to reference content provider devices, then content delivery flexibility is improved, but latency measurement difficulty increases
Solution Approach 1:
The patent introduces CDN PoPs as intermediary nodes between clients and content provider devices. These intermediaries receive requests with embedded resource identifiers, measure latency to the ultimate content provider, and handle the complexity of content delivery. This allows flexible content delivery through multiple paths while the intermediary systematically measures and reports latency, making measurement manageable despite the complexity introduced by embedded identifiers.
Solution Approach 2:
The patent performs preliminary latency measurement at the CDN PoP level before requests reach the final content provider. By measuring latency early in the request chain and using this data for routing decisions, the system maintains delivery flexibility through various PoP paths while simplifying the measurement process - latency is measured once at the CDN edge rather than attempting to measure through multiple embedded identifier resolutions.
3Measurement precision
If latency measurement is implemented through resource requests, then performance monitoring capability is improved, but computing resource consumption increases
Solution Approach 1:
The patent makes CDN PoPs multi-functional by having them simultaneously handle content delivery and perform latency measurement tasks. The same infrastructure that delivers content also measures performance metrics by analyzing request-response timing. This eliminates the need for separate measurement systems, providing precise performance monitoring without proportionally increasing computing resource consumption, as the measurement function is embedded within existing operational workflows.
Data Source
AI summary
Systems and method for the management and processing of resource requests by a service provider, such as a content delivery network (“CDN”) service provider, on behalf of a content provider are provided. The CDN service provider can measure the performance associated with the delivery of resources to a requesting client computing devices from various computing devices associated with the CDN service provider. In one embodiment, the CDN service provider can utilize commands responsive to an initial request for a resource that causes the requesting client computing device to transmit one or more supplemental resource requests. Information associated with the processing of the sequence of resource requests can be used to measure CDN service provider latencies.