# US 2024/0205138 A1 · Systems and methods for determining problematic paths between interest points in a multi-cloud environment

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

- Number: US 2024/0205138 A1
- Document ID: US20240205138A1
- Status: Published application
- Kind: A1
- Application number: 18/589,837
- Filed: 2024-02-28
- Published: 2024-06-20
- Earliest claimed: 2021-07-30
- Assignees: Cisco Technology, Inc.
- Applicants: Cisco Technology, Inc.
- Inventors: Vijay Kumar Devendran; Kiran Kumar Meda; Rajagopalan Janakiraman; Shyam N. Kapadia; Javed Asghar
- Web page: https://patentgrep.com/patent/US20240205138A1

## CPC

- H04L 41/0677: Localisation of faults
- H04L 45/22: {Alternate routing}
- H04L 43/0829: Packet loss
- H04L 43/0852: Delays
- H04L 43/0858: {One way delays}
- H04L 43/087: Jitter
- H04L 43/091: Measuring contribution of individual network components to actual service level
- H04L 43/10: Active monitoring, e.g. heartbeat, ping or trace-route
- H04L 43/12: Network monitoring probes
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

In one embodiment, a method includes identifying a problematic event between a first interest point and a second interest point of a network and activating, in response to identifying the problematic event between the first interest point and the second interest point, a first endpoint associated with the first interest point and a second endpoint associated with the second interest point. The method also includes receiving, from the first endpoint and the second endpoint, telemetry data associated with a problematic path between the first interest point and the second interest point. The method further includes determining the problematic path between the first interest point and the second interest point using the telemetry data received from the first endpoint and the second endpoint.

## Claims

### Claim at position 1

-20. (canceled)

### Claim 21

A network component, comprising:
one or more processors; and
one or more computer-readable non-transitory storage media coupled to the one or more processors and comprising instructions that, when executed by the one or more processors, cause the network component to perform operations comprising:
identifying a problematic event between a first interest point and a second interest point of a network;
activating a first endpoint associated with the first interest point and a second endpoint associated with the second interest point, wherein:
activating the first endpoint and the second endpoint initiates a generation of Operations, Administration, and Maintenance (OAM) out-of-band data packets by the first endpoint and the second endpoint; and
each of the OAM out-of-band data packets uses an OAM packet format, the OAM packet format comprising:
a Media Access Control (MAC) header;
an EtherType;
an Internet Protocol (IP) header;
a User Datagram Protocol (UDP) header;
at least one cloud OAM option; and
a Cyclic Redundancy Check (CRC);
receiving, from the first endpoint and the second endpoint, telemetry data associated with a problematic path between the first interest point and the second interest point; and
determining the problematic path between the first interest point and the second interest point using the telemetry data received from the first endpoint and the second endpoint, wherein the telemetry data is collected by the OAM out-of-band data packets.

### Claim 22 (depends on 21)

The network component of claim 21, wherein the telemetry data comprises an identity of one or more cloud providers.

### Claim 23 (depends on 21)

The network component of claim 21, wherein each of the first interest point and the second interest point are associated with one of the following:
a public cloud;
a private cloud; or
an on-premise data center.

### Claim 24 (depends on 21)

The network component of claim 21, wherein the problematic event is associated with at least one of the following network characteristics:
latency;
jitter; or
packet drop.

### Claim 25 (depends on 21)

The network component of claim 21, wherein the at least one cloud OAM option comprises a cloud OAM option type, a cloud OAM provider ID, and cloud OAM option data.

### Claim 26 (depends on 21)

The network component of claim 21, the operations further comprising:
activating one or more cloud agents within the network;
receiving, from the one or more cloud agents, additional telemetry data associated with the problematic path between the first interest point and the second interest point; and
computing the problematic path between the first interest point and the second interest point using the additional telemetry data received from the one or more cloud agents.

### Claim 27 (depends on 21)

The network component of claim 21, the operations further comprising instructing one or more transit routers within the network to redirect an identified traffic flow to a cloud agent.

### Claim 28

