# US 2024/0195725 A1 · System and method of discovering and validating different network action hardware capabilities

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

- Number: US 2024/0195725 A1
- Document ID: US20240195725A1
- Status: Published application
- Kind: A1
- Application number: 18/360,700
- Filed: 2023-07-27
- Published: 2024-06-13
- Earliest claimed: 2022-12-09
- Assignees: Cisco Technology, Inc.
- Applicants: Cisco Technology, Inc.
- Inventors: Jaganbabu Rajamanickam; Rakesh Gandhi; Nagendra Kumar Nainar; Madhan Sankaranarayanan
- Web page: https://patentgrep.com/patent/US20240195725A1

## CPC

- H04L 43/12: Network monitoring probes
- H04L 43/10: Active monitoring, e.g. heartbeat, ping or trace-route
- H04L 45/20: {Hop count for routing purposes, e.g. TTL}
- H04L 45/50: using label swapping, e.g. multi-protocol label switch [MPLS]
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Systems and methods for validating a hardware path capability are provided. The method includes generating, at an ingress node of a network, an operations, administration and maintenance (OAM) probe packet having an OAM bit set associated with validating the hardware path capability, wherein the OAM probe packet comprises a plurality of features; indicating, by each respective intermediate node of a plurality of intermediate nodes in the network along a network path and as instructed by the OAM bit set, whether the respective intermediate node can support the respective feature of the plurality of features; generating, at an egress node associated with the network path, a report regarding whether the plurality of intermediate nodes can support each respective feature of the plurality of features within the OAM probe packet; and determining, based on the report, whether to enable customer traffic implementing the plurality of features along the network path.

## Claims

### Claim 1

A method of validating a hardware path capability, the method comprising:
generating, at an ingress node of a network, an operations, administration and maintenance (OAM) probe packet having an OAM bit set associated with validating the hardware path capability, wherein the OAM probe packet comprises a plurality of features;
indicating, by each respective intermediate node of a plurality of intermediate nodes in the network along a network path and as instructed by the OAM bit set, whether the respective intermediate node can support the respective feature of the plurality of features;
generating, at an egress node associated with the network path, a report regarding whether the plurality of intermediate nodes can support each respective feature of the plurality of features within the OAM probe packet; and
determining, based on the report, whether to enable customer traffic implementing the plurality of features along the network path.

### Claim 2 (depends on 1)

The method of claim 1, wherein each respective feature of the plurality of features is indicated by a network action indicator operational code.

### Claim 3 (depends on 1)

The method of claim 1, wherein the OAM bit set comprises one to three bits.

### Claim 4 (depends on 3)

The method of claim 3, wherein the OAM bit set determines forwarding behavior for the OAM probe packet.

### Claim 5 (depends on 4)

The method of claim 4, wherein the OAM bit set one or more of a default value, a read, update and forward value, and a read, update, copy to CPU and forward value.

### Claim 6 (depends on 1)

The method of claim 1, wherein the OAM probe packet comprises a multiprotocol label switching network actions packet with the OAM bit set.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
when, based on the report, each of the plurality of intermediate nodes supports each of the plurality of features, enabling the customer traffic on the network path;
when, based on the report, at least one of the plurality of intermediate nodes does not support each of the plurality of features, not enabling the customer traffic on the network path; and
when, based on the report, each of the plurality of the intermediate nodes supports a maximum readable segment depth (MRSD) of the plurality of features, enabling the customer traffic on the network path.

### Claim 8 (depends on 1)

The method of claim 1, wherein indicating, by each respective intermediate node of the plurality of intermediate nodes in the network along the network path and as instructed by the OAM bit set, whether the respective intermediate node can support the respective feature of the plurality of features further comprises incrementing a counter for each respective intermediate node that supports each respective feature of the plurality of features.

### Claim 9 (depends on 1)

The method of claim 1, wherein whether the respective intermediate node can support the respective feature of the plurality of features is stored in the OAM probe packet in an ancillary data field.

### Claim 10 (depends on 9)

The method of claim 9, wherein the report is generated at the egress node based on a time to live value in the OAM probe packet.

### Claim 11 (depends on 9)

The method of claim 9, further comprising:
determining a feature capability of specific intermediate nodes of the plurality of intermediate nodes by setting the OAM bit set to a value;
incrementing a time to live (TTL) value at each respective intermediate node of the plurality of intermediate nodes;
receiving, at the ingress node and from each respective intermediate node based on the OAM bit set at the value, a respective return value of a multiprotocol label switching network action opcode ancillary value stored in the ancillary data field of the OAM probe packet; and
determining, at the ingress node and based on the respective return value of a multiprotocol label switching network action opcode ancillary value, which respective intermediate node is not incrementing the multiprotocol label switching network action opcode ancillary value stored in the ancillary data field of the OAM probe packet for a specific feature of the plurality of features.

