Latency Measurement in CDN Resource Requests
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Content delivery networks (CDNs) face challenges in efficiently managing and measuring latency in resource requests across distributed computing devices, which affects service quality and compliance with service level agreements.
Innovation Solution
Implementing a system where client computing devices are provided with executable code that generates resource requests to different computing devices within the CDN's domain, allowing for the measurement of latency by processing responses and protocol interactions, enabling the CDN service provider to determine performance metrics and optimize resource delivery.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If CDN service providers maintain multiple computing devices to deliver content to high volumes of clients, then content delivery capacity and service coverage are improved, but system complexity and difficulty in measuring latency across distributed devices increase
Solution Approach 1:
The patent introduces a timing marker as an intermediary element that is embedded in content requests and responses. This timing marker serves as a mediator that carries latency measurement information between client computing devices and CDN computing devices, enabling centralized latency measurement without requiring complex distributed measurement infrastructure across all CDN nodes.
Solution Approach 2:
The system implements feedback by having client computing devices send timing information back to the CDN service provider along with resource requests. The CDN service provider receives this feedback containing latency data and uses it to measure and optimize delivery performance, creating a closed-loop system for continuous improvement.
2Reliability
If CDN service providers track latency across multiple computing devices to meet service level agreements, then service quality and compliance are improved, but measurement precision and reliability of latency data decrease due to system complexity
Solution Approach 1:
The timing marker acts as a standardized intermediary that ensures consistent latency measurement across all CDN computing devices. By embedding this specific timing marker in requests and responses, the system achieves reliable and precise latency measurements that can be consistently tracked against service level agreements.
Solution Approach 2:
The timing marker serves multiple functions: it acts as a request identifier, a timestamp for latency calculation, and a correlation key between requests and responses. This multi-functionality simplifies the measurement system while improving reliability and precision across the distributed CDN infrastructure.
3Measurement precision
If client computing devices are provided executable code to generate resource requests for latency measurement, then latency measurement capability is improved, but device complexity and processing overhead increase
Solution Approach 1:
The patent uses timing markers that are copied and embedded within existing content request structures. Rather than creating entirely new complex measurement protocols, the system copies timing information into standard request formats, minimizing client device processing overhead while maintaining measurement precision.
Solution Approach 2:
The latency measurement functionality is merged with the existing content request process. The timing marker is combined with the resource request identifier, and the latency measurement is integrated into the normal request-response flow, eliminating the need for separate measurement protocols and reducing client device complexity.
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, a client computing device can execute code, such as scripts, that cause the client computing device to transmit requests to different computing devices associated with the CDN service provider's domain. Information associated with the processing of the responses can be used to measure CDN service provider latencies.