Branch node-initiated point to multi-point label switched path signaling with centralized path computation

• US 8,953,500 B1
• Filed: 03/29/2013
• Issued: 02/10/2015
• Est. Priority Date: 03/29/2013
• Status: Active Grant

• Current Assignee: Juniper Networks Incorporated
• Original Assignee: Juniper Networks Incorporated
• Inventors: Minei, Ina, Torvi, Raveendra, Shen, Yimin
• Primary Examiner(s): HAN, CLEMENCE S
• Application Number:
  US13/853,966
• Time in Patent Office: 683 Days
• Field of Search: None
• US Class Current: 370/256
• CPC Class Codes: H04L 45/16 Multipoint routing
• CPC Class Codes: H04L 45/46 Cluster building

Abstract

Techniques are described for establishing a point-to-multipoint (P2MP) label switched path (LSP) using a branch node-initiated signaling model in which branch node to leaf (B2L) sub-LSPs are signaled and utilized to form a P2MP LSP. The techniques described herein provides a scalable solution in which the number of sub-LSPs for which the source node or any given branch node need maintain state is equal to the number of physical data flows output from that node to downstream nodes, i.e., the number of output interfaces used for the P2MP LSP by that node to output data flows to downstream nodes. As such, unlike the conventional source node-initiated model in which each node maintains state for sub-LSPs that service each of the leaf nodes downstream from the device, the size and scalability of a P2MP LSP is no longer bound to the number of leaves that are downstream from that node.

Claims

1. A method comprising:

receiving, with a controller, a request for a point-to-multipoint (P2MP) label switched path (LSP) from a source node through one or more branch nodes to a plurality of leaf nodes within a network;

determining, with the controller, a hierarchy of point-to-point (P2P) sub-LSPs, wherein a first level of the hierarchy includes at least one P2P source-to-leaf (S2L) sub-LSP from the source node as an ingress for the P2P S2L sub-LSP through one or more of the branch nodes to a first one of the leaf nodes as an egress for the P2P S2L LSP, and wherein each remaining level of the hierarchy includes at least one P2P branch-to-leaf (B2L) sub-LSP from one of the branch nodes as in ingress to the P2P B2L sub-LSP to a different one of the leaf nodes as an egress for the P2P B2L sub-LSP; and

outputting messages, with the controller, to direct the source node, the one or more branch nodes and the plurality of leaf nodes to signal the hierarchy of P2P sub-LSPs to form the P2MP LSP.

2. The method of claim 1, wherein determining a hierarchy of P2P sub-LSPs including selecting each of the P2P sub-LSPs so that, for each of the source node and the branch nodes, the number of P2P sub-LSPs flowing through the node for the P2MP LSP is equal to the number of output interfaces from that node to downstream nodes used for the P2MP LSP.

3. The method of claim 1, further comprising, at each of the branch nodes, installing a flooding next hop to forward traffic from a higher level one of the P2P S2L sub-LSPs or P2P B2L sub-LSPs to one of the P2P B2L sub-LSPs for which the branch node operates as an ingress.

4. The method of claim 1, wherein outputting messages comprises outputting, from the controller, messages in accordance with a Path Computation Element (PCE) Communication Protocol (PCEP), wherein the messages include explicit route objects (EROS) specifying the P2P S2L sub-LSP and the P2P B2L sub-LSPs.

5. The method of claim 1, wherein outputting messages comprises outputting, from the controller, messages in accordance with a software-defined networking (SDN) protocol.

6. The method of claim 1, wherein the controller comprises a centralized controller within the network.

7. The method of claim 1, wherein receiving a request for a P2MP LSP comprises receiving a request for a network service to be delivered from a source to a plurality of subscribers.

8. The method of claim 1, wherein receiving a request for a P2MP LSP comprises receiving configuration data from an administrator specifying the P2MP LSP.

9. A device comprising:

