Network fault system

• US 6,252,852 B1
• Filed: 02/11/1999
• Issued: 06/26/2001
• Est. Priority Date: 02/02/1996
• Status: Expired due to Fees

• Current Assignee: Telstra Corporation Limited (Telstra Group Ltd.)
• Original Assignee: Telestra Corporation Limited
• Inventors: Szymczak, Mark, Rowles, Christopher David, Sember, Peter Paul
• Primary Examiner(s): CANGIALOSI, SALVATORE A
• Application Number:
  US09/117,590
• Time in Patent Office: 866 Days
• Field of Search: 370/242, 455/423-425, 455/456, 455/457
• US Class Current: 370/242
• CPC Class Codes: H04L 41/0618 based on the physical or logical position
• CPC Class Codes: H04L 41/065 involving logical or physical relationship, e.g. grouping and hierarchies
• CPC Class Codes: H04L 41/5074 Handling of user complaints or trouble tickets
• CPC Class Codes: H04L 43/00 Arrangements for monitoring or testing data switching networks
• CPC Class Codes: H04L 43/06 Generation of reports
• CPC Class Codes: H04L 43/0811 by checking connectivity
• CPC Class Codes: H04L 43/106 using time related information in packets, e.g. by adding timestamps

Abstract

The fault system includes an interface for accessing first data fault representative of faults in the reported by users of mobile stations of the network, an interface for accessing second fault, data representative of faults in the network determined by a network analysis system, and pattern matching device for allocating the first and second fault data to fault patterns, representative of faults having at least one common characteristic. The common characteristics is geographic location and fault type. The fault system further includes pattern generation device for generating the fault pattern using respective fault templates to allocate the fault data to the fault patterns.

Claims

1. A network fault system for a mobile telecommunications network including:

a first interface for accessing first fault data representative of faults reported by users of mobile stations of said network;

a second interface for accessing second fault data representative of faults in said network determined by a network analysis system; and

pattern matching means for allocating said first and second fault data to fault patterns representative of faults having at least one common characteristic.

2. A network fault system as claimed in claim 1, wherein the common characteristic is geographic location.

3. A network fault system as claimed in claim 2, wherein a further common characteristic is fault type.

4. A network fault system as claimed in claim 1, including pattern generation means for generating said fault patterns using respective fault templates to allocate said fault data to said fault patterns.

5. A network fault system as claimed in claim 4, wherein said fault templates represent a predetermined condition having occurred over a predetermined period of time, said condition comprising a predetermined number of faults of a predetermined type having occurred.

6. A network fault system as claimed in claim 5, wherein said fault templates represent a logical relationship between at least two of said predetermined condition having occurred over a predetermined period of time.

7. A network fault system as claimed in claim 4, wherein said fault templates represent a predetermined number of faults of different predetermined types having occurred.

8. A network fault system as claimed in claim 1 or 4, wherein said fault patterns each include geographic data representing at least one geographic location associated with respective faults, said fault data each include location data representative of at least one geographic location associated with the fault represented by said fault data, and said pattern matching means allocates said fault data to one of said patterns when the location data of the fault data corresponds to the geographic data of the pattern.

9. A network fault system as claimed in claim 8, wherein to allocate the fault data to said pattern, the pattern further includes faults of the same type as the fault represented by said fault data.

10. A network fault system as claimed in claim 4, wherein said pattern generation means generates new fault patterns by applying said templates to said fault data not allocated to existing fault patterns.

11. A network fault system as claimed in claim 1, including a customer service system for providing access to said patterns when processing said faults reported by users, and for generating and storing said first fault data.

12. A network fault system as claimed in claim 1 or 11, including a distribution module allowing access, editing and transmission of said patterns by parties having different tasks in relation to processing of said patterns.

13. A network fault system as claimed in claim 12, wherein said patterns have respective statuses, and the status of a pattern is changed to closed by one of said parties when a network problem associated with the faults of the pattern is fixed.

14. A network fault system as claimed in claim 8, wherein said location data includes:

