Abstract: An apparatus comprising a memory, and a processor coupled to the memory and configured to transmit a backup Label Switched Path (LSP) multicast Resource Reservation Protocol-Traffic Engineering (mRSVP-TE) path request (PATH) message upstream, wherein the backup LSP PATH message requests reservation of a first backup LSP to protect a first primary LSP configured to transmit multicast data, and wherein the backup LSP PATH message is transmitted to support a facility mode one to many (1:N) fast reroute protocol.

Abstract: A path control element (PCE) is provided, including a processor and a non-transitory computer readable storage medium coupled to the processor. The storage medium stores programming for execution by the processor, wherein the programming, when executed by the processor, configures the PCE to receive a request for a path of a unicast or multicast label switching path (LSP), determine a primary path and a secondary/local protection path through a plurality of nodes in a label switched network, and provide the primary path and the secondary/local protection path to the plurality of nodes.

Abstract: A network configuring method including receiving a label switched path (LSP) tunnel request from a path computation element (PCE), computing an LSP path, sending an LSP initiation message that comprises a label stack for the LSP path computed to the PCE, receiving an LSP delegation message from the PCE, and sending a label entry update message that comprises the label stack to PCEs along the computed LSP. A network configuring method including sending an LSP tunnel request to a path computation element central controller (PCECC), receiving an LSP initiation message that comprises a label stack for a computed LSP path from the PCECC, creating an LSP tunnel using the label stack, sending an LSP delegation message to the PCECC, receiving a label entry update message that comprises the label, and obtaining the label stack using the label entry update message.

Abstract: An apparatus comprising a memory, and a processor coupled to the memory and configured to transmit a multicast Resource Reservation Protocol-Traffic Engineering (mRSVP-TE) path request (PATH) message upstream, wherein the PATH message requests reservation of a backup Label Switched Path (LSP) to protect an active LSP configured to transmit multicast data. The disclosure also includes a computer program product comprising computer executable instructions stored on a non-transitory computer readable medium such that when executed by a processor cause a network element (NE) to receive a multicast PATH message from a downstream node, wherein the NE acts as a Point of Local Repair (PLR) along an active LSP, wherein the active LSP is configured to transmit multicast data, and wherein the PATH message requests reservation of a backup LSP to protect the active LSP.

Abstract: An ingress node in a Software Defined Network (SDN) comprising a receiver for receiving a data packet, a processor coupled to the receiver and further configured to obtain the data packet from the receiver in a transport protocol agnostic manner, and encapsulate the data packet in an SDN packet header, wherein the packet header comprises SDN flow-specific information provided by an SDN controller, and a transmitter coupled to the processor and further configured to transmit the encapsulated data packet across a single SDN toward an egress node in the SDN.

Abstract: A network component comprising at least one processor configured to implement a method comprising receiving a packet, determining whether the packet comprises a topology label, and adding the topology label to the packet if the packet does not comprise the topology label. Included is a method comprising routing a plurality of packets corresponding to a plurality of forwarding equivalence classes (FECs) over a plurality of network topologies using a topology label and plurality of forwarding labels for each network topology. Also included is a network comprising a plurality of nodes in communication with each other and having a plurality of network topologies, wherein at least some of the nodes are configured to route data packets for a plurality of FECs along a path in each network topology using a topology label corresponding to each network topology and an inner label corresponding to each FEC.

Abstract: A computer program product comprising computer executable instructions stored on a non-transitory medium of an upstream node in a network system comprising a plurality of nodes that when executed by a processor cause the node to advertise an upstream assigned label to a downstream node, receive a message from the downstream node, and if the received message confirms that no conflict with the upstream assigned label exists at the downstream node, assign the upstream-assigned label, or if the received message confirms that a conflict with the upstream-assigned label exists at the downstream node, either select a new upstream-assigned label or wait until indication is received that the label resource has become available.

Abstract: An apparatus comprising a processor configured to store a first upstream label in a forwarding table upon receipt of a first message encapsulating the first upstream label from a first adjacent node, store a first downstream label in the forwarding table upon receipt of a second message encapsulating the first downstream label from a second adjacent node, send a third message encapsulating a second downstream label to the first adjacent node, send a fourth message encapsulating a second upstream label to the second adjacent node; and forward data received from a plurality of adjacent nodes over a MP2MP LSP using at least a portion of the labels stored in the forwarding table, wherein each adjacent node is associated with only one upstream label and only one downstream label, and wherein the maximum state complexity of the forwarding table is linear relative to the number of adjacent nodes.

Abstract: An apparatus comprising a processor configured to send a first notification message to a first label switch router (LSR) to discover the upstream multipoint Label Distribution Protocol (mLDP) LSR, wherein the apparatus is configured to couple to the first LSR, and wherein the first LSR is not an mLDP LSR, receive a second notification message from the upstream mLDP node, and in response to receiving the second notification message, establish an mLDP Label Switch Path (LSP) to the upstream mLDP node via the first LSR.

Abstract: In one aspect, the disclosure includes an apparatus comprising a processor configured to receive node protection backup route data at an upstream node and determine at least one backup route to at least one merge point node of a protected link or node according to the node protection data. In another aspect, the disclosure includes an apparatus comprising a processor configured to: receive at an upstream component information from a downstream component, wherein the received information comprises one or more of the following data elements related to one or more merge point nodes of a protected node: a number of leaf nodes, a plurality of merge point node addresses, a plurality of merge point node label reserve times and a plurality of merge point node forwarding labels, and establish a backup tunnel at the upstream component using at least one of the data elements received from the downstream component.

