Processes for assisting in troubleshooting

• US 20070168726A1
• Filed: 09/29/2005
• Published: 07/19/2007
• Est. Priority Date: 09/29/2005
• Status: Abandoned Application

• Current Assignee: Bellsouth Intellectual Property Corporation (AT&T, Inc.)
• Original Assignee: Bellsouth Intellectual Property Corporation (AT&T, Inc.)
• Inventors: Amos, Richard
• Application Number:
  US11/239,524
• Publication Number:
  US 20070168726A1
• Time in Patent Office: Days
• US Class Current: 714/25
• CPC Class Codes: G06F 11/2252 using fault dictionaries

Abstract

A systematic process is disclosed for isolating customer issues with computer systems and implementing solutions to those issues. A basic troubleshooting methodology provides a systematic approach by which a technician can efficiently define and resolve a customer'"'"'s problem. The methodology seeks to identify the symptoms and scope of a customer'"'"'s problem and provides a series of interrelated and layered steps for arriving at a solution to the problem.

Claims

1. A computer-implemented process for use by an operator in troubleshooting a problem in a computer-implemented system of a customer in which the computer-implemented system is used in connection with an internet service provided for the customer, the computer-implemented system implemented with plural application programs associated with a customer'"'"'s computer with which the customer is attempting to use the internet service, the process comprising:

identifying a symptom of the problem;

identifying outer limits of the symptom by determining whether the customer has connectivity to fewer than all the application programs associated with the computer, thereby determining whether the problem is a connectivity issue with the internet service provider or whether the problem is with one of the plural application programs associated with the customer'"'"'s computer, so as to determine the scope of the problem in the computer-implemented system;

determining whether any change to the computer-implemented system was made before the problem arose;

identifying a probable cause of the problem;

locating in a database a probable solution to the probable cause, the probable solution being one of a plurality of possible solutions;

implementing the probable solution to determine whether the probable solution solves the problem in the computer-implemented system;

if the probable solution fails to solve the problem, reverting to the database to locate a second probable solution and implementing the second solution; and

after determining that one solution of the plurality of possible solutions in the database solves the problem, documenting the one solution in a the database so as to provide a template for future reference if the customer again requests assistance with the same problem.

2. The computer-implemented process as in claim 1, further comprising:

after the one solution is determined to solve the problem, identifying potential effects of the one solution and explaining any such effects to the customer.

4. The process as in claim 1, wherein:

if the problem is determined to be a connectivity issue because the customer cannot connect to any available internet application program, verifying whether synchronization exists between the internet service provider and customer equipment relating to providing the service.

5. The process as in claim 4, wherein:

if synchronization is not verified and is thus determined to be a problem, advising the customer how to restore synchronization to the equipment at the customer'"'"'s premises.

6. The process as in claim 4, wherein:

if synchronization is verified and thus is not determined to be a problem, determining a current IP address used at the customer'"'"'s equipment is valid.

7. The process as in claim 6, wherein:

if the current IP address is determined to be valid, determining whether the connection between the customer'"'"'s computer and the internet service provider is valid.

8. The process as in claim 7, wherein:

if the connection is determined to be valid, investigating whether one of the application programs associated with the computer used by the customer is the cause of the problem.

9. The process as in claim 1, wherein identifying the probable cause comprises:

predetermining plural possible causes of the problem, within the identified outer limits;

ranking those possible causes in a logical predetermined order so as to provide a set of layers for testing the causes of the problem; and

testing the possible causes in order of the ranking so as to implement possible solutions in the order of the layers of possible causes.

3. (canceled)

10. A system for use by an operator in troubleshooting a particular problem encountered by a customer in a computer-implemented system of the customer, in which the computer-implemented system is used in connection with an internet service provided for the customer, the computer-implemented system implemented with plural application programs associated with a computer with which the customer is attempting to use the internet service, the system comprising:

at least one database comprising, separately or together, process flow data associated with certain problems that may arise with respect to the customer'"'"'s system and solution data associated with a predetermined array of probable solutions to the certain problems;

a processor for accessing the process flow data to assist in identifying a symptom of the particular problem in the customer'"'"'s system, in identifying outer limits of the symptom so as to determine the scope of the particular problem, in determining adverse effects if a change to the customer'"'"'s system was made before the symptom arose, and in identifying a probable cause of the particular problem;

the processor identifying the outer limits by accessing process flow data for determining whether the customer has connectivity to fewer than all the application programs associated with the computer, thereby determining whether the problem is a connectivity issue with the internet service provider or the problem is with one of the plural application programs associated with the computer with which the customer is attempting to use the internet service;

the processor being operative for accessing the solution data in the database to assist in identifying a first probable solution to the probable cause, the first probable solution being one of a plurality of possible solutions, implementing the first probable solution to determine whether the first probable solution solves the particular problem in the customer'"'"'s computer-implemented system, and reverting to the database to locate a second probable solution and implementing the second probable solution if the first probable solution fails to solve the particular problem; and

after determining that one solution of the plurality of possible solutions solves the particular problem, the processor documenting the one solution in the database so as to provide a template for future reference if the customer again requests assistance with the problem.

11. The system as in claim 10, wherein:

the processor is operative to identify potential effects of the one solution, after the one solution is determined to solve the problem, so as to enable explaining any such effects to the customer.

13. The system as in claim 10, wherein the processor:

identifies the probable cause by accessing process flow data associated with predetermined plural possible causes of the particular problem;

ranks those possible causes in a logical predetermined order so as to provide a set of layers for testing the causes of the problem; and

tests the possible causes in order of the ranking so as to implement possible solutions in the order of the layers of possible causes.

12. (canceled)

14. A method for troubleshooting a problem in a computer-implemented system comprising an internet service provided for a customer and implemented with plural application programs associated with a computer with which the customer is attempting to use the internet service, the method comprising:

identifying a symptom of the problem;

identifying outer limits of the symptom so as to determine the scope of the problem in the system by determining whether the customer has connectivity to fewer than all the application programs associated with the computer, thereby determining whether the problem is a connectivity issue with the internet service provider or the problem is with one of the application programs associated with the computer with which the customer is attempting to use the internet service;

determining whether any change to the computer-implemented system was made before the problem arose;

identifying one probable cause of the problem;

locating in a database a probable solution to the probable cause, the probable solution being one of a plurality of possible solutions;

implementing the probable solution to determine whether the probable solution solves the problem in the computer-implemented system;

if the probable solution fails to solve the problem, reverting to the database to locate a second probable solution and implementing the second probable solution; and

after determining that one solution of the plurality of possible solutions in the database solves the problem, documenting the one solution in a the database so as to provide a template for future reference if the customer again requests assistance with the same problem.

15. The method as in claim 14, further comprising:

after the one solution is determined to solve the problem, identifying potential effects of the one solution and explaining any such effects to the customer.

17. The method as in claim 14, wherein:

if the problem is determined to be a connectivity issue because the customer cannot connect to any available internet application program, verifying whether synchronization exists between the internet service provider and customer equipment relating to providing the service.

18. The method as in claim 14, wherein identifying the probable cause comprises:

predetermining plural possible causes of the problem;

ranking those possible causes in a logical predetermined order so as to provide a set of layers for testing the causes of the problem; and

testing the possible causes in order of the ranking so as to implement possible solutions in the order of the layers of possible causes.

16. (canceled)