Abstract: In a source provider edge (PE) router, a method of forming a data multicast distribution tree (MDT) comprising the steps of monitoring a rate of multicast data traffic within a default MDT, determining that the rate exceeds a threshold, sending a join message to at least one receiver PE router in response to the determining, wherein the join message comprises a MDT number that identifies the data MDT, receiving a path message from the at least one receiver PE router and thereby forming the data MDT, and sending multicast data traffic via the data MDT.

Abstract: In a receiver provider edge (PE) router, a method for supporting protocol independent multicast source-specific mode (PIM-SSM) using multicast resource reservation protocol-traffic engineering (mRSVP-TE) comprising the steps of receiving a protocol independent multicast (PIM) join message, in response to receiving the PIM join message sending a path message to a source PE router, wherein the path message is a multicast resource reservation protocol-traffic engineering (mRSVP-TE) message, and sending the PIM join message to the source PE router, wherein the path message and the PIM join message trigger setup of a data multicast data tree (MDT), creating a PIM state, and receiving multicast data traffic via the data MDT using the PIM state.

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 a source provider edge (PE) router, a method for supporting protocol independent multicast sparse-mode (PIM-SM) using multicast resource reservation protocol-traffic engineering (mRSVP-TE) comprising the steps of creating a protocol independent multicast (PIM) state, sending a first unicast data message to a rendezvous point (RP) PE router using the PIM state, wherein the first unicast data message is a PIM register message encapsulated as a unicast multiprotocol label switching (MPLS) packet, receiving a PIM join message from the RP PE router, wherein the PIM join message triggers creating a second PIM state, sending a second unicast data message to the RP PE router via a default multicast distribution tree (MDT) using the second PIM state, receiving a PIM register-stop message from the RP PE router, wherein the PIM register-stop message suspends sending the second unicast data message.

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 a network node positioned inside a Multiprotocol Label Switching (MPLS) core network, a method of establishing a multicast Virtual Private Network (MVPN) comprising receiving a packet for multicast data from a Virtual Private Network (VPN) via a provider edge (PE) node positioned on the edge of the MPLS core network, wherein the network node is a root node and the PE node is a leaf node of a multicast Label Switched Path (mLSP) established in the MPLS core network, swapping an upstream label in the packet that is assigned to the PE node with a downstream label assigned to a next hop of the mLSP, and forwarding the packet to the next hop.

Abstract: A network component for supporting packet forwarding in a United Router Farm (URF), the network component comprising a processor configured to receive a packet, encapsulate the packet using a URF header comprising a URF Layer Two (L2) header that indicates Media Access Control (MAC) addresses of current and next hops, an outer label that indicates a tunnel to a destination node in the URF, and an inner label that indicates an egress port on the destination node, and send the packet to a next hop in the URF after encapsulating the packet.

Abstract: A network node for forwarding a data packet to a virtual network. The network node may maintain a table comprising one-to-one mapping information between one or more virtual private network (VPN) labels and one or more identifying labels for a destination virtual network. The network node may receive a data packet from a Multiprotocol Label Switching (MPLS) network. The data packet may comprise one or more VPN labels, at least one of which may be a MPLS Big Label Value that supports one-to-one mapping for more than one million destination virtual network addresses. The MPLS Big Label Value may comprise a destination virtual network address. The network element may map the one or more VPN labels to corresponding identifying labels for the destination virtual network according to the table, and forward the data packet to the destination virtual network.

Abstract: One embodiment of the present invention provides a computing system. The computing system includes a processor, a memory, a logical switch management mechanism, and a layer-2 path management mechanism. The logical switch management mechanism operates the computing system in conjunction with a plurality of remote switches as a single logical switch. The layer-2 path management mechanism includes a path calculation mechanism and a layer-2 forwarding table. The path calculation mechanism calculates layer-2 shortest paths among the computing system and the remote switches. The layer-2 forwarding table is for a first switch in the plurality of remote switches and created based on one or more of the shortest paths, wherein a respective entry in the forwarding table corresponds to a layer-2 network address. The layer-2 path management mechanism suppresses advertisement of the shortest paths outside of the logical switch, thereby hiding internal paths of the logical switch.

Abstract: One embodiment of the present invention provides a computing system. The computing system includes a processor, a memory, a discovery mechanism, a switch management mechanism, and a configuration management mechanism. The discovery mechanism discovers a remote switch. The switch management mechanism registers the remote switch and transmits a switch image to the remote switch, thereby allowing the remote switch to install the image. The configuration management mechanism configures the remote switch, thereby allowing the remote switch to be controlled by the computing system.

Abstract: A method for network control, comprising receiving a request for a network view from an application at a Software Defined Network (SDN) controller, creating a network view from a network map, wherein the network map comprises a representation of a plurality of network devices and network paths in a SDN-based multiple layer network, and wherein the network view comprises at least a portion of the devices or paths in the network map, and sharing the network view with the application.

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: 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.

Abstract: A network component for supporting packet forwarding in a United Router Farm (URF), the network component comprising a processor configured to receive a packet, encapsulate the packet using a URF header comprising a URF Layer Two (L2) header that indicates Media Access Control (MAC) addresses of current and next hops, an outer label that indicates a tunnel to a destination node in the URF, and an inner label that indicates an egress port on the destination node, and send the packet to a next hop in the URF after encapsulating the packet.

Abstract: In a receiver provider edge (PE) router, a method for supporting protocol independent multicast source-specific mode (PIM-SSM) using multicast resource reservation protocol-traffic engineering (mRSVP-TE) comprising the steps of receiving a protocol independent multicast (PIM) join message, in response to receiving the PIM join message sending a path message to a source PE router, wherein the path message is a multicast resource reservation protocol-traffic engineering (mRSVP-TE) message, and sending the PIM join message to the source PE router, wherein the path message and the PIM join message trigger setup of a data multicast data tree (MDT), creating a PIM state, and receiving multicast data traffic via the data MDT using the PIM state.

Abstract: In a source provider edge (PE) router, a method of forming a data multicast distribution tree (MDT) comprising the steps of monitoring a rate of multicast data traffic within a default MDT, determining that the rate exceeds a threshold, sending a join message to at least one receiver PE router in response to the determining, wherein the join message comprises a MDT number that identifies the data MDT, receiving a path message from the at least one receiver PE router and thereby forming the data MDT, and sending multicast data traffic via the data MDT.

Abstract: In a network node positioned inside a Multiprotocol Label Switching (MPLS) core network, a method of establishing a multicast Virtual Private Network (MVPN) comprising receiving a packet for multicast data from a Virtual Private Network (VPN) via a provider edge (PE) node positioned on the edge of the MPLS core network, wherein the network node is a root node and the PE node is a leaf node of a multicast Label Switched Path (mLSP) established in the MPLS core network, swapping an upstream label in the packet that is assigned to the PE node with a downstream label assigned to a next hop of the mLSP, and forwarding the packet to the next hop.