NETWORK CONNECTIVITY MANAGEMENT

• US 20110116385A1
• Filed: 11/13/2009
• Published: 05/19/2011
• Est. Priority Date: 11/13/2009
• Status: Active Grant

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Inventors: Bencheck, Michael U., Kotrla, Scott R., Turlington, Matthew W.
• Granted Patent: US 9,521,055 B2
• Time in Patent Office: Days
• US Class Current: 370/242
• CPC Class Codes: H04L 12/4633 Interconnection of networks using encapsulation techniques, e.g. tunneling
• CPC Class Codes: H04L 12/4641 Virtual LANs, VLANs, e.g. virtual private networks [VPN] LAN interconnection over a bridge based backbone H04L12/462; encapsulation techniques H04L12/4633; routing of packets H04L45/00; packet switches H04L49/00; virtual private networks for security H04L63/0272
• CPC Class Codes: H04L 41/0681 Configuration of triggering conditions
• CPC Class Codes: H04L 43/0811 by checking connectivity
• CPC Class Codes: H04L 43/20 the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV

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.

Claims

1. A method, comprising:

identifying a circuit to monitor, wherein the circuit is a virtual connection between multiple networks via a provider core network;

receiving a plurality of network management messages associated with the circuit in a provider edge device;

determining, in a computing device, if the circuit is experiencing a connectivity issue based on the network management messages;

identifying a pathway associated with the circuit; and

when it is determined that the circuit is experiencing a connectivity issue, then initiating a takedown of the identified pathway.

2. The method of claim 1, wherein the pathway is a data link layer pathway.

3. The method of claim 1, wherein the circuit is at least one of an Ethernet Virtual Connection (EVC), an Ethernet Virtual Private Line (EVPL), a Virtual Local Area Network (VLAN), and a Virtual Private Network (VPN) Tunnel.

4. The method of claim 1, wherein the circuit is a Virtual Local Area Network (VLAN) tunnel and identified by a Virtual Local Area Network (VLAN) tag.

5. The method of claim 1, wherein the plurality of network management messages associated with the circuit are Ethernet OAM messages in accordance with IEEE 802.1ag.

6. The method of claim 1, wherein the provider edge device is a MultiProtocol Label Switching (MPLS) label edge router.

7. The method of claim 1, further comprising initiating an alert when it is determined that the circuit is experiencing a connectivity issue.

8. The method of claim 1, further comprising:

configuring the provider edge device to detect an Ethernet 802.1ag continuity check message;

determining, in the provider edge device, a number of missed Ethernet 802.1ag continuity check messages; and

determining that the circuit is experiencing a connectivity issue when the number of missed Ethernet 802.1ag continuity check messages exceeds a predetermined threshold.

9. A system, comprising:

a provider network configured to facilitate data communications between a plurality of networks using a data link layer communications protocol;

a circuit configured to create a logical communications pathway between at least two of the plurality of networks via the provider network;

a pseudowire configured to support the circuit, wherein the pseudowire is associated with a data link layer communications protocol;

an access device communicatively coupled to at least one of the plurality of networks; and

a provider edge device communicatively coupled to the access device, the provider edge device being configured to hand off network traffic from at least one network to the provider network, wherein at least one of the provider edge device and the access device is configured to;

receive a plurality of network management messages associated with the circuit;

determine if the circuit is experiencing a connectivity issue based on the network management messages; and

when it is determined that the circuit is experiencing a connectivity issue, then initiating a takedown of the pseudowire.

10. The system of claim 9, wherein the data link layer communications protocol is at least one of MultiProtocol Label Switching (MPLS), Frame Relay, and Asynchronous Transfer Mode (ATM).

11. The system of claim 9, wherein the network communicatively coupled to the access device utilizes Ethernet, and the access device is configured to facilitate communication between the Ethernet network and the provider network.

12. The system of claim 9, wherein the circuit is at least one of an Ethernet Virtual Connection (EVC), an Ethernet Virtual Private Line (EVPL), a Virtual Local Area Network (VLAN), and a Virtual Private Network (VPN) Tunnel.

13. The system of claim 9, wherein the circuit is a Virtual Local Area Network (VLAN) tunnel and identified by a Virtual Local Area Network (VLAN) tag.

14. The system of claim 9, wherein the plurality of network management messages associated with the circuit are Ethernet OAM messages in accordance with IEEE 802.1ag.

15. The system of claim 9, wherein the provider edge device is a MultiProtocol Label Switching (MPLS) label edge router.

16. The system of claim 9, wherein at least one of the provider edge device and the access device is further configured to initiate an alert when it is determined that the circuit is experiencing a connectivity issue.

17. The system of claim 9, wherein at least one of the provider edge device and the access device is further configured to:

detect an Ethernet 802.1ag continuity check message;

determine a number of missed Ethernet 802.1ag continuity check messages; and

determine that the circuit has experienced a fault when the number of missed Ethernet 802.1ag continuity check messages exceeds a predetermined threshold.

18. A computer-readable medium tangibly embodying computer-executable instructions configured to:

facilitate data communication between a network and a provider network, wherein the provider network is configured to utilize a first protocol and the network is configured to utilize a second protocol;

receive a plurality of network management messages associated with a circuit, wherein the customer circuit is a virtual connection between multiple networks via the provider network;

determine if the circuit is experiencing a connectivity issue based on the network management messages;

identify a pseudowire associated with the circuit; and

initiate a takedown of the pseudowire when it is determined that the circuit is experiencing a connectivity issue.

19. The computer-readable medium of claim 18, wherein the first protocol is at least one of MultiProtocol Label Switching (MPLS), Frame Relay, and Asynchronous Transfer Mode (ATM), and wherein the second protocol is Ethernet.

20. The computer-readable medium of claim 18, wherein the plurality of network management messages associated with the circuit are Ethernet OAM messages in accordance with IEEE 802.1ag.

21. The computer-readable medium of claim 18, further comprising computer-executable instructions configured to send an alert to a customer associated with the circuit when it is determined that the circuit is experiencing a connectivity issue.

22. The computer-readable medium of claim 18, further comprising computer-executable instructions configured to:

detect an Ethernet 802.1ag continuity check message;

determine a number of missed Ethernet 802.1ag continuity check messages; and

determine that the circuit is experiencing a connectivity issue when the number of missed Ethernet 802.1ag continuity check messages exceeds a predetermined threshold.