a network interface to receive a request for a point-to-multipoint (P2MP) label switched path (LSP) from a source node through one or more branch nodes to a plurality of leaf nodes within a network;

a path computation module executing on one or more processors, wherein the path computation module determines a hierarchy of point-to-point (P2P) sub-LSPs, wherein a first level of the hierarchy includes at least one P2P source-to-leaf (S2L) sub-LSP from the source node as an ingress for the P2P S2L sub-LSP through one or more of the branch nodes to a first one of the leaf nodes as an egress for the P2P S2L LSP, and wherein each remaining level of the hierarchy includes at least one P2P branch-to-leaf (B2L) sub-LSP from one of the branch nodes as in ingress to the P2P B2L sub-LSP to a different one of the leaf nodes as an egress for the P2P B2L sub-LSP; and

a path provisioning module to output messages to direct the source node, the one or more branch nodes and the plurality of leaf nodes to signal the hierarchy of P2P sub-LSPs to form the P2MP LSP.

10. The device of claim 9, wherein the path computation module selects each of the P2P sub-LSPs so that, for each of the source node and the branch nodes, the number of P2P sub-LSPs flowing through the node for the P2MP LSP is equal to the number of output interfaces from that node to downstream nodes used for the P2MP LSP.

11. The device of claim 9, wherein the path provisioning module outputs messages to install a flooding next hop at each of the branch nodes to forward traffic from a higher level one of the P2P S2L sub-LSPs or P2P B2L sub-LSPs to one of the P2P B2L sub-LSPs for which the branch node operates as an ingress.

12. The device of claim 9, wherein the path provisioning module outputs messages in accordance with a Path Computation Element (PCE) Communication Protocol (PCEP), wherein the messages include explicit route objects (EROS) specifying the P2P S2L sub-LSP and the P2P B2L sub-LSPs.

13. The device of claim 9, wherein the path provisioning module outputs messages in accordance with a software-defined networking (SDN) protocol.

14. The device of claim 9, wherein the device comprises a software-defined network controller.

15. The device of claim 9, further comprising a network services application to receive, via the network interface, the request for a network service to be delivered from a source to a plurality of subscribers.

16. The device of claim 9, wherein the request for the P2MP LSP comprises configuration data received from an administrator specifying the P2MP LSP.

17. A computer-readable storage medium comprising instructions that cause a network device to:

receive a request for a point-to-multipoint (P2MP) label switched path (LSP) from a source node through one or more branch nodes to a plurality of leaf nodes within a network;

determine a hierarchy of point-to-point (P2P) sub-LSPs, wherein a first level of the hierarchy includes at least one P2P source-to-leaf (S2L) sub-LSP from the source node as an ingress for the P2P S2L sub-LSP through one or more of the branch nodes to a first one of the leaf nodes as an egress for the P2P S2L LSP, and wherein each remaining level of the hierarchy includes at least one P2P branch-to-leaf (B2L) sub-LSP from one of the branch nodes as in ingress to the P2P B2L sub-LSP to a different one of the leaf nodes as an egress for the P2P B2L sub-LSP; and

output messages, with the controller, to direct the source node, the one or more branch nodes and the plurality of leaf nodes to signal the hierarchy of P2P sub-LSPs to form the P2MP LSP.

18. The computer-readable storage medium of claim 17, wherein the instructions cause the processor to select each of the P2P sub-LSPs so that, for each of the source node and the branch nodes, the number of P2P sub-LSPs flowing through the node for the P2MP LSP is equal to the number of output interfaces from that node to downstream nodes used for the P2MP LSP.

19. The computer-readable storage medium of claim 17, wherein the instructions cause the processor to output the messages in accordance with a Path Computation Element (PCE) Communication Protocol (PCEP), wherein the messages include explicit route objects (EROS) specifying the P2P S2L sub-LSP and the P2P B2L sub-LSPs.

20. The computer-readable storage medium of claim 17, wherein the instructions cause the processor to output the messages in accordance a software-defined networking (SDN) protocol.