locations and location confidence values representing the probability of the fault of said fault data having occurred at at least one of the locations and another confidence value representing the probability of the fault not having occurred in said locations; and

said geographic data includes locations and location confidence values representing the probability of the faults of said pattern having occurred at at least one of said locations and another confidence value representing the probability of the faults not having occurred in said locations, said confidence values of said pattern being normalised.

15. A network fault system as claimed in claim 14, wherein said location data corresponds to said fault data when at least one of the locations of said location data is the same as one of the locations of said geographic data.

16. A network fault system as claimed in claim 15, wherein on allocating said fault data to said pattern, said confidence values of said pattern are the product of said location confidence values of said fault and said another confidence value of said pattern, the product of said location confidence values of said pattern and said another confidence value of said fault data and, for location confidence values of said fault data and said pattern having the same respective locations, the product of these location confidence values.

17. A fault pattern matching process including:

accessing first fault data representative of faults reported by users of mobile stations of a mobile telecommunications network;

accessing second fault data representative of faults in said network determined by a network analysis system; and

matching said first and second fault data to fault patterns representative of faults having at least one common characteristic.

18. A fault pattern matching process as claimed in claim 17, wherein the common characteristic is geographic location.

19. A fault pattern matching process as claimed in claim 18, wherein a further common characteristic is fault type.

20. A fault pattern matching process as claimed in claim 17, including generating said fault patterns using respective fault templates to allocate said fault data to said fault patterns.

21. A fault pattern matching process as claimed in claim 20, wherein said fault templates represent a predetermined condition having occurred over a predetermined period of time, said condition comprising a predetermined number of faults of a predetermined type having occurred.

22. A fault pattern matching process as claimed in claim 21, wherein said fault templates represent a logical relationship between at least two of said predetermined condition having occurred over a predetermined period of time.

23. A fault pattern matching process as claimed in claim 20, wherein said fault templates represent a predetermined number of faults of different predetermined types having occurred.

24. A fault pattern matching process as claimed in claim 17 or 20, wherein said fault patterns each include geographic data representing at least one geographic location associated with respective faults, said fault data each include location data representative of at least one geographic location associated with the fault represented by said fault data, and matching said fault data to one of said patterns occurs when the location data of the fault data corresponds to the geographic data of the pattern.

25. A fault pattern matching process as claimed in claim 24, wherein matching the fault data to said pattern, the pattern further includes faults of the same type as the fault represented by said fault data.

26. A fault pattern matching process as claimed in claim 20, including generating new fault patterns by applying said templates to said fault data not allocated to existing fault patterns.

27. A fault pattern matching process as claimed in claim 17, including providing access to said patterns when processing said faults reported by users, and generating and storing said first fault data.

28. A fault pattern matching process as claimed in claim 17 or 27, including enabling access, editing and transmission of said patterns by parties having different tasks in relation to processing of said patterns.

29. A fault pattern matching process as claimed in claim 28, wherein said patterns have respective statuses, and including one of said parties changing the status of a pattern to closed when a network problem associated with the faults of the pattern is fixed.

30. A fault pattern matching process as claimed in claim 24, wherein said location data includes:

locations and location confidence values representing the probability of the fault of said fault data having occurred at at least one of the locations and another confidence value representing the probability of the fault not having occurred in said locations; and

said geographic data includes locations and location confidence values representing the probability of the faults of said pattern having occurred at at least one of said locations and another confidence value representing the probability of the faults not having occurred in said locations, said confidence values of said pattern being normalised.

31. A fault pattern matching process as claimed in claim 30, wherein said location data corresponds to said fault data when at least one of the locations of said location data is the same as one of the locations of said geographic data.

32. A fault pattern matching process as claimed in claim 31, wherein said matching of said fault data to said pattern includes setting said confidence values of said pattern to the product of said location confidence values of said fault and said another confidence value of said pattern, the product of said location confidence values of said pattern and said another confidence value of said fault data and, for location confidence values of said fault data and said pattern having the same respective locations, the product of these location confidence values.