Content-Based Network Latency Measurement for Route Selection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing technologies face challenges in efficiently measuring, collating, and comparing network latencies, leading to suboptimal routing of network traffic and increased computing resource consumption.
Innovation Solution
A system and method that utilizes a client device to send requests for content via multiple routes with a common identifier, allowing for latency measurement and comparison, and uses a route module to select the lowest-latency route for future requests.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If network latency is measured using traditional methods with separate measurement packets, then measurement capability is provided, but network overhead increases and measurement precision deteriorates due to additional traffic
Solution Approach 1:
The patent combines latency measurement functionality with regular content delivery by embedding measurement data in HTTP headers and using existing content request/response traffic for measurement purposes. This merges two functions (content delivery and latency measurement) into a single integrated process, eliminating the need for separate measurement packets and reducing network overhead while maintaining measurement precision
2Speed
If multiple routes are tested to find the optimal path, then routing optimization improves, but time consumption increases due to repeated measurements
Solution Approach 1:
The patent performs latency measurements for multiple routes in advance during initial content delivery operations, storing the results for future routing decisions. This preliminary measurement approach allows the system to have routing optimization data ready before actual traffic needs to be routed, eliminating the need for repeated real-time measurements and reducing time consumption while maintaining routing efficiency
Solution Approach 2:
The patent reuses existing content request and response traffic copies for latency measurement purposes. By leveraging the necessary traffic that must occur for content delivery anyway, the system can measure latency without generating additional measurement traffic, thus avoiding time consumption from repeated measurements while achieving routing optimization
3Measurement precision
If comprehensive latency data is collected from multiple sources, then analysis accuracy improves, but data processing complexity increases
Solution Approach 1:
The patent introduces an intermediary component that standardizes and normalizes latency data from multiple sources before analysis. This intermediary layer handles data formatting, validation, and preprocessing, which simplifies the subsequent analysis process by presenting standardized data structures. This approach maintains analysis accuracy from comprehensive data collection while reducing processing complexity through systematic data preparation
Data Source
AI summary
Deploying a point of presence (PoP) changes traffic flow to a cloud service provider. To determine if the PoP improves the performance of a cloud service to a client, actual network latencies between the client and the cloud service are measured. In more complex scenarios, multiple PoPs are used. The client sends multiple requests for the same content to the cloud provider. The requests are sent via different routes. The cloud provider serves the requests and collates the latency information. Based on the latency information, a route for a future request is selected, resources are allocated, or a user interface is presented. The process of determining the latency for content delivered by different routes may be repeated for content of different sizes. A future request is routed along the network path that provides the lowest latency for the data being requested.