# US 2018/0026884 A1 · Cloud overlay for operations administration and management

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

- Number: US 2018/0026884 A1
- Document ID: US20180026884A1
- Status: Published application
- Kind: A1
- Application number: 15/216,334
- Filed: 2016-07-21
- Published: 2018-01-25
- Earliest claimed: 2016-07-21
- Assignees: Cisco Technology, Inc.
- Applicants: Cisco Technology, Inc.
- Inventors: Nagendra Kumar Nainar; Carlos M. Pignataro; Deepak Kumar
- Web page: https://patentgrep.com/patent/US20180026884A1

## CPC

- H04L 45/50: using label swapping, e.g. multi-protocol label switch [MPLS]
- H04L 41/04: Network management architectures or arrangements
- H04L 41/344: Out-of-band transfers
- H04L 45/64: using an overlay routing layer
- H04L 12/4633: {Interconnection of networks using encapsulation techniques, e.g. tunneling}
- H04L 43/0811: by checking connectivity
- H04L 43/10: Active monitoring, e.g. heartbeat, ping or trace-route
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Systems, methods, and computer-readable media are provided for facilitating the implementation of an operations, administration, and management (OAM) protocol in a network overlay environment. In particular, aspects of the technology facilitating the transport of OAM communications across overlay environments of different types. Aspects of the technology can include steps for receiving a packet comprising an OAM payload, and encapsulating the packet with an OAM transport header, wherein the transport header is configured to be read by transit nodes of different overlay types.

## Claims

### Claim 1

A method for facilitating operations administration and management (OAM) communications across different network overlay types, the method comprising:
receiving a packet comprising an OAM payload and an overlay header; and
encapsulating the packet with a transport header, wherein the transport header is configured to be read by two or more transit nodes of different overlay types.

### Claim 2 (depends on 1)

The method of claim 1, wherein the transport header comprises a pointer indicating a location of the OAM payload within the packet.

### Claim 3 (depends on 2)

The method of claim 2, wherein the pointer provides an offset indicating a number of bits that a transit node should skip to read the OAM payload.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
transmitting the packet to a first overlay node via a second overlay node, wherein the first overlay node and the second overlay node correspond with different overlay types.

### Claim 5 (depends on 1)

The method of claim 1, wherein the OAM payload comprises one or more type-length-value (TLV) data strings corresponding with a requested functionality to be performed at a destination node.

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
encapsulating the packet with a transport encapsulation marker, wherein the transport encapulation marker comprises an OAM marker that indentifies the packet as an OAM packet.

### Claim 7 (depends on 6)

The method of claim 6, wherein the OAM marker corresponds with encapsulation data corresponding with one or more of: IPv4, IPv6, segment routing with multiprotocol label switching (SR/MPLS), SRv6, and Ethernet.

### Claim 8

A packet encapsulation system comprising:
at least one processor; and
a memory device storing instructions that, when executed by the at least one processor, cause the system to:
receiving a packet comprising an operations administration and management (OAM) payload and an overlay header; and
encapsulating the packet with a transport header, wherein the transport header is configured to be read by two or more transit nodes of different overlay types.

### Claim 9 (depends on 8)

The system of claim 8, wherein the transport header comprises a pointer indicating a location of the OAM payload within the packet.

### Claim 10 (depends on 9)

The system of claim 9, wherein the pointer provides an offset indicating a number of bits that a transit node should skip to read the OAM payload.

### Claim 11 (depends on 8)

The system of claim 8, further comprising:
transmitting the packet to a first overlay node via a second overlay node, wherein the first overlay node and the second overlay node correspond with different overlay types.

### Claim 12 (depends on 8)

The system of claim 8, wherein the OAM payload comprises one or more type-length-value (TLV) data strings corresponding with a requested functionality to be performed at a destination node.

### Claim 13 (depends on 8)

The system of claim 8, further comprising:
encapsulating the packet with a transport encapsulation marker, wherein the transport encapulation marker comprises an OAM marker that indentifies the packet as an OAM packet.

### Claim 14 (depends on 13)

The system of claim 13, wherein the OAM marker corresponds with encapsulation data corresponding with one or more of: IPv4, IPv6, segment routing with multiprotocol label switching (SR/MPLS), SRv6, and Ethernet.

### Claim 15

A non-transitory computer-readable storage medium comprising instructions stored therein, which when executed by one or more processors, cause the processors to perform operations comprising:
receiving a packet comprising an OAM payload and an overlay header; and
encapsulating the packet with a transport header, wherein the transport header is configured to be read by two or more transit nodes of different overlay types.

### Claim 16 (depends on 15)

The storage medium of claim 15, wherein the transport header comprises a pointer indicating a location of the OAM payload within the packet.

### Claim 17 (depends on 16)

The storage medium of claim 16, wherein the pointer provides an offset indicating a number of bits that a transit node should skip to read the OAM payload.

### Claim 18 (depends on 15)

The storage medium of claim 15, further comprising:
transmitting the packet to a first overlay node via a second overlay node, wherein the first overlay node and the second overlay node correspond with different overlay types.

### Claim 19 (depends on 15)

The storage medium of claim 15, wherein the OAM payload comprises one or more type-length-value (TLV) data strings corresponding with a requested functionality to be performed at a destination node.

### Claim 20 (depends on 15)

The storage medium of claim 15, further comprising:
encapsulating the packet with a transport encapsulation marker, wherein the transport encapulation marker comprises an OAM marker that indentifies the packet as an OAM packet.
