Using different connectivity checks to determine causes of connectivity issues

US9544207B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9544207-B2
Application numberUS-201313923895-A
CountryUS
Kind codeB2
Filing dateJun 21, 2013
Priority dateJun 21, 2013
Publication dateJan 10, 2017
Grant dateJan 10, 2017

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

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.

First claim

Opening claim text (preview).

What is claimed is: 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. The method of claim 1 , wherein the Internet failure zone comprise an Internet Service Provider (ISP) and an Internet backbone, and wherein the service failure zone comprises a service computing device and a service network environment. 3. The method of claim 1 , wherein performing the client connectivity test comprises using an account of the client when performing a first client connectivity test. 4. The method of claim 1 , further comprising performing multiple tests for each of the client connectivity test and the outside connectivity test. 5. The method of claim 1 , wherein performing the client connectivity test further comprises performing a plurality of connectivity checks from a client computing device in the client failure zone. 6. The method of claim 1 , wherein sending the possible cause of the connectivity issue comprises sending a message to an application experiencing the connectivity issue a possible solution to the connectivity issue. 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. 8. The system of claim 7 , wherein performing the client connectivity tests further comprises using an account of the client when performing a set of first client connectivity tests and using a test account when performing a second set of client connectivity tests. 9. The system of claim 8 , wherein the Internet failure zone comprise an Internet Service Provider (ISP) and an Internet backbone; and wherein the service failure zone comprises a service computing device and a service network environment. 10. The system of claim 7 , further comprising aggregating results by aggregating the client connectivity test results, the outside connectivity test results, and the service connectivity test results to form aggregated results; analyzing the aggregated results to determine a service wide issue and automatically triggering an alert in response to determining the service wide issue. 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. 12. The computer storage medium of claim 11 , wherein performing the client connectivity tests comprises using an account of the client when performing a set of first client connectivity tests. 13. The computer storage medium of claim 11 , wherein the Internet failure zone comprise an Internet Service Provider (ISP) and an Internet backbone, and wherein the service failure zone comprises a service computing device and a service network environment.

Assignees

Inventors

Classifications

  • H04L43/065Primary

    related to network devices · CPC title

  • by additionally acting on or stimulating the network after receiving notifications · CPC title

  • Localisation of faults · CPC title

  • by checking connectivity · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9544207B2 cover?
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 conn…
Who is the assignee on this patent?
Microsoft Technology Licensing Llc
What technology area does this patent fall under?
Primary CPC classification H04L43/065. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Jan 10 2017 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 1 related publication on this page (citations in our corpus or others sharing the same primary CPC).