In-Flight Telemetry Data Routing for Network Devices

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Pushing telemetry data from network devices to multiple recipients can negatively impact the performance of resource-constrained network devices due to low CPU power and memory limitations, leading to reduced operating efficiency.

Innovation Solution

Telemetry data is routed in-flight to multiple receivers without being stored in a storage device, using a duplication policy to identify and format the data streams for each receiver, and a receiver destination policy to ensure secure and efficient delivery, thereby mitigating security risks, processing overhead, and latency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If telemetry data is pushed from network device to multiple recipients, then data delivery function is achieved, but network device performance deteriorates due to CPU and memory constraints

Engineering Contradiction:
Improvedata delivery efficiencyVSAvoidnetwork device CPU power
Core Design Contradiction:
ProductivityVSPower

Solution Approach 1:

The patent extracts the data storage and distribution function from the network device to an external storage device. The network device only pushes data to the storage device, which then handles distribution to multiple recipients. This removes the burden of managing multiple data copies and subscriptions from the resource-constrained network device, resolving the contradiction between data delivery capability and CPU power consumption.

Inventive Principle:
Principle #2Taking out (Extraction)

2Adaptability or versatility

If telemetry data is stored in storage device for processing, then data distribution to multiple receivers is enabled, but security risks and processing overhead increase

Engineering Contradiction:
Improvedata distribution capabilityVSAvoidsecurity risks
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent applies preliminary action by having the network device push data to the storage device in advance, where it is stored in a standardized format. This preliminary storage action enables the storage device to subsequently distribute data to multiple receivers without requiring the network device to perform multiple push operations. The data is processed and distributed from the storage device rather than being repeatedly handled by the network device, reducing security risks and processing overhead.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If telemetry data is pushed to multiple recipients directly from network device, then data origin integrity is maintained, but operating efficiency of network device reduces

Engineering Contradiction:
Improvedata origin integrityVSAvoidnetwork device operating efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent introduces an intermediary storage device between the network device and multiple recipients. The storage device acts as a mediator that receives data from the network device and distributes it to recipients. This intermediary approach maintains data origin integrity because the storage device preserves the original data format and metadata from the network device, while simultaneously improving network device operating efficiency by eliminating the need for it to directly manage multiple data distribution channels.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS8953600B2Telemetry data routing
Publication Date: 2015.02.10 MICROSOFT TECHNOLOGY LICENSING LLC
  • US8953600B2 patent drawing
  • US8953600B2 patent drawing
  • US8953600B2 patent drawing

AI summary

Among other things, one or more techniques and/or systems are provided for routing telemetry data to one or more receivers. That is, telemetry data, such as activity data associated with a network device (e.g., a switch, a router, etc.), may be routed to one or more receivers in-flight (e.g., while the telemetry data is being processed by a network device, as opposed to being stored within a storage device for processing). In one example, telemetry data may be forked into a first telemetry data stream for a first receiver, a second telemetry data stream for a second receiver, and/or other telemetry data streams. Respective telemetry data streams may be formatted according to a receiver destination policy. In this way, one or more telemetry data streams, forked from the telemetry data in-flight, may be delivered to one or more receivers in-flight.