# US 12,113,700 B2 · Method and apparatus for telemetry monitoring of BGP prefixes in a network topology

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

- Number: US 12,113,700 B2
- Document ID: US12113700B2
- Status: Granted
- Kind: B2
- Application number: 18/084,828
- Filed: 2022-12-20
- Published: 2024-06-20
- Granted: 2024-10-08
- Earliest claimed: 2022-12-20
- Assignees: Arrcus Inc.
- Applicants: Arrcus Inc.
- Inventors: Lakshman Swaroop Babu; Ting-Chi Yeh; Alpesh Patel; Keyur Patel
- Web page: https://patentgrep.com/patent/US12113700B2

## CPC

- H04L 45/22: {Alternate routing}
- H04L 45/02: Topology update or discovery
- H04L 45/033: by updating distance vector protocols
- H04L 45/24: Multipath
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Telemetry monitoring of BGP prefixes in a network topology. A method includes receiving a route for a network topology and determining whether the route corresponds with an existing route stored on a route store. The method includes determining whether any network routing paths have been modified between the existing route and the route in response to determining the route corresponds with the existing route. The method includes generating a path configuration key for each of the at least one network routing path in response to determining at least one network routing path was modified between the existing route and the route.

## Claims

### Claim 1

A method comprising:
receiving a route for a network topology;
determining whether the route corresponds with an existing route stored on a route store;
in response to determining the route corresponds with the existing route, determining whether any network routing paths have been modified between the existing route and the route; and
in response to determining at least one network routing path was modified between the existing route and the route, generating a path configuration key for each of the at least one network routing path.

### Claim 2 (depends on 1)

The method of claim 1, wherein receiving the route for the network topology comprises receiving an update directly from an input topic stream that is dedicated to receiving updated route information for the network topology.

### Claim 3 (depends on 1)

The method of claim 1, wherein determining whether the route corresponds with the existing route stored on the route store comprises determining based on data associated with the route, and wherein the data comprises one or more of a prefix, a virtual routing and forwarding (VRF) address, or a device.

### Claim 4 (depends on 1)

The method of claim 1, further comprising receiving an ADD or DELETE operation associated with the route, and wherein the method further comprises updating the route store in accordance with the ADD or the DELETE operation.

### Claim 5 (depends on 4)

The method of claim 4, further comprising, in response to the route being associated with the ADD operation; and
further in response to identifying the existing route on the route store, updating the route store to UPDATE the existing route to reflect the route; or
further in response to determining there is no existing route stored on the route store that corresponds with the route, updating the route store to ADD the route.

### Claim 6 (depends on 4)

The method of claim 4, further comprising, in response to the route being associated with the DELETE operation; and
further in response to identifying the existing route on the route store, updating the route to DELETE the existing route; or
further in response to determining there is no existing route stored on the route store that corresponds with the route, ending processing operations associated with the route.

### Claim 7 (depends on 1)

The method of claim 1, wherein determining whether any network routing paths have been modified between the existing route and the route comprises:
determining whether any routing path that is not present within the existing route has been added to the route;
determining whether any routing path present in the existing route has been modified within the route; and
determining whether any routing path present in the existing route has been withdrawn in the route.

### Claim 8 (depends on 1)

The method of claim 1, wherein the path configuration key comprises one or more of a device identifier, a Border Gateway Protocol (BGP) path attribute type, or a BGP path attribute value.

### Claim 9 (depends on 1)

The method of claim 1, wherein the path configuration key comprises an indication of one or more BGP prefixes to be tracked.

### Claim 10 (depends on 1)

The method of claim 1, wherein generating the path configuration key comprises generating a plurality of path configuration keys, and wherein each of the plurality of path configuration keys is associated with at least one network routing path that has been added, modified, or deleted between the existing route and the route.

### Claim 11 (depends on 10)

The method of claim 10, further comprising identifying at least one path configuration key of the plurality of path configuration keys that matches configuration data for the new path, wherein the configuration data is stored in a configuration store.

### Claim 12 (depends on 11)

The method of claim 11, wherein the configuration store comprises attributes associated with the new path, and wherein the attributes comprise one or more of an extended community attribute, a community attribute, or a prefix attribute.

### Claim 13 (depends on 1)

The method of claim 1, further comprising determining whether the route should be tracked based on user input.

### Claim 14 (depends on 13)

The method of claim 13, further comprising:
in response to determining the route should be tracked, determining whether the route is already stored on a prefix tracker store; and
in response to determining the route is not already stored on the prefix tracker store, writing to the prefix tracker store to include the route.

### Claim 15 (depends on 14)

The method of claim 14, further comprising:
processing the path configuration key for each of the at least one network routing path; and
writing to the prefix tracker store to include the path configuration key for each of the at least one network routing path.

### Claim 16 (depends on 15)

The method of claim 15, further comprising detecting a route purge in response to determining that at least one element of the route has been deleted from the prefix tracker store.

### Claim 17 (depends on 1)

The method of claim 1, wherein receiving the route for the network topology comprises receiving an update via a stream within a real-time streaming framework.

### Claim 18 (depends on 1)

The method of claim 1, wherein the route store is a stream store in communication with a route processor, and wherein the route processor is in communication with a plurality of input topic streams that receive data in real-time.

### Claim 19 (depends on 1)

The method of claim 1, wherein receiving the route for the network topology further comprises identifying an operation associated with the route, and wherein the operation comprises one of ADD, DELETE, or UPDATE.

### Claim 20 (depends on 1)

The method of claim 1, wherein the method is performed by a prefix tracker application operated on one or more servers associated with a network platform configured to manage, analyze, and visualize a network topology.