# US 2017/0289028 A1 · Label switched path reporting

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

- Number: US 2017/0289028 A1
- Document ID: US20170289028A1
- Status: Published application
- Kind: A1
- Application number: 15/085,897
- Filed: 2016-03-30
- Published: 2017-10-05
- Earliest claimed: 2016-03-30
- Assignees: Juniper Networks, Inc.
- Applicants: Juniper Networks, Inc.
- Inventors: Kumuthini Ratnasingham
- Web page: https://patentgrep.com/patent/US20170289028A1

## CPC

- H04L 45/50: using label swapping, e.g. multi-protocol label switch [MPLS]
- H04L 41/12: Discovery or management of network topologies
- H04L 45/42: Centralised routing
- H04L 47/724: at intermediate nodes, e.g. resource reservation protocol [RSVP]
- H04L 45/02: Topology update or discovery
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Techniques are described for reporting, by non-ingress routers for traffic engineering label switched paths (TE LSPs) and to a path computation element, actual paths taken by the TE LSPs through the network. A first network device: receives, from a second network device, an LSP path signaling message that includes a route object having a first indication of at least a sub-path of a path for TE LSP through a network, wherein the first network device is not an ingress label edge router for the TE LSP; generates, in response to the LSP path signaling message and based at least in part on the route object, an LSP path report message that includes a second indication of the at least the sub-path of the path for the TE LSP; and sends, to a path computation element, the LSP path report message to notify the PCE.

## Claims

### Claim 1

A method comprising:
receiving, by a first network device that is not an ingress label edge router (LER) for a traffic engineering label switching path (TE LSP) and from a second network device, an LSP path signaling message that includes a route object having a first indication of at least a sub-path of a path for the TE LSP through a network;
generating, by the first network device in response to the LSP path signaling message and based at least in part on the route object, an LSP path report message that includes a second indication of the at least the sub-path of the path for the TE LSP; and
sending, by the first network device to a path computation element (PCE), the LSP path report message to notify the PCE of the at least the sub-path of the path for the TE LSP.

### Claim 2 (depends on 1)

The method of claim 1,
wherein the LSP path signaling message comprises a Resource Reservation Protocol with Traffic Engineering extensions (RSVP-TE) Path message requesting that the first network device bind a label for the TE LSP and return the label to the second network device, and
wherein the route object comprises one of an Explicit Route Object (ERO) and a Record Route Object (RRO).

### Claim 3 (depends on 1)

The method of claim 1,
wherein the LSP path signaling message comprises a Resource Reservation Protocol (RSVP) Resv message that includes a label that is bound for the TE LSP by the second network device, and
wherein the route object comprises one of an Explicit Route Object (ERO) and a Record Route Object (RRO).

### Claim 4 (depends on 1)

The method of claim 1, wherein the LSP path report message includes an indication that the first network device is one of a transit label switching router and an egress LER for the TE LSP.

### Claim 5 (depends on 1)

The method of claim 1,
wherein the LSP path report message comprises a Path Computation Element Protocol (PCEP) Path Computation State Report (PCRpt) message that includes an LSP state report for the TE LSP, and
wherein sending the LSP path report message comprises sending, by the first network device via a PCEP session with the PCE, the LSP path report message.

### Claim 6 (depends on 5)

The method of claim 5,
wherein the PCRpt message includes an LSP state report for the TE LSP, and
wherein the LSP state report includes at least one flag to indicate that the first network device is one of a transit label switching router and an egress LER for the TE LSP.

### Claim 7 (depends on 1)

The method of claim 1, wherein the first network device is one of a transit label switching router and an egress LER for the TE LSP.

### Claim 8 (depends on 1)

The method of claim 1, wherein the second indication of the at least the sub-path of the path for the TE LSP comprises one of an Explicit Route Object (ERO) and a Record Route Object (RRO).

### Claim 9 (depends on 1)

The method of claim 1, further comprising:
signaling, by the ingress LER for the TE LSP in response to computing a computed path for the TE LSP, the TE LSP to establish the TE LSP along the computed path; and
receiving, by the ingress LER for the TE LSP from a next hop of the ingress LER for the TE LSP and in response to the signaling, the path for the TE LSP without reporting the path to the PCE.

### Claim 10 (depends on 1)

The method of claim 1, further comprising:
signaling, by the ingress LER for the TE LSP in response to receiving a computed path for the TE LSP from the PCE, the TE LSP to establish the TE LSP along the computed path; and
receiving, by the ingress LER for the TE LSP from a next hop of the ingress LER for the TE LSP and in response to the signaling, the path for the TE LSP without reporting the path to the PCE.

### Claim 11

