Multicast Latency Monitoring via Sequence Number Timing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods lack a simple, inexpensive, and real-time or near real-time capability to monitor and calculate latency in multicast communications, which is crucial for diagnosing and resolving communication issues, especially in financial markets where low latency is premium.
Innovation Solution
The method involves monitoring sequence numbers of multicast messages at multiple physical network locations and using a latency determination server to generate indications of relative latencies and time-based data locations by tracking the arrival times of these sequence numbers, allowing for passive monitoring and real-time latency calculation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If traditional sequence number analysis methods are used to detect packet loss, then packet loss detection is achieved, but latency monitoring capability is not provided
Solution Approach 1:
The patent makes the existing sequence number analysis infrastructure multi-functional by enabling it to perform both its original function (packet loss detection) and a new function (latency monitoring). The sequence number analysis units continue to detect packet loss while simultaneously capturing timing information for latency calculation, eliminating the need for separate monitoring equipment.
Solution Approach 2:
The monitoring system uses its own operational data (sequence number reception timing) to generate latency measurements. The sequence number analysis units that are already processing data for packet loss detection automatically capture and report timing information, making the system self-sufficient for latency monitoring without requiring external monitoring devices.
2Loss of time
If dedicated latency monitoring equipment is deployed, then real-time latency detection is achieved, but system cost and complexity increase
Solution Approach 1:
Existing network equipment is made multi-functional to perform both data processing and latency monitoring. The sequence number analysis units in the multicast network continue their primary function while simultaneously providing timing data for latency calculation, eliminating the need for dedicated monitoring hardware.
Solution Approach 2:
The patent uses the existing sequence number metadata as an intermediary carrier of timing information. Rather than deploying new equipment, the system leverages the sequence numbers that are already embedded in multicast packets to convey arrival time information to the latency determination server.
3Measurement precision
If comprehensive latency monitoring is implemented across all network locations, then real-time latency visibility is achieved, but data processing complexity increases
Solution Approach 1:
The patent extracts only the essential timing information (when specific sequence numbers arrive at each location) from the full data stream, rather than analyzing complete packet contents. The sequence number analysis units extract arrival timestamps for reported sequence numbers, and the latency determination server uses only these extracted timing data points to calculate latency, minimizing processing complexity.
Solution Approach 2:
The system monitors a subset of sequence numbers (those that are reported based on predetermined criteria) rather than analyzing every single packet. This partial monitoring approach provides sufficient latency measurement capability while reducing the processing burden compared to comprehensive full-stream analysis.
Data Source
AI summary
Methods, systems, and computer readable media for monitoring latency and/or time-based data locations of multicast communications are disclosed. One exemplary method includes monitoring sequence numbers of multicast messages at a plurality of physical network locations, reporting when a sequence number value for the multicast messages reaches a predetermined value, and receiving the reports and using the reports to generate an indication of relative latencies and/or time-based data locations across the physical network locations.