# US 2015/0029837 A1 · Protection Switched Source Routing

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

- Number: US 2015/0029837 A1
- Document ID: US20150029837A1
- Status: Published application
- Kind: A1
- Application number: 14/339,036
- Filed: 2014-07-23
- Published: 2015-01-29
- Earliest claimed: 2013-07-26
- Assignees: Futurewei Technologies, Inc.
- Applicants: Futurewei Technologies, Inc.
- Inventors: Peter Ashwood-Smith
- Web page: https://patentgrep.com/patent/US20150029837A1

## CPC

- H04L 45/34: {Source routing}
- H04L 43/0811: by checking connectivity
- H04L 43/10: Active monitoring, e.g. heartbeat, ping or trace-route
- H04L 45/22: {Alternate routing}
- H04L 45/70: {Routing based on monitoring results}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A network element configured to operate in a source routing network, wherein the network element comprises a receiver, a transmitter, and a processor coupled to the receiver and the transmitter. The processor may be configured to cause the network element to receive from an upstream network element, a liveness protection probe comprising a header that comprises a list of one or more ordered connection identifiers that indicate a network path traversing the source routing network through which the liveness protection probe should be forwarded, transmit the liveness protection probe toward a downstream network element according to the connection identifiers, receive the liveness protection probe from the downstream network element, and transmit the liveness protection probe to the upstream network element according to a second list of one or more ordered connection identifiers contained within the header.

## Claims

### Claim 1

A network element (NE) configured to operate in a source routing network, wherein the NE comprises:
a receiver;
a transmitter; and
a processor coupled to the receiver and the transmitter and configured to cause the NE to:
receive from an upstream NE, a liveness protection probe comprising a header that comprises a list of one or more ordered connection identifiers that indicate a network path traversing the source routing network through which the liveness protection probe should be forwarded;
transmit the liveness protection probe toward a downstream NE according to the connection identifiers;
receive the liveness protection probe from the downstream NE; and
transmit the liveness protection probe to the upstream NE according to a second list of one or more ordered connection identifiers contained within the header.

### Claim 2 (depends on 1)

The NE of claim 1, wherein the liveness protection probe indicates a connectivity status of the network path.

### Claim 3 (depends on 2)

The NE of claim 2, wherein the liveness protection probe is received and transmitted according to strict source routing headers via a stateless connection.

### Claim 4 (depends on 1)

The NE of claim 1, wherein the connection identifiers each comprise an identification of a link in the source routing network, or wherein the connection identifiers each comprises an identification of a node in the source routing network.

### Claim 5 (depends on 2)

The NE of claim 2, wherein the connection identifiers are assigned locally in the source routing network, or wherein the connection identifiers are assigned globally in the source routing network.

### Claim 6 (depends on 1)

The NE of claim 1, wherein the processor is further configured to cause the NE to:
receive from the upstream NE, a data packet comprising a header that comprises the connection identifiers; and
transmit the data packet to the downstream NE according to the connection identifiers.

### Claim 7 (depends on 4)

The NE of claim 4, wherein the liveness protection probe and the data packet are received and transmitted according to the same connection identifiers.

### Claim 8

A method for performing protection switching in a source routing network, implemented in a network element, wherein the method comprises:
receiving via a tandem network element in the source routing network, a data packet transmitted through a network path from an ingress node;
receiving from the ingress node, via the network path of the data packet, a source routing network failure detection probe comprising a header and a payload; and
transmitting the failure detection probe toward the ingress node through the source routing network in response to receiving the failure detection probe from the ingress node.

### Claim 9 (depends on 6)

The method of claim 6, wherein the failure detection probe is transmitted to the ingress node according to indicators included in the header of the failure detection probe by reversing a route indicated in the header.

### Claim 10 (depends on 7)

The method of claim 7, wherein the failure detection probe is transmitted to the ingress node according to indicators included in the header of the failure detection probe by employing a reverse route indicated in the header.

### Claim 11 (depends on 6)

The method of claim 6, wherein the failure detection probe is transmitted to the ingress node according to indicators included in the payload of the failure detection probe.

### Claim 12 (depends on 6)

The method of claim 6, wherein the failure detection probe is transmitted to the ingress node according to a network path encapsulation stored at the network element.

### Claim 13 (depends on 6)

The method of claim 6, wherein the failure detection probe comprises a connectivity status of the network path that indicates a liveness of the network path.

### Claim 14 (depends on 11)

The method of claim 11, wherein timing and packet count information is appended to the failure detection probe before being transmitted to the ingress node.

### Claim 15 (depends on 6)

The method of claim 6, wherein the data packet is associated with a data flow, wherein the network path comprises a primary network path, and wherein the method further comprises:
receiving the data flow and a protection probe over a backup network path when the primary network path has failed; and
receiving the dataflow and a protection probe over the primary network path when a plurality of protection probes indicate the primary network path has returned to normal operation.

### Claim 16

An ingress node in a source routing network comprising:
a receiver;
a transmitter; and
a processor coupled to the receiver and the transmitter and configured to cause the ingress node to:
receive a data packet from a source;
receive a plurality of source routing encapsulation identifiers that indicate a plurality of paths across the source routing network for transmitting the data packet to an egress node; and
transmit to the egress node, a source routing network path protection probe along a primary network path indicated by a first set of encapsulation identifiers;
encapsulate the data packet with the first set of encapsulation identifiers when the protection probe is received from the egress node;
encapsulate the data packet with a second set of encapsulation identifiers that indicate a backup network path over which the data packet should be forwarded when the protection probe is not received from the egress node within a predetermined duration; and
transmit the data packet to a downstream node according to the encapsulation identifiers.

### Claim 17 (depends on 14)

The ingress node of claim 14, wherein the ingress node transmits a source routing network path protection probe over both the primary network path using the first set of encapsulation identifiers and the backup network path using the second set of encapsulation identifiers when the data packet is transmitted through the backup network path according to the second set of encapsulation identifiers.

### Claim 18 (depends on 15)

The ingress node of claim 15, wherein the ingress node reverts from transmitting a data flow associated with the data packet on the backup network path to transmitting the data flow on the primary network path when the source routing network path protection probes indicate the primary network path has resumed normal operation.

### Claim 19 (depends on 14)

The ingress node of claim 14, wherein timing and packet count information is appended to the source routing network path protection probe.

### Claim 20 (depends on 14)

The ingress node of claim 14, wherein the ingress node further comprises a memory coupled to the processor, and wherein the memory comprises a table that comprises a plurality of network routing paths for data flows for which the ingress node serves as the ingress node to the source routing network, and wherein the table does not contain network routing paths for data flows for which the ingress node does not serve as the ingress node to the source routing network.