A first network device comprising:
one or more processors coupled to a memory;
a routing protocol daemon configured for execution by the one or more processors to receive, from a second network device, an LSP path signaling message that includes a route object having a first indication of at least a sub-path of a path for a traffic engineering label switching path (TE LSP) through a network, wherein the first network device is not an ingress label edge router (LER) for the TE LSP; and
a path computation client configured for execution by the one or more processors to generate, in response to the LSP path signaling message and based at least in part on the route object, an LSP path report message that includes a second indication of the at least the sub-path of the path for the TE LSP,
wherein the path computation client is further configured to send, to a path computation element (PCE), the LSP path report message to notify the PCE of the at least the sub-path of the path for the TE LSP.

### Claim 12 (depends on 11)

The first network device of claim 11,
wherein the LSP path signaling message comprises a Resource Reservation Protocol with Traffic Engineering extensions (RSVP-TE) Path message requesting that the first network device bind a label for the TE LSP and return the label to the second network device, and
wherein the route object comprises one of an Explicit Route Object and a Record Route Object.

### Claim 13 (depends on 11)

The first network device of claim 11,
wherein the LSP path signaling message comprises a Resource Reservation Protocol (RSVP) Resv message that includes a label that is bound for the TE LSP by the second network device, and
wherein the route object comprises one of an Explicit Route Object (ERO) and a Record Route Object (RRO).

### Claim 14 (depends on 11)

The first network device of claim 11, wherein the LSP path report message includes an indication that the first network device is one of a transit label switching router and an egress LER for the TE LSP.

### Claim 15 (depends on 11)

The first network device of claim 11,
wherein the LSP path report message comprises a Path Computation Element Protocol (PCEP) Path Computation State Report (PCRpt) message that includes an LSP state report for the TE LSP, and
wherein sending the LSP path report message comprises sending, by the first network device via a PCEP session with the PCE, the LSP path report message.

### Claim 16 (depends on 15)

The first network device of claim 15,
wherein the PCRpt message includes an LSP state report for the TE LSP, and
wherein the LSP state report includes at least one flag to indicate that the first network device is one of a transit label switching router and an egress LER for the TE LSP.

### Claim 17 (depends on 11)

The first network device of claim 11, wherein the first network device is one of a transit label switching router and an egress LER for the TE LSP.

### Claim 18 (depends on 11)

The first network device of claim 11, wherein the second indication of the at least the sub-path of the path for the TE LSP comprises one of an Explicit Route Object (ERO) and a Record Route Object (RRO).

### Claim 19

A system comprising:
a software-defined networking (SDN) controller for a network, the SDN controller comprising a path computation element (PCE) for a path computation domain of a network;
a second network device of the network;
a first network device of the network, the first network device configured to receive, from a second network device, an LSP path signaling message that includes a route object having a first indication of at least a sub-path of a path for a traffic engineering label switching path (TE LSP) through a network, wherein the first network device is not an ingress label edge router (LER) for the TE LSP,
wherein the first network device is further configured to generate, in response to the LSP path signaling message and based at least in part on the route object, an LSP path report message that includes a second indication of the at least the sub-path of the path for the TE LSP, and
wherein the first network device is further configured to send, to the SDN controller, the LSP path report message to notify the SDN controller of the at least the sub-path of the path for the TE LSP.

### Claim 20 (depends on 19)

The system of claim 19,
wherein the SDN controller is configured to receive the LSP path report, and
wherein the PCE is configured to compute, based on the at least the sub-path of the path for the TE LSP received from the first network device, one or more paths for additional TE LSPs in the path computation domain.

### Claim 21

A first network device comprising:
one or more processors coupled to a memory;
a routing protocol daemon configured for execution by the one or more processors to receive, from a second network device, an LSP path signaling message that includes a route object having a first indication of at least a sub-path of a path for a traffic engineering label switching path (TE LSP) through a network; and
a path computation client configured for execution by the one or more processors to generate, in response to the LSP path signaling message and based at least in part on the route object, an LSP path report message that includes a second indication of the at least the sub-path of the path for the TE LSP and an indication that the first network device is one of an ingress label edge router (LER), a transit label switching router, and an egress LER for the TE LSP,
wherein the path computation client is further configured to send, to a path computation element (PCE), the LSP path report message to notify the PCE of the at least the sub-path of the path for the TE LSP.

### Claim 22 (depends on 21)

The first network device of claim 21,
wherein the LSP path report message comprises a Path Computation Element Protocol (PCEP) Path Computation State Report (PCRpt) message that includes an LSP state report for the TE LSP, and
wherein sending the LSP path report message comprises sending, by the first network device via a PCEP session with the PCE, the LSP path report message.

### Claim 23 (depends on 22)

The first network device of claim 22,
wherein the PCRpt message includes an LSP state report for the TE LSP, and
wherein the LSP state report includes at least one flag to indicate that the first network device is one of a transit label switching router and an egress LER for the TE LSP.