Telemetry Error Detection Using Context Timestamps

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing telemetry systems face inefficiencies in detecting errors in event records due to delayed context entries, leading to incorrect device associations and wastage of computing and network resources, especially in cases of malicious activity.

Innovation Solution

A network device with a telemetry data analyzer that uses a lookup table and timestamps to quickly identify erroneous event records by comparing context entries with stored timestamps, allowing for immediate detection and correction of errors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If batch processing is used to detect errors in event records, then detection thoroughness is improved, but detection time is significantly delayed (days or weeks)

Engineering Contradiction:
Improveerror detection thoroughnessVSAvoiddetection delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by maintaining a lookup table with context information and timestamps before event records are fully processed. When context entries arrive, the system immediately checks the lookup table for timestamp consistency, enabling real-time error detection without waiting for batch processing to complete. This proactive approach prevents erroneous records from being stored or analyzed further.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If real-time error detection is implemented using timestamps and lookup tables, then detection speed is improved, but device complexity increases

Engineering Contradiction:
Improveerror detection speedVSAvoidsystem structure complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces a lookup table as an intermediary data structure that stores context information and timestamps. This intermediary component enables real-time comparison between arriving context entries and previously stored data, facilitating fast error detection without requiring complex real-time processing logic. The lookup table acts as a buffer that simplifies the detection mechanism while maintaining high speed.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Loss of energy

If context entries are processed immediately upon arrival, then resource wastage is reduced, but processing complexity increases

Engineering Contradiction:
Improvecomputing resource wastageVSAvoidprocessing logic complexity
Core Design Contradiction:
Loss of energyVSDevice complexity

Solution Approach 1:

The system applies self-service by automatically checking each context entry against the lookup table upon arrival, without requiring manual intervention or complex batch processing workflows. The timestamp comparison mechanism autonomously identifies erroneous records, flags them for exclusion, and prevents waste of computing resources on invalid data. This automated self-checking approach reduces resource wastage while keeping processing logic relatively simple.

Inventive Principle:
Principle #25Self-service

Data Source

PatentEP4198762B1Telemetry data error detection
Publication Date: 2026.02.11 JUNIPER NETWORKS INC
  • EP4198762B1 patent drawingFigure 1A
  • EP4198762B1 patent drawingFigure 1B
  • EP4198762B1 patent drawingFigure 2

AI summary

A device may receive a first telemetry data entry associated with an attribute and store a record associated with the first telemetry data entry, wherein the record identifies a first context value associated with the attribute. The device may log a first timestamp of the first telemetry data entry in a lookup table, wherein the lookup table includes a mapping of the attribute to the first context value and to the first timestamp. The device may receive a second telemetry data entry associated with the attribute and may determine, from the mapping, that the second telemetry data entry is associated with a second context value that is different from the first context value. The device may determine whether a second timestamp, of the second telemetry data entry, is before the first timestamp. The device may perform an action based on whether the second timestamp is before the first timestamp.