Testing platform integration methodology

• US 7,103,795 B1
• Filed: 05/31/2002
• Issued: 09/05/2006
• Est. Priority Date: 05/31/2002
• Status: Expired due to Fees

• Current Assignee: Sprint Communications Company LP (Deutsche Telekom AG)
• Original Assignee: Sprint Communications Company LP (Deutsche Telekom AG)
• Inventors: Hansen, Kevin
• Primary Examiner(s): Beausoliel, Robert
• Assistant Examiner(s): MCCARTHY, CHRISTOPHER S
• Application Number:
  US10/160,680
• Time in Patent Office: 1,558 Days
• Field of Search: 379/9.03, 379/9.04, 379/10.01, 379/9.02, 379/27.04, 379/29.09, 379/29.1, 714/57, 714/56, 714/4
• US Class Current: 714/4.1
• CPC Class Codes: H04L 41/064 involving time analysis
• CPC Class Codes: H04L 41/0659 by isolating or reconfiguring faulty entities
• CPC Class Codes: H04L 41/22 comprising specially adapted graphical user interfaces [GUI]
• CPC Class Codes: H04L 43/50 Testing arrangements
• CPC Class Codes: H04M 3/08 Indicating faults in circuits or apparatus
• CPC Class Codes: H04M 3/10 Providing fault- or trouble-signals
• CPC Class Codes: H04M 3/22 Arrangements for supervision, monitoring or testing

Abstract

A method for automatically testing elements in a telecommunications network. An automated testing protocol is initiated based on the notification of a network event. When test results are received from the automated testing protocol, a trouble ticket is automatically opened containing the test results. The trouble ticket is then routed to the appropriate party. In embodiments of the invention, test results are logged, a database is queried to determine if the event has occurred previously, the trouble ticket is prioritized based on the severity of the event, and a time stamp is placed on the trouble ticket. The automated testing protocol and the event correlation database can be accessed through a graphical user interface. Multiple automated testing modules can be integrated into a single graphical user interface. Users can log in to prevent interference among users.

Claims

1. A method for automatically testing elements in a telecommunications network comprising:

receiving notification of a network event;

verifying the existence of the event;

determining whether the event has been previously reported; and

responsive to the determination that the event has not been previously reported, performing steps comprising;

initiating an automated testing protocol based on the event notification, wherein the automated testing protocol identifies the faulty element and generates test results regarding the faulty element;

receiving test results from the automated testing protocol;

automatically completing a trouble ticket containing the test results obtained from the automated testing protocol; and

routing the trouble ticket to the appropriate party.

2. The method of claim 1 further comprising logging the results from the testing protocol.

3. The method of claim 2 further comprising querying an event correlation database to determine if the event has occurred previously.

4. The method of claim 3 further comprising prioritizing the trouble ticket based on the severity of the event.

5. The method of claim 4 further comprising placing a time stamp on the trouble ticket.

6. The method of claim 5 further comprising interfacing with the automated testing protocol and the event correlation database via a graphical user interface.

7. The method of claim 6 further comprising integrating multiple automated testing protocols into one graphical user interface.

8. The method of claim 7 further comprising logging in users to prevent interference among users.

9. The method of claim 1 further comprising:

providing event identifying data to a network elements database so that the network elements database can identify the faulty element.

10. The method of claim 9 wherein the identification of the network element comprises the name and the physical location of the faulty element.

11. The method of claim 10 further comprising:

characterizing the type of event.

12. The method of claim 11 wherein the automated testing protocol physically tests the faulty element.

13. The method of claim 12 wherein the automated testing protocol isolates the faulty element.

14. The method of claim 13 wherein the automated testing protocol analyzes the faulty element to determine the cause of the event within the faulty element.

15. The method of claim 14 wherein the trouble ticket includes the physical location to which a technician needs to be dispatched to repair or further test the faulty element.