Using different connectivity checks to determine causes of connectivity issues
First Claim
1. A computer implemented method for analyzing connectivity issues between a client and a service, comprising:
- performing a client connectivity test on a client failure zone, wherein the client connectivity test includes at least one of testing a client device, testing one or more applications running on a client device, testing a client network equipment, and testing a client network;
generating client connectivity test results;
performing a service connectivity test on a service failure zone, the service connectivity test including at least one of testing the operation of the service, testing network of the service, testing the service applications;
generating service connectivity test results;
performing an outside connectivity test on an Internet failure zone, wherein the outside connectivity test includes testing the connectivity of the Internet outside of the client failure zone and the service failure zone;
generating outside connectivity test results;
automatically analyzing the client connectivity test results, the outside connectivity test results, and the service connectivity results to determine a possible cause of a connectivity issue; and
sending the possible cause to the client device.
2 Assignments
0 Petitions
Accused Products
Abstract
Connectivity is tested using different locations and contexts selected from different possible failure zones. The failure zones may include: client failure zones; Internet failure zones; and online service failure zones. The results relating to different connectivity tests performed using the different failure zones are correlated and analyzed in an attempt to determine a root cause of the connectivity issue. For example, the root cause may be determined to be a configuration problem of the client, a problem with the client'"'"'s networking equipment, an ISP problem, an Internet backbone problem; a problem of the online service, and the like. Different contexts may also be used when performing the tests. These results may be compared to the other connectivity test results. The results from the tests may be provided to the client experiencing the problem. Aggregated test results may also be used to detect service wide issues and trigger an alert.
38 Citations
13 Claims
-
1. A computer implemented method for analyzing connectivity issues between a client and a service, comprising:
-
performing a client connectivity test on a client failure zone, wherein the client connectivity test includes at least one of testing a client device, testing one or more applications running on a client device, testing a client network equipment, and testing a client network; generating client connectivity test results; performing a service connectivity test on a service failure zone, the service connectivity test including at least one of testing the operation of the service, testing network of the service, testing the service applications; generating service connectivity test results; performing an outside connectivity test on an Internet failure zone, wherein the outside connectivity test includes testing the connectivity of the Internet outside of the client failure zone and the service failure zone; generating outside connectivity test results; automatically analyzing the client connectivity test results, the outside connectivity test results, and the service connectivity results to determine a possible cause of a connectivity issue; and sending the possible cause to the client device. - View Dependent Claims (2, 3, 4, 5, 6)
-
-
7. A system comprising:
-
a processor and memory; an operating environment executing using the processor; and a connectivity manager that is configured to perform actions comprising; performing client connectivity tests on a client failure zone, wherein the client connectivity test includes at least one of testing a client device, testing one or more applications running on a client device, testing a client network equipment, and testing a client network; generating client connectivity test results; performing a service connectivity test on a service failure zone, the service connectivity test including at least one of testing the operation of the service, testing network of the service, testing the service applications; generating service connectivity test results; performing outside connectivity tests on an Internet failure zone, wherein the outside connectivity test includes testing the connectivity of the Internet outside of the client failure zone and the service failure zone; generating outside connectivity test results; automatically analyzing the client connectivity test results, the outside connectivity test results, and the service connectivity results to determine a possible cause of a connectivity issue; and sending the possible cause to the client device. - View Dependent Claims (8, 9, 10)
-
-
11. A computer storage medium storing computer-executable instructions for analyzing connectivity issues between a client and a service, comprising:
-
performing client connectivity tests on a client failure zone, wherein the client connectivity test includes at least one of testing a client device, testing one or more applications running on a client device, testing a client network equipment, and testing a client network; generating client connectivity test results; performing a service connectivity test on a service failure zone, the service connectivity test including at least one of testing the operation of the service, testing network of the service, testing the service applications; generating service connectivity test results; perform an outside connectivity test on an Internet failure zone, wherein the outside connectivity test includes testing the connectivity of the Internet outside of the client failure zone and the service failure zone; generating outside connectivity test results; automatically analyzing the client connectivity test results, the outside connectivity test results, and the service connectivity results to determine a possible cause of a connectivity issue; and sending the possible cause to the client device. - View Dependent Claims (12, 13)
-
Specification