Inband Telemetry Flow Aggregation for Collector Load Reduction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Inband telemetry collectors become overwhelmed due to the need to process telemetry data from each packet received from multiple INT nodes, leading to processing capability burdens and inefficiencies.
Innovation Solution
Implementing an inband telemetry system where network devices report aggregated flow-specific telemetry metrics instead of individual packet data, using flow tables to compute and store metrics, and periodically transmitting these metrics to the collector, thereby reducing the data load on the collector.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If telemetry data from each packet is reported to the collector, then measurement precision is improved, but the collector becomes overwhelmed and processing capability is burdened
Solution Approach 1:
The patent combines multiple individual packet telemetry reports into aggregated flow-based telemetry metrics. Instead of reporting each packet's telemetry data separately to the collector, the system aggregates telemetry data from multiple packets belonging to the same flow and reports combined metrics (such as average latency, packet loss rates, or other statistical measures) periodically. This merging approach maintains measurement precision by preserving flow-level telemetry information while dramatically reducing the collector's processing burden by consolidating numerous individual reports into fewer aggregated reports.
2Quantity of substance
If individual packet telemetry data is transmitted, then data completeness is improved, but data load on the collector increases
Solution Approach 1:
The patent applies preliminary aggregation action at the telemetry reporting node before data is transmitted to the collector. The system pre-processes telemetry data by grouping packets into flows and computing aggregated metrics (such as average latency, jitter, packet loss percentages, or other statistical measures) locally at the reporting node. This preliminary action reduces the volume of data that needs to be transmitted to and processed by the collector, while still maintaining complete and accurate flow-level telemetry information. The aggregation is performed in advance, so the collector receives ready-to-analyze summarized data rather than raw individual packet telemetry records.
3Productivity
If flow-based aggregated metrics are reported, then collector processing burden is reduced, but individual packet telemetry detail is lost
Solution Approach 1:
The patent changes the parameter representation of telemetry data from individual packet-level measurements to flow-level aggregated statistical parameters. Instead of transmitting raw telemetry data for each packet (which would preserve complete detail but overwhelm the collector), the system transforms the data into meaningful statistical parameters such as average latency, maximum latency, minimum latency, jitter (standard deviation of latency), packet loss rates, and other flow-level metrics. This parameter transformation maintains the essential telemetry information needed for network performance monitoring and analysis while dramatically reducing data volume. The aggregated parameters capture the critical characteristics of packet flows without requiring transmission of every individual packet's telemetry data.
Data Source
AI summary
Methods and systems are described for inband telemetry. The system receives a plurality of packets, each packet comprising a portion with INT data. The system identifies a packet flow from a source device to a destination device in the plurality of packets and calculates a telemetry metric based on INT data of a plurality of packets of the packet flow. Then the system forwards the calculated telemetry metric to an INT collector.


