Network connectivity management
AssigneeVerizon Patent and Licensing Inc.
InventorsMatthew W. Turlington, Michael U. Bencheck, Scott R. Kotrla
Life of this patent
Estimating the term…
Abstract
Network connectivity management includes monitoring a circuit, wherein the circuit is a virtual connection between multiple networks via a provider core network. A device receives a plurality of network management messages associated with the circuit, and a determination is made regarding whether the circuit is experiencing a connectivity issue based on the network management messages. When it is determined that the circuit is experiencing a connectivity issue, then certain actions can be initiated.
Claims25
A method, comprising:
- identifying a circuit to monitor, the circuit including a virtual connection between multiple networks via a provider network and a physical connection between an access device and a provider edge device configured to provide an entry point to the provider network;
- configuring a maintenance entity association between the access device and the provider edge device such that at least one of the access device and provider edge device is configured to perform a fault determination and initiate a corrective action in response to a network management message of a first protocol, the association including at least one criterion for determining presence of connectivity issues;
- receiving, using at least one of the provider edge device and the access device, the network management message associated with the circuit;
- determining, by the provider edge device according to the at least one criterion of the association, if the physical connection portion of the circuit is experiencing a connectivity issue based on the network management message;
- and
- automatically in response to determining that the physical connection portion of the circuit is experiencing a connectivity issue, translating the network management message of the first protocol to an interface status of a second protocol to identify a pseudowire pathway associated with the physical connection portion experiencing the connectivity issue, placing the interface status of the identified pseudowire pathway in a failed state, and sending a release message thereby initiating a takedown of the identified pseudowire pathway to withdraw at least a portion of the virtual connection.
A system, comprising:
- a provider network configured to facilitate data communications between a plurality of networks using a data link layer communications protocol;
- a provider edge device communicatively coupled to an access device, the access device communicatively coupled to at least one of the plurality of networks, the provider edge device configured to provide an entry point to the provider network to hand off network traffic from the at least one of the plurality of networks to the provider network;
- a circuit configured to include a logical communications pathway between at least two of the plurality of networks via the provider network and a physical connection between the access device and the provider edge device;
- a pseudowire pathway configured to support the logical communications pathway of the circuit, wherein the pseudowire pathway is associated with the data link layer communications protocol;
- and
- wherein the provider edge device is configured to:
- configure a maintenance entity association between the access device and the provider edge device such that at least one of the access device and provider edge device is configured to perform a fault determination and initiate a corrective action in response to a network management message of a first protocol, the association including at least one criterion for determining presence of connectivity issue;
- receive from the access device the network management message associated with the circuit;
- determine according to the at least one criterion of the association if the physical connection portion of the circuit is experiencing a connectivity issue based on the network management message;
- and
- automatically in response to determining that the physical connection portion of the circuit is experiencing a connectivity issue, translate the network management message of the first protocol to an interface status of a second protocol to identify a pseudowire pathway associated with the physical connection portion experiencing the connectivity issue, initiate placement of the interface status of the identified pseudowire pathway in a failed state, and initiate a takedown of the identified pseudowire pathway.
A non-transitory computer-readable medium tangibly embodying computer-executable instructions configured to:
- facilitate data communication between a network and a provider network, wherein the network is configured to utilize a first protocol and the provider network is configured to utilize a second protocol;
- configure a maintenance entity association between an access device and a provider edge device such that at least one of the access device and provider edge device configured to perform a fault determination and initiate a corrective action in response to a network management message of the first protocol, the association including at least one criterion for determining presence of connectivity issues;
- receive the network management message associated with a circuit, the circuit including a virtual connection between multiple networks via the provider network and a physical connection between an access device and a provider edge device configured to provide an entry point to the provider network;
- determine according to the at least one criterion of the association if the physical connection portion of the circuit is experiencing a connectivity issue based on the network management message;
- and
- automatically in response to determining that the physical connection portion of the circuit is experiencing a connectivity issue, translate the network management message of the first protocol to an interface status of the second protocol to identify a pseudowire pathway associated with the physical connection portion experiencing the connectivity issue, initiate placement of the interface status of the identified pseudowire pathway in a failed state, and initiate a takedown of the identified pseudowire pathway.
Dependencies are inferred from the claim text.