Fault management in a VDSL network

• US 7,134,135 B2
• Filed: 08/01/2001
• Issued: 11/07/2006
• Est. Priority Date: 08/01/2000
• Status: Active Grant

• Current Assignee: Qwest Communications International Incorporated (Lumen Technologies, Inc.)
• Original Assignee: Qwest Communications International Incorporated (Lumen Technologies, Inc.)
• Inventors: Cerami, Richard, Storaasli, Roxanna, Figueroa, Timothy
• Primary Examiner(s): BUI, KIEU OANH T
• Application Number:
  US09/921,277
• Publication Number:
  US 20020078017A1
• Time in Patent Office: 1,924 Days
• Field of Search: 725/100, 725/105, 725/106, 725/109, 725/111, 725/116, 725/120, 709/203, 709/217, 709/224, 709/227, 709/232, 370/353, 370/396, 370/397, 370/485, 707/1, 707/10, 714/4, 714/43
• US Class Current: 725/105
• CPC Class Codes: G06Q 10/087 Inventory or stock management, e.g. order filling, procurement or balancing against orders
• CPC Class Codes: H04L 12/66 Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
• CPC Class Codes: H04L 41/06 Management of faults, events, alarms or notifications
• CPC Class Codes: H04L 41/0631 using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
• CPC Class Codes: H04L 41/0654 using network fault recovery ring fault isolation or reconfiguration in loop networks without recovery actions by a network management system H04L12/437
• CPC Class Codes: H04L 41/0896 Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities flow or congestion control using dynamic resource allocation, e.g. in-call renegotiation, H04L47/76
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 41/32 Specific management aspects for broadband networks
• CPC Class Codes: H04L 41/40 using virtualisation of network functions or resources, e.g. SDN or NFV entities
• CPC Class Codes: H04L 41/5003 Managing SLA; Interaction between SLA and QoS
• CPC Class Codes: H04L 41/5009 Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
• CPC Class Codes: H04L 41/5025 by proactively reacting to service quality change, e.g. by reconfiguration after service quality degradation or upgrade
• CPC Class Codes: H04L 41/5032 Generating service level reports
• CPC Class Codes: H04L 41/5061 characterised by the interaction between service providers and their network customers, e.g. customer relationship management
• CPC Class Codes: H04L 41/5067 Customer-centric QoS measurements
• CPC Class Codes: H04L 41/507 Filtering out customers affected by service problems
• CPC Class Codes: H04L 41/5074 Handling of user complaints or trouble tickets
• CPC Class Codes: H04L 41/509 wherein the managed service relates to media content delivery, e.g. audio, video or TV
• CPC Class Codes: H04L 43/00 Arrangements for monitoring or testing data switching networks
• CPC Class Codes: H04L 43/0811 by checking connectivity
• CPC Class Codes: H04L 43/0817 : by checking functioning
• CPC Class Codes: H04L 43/0823 : Errors, e.g. transmission errors
• CPC Class Codes: H04L 43/0882 : Utilisation of link capacity
• CPC Class Codes: H04L 43/091 : Measuring contribution of individual network components to actual service level
• CPC Class Codes: H04L 43/10 : Active monitoring, e.g. heartbeat, ping or trace-route
• CPC Class Codes: H04L 43/16 : Threshold monitoring
• 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
• CPC Class Codes: H04L 43/50 : Testing arrangements
• CPC Class Codes: H04L 69/40 : for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06
• CPC Class Codes: H04M 11/062 : using different frequency bands for speech and other data
• CPC Class Codes: H04N 21/6125 : involving transmission via Internet transmission by internet of broadcast information H04H60/82
• CPC Class Codes: H04N 21/6473 : Monitoring network processes errors for recovering from a failure of a protocol instance or entity H04L69/40
• CPC Class Codes: H04N 21/64738 : Monitoring network characteristics, e.g. bandwidth, congestion level data switched network analysis H04L41/14; monitoring functioning in data switched networks H04L43/0817; flow control in packet networks H04L47/10
• CPC Class Codes: Y10S 707/99931 : Database or file accessing

Abstract

A method for managing a plurality of failures in a video and data network is provided. The method includes discovering a failure in the video and data network. The failure is correlated with the plurality of failures to determine related failures. A root cause of the failure is then isolated. Next, the related failures that were generated as a result of the root cause failure are suppressed. If the root cause is automatically resolvable, the root cause is resolved.

Claims

1. A method for managing a plurality of failures in a video and data network comprising:

discovering a failure in the video and data network;

correlating the failure with the plurality of failures to determine related failures;

isolating a root cause of the failure;

suppressing the related failures that were generated as a result of the root cause failure;

determining if the root cause is automatically resolvable; and

if the root cause is automatically resolvable, resolving the root cause.

2. The method of claim 1, wherein the video and data network comprises a Digital Subscriber Line (xDSL) network.

3. The method of claim 1, wherein the video and data network comprises a Very high bit rate DSL (VDSL) network.

4. The method of claim 1, further comprising creating a repair ticket for the failure.

5. The method of claim 1, wherein correlating the failure comprises:

interacting with a physical network transport inventory; and

determining upstream and downstream physical network elements from the failure.

6. The method of claim 5, wherein correlating the failure comprises:

interacting with a virtual network transport inventory; and

determining upstream and downstream virtual network elements from the failure.

7. The method of claim 6, wherein correlating the failure comprises:

correlating related failures from the upstream and downstream physical and virtual network elements with the failure.

8. The method of claim 1, wherein isolating the root cause of the failure comprises gathering performance data.

9. The method of claim 1, wherein isolating the root cause of the failure comprises performing tests on the video and data network.

10. The method of claim 9, wherein performing tests on the network comprises performing a physical connectivity test.

11. The method of claim 10, wherein the physical connectivity test comprises a Physical Loop Test.

12. The method of claim 9, wherein performing tests on the video and data network comprises performing a virtual connectivity test.

13. The method of claim 12, wherein the physical connectivity test comprises an Operations And Maintenance (OAM) test.

14. The method of claim 1, further comprising determining one or more user'"'"'s affected by the failure.

15. The method of claim 14, wherein determining one or more user'"'"'s affected by the failure comprises using customer data to correlate the one or more users to the root cause.

16. The method of claim 1, further comprising notifying the one or more user'"'"'s affected by the root cause.

17. The method of claim 1, further comprising opening a repair ticket in one or more records of the one or more user'"'"'s affected by the root cause.

18. The method of claim 17, further comprising determining when the root cause was resolved.

19. The method of claim 18, further comprising closing the repair ticket in the one or more records of the one or more user'"'"'s affected by the root cause when the root cause has been resolved.

20. The method of claim 19, wherein notifying the one or more user'"'"'s affected by the root cause when the root cause is resolved.

21. The method of claim 20, further comprising validating the resolution of the root cause.

22. The method of claim 21, wherein validating the resolution of the failure comprises testing a physical connectivity of the video and data network.

23. The method of claim 21, wherein validating the resolution of the failure comprises testing a virtual connectivity of the video and data network.

24. The method of claim 1, further comprising storing the root cause and failure in a history of failures.