CDN Latency Measurement via Embedded Client Code
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Content providers and CDN service providers face challenges in 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 delivery efficiency and cost considerations.
Innovation Solution
Implementing a system where CDN service providers measure latency by generating and processing resource requests through executable code and protocol interactions, allowing for the collection of performance metrics and latency determination across multiple Points of Presence, enabling efficient resource delivery and service optimization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If CDN service providers maintain multiple computing devices to handle high volumes of resource requests, then the ability to serve more clients improves, but the strain on computing resources and operational costs worsen
Solution Approach 1:
The system enables self-service through automated latency measurement and reporting mechanisms. Client computing devices automatically execute embedded code to measure latency, and CDN service providers automatically process this data to identify performance issues, reducing the need for manual intervention and extensive computing resources
Solution Approach 2:
The patent implements preliminary action by embedding latency measurement code in advance within resource responses. This pre-positioned code automatically executes when clients receive resources, performing measurements before the CDN needs to analyze performance data, thus reducing real-time computing strain
2Adaptability or versatility
If embedded resource identifiers are used to reference content provider computing devices, then resource delivery flexibility improves, but latency measurement difficulty worsens
Solution Approach 1:
The patent introduces an intermediary mechanism by embedding measurement code within the resource responses themselves. This embedded code acts as a mediator that automatically captures latency data between the client and CDN, eliminating the need for complex external measurement systems while maintaining delivery flexibility
Solution Approach 2:
The embedded measurement code serves multiple functions: it delivers resources normally while simultaneously measuring latency, reporting performance data, and enabling flexible resource routing. This multi-functionality resolves the contradiction by making the same mechanism serve both delivery and measurement purposes
3Reliability
If CDN service providers process performance metrics from multiple Points of Presence, then service level agreement compliance improves, but system complexity worsens
Solution Approach 1:
The system segments latency measurement operations at each individual Point of Presence, with local embedded code executing measurements independently. Each POP processes and reports its own performance data separately, avoiding the need for a complex centralized measurement system while ensuring reliable compliance monitoring across all locations
Data Source
AI summary
Systems and method for the management and processing resource of 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 requesting client computing devices from various computing devices associated with the CDN service provider. In one embodiment, the CDN service provider can utilize commands correspond to communication protocols that causes the requesting client computing device to transmit or receive protocol information from multiple computing devices associated with the CDN service provider's domain. Information associated with the processing of the protocol responses can be used to measure CDN service provider latencies.