### Claim 12 (depends on 1)

The method of claim 1, wherein the OAM bit set is in a header configured according to a multiprotocol label switching network actions framework.

### Claim 13

A system for validating a hardware path capability, the system having a plurality of intermediate nodes in a network, the system comprising:
at least one processor; and
a computer-readable storage medium storing instructions which, when executed by the at least one processor, cause the at least one processor to perform operations comprising:
generating an operations, administration and maintenance (OAM) probe packet having an OAM bit set associated with validating a hardware path capability, wherein the OAM probe packet comprises a plurality of features;
indicating, by each respective intermediate node of the plurality of intermediate nodes in the network along a network path and as instructed by the OAM bit set, whether the respective intermediate node can support the respective feature of the plurality of features;
generating a report regarding whether the plurality of intermediate nodes can support each respective feature of the plurality of features within the OAM probe packet; and
determining, based on the report, whether to enable customer traffic implementing the plurality of features along the network path.

### Claim 14 (depends on 13)

The system of claim 13, wherein each respective feature of the plurality of features is indicated by a network action indicator operational code; wherein the OAM bit set comprises from one to three bits and wherein the OAM bit set determines forwarding behavior for the OAM probe packet.

### Claim 15 (depends on 14)

The system of claim 14, wherein the OAM bit set represents one or more of a default value, a read, update and forward value, and a read, update, copy to CPU and forward value.

### Claim 16 (depends on 13)

The system of claim 13, wherein the OAM probe packet comprises a multiprotocol label switching network actions packet with the OAM bit set and wherein the computer-readable storage medium stores further instructions which, when executed by the at least one processor, cause the at least one processor to perform operations further comprising:
when, based on the report, each of the plurality of intermediate nodes supports each of the plurality of features, enabling the customer traffic on the network path; and
when, based on the report, at least one of the plurality of intermediate nodes does not support each of the plurality of features, not enabling the customer traffic on the network path.

### Claim 17 (depends on 13)

The system of claim 13, wherein indicating, by each respective intermediate node of the plurality of intermediate nodes in the network along the network path and as instructed by the OAM bit set, whether the respective intermediate node can support the respective feature of the plurality of features further comprises incrementing a counter for each respective intermediate node that supports each respective feature of the plurality of features, wherein whether the respective intermediate node can support the respective feature of the plurality of features is stored in the OAM probe packet in an ancillary data field and wherein the report is generated at the egress node based on a time to live value in the OAM probe packet.

### Claim 18 (depends on 17)

The system of claim 17, wherein the computer-readable storage medium stores further instructions which, when executed by the at least one processor, cause the at least one processor to perform operations further comprising:
determining a feature capability of specific intermediate nodes of the plurality of intermediate nodes by setting the OAM bit set to a value;
incrementing a time to live (TTL) value at each respective intermediate node of the plurality of intermediate nodes;
receiving, at the ingress node and from each respective intermediate node based on the OAM bit set at the value, a respective return value of a multiprotocol label switching network action opcode ancillary value stored in the ancillary data field of the OAM probe packet; and
determining, at the ingress node and based on the respective return value of a multiprotocol label switching network action opcode ancillary value, which respective intermediate node is not incrementing the multiprotocol label switching network action opcode ancillary value stored in the ancillary data field of the OAM probe packet for a specific feature of the plurality of features.

### Claim 19 (depends on 13)

The system of claim 13, wherein the OAM bit set is in a header configured according to a multiprotocol label switching network actions framework.

### Claim 20

A computer-readable storage medium storing instructions for validating a hardware path capability which, when executed by at least one processor, cause the at least one processor to perform operations comprising:
generating an operations, administration and maintenance (OAM) probe packet having an OAM bit set associated with validating a hardware path capability, wherein the OAM probe packet comprises a plurality of features;
indicating, by each respective intermediate node of a plurality of intermediate nodes in a network along a network path and as instructed by the OAM bit set, whether the respective intermediate node can support the respective feature of the plurality of features;
generating a report regarding whether the plurality of intermediate nodes can support each respective feature of the plurality of features within the OAM probe packet; and
determining, based on the report, whether to enable customer traffic implementing the plurality of features along the network path.
