Abstract: A network controller detects a congested peering link between a first router and a second router, and selects a first group of traffic flows from among the plurality of traffic flows to be offloaded from the congested peering link. The congested peering link carries a plurality of traffic flows, and the first group of traffic flows is associated with a first steering entity indicative of destination information for the first group of traffic flows. The network controller then selects an alternate peering link between the first and second routers to which to offload the first group of traffic flows from the congested peering link, and steers the first group of traffic flows from the congested peering link to the alternate peering link.

Abstract: The present disclosure generally discloses improvements in computer performance in communication networks, which may include improvements in computer performance in supporting discovery of ingress provider edge (PE) devices in a communication network using egress peer engineering (EPE) and software defined networking (SDN). The ingress PE devices of a network may have peering relationships with an egress peer link of an egress peer node of the network. The ingress PE devices may be discovered by identifying a set of traffic flows on an egress peer link of an egress peer node, identifying a set of ingress PE devices that have peering relationships with the egress peer node, determining bandwidth usage information, selecting, from the set of ingress PE devices based on the bandwidth usage information, a set of selected ingress PE devices, and initiating a management action for at least one of the selected ingress PE devices.

Abstract: The present disclosure discloses improvements in computer performance for supporting traffic steering based on a traffic steering capability. The traffic steering capability may be configured to support steering of traffic of a traffic flow, to be supported by a provider core network, along an end-to-end path between a source ingress provider edge router of the provider core network and a destination outside of the provider core network based on determination of the end-to-end path for the traffic flow (e.g., based on end-to-end path performance measurement information that includes internal path performance measurement information of potential internal paths of the provider core network and external path performance measurement information of potential external paths outside of the provider core network) and programming of the provider core network to support steering of the traffic of the traffic flow onto the end-to-end path for the traffic flow (e.g.

Abstract: The present disclosure discloses improvements in computer performance for supporting traffic steering based on a traffic steering capability. The traffic steering capability may be configured to support steering of traffic of a traffic flow, to be supported by a provider core network, along an end-to-end path between a source ingress provider edge router of the provider core network and a destination outside of the provider core network based on determination of the end-to-end path for the traffic flow (e.g., based on end-to-end path performance measurement information that includes internal path performance measurement information of potential internal paths of the provider core network and external path performance measurement information of potential external paths outside of the provider core network) and programming of the provider core network to support steering of the traffic of the traffic flow onto the end-to-end path for the traffic flow (e.g.

Abstract: The present disclosure generally discloses improvements in computer performance in communication networks, which may include improvements in computer performance in supporting discovery of ingress provider edge (PE) devices in a communication network using egress peer engineering (EPE) and software defined networking (SDN). The ingress PE devices of a network may have peering relationships with an egress peer link of an egress peer node of the network. The ingress PE devices may be discovered by identifying a set of traffic flows on an egress peer link of an egress peer node, identifying a set of ingress PE devices that have peering relationships with the egress peer node, determining bandwidth usage information, selecting, from the set of ingress PE devices based on the bandwidth usage information, a set of selected ingress PE devices, and initiating a management action for at least one of the selected ingress PE devices.

Abstract: A technique for implementing an optical virtual private network is disclosed. In one particular exemplary embodiment, the technique may be realized by a method comprising the steps of managing at least one client edge-virtual private network at a client edge by a service provider; and supporting a set of client edge-users at each client edge-virtual private network at each client edge wherein each client edge provides at least one virtual private network service to each client edge-user; wherein each client edge determines connectivity associated with each client edge-user and the service provider establishes the connectivity determined by each client edge.

Abstract: A method of establishing a multi-segment pseudowire (MS-PW) across domains executing different pseudowire signaling protocols augments a Label Distribution Protocol (LDP) label message to include a MS-PW Type-Length-Value (TLV). The MS-PW TLV carries pseudowire signal protocol information associated with signaling protocols of other segments of the MS-PW. As a result, a multi-segment pseudowire can be extended between domains that execute different pseudowire signaling protocols.

Abstract: An architecture for providing service mediation in a network having a Layer-2 domain and an MPLS domain includes at least one Layer-2 provider edge device in communication with a first customer site; at least one Layer-2 edge device in communication with the Layer-2 provider edge device; at least one MPLS mediation edge device in communication with the Layer-2 edge device; and at least one MPLS provider edge device in communication with both the MPLS mediation edge device and a second customer site. An end-to-end connection is established using native Layer-2 signaling, if any, in the Layer-2 domain and PWE3 signaling protocols in the MPLS domain. The MPLS mediation edge device resolves associations between Layer-2 edge devices and MPLS provider edge devices. The service is “mediated” in the sense that native Layer-2 signaling is terminated at the MME, and a new domain, i.e., pseudowire, is established across the MPLS domain.

Abstract: Frames of customer traffic may be encapsulated by adding Mac-in-Mac (MiM) encapsulation fields for transportation of the frames over a portion of provider network. The MiM encapsulated traffic may be further encapsulated using VPLS by adding VPLS encapsulation fields for transportation of the frames over another portion of the provider network. The MiM encapsulations use provider network_MAC addresses which enables VPLS MAC learning to occur using provider network MAC address space. MiM tunnels are mapped to VPLS service instances which are assigned pseudowire tags for transportation over the VPLS portion of provider network. The MiM header is retained when the MiM encapsulated frames are transported over the VPLS portion of the provider network. As VPLS frames exit the core network, the VPLS encapsulation fields are removed to extract the original MiM encapsulated frames for further transportation over the MiM portion of the provider network.

Abstract: Described are a network, computer program product, and method of distributing routing information for a virtual private network (VPN) application through a packet-switched network (PSN) having fully meshed provider edge (PE) routers through Provider Backbone Bridge (PBB) tunnels. A PE router is configured to participate in a VPN and to run a BGP (Border Gateway Protocol) as an auto-discovery process for finding one or more other PE routers participating in the VPN. The VPN is associated with a PBB tunnel. A service instance identifier (I-SID) is assigned to the VPN. The PE router advertises membership in the VPN by including the I-SID assigned to the VPN in a BGP message issued during the auto-discovery process.

Abstract: A Layer-2 virtual private network arrangement and method is disclosed for switched virtual circuits. The switched virtual circuit Layer-2 VPN includes logical ports of two types, customer and provider, and port information tables to relate both types which provides simplified provisioning and a degree of customer autonomy regarding establishing virtual connections without the assistance of the service provider across the service provider's network. The switched virtual circuit Layer-2 VPN is particularly useful for overcoming the need for customers to store and manipulate provider addresses with respect to closed user groups as is done in existing Layer-2 VPNs known in the art.

Abstract: An apparatus and a method for layer-2 and layer-3 VPN discovery are disclosed. The apparatus is incorporated in a network, and the network includes a first carrier network. The first carrier network includes at least two layer-1 provider edge devices. Layer-1 VPN information is created within the first carrier network. BGP next hop information passes within the first carrier network. The BGP next hop information is for a selected one of the following: a layer-2 VPN-based provider edge device, a layer-3 VPN-based provider edge device, and a layer-2 and layer-3 VPN-based provider edge device. The network also includes a second carrier network within which the BGP next hop information is used for VPN discovery.

Abstract: An apparatus and a method for layer-2 and layer-3 VPN discovery are disclosed. The apparatus is incorporated in a network, and the network includes a first carrier network. The first carrier network includes at least two layer-1 provider edge devices. Layer-1 VPN information is created within the first carrier network. BGP next hop information passes within the first carrier network. The BGP next hop information is for a selected one of the following: a layer-2 VPN-based provider edge device, a layer-3 VPN-based provider edge device, and a layer-2 and layer-3 VPN-based provider edge device. The network also includes a second carrier network within which the BGP next hop information is used for VPN discovery.

Abstract: A technique for implementing an optical virtual private network is disclosed. In one particular exemplary embodiment, the technique may be realized by a method comprising the steps of managing at least one client edge-virtual private network at a client edge by a service provider; and supporting a set of client edge-users at each client edge-virtual private network at each client edge wherein each client edge provides at least one virtual private network service to each client edge-user; wherein each client edge determines connectivity associated with each client edge-user and the service provider establishes the connectivity determined by each client edge.

Abstract: A technique for implementing an optical virtual private network is disclosed. In one particular exemplary embodiment, the technique may be realized by a method comprising the steps of managing at least one client edge-virtual private network at a client edge by a service provider; and supporting a set of client edge-users at each client edge-virtual private network at each client edge wherein each client edge provides at least one virtual private network service to each client edge-user; wherein each client edge determines connectivity associated with each client edge-user and the service provider establishes the connectivity determined by each client edge.

Abstract: Described are a network, computer program product, and method of distributing routing information for a virtual private network (VPN) application through a packet-switched network (PSN) having fully meshed provider edge (PE) routers through Provider Backbone Bridge (PBB) tunnels. A PE router is configured to participate in a VPN and to run a BGP (Border Gateway Protocol) as an auto-discovery process for finding one or more other PE routers participating in the VPN. The VPN is associated with a PBB tunnel. A service instance identifier (I-SID) is assigned to the VPN. The PE router advertises membership in the VPN by including the I-SID assigned to the VPN in a BGP message issued during the auto-discovery process.

Abstract: A technique for recovering MPLS or IP-based pseudo-wires or layer-2 VPNs to a backup site using a backup pseudo-wire is provided. In one particular exemplary embodiment, the technique may be realized by a mechanism that allows one end of the original pseudo-wire to dynamically and automatically establish a backup pseudo-wire to an alternate destination without requiring an operator intervention or manual configuration of alternate destinations. This mechanism is triggered when one end of an emulated service experiences a failure such as a node failure, a link failure, and the like, or an intentional shut-down. A VPN auto-discovery mechanism is employed to inform all of the potential attachment circuits of the existence of the backup destinations that can be used in case of failure situations.

Abstract: An architecture for providing service mediation in a network having a Layer-2 domain and an MPLS domain includes at least one Layer-2 provider edge device in communication with a first customer site; at least one Layer-2 edge device in communication with the Layer-2 provider edge device; at least one MPLS mediation edge device in communication with the Layer-2 edge device; and at least one MPLS provider edge device in communication with both the MPLS mediation edge device and a second customer site. An end-to-end connection is established using native Layer-2 signaling, if any, in the Layer-2 domain and PWE3 signaling protocols in the MPLS domain. The MPLS mediation edge device resolves associations between Layer-2 edge devices and MPLS provider edge devices. The service is “mediated” in the sense that native Layer-2 signaling is terminated at the MME, and a new domain, i.e., pseudowire, is established across the MPLS domain.

Abstract: Frames of customer traffic may be encapsulated by adding Mac-in-Mac (MiM) encapsulation fields for transportation of the frames over a portion of provider network. The MiM encapsulated traffic may be further encapsulated using VPLS by adding VPLS encapsulation fields for transportation of the frames over another portion of the provider network. The MiM encapsulations use provider network_MAC addresses which enables VPLS MAC learning to occur using provider network MAC address space. MiM tunnels are mapped to VPLS service instances which are assigned pseudowire tags for transportation over the VPLS portion of provider network. The MiM header is retained when the MiM encapsulated frames are transported over the VPLS portion of the provider network. As VPLS frames exit the core network, the VPLS encapsulation fields are removed to extract the original MiM encapsulated frames for further transportation over the MiM portion of the provider network.

Abstract: Frames of customer traffic may be encapsulated by adding Mac-in-Mac (MiM) encapsulation fields for transportation of the frames over a portion of provider network. The MiM encapsulated traffic may be further encapsulated using VPLS by adding VPLS encapsulation fields for transportation of the frames over another portion of the provider network. The MiM encapsulations use provider network_MAC addresses which enables VPLS MAC learning to occur using provider network MAC address space. MiM tunnels are mapped to VPLS service instances which are assigned pseudowire tags for transportation over the VPLS portion of provider network. The MiM header is retained when the MiM encapsulated frames are transported over the VPLS portion of the provider network. As VPLS frames exit the core network, the VPLS encapsulation fields are removed to extract the original MiM encapsulated frames for further transportation over the MiM portion of the provider network.