Abstract: Embodiments relate generally to systems and methods for transitioning a system from a tradition network to a Software Defined Network (SDN) enabled network. In some embodiments, the systems and methods may comprise the use of a Path Computation Element (PCE) as a central controller. Smooth transition between traditional network and the new SDN enabled network, especially from a cost impact assessment perspective, may be accomplished using the existing PCE components from the current network to function as the central controller of the SDN network is one choice, which not only achieves the goal of having a centralized controller to provide the functionalities needed for the central controller, but also leverages the existing PCE network components.

Abstract: A computer program product comprising computer executable instructions stored on a non-transitory medium of an upstream node in a network system comprising a plurality of nodes that when executed by a processor cause the node to advertise an upstream assigned label to a downstream node, receive a message from the downstream node, and if the received message confirms that no conflict with the upstream assigned label exists at the downstream node, assign the upstream-assigned label, or if the received message confirms that a conflict with the upstream-assigned label exists at the downstream node, either select a new upstream-assigned label or wait until indication is received that the label resource has become available.

Abstract: In one aspect, the disclosure includes an apparatus comprising a processor configured to function as a merge point (MP) in a point to multi-point (P2MP) backup label switching path (LSP) for a primary LSP, receive P2MP backup LSP information originating from a protected node, wherein the P2MP backup LSP information comprises the identity of a point of local repair (PLR), determine a backup label switching router (LSR), and send a message with the identity of the backup LSR to an upstream node.

Abstract: An apparatus comprising a path computation element (PCE) configured to communicate with a path computation client (PCC) and compute a point-to-multipoint (P2MP) path across an autonomous system (AS) domain. Also included is a network component comprising at least one processor configured to implement a method comprising obtaining a computation request for a P2MP path across a plurality of AS domains, attempting to calculate the P2MP path across the AS domains, thereby generating a computed path or a failure reason, and transmitting a reply comprising the computed path or an indication of the failure reason. Included is a method comprising exchanging a request message and a reply message about a P2MP path across an AS domain between a PCC and a PCE.

Abstract: An apparatus comprising a backup node coupled to an ingress node of a point-to-multipoint (P2MP) label switched path (LSP) and to a plurality of next-hop nodes of the ingress node of the P2MP LSP via a backup tree, wherein the backup node and the ingress node are both coupled to an external node, and wherein the backup node is configured to ensure data delivery in the P2MP LSP when the ingress node fails. Included is a network component comprising at least one processor configured to implement a method comprising detecting a failure in an ingress node of a P2MP LSP, receiving a data packet destined for the ingress node and to be transported by the P2MP LSP from a provider node when the ingress node fails, and transmitting the data packet on a backup tree that merges with the P2MP LSP prior to reaching an egress node.

Abstract: A computer program product comprising computer executable instructions stored on a non-transitory medium of an upstream node in a network system comprising a plurality of nodes that when executed by a processor cause the node to advertise an upstream assigned label to a downstream node, receive a message from the downstream node, and if the received message confirms that no conflict with the upstream assigned label exists at the downstream node, assign the upstream-assigned label, or if the received message confirms that a conflict with the upstream-assigned label exists at the downstream node, either select a new upstream-assigned label or wait until indication is received that the label resource has become available.

Abstract: A computer program product comprising computer executable instructions stored on a non-transitory medium of an upstream node in a network system comprising a plurality of nodes that when executed by a processor cause the node to advertise an upstream assigned label to a downstream node, receive a message from the downstream node, and if the received message confirms that no conflict with the upstream assigned label exists at the downstream node, assign the upstream-assigned label, or if the received message confirms that a conflict with the upstream-assigned label exists at the downstream node, either select a new upstream-assigned label or wait until indication is received that the label resource has become available.

Abstract: A system and method for providing multi-topology support in RSVP-TE in a multi-protocol label switching network is provided. A method includes reserving path states for a traffic engineered label switched path (TE LSP), and releasing the reserved path states. The TE LSP is established within a single network topology in an environment of multiple network topologies, and the reserving path states includes sending a first resource reservation protocol with traffic engineering (RSVP-TE) message containing multi-topology information.

Abstract: Embodiments are provided herein to enable single level network abstraction for a service across one or more domains. The embodiments use a single network ID to identify a service and a corresponding virtual network topology across any number of domains at a physical network. A virtual network topology can be abstracted for each service, based on the physical underlying network topology. A network controller determines, for a service, the virtual network topology within a physical network, and binds the service to the virtual network topology via a virtual network ID, which defines a single forwarding domain of the virtual network topology across the physical network. The virtual network ID is then indicated to the nodes of the virtual network topology, thus enabling the nodes to identify and forward traffic for the service, within the single forwarding domain, between end clients from edge to edge of the physical network.

Abstract: An ingress node in a Software Defined Network (SDN) comprising a receiver for receiving a data packet, a processor coupled to the receiver and further configured to obtain the data packet from the receiver in a transport protocol agnostic manner, and encapsulate the data packet in an SDN packet header, wherein the packet header comprises SDN flow-specific information provided by an SDN controller, and a transmitter coupled to the processor and further configured to transmit the encapsulated data packet across a single SDN toward an egress node in the SDN.