# US 2026/0149635 A1 · Telemetry standardization for multi-configuration protocols

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0149635 A1
- Document ID: US20260149635A1
- Status: Published application
- Kind: A1
- Application number: 19/316,991
- Filed: 2025-09-02
- Published: 2026-05-28
- Earliest claimed: 2024-11-26
- Assignees: Mellanox Technologies, Ltd.
- Applicants: Mellanox Technologies, Ltd.
- Inventors: Siddanagouda Khot
- Web page: https://patentgrep.com/patent/US20260149635A1

## CPC

- H04L 41/0803: Configuration setting
- H04L 45/52: Multiprotocol routers
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A network, one or more circuits, or a method disclosed herein may include or be associated with one or more network devices for standardizing telemetry in the network. The network may be adapted to handle different network configuration protocols and different telemetry protocols using a routing process and a telemetry process provided for the network. The routing process may allow generation of telemetry data for the different network configuration protocols. The telemetry process may allow repackaging of the telemetry data to be specific to at least one of the network configuration protocols and to at least one of the different telemetry protocols.

## Claims

### Claim 1

A network comprising one or more network devices configured to handle different network configuration protocols and different telemetry protocols, the one or more network devices associated with a routing process and with a telemetry process, wherein the routing process allows generation of telemetry data for the different network configuration protocols, and wherein the telemetry process allows repackaging of the telemetry data to be specific to at least one of the different network configuration protocols and to at least one of the different telemetry protocols.

### Claim 2 (depends on 1)

The network of claim 1, wherein the different network configuration protocols comprise BGP (Border Gateway Protocol), OSPF (Open Shortest Path First), RIP (Routing Information Protocol), IS-IS (Intermediate System-to-Intermediate System), PIM (Protocol Independent Multicast), LDP (Label Distribution Protocol), BFD (Bidirectional Forwarding Detection), Babel, PBR (Policy-Based Routing), OpenFabric, or VRRP (Virtual Router Redundancy Protocol), and wherein the different telemetry protocols comprise OpenTelemetry (OTEL) or gRPC Network Management Interface (gNMI).

### Claim 3 (depends on 1)

The network of claim 1, wherein the one or more network devices comprises a Linux operating system and wherein the routing process is Free Range Routing (FRR).

### Claim 4 (depends on 1)

The network of claim 1, wherein the routing process and the telemetry process are configured for communication using gRPC.

### Claim 5 (depends on 1)

The network of claim 1, further comprising one or more of a telemetry agent or a user experience interface, the telemetry agent or the user experience interface to provide subscription requests associated with the telemetry data to the telemetry process.

### Claim 6 (depends on 5)

The network of claim 5, wherein the telemetry process is configured to repackage the subscription requests with gRPC for the routing process.

### Claim 7 (depends on 6)

The network of claim 6, wherein the routing process is associated with a library of the different network configuration protocols to provide a native format of the telemetry data to the telemetry process.

### Claim 8 (depends on 7)

The network of claim 7, wherein the telemetry process is to repackage the telemetry data from the native format to a format specific to the at least one of the different telemetry protocols.

### Claim 9 (depends on 1)

The network of claim 1, wherein the telemetry process is to perform a health check for the routing process, wherein the routing process comprises an identifier which is subject to changes upon restarting the routing process, wherein the health check is to determine that the identifier has changed, and wherein the telemetry process is to repeat at least one subscription request for the telemetry data by reading the at least one subscription request from a configuration file and performing the repackaging of the telemetry data to be specific to the at least one of the different network configuration protocols and the at least one of the different telemetry protocols.

### Claim 10

One or more circuits configured to handle different network configuration protocols of a network and to handle different telemetry protocols, the one or more circuits associated with a routing process and with a telemetry process, wherein the routing process allows generation of telemetry data for the different network configuration protocols, and wherein the telemetry process allows repackaging of the telemetry data to be specific to at least one of the different network configuration protocols and to at least one of the different telemetry protocols.

### Claim 11 (depends on 10)

The one or more circuits of claim 10, wherein the one or more circuits are configured for one or more of: execution of a Linux operating system, routing using Free Range Routing (FRR), and communication using gRPC between the routing process and the telemetry process.

### Claim 12 (depends on 10)

The one or more circuits of claim 10, further comprising one or more of a telemetry agent or a user experience interface, the telemetry agent or the user experience interface to provide subscription requests associated with the telemetry data to the telemetry process.

### Claim 13 (depends on 10)

The one or more circuits of claim 10, further comprising one or more of: a library, of the routing process, comprising the different network configuration protocols to provide a native format of the telemetry data to the telemetry process; or configuration, of the telemetry process, to repackage the telemetry data from the native format to a format specific to the at least one of the different telemetry protocols.

### Claim 14 (depends on 10)

The one or more circuits of claim 10, wherein the telemetry process is to perform a health check for the routing process, wherein the routing process comprises an identifier which is subject to changes upon restarting the routing process, wherein the health check is to determine that the identifier has changed, and wherein the telemetry process is to repeat at least one subscription request for the telemetry data by reading the at least one subscription request from a configuration file and performing the repackaging of the telemetry data to be specific to the at least one of the different network configuration protocols and the at least one of the different telemetry protocols.

### Claim 15

A method for telemetry standardization, comprising:
handling, using one or more network devices in a network, different network configuration protocols and different telemetry protocols associated with telemetry in the network;
generating, by a routing process of the one or more network devices, telemetry data for the different network configuration protocols; and
repackaging, by a telemetry process of the one or more network devices, the telemetry data to be specific to at least one of the different network configuration protocols and to at least one of the different telemetry protocols.

### Claim 16 (depends on 15)

The method of claim 15, further comprising one or more of:
using one or more of OpenTelemetry (OTEL) or gRPC Network Management Interface (gNMI) as the different telemetry protocols;
using BGP (Border Gateway Protocol), OSPF (Open Shortest Path First), RIP (Routing Information Protocol), IS-IS (Intermediate System-to-Intermediate System), PIM (Protocol Independent Multicast), LDP (Label Distribution Protocol), BFD (Bidirectional Forwarding Detection), Babel, PBR (Policy-Based Routing), OpenFabric, or VRRP (Virtual Router Redundancy Protocol) as the different network configuration protocols;
executing a Linux operating system in the one or more network devices; or
using Free Range Routing (FRR) for the routing process.

### Claim 17 (depends on 15)

The method of claim 15, further comprising:
using gRPC for communications between the routing process and the telemetry process.

### Claim 18 (depends on 15)

The method of claim 15, further comprising:
allowing subscription requests to be received in the telemetry process through a telemetry agent or a user experience interface;
repackaging, by the telemetry process, the subscription requests for gRPC with respect to the routing process; and
generating the telemetry data in the routing process based in part on the subscription requests, wherein the routing process is associated with a library of the different network configuration protocols to provide a native format of the telemetry data to the telemetry process.

### Claim 19 (depends on 18)

The method of claim 18, further comprising:
repackaging, by the telemetry process, the telemetry data from the native format to a format specific to the at least one of the different network configuration protocols and the at least one of the different telemetry protocols.

### Claim 20 (depends on 18)

The method of claim 18, further comprising
allowing the routing process to comprise an identifier which is subject to changes upon restarting the routing process;
performing, by the telemetry process, a health check for the routing process;
determining, as part of the health check, that the identifier has changed;
repeating, by the telemetry process, at least one subscription request for the telemetry data by reading the at least one subscription request from a configuration file; and
performing the repackaging of the telemetry data to be specific to the at least one of the different network configuration protocols and the at least one of the different telemetry protocols.