A method, comprising:
identifying a problematic event between a first interest point and a second interest point of a network;
activating a first endpoint associated with the first interest point and a second endpoint associated with the second interest point, wherein:
activating the first endpoint and the second endpoint initiates a generation of Operations, Administration, and Maintenance (OAM) out-of-band data packets by the first endpoint and the second endpoint; and
each of the OAM out-of-band data packets uses an OAM packet format, the OAM packet format comprising:
a Media Access Control (MAC) header;
an EtherType;
an Internet Protocol (IP) header;
a User Datagram Protocol (UDP) header;
at least one cloud OAM option; and
a Cyclic Redundancy Check (CRC);
receiving, from the first endpoint and the second endpoint, telemetry data associated with a problematic path between the first interest point and the second interest point; and
determining the problematic path between the first interest point and the second interest point using the telemetry data received from the first endpoint and the second endpoint, wherein the telemetry data is collected by the OAM out-of-band data packets.

### Claim 29 (depends on 28)

The method of claim 28, wherein the telemetry data comprises an identity of one or more cloud providers.

### Claim 30 (depends on 28)

The method of claim 28, wherein each of the first interest point and the second interest point are associated with one of the following:
a public cloud;
a private cloud; or
an on-premise data center.

### Claim 31 (depends on 28)

The method of claim 28, wherein the problematic event is associated with at least one of the following network characteristics:
latency;
jitter; or
packet drop.

### Claim 32 (depends on 28)

The method of claim 28, wherein the at least one cloud OAM option comprises a cloud OAM option type, a cloud OAM provider ID, and cloud OAM option data.

### Claim 33 (depends on 28)

The method of claim 28, further comprising:
activating one or more cloud agents within the network;
receiving, from the one or more cloud agents, additional telemetry data associated with the problematic path between the first interest point and the second interest point; and
computing the problematic path between the first interest point and the second interest point using the additional telemetry data received from the one or more cloud agents.

### Claim 34 (depends on 28)

The method of claim 28, further comprising instructing one or more transit routers within the network to redirect an identified traffic flow to a cloud agent.

### Claim 35

One or more computer-readable non-transitory storage media embodying instructions that, when executed by a processor, cause the processor to perform operations comprising:
identifying a problematic event between a first interest point and a second interest point of a network;
activating a first endpoint associated with the first interest point and a second endpoint associated with the second interest point, wherein:
activating the first endpoint and the second endpoint initiates a generation of Operations, Administration, and Maintenance (OAM) out-of-band data packets by the first endpoint and the second endpoint; and
each of the OAM out-of-band data packets uses an OAM packet format, the OAM packet format comprising:
a Media Access Control (MAC) header;
an EtherType;
an Internet Protocol (IP) header;
a User Datagram Protocol (UDP) header;
at least one cloud OAM option; and
a Cyclic Redundancy Check (CRC);
receiving, from the first endpoint and the second endpoint, telemetry data associated with a problematic path between the first interest point and the second interest point; and
determining the problematic path between the first interest point and the second interest point using the telemetry data received from the first endpoint and the second endpoint, wherein the telemetry data is collected by the OAM out-of-band data packets.

### Claim 36 (depends on 35)

The or more computer-readable non-transitory storage media of claim 35, wherein the telemetry data comprises an identity of one or more cloud providers.

### Claim 37 (depends on 35)

The or more computer-readable non-transitory storage media of claim 35, wherein each of the first interest point and the second interest point are associated with one of the following:
a public cloud;
a private cloud; or
an on-premise data center.

### Claim 38 (depends on 35)

The or more computer-readable non-transitory storage media of claim 35, wherein the problematic event is associated with at least one of the following network characteristics:
latency;
jitter; or
packet drop.

### Claim 39 (depends on 35)

The or more computer-readable non-transitory storage media of claim 35, wherein the at least one cloud OAM option comprises a cloud OAM option type, a cloud OAM provider ID, and cloud OAM option data.

### Claim 40 (depends on 35)

The or more computer-readable non-transitory storage media of claim 35, the operations further comprising:
activating one or more cloud agents within the network;
receiving, from the one or more cloud agents, additional telemetry data associated with the problematic path between the first interest point and the second interest point; and
computing the problematic path between the first interest point and the second interest point using the additional telemetry data received from the one or more cloud agents.
