# US 2014/0207937 A1 · Determination of Internet Access

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2014/0207937 A1
- Document ID: US20140207937A1
- Status: Published application
- Kind: A1
- Application number: 13/747,666
- Filed: 2013-01-23
- Published: 2014-07-24
- Earliest claimed: 2013-01-23
- Assignees: Adobe Systems Incorporated
- Applicants: Adobe Systems Incorporated
- Inventors: Evtim Ivanov Georgiev; John R. Shapiro; Robert Tyler Voliter; Kim P. Pimmel; Joseph Michael Andolina
- Web page: https://patentgrep.com/patent/US20140207937A1

## CPC

- H04L 43/0811: by checking connectivity
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 43/10: Active monitoring, e.g. heartbeat, ping or trace-route
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Internet access or connectivity is determined by sending a request to a third-party service to which connectivity is desired with an application on a client computing device and responsive to receiving a response, attempting to rule out a false positive response from an entity other than the third-party service.

## Claims

### Claim 1

A method comprising:
sending, by a client computing device, a request to a third-party service to which connectivity is desired with an application on the client computing device; and
responsive to receiving a response, attempting to rule out a false positive response from an entity other than the third-party service.

### Claim 2 (depends on 1)

A method as described in claim 1, wherein said attempting comprises attempting to rule out a false positive response from a proxy server.

### Claim 3 (depends on 1)

A method as described in claim 1, wherein said attempting comprises attempting to contact a connectivity check server.

### Claim 4 (depends on 1)

A method as described in claim 1, wherein said attempting comprises attempting to contact a connectivity check server, the application being affiliated with the connectivity check server.

### Claim 5 (depends on 1)

A method as described in claim 1, wherein said attempting comprises:
attempting to contact a connectivity check server;
responsive to attempting to contact the connectivity check server, receiving a response; and
concluding, from the response, whether or not there is connectivity to the third-party service.

### Claim 6 (depends on 5)

A method as described in claim 5, wherein said concluding comprises:
comparing response data included in the response with client data that resides at the client computing device; and
if the response data matches the client data, concluding that there is connectivity to the third-party service.

### Claim 7 (depends on 5)

A method as described in claim 5, wherein said concluding comprises:
comparing response data included in the response with client data that resides at the client computing device; and
if the response data does not match the client data, concluding that there is not connectivity to the third-party service.

### Claim 8 (depends on 5)

A method as described in claim 5, wherein said concluding comprises:
comparing response data included in the response with client data that resides at the client computing device; and:
if the response data matches the client data, concluding that there is connectivity to the third-party service; and
if the response data does not match the client data, concluding that there is not connectivity to the third-party service.

### Claim 9 (depends on 1)

A method as described in claim 1, wherein said attempting comprises attempting to contact a connectivity check server;
responsive to attempting to contact the connectivity check server, not receiving a response; and responsive to not receiving the response, assuming that there is connectivity to the third-party service.

### Claim 10

One or more computer-readable storage media comprising instructions that are stored thereon that, responsive to execution by a computing device, causes the computing device to at least:
send a request to a third-party service to which Internet connectivity is desired; and
responsive to receiving a response, attempt to rule out a false positive response from a proxy server associated with wireless Internet access.

### Claim 11 (depends on 10)

One or more computer-readable storage media as described in claim 10, wherein said attempt to rule out a false positive comprises an attempt to contact a connectivity check server.

### Claim 12 (depends on 10)

One or more computer-readable storage media as described in claim 10, wherein said attempt to rule out a false positive comprises an attempt to contact a connectivity check server that is affiliated with an application that caused said request to be sent.

### Claim 13 (depends on 10)

One or more computer-readable storage media as described in claim 10, wherein said attempt comprises an attempt to contact a connectivity check server; and wherein said instructions further cause the computing device to:
responsive to attempting to contact the connectivity check server, receive a response; and
conclude, from the response, whether or not there is connectivity to the third-party service.

### Claim 14 (depends on 13)

One or more computer-readable storage media as described in claim 13, wherein concluding whether or not there is connectivity is based on a comparison of response data included in the response with client data that resides at the computing device from which the request was sent; and
if the response data matches the client data, conclude that there is connectivity to the third-party service.

### Claim 15 (depends on 13)

One or more computer-readable storage media as described in claim 13, wherein concluding whether or not there is connectivity is based on a comparison of response data included in the response with client data that resides at the computing device; and
if the response data does not match the client data, conclude that there is not connectivity to the third-party service.

### Claim 16 (depends on 13)

One or more computer-readable storage media as described in claim 13, wherein concluding whether or not there is connectivity is based on a comparison of response data included in the response with client data that resides at the computing device from which the request was sent; and:
if the response data matches the client data, conclude that there is connectivity to the third-party service; and
if the response data does not match the client data, conclude that there is not connectivity to the third-party service.

### Claim 17 (depends on 10)

One or more computer-readable storage media as described in claim 10, wherein said attempt comprises an attempt to contact a connectivity check server; and responsive to attempting to contact the connectivity check server and not receiving a response; assume that there is connectivity to the third-party service.

### Claim 18

A computing device comprising:
one or more processors;
one or more computer readable storage media embodying computer-readable instructions which, when executed under the influence of the one or more processors, implement a method comprising:
sending a request to a third-party service to which connectivity is desired with an application on the client computing device; and
responsive to receiving a response, attempting to rule out a false positive response from an entity other than the third-party service.

### Claim 19 (depends on 18)

The computing device of claim 18, wherein said attempting comprises attempting to rule out a false positive response from a proxy server.

### Claim 20 (depends on 18)

The computing device of claim 18, wherein said attempting comprises attempting to contact a connectivity check server.

### Claim 21 (depends on 18)

The computing device of claim 18, wherein said attempting comprises attempting to contact a connectivity check server, the application being affiliated with the connectivity check server.

### Claim 22 (depends on 18)

The computing device of claim 18, wherein said attempting comprises attempting to contact a connectivity check server;
responsive to attempting to contact the connectivity check server, receiving a response; and
concluding, from the response, whether or not there is connectivity to the third-party service.

### Claim 23 (depends on 22)

The computing device of claim 22, wherein said concluding comprises comparing response data included in the response with client data that resides at the client computing device; and if the response data matches the client data, concluding that there is connectivity to the third-party service.

### Claim 24 (depends on 22)

The computing device of claim 22, wherein said concluding comprises comparing response data included in the response with client data that resides at the client computing device; and if the response data does not match the client data, concluding that there is not connectivity to the third-party service.

### Claim 25 (depends on 22)

The computing device of claim 22, wherein said concluding comprises comparing response data included in the response with client data that resides at the client computing device; and:
if the response data matches the client data, concluding that there is connectivity to the third-party service; and
if the response data does not match the client data, concluding that there is not connectivity to the third-party service.

### Claim 26 (depends on 18)

The computing device of claim 18, wherein said attempting comprises attempting to contact a connectivity check server;
responsive to attempting to contact the connectivity check server, not receiving a response; and
responsive to not receiving a response, assuming that there is connectivity to the third-party service.

### Claim 27

A method comprising:
sending a request to a third-party server to which Internet connectivity is desired by an application executing on a computing device;
ascertaining whether a response to the request is received;
responsive to not receiving a response, concluding that the third-party service is unavailable and displaying an associated user interface notification; and
responsive to receiving a response to the request, ascertaining whether the response is from the third-party service or a proxy server that is associated with wireless Internet access.

### Claim 28 (depends on 27)

The method as described in claim 27, wherein said ascertaining whether the response is from the third-party service or a proxy server comprises:
attempting to contact a connectivity check server and:
responsive to not receiving a response:
assuming that the connectivity check server is down and that there is connectivity to the third-party service; and
responsive to receiving a response:
processing the response to ascertain that the response is either from the connectivity check server or the proxy server;
wherein if the response is from the connectivity check server, concluding that there is connectivity to the third-party service; and
if the response is from the proxy server, concluding that there is no connectivity to the third-party service.

### Claim 29 (depends on 28)

The method as described in claim 28, wherein processing the response comprises comparing response data in the response with data maintained on the computing device.

### Claim 30 (depends on 28)

The method as described in claim 28, wherein processing the response comprises comparing response data in the response with data maintained on the computing device; and
if the response data matches the data maintained on the computing device, concluding that there is connectivity to the third-party service, otherwise, concluding that there is no connectivity to the third-party service.

### Claim 31

One or more computer-readable storage media comprising instructions that are stored thereon that implement an access determination module configured to implement a method comprising:
sending a request to a third-party server to which Internet connectivity is desired by an application executing on a computing device, the third-party server being a remote source of user-specific content, the application comprising an adaptive, navigable content canvas configured to enable access to the user-specific content for consumption in content-fillable containers;
ascertaining whether a response to the request is received;
responsive to not receiving a response, concluding that the third-party service is unavailable and displaying an associated user interface notification; and
responsive to receiving a response to the request, ascertaining whether the response is from the third-party service or a proxy server that is associated with wireless Internet access.

### Claim 32 (depends on 31)

The one or more computer-readable storage media of claim 31, wherein said ascertaining whether the response is from the third-party service or a proxy server comprises:
attempting to contact a connectivity check server and:
responsive to not receiving a response:
assuming that the connectivity check server is down and that there is connectivity to the third-party service; and
responsive to receiving a response:
processing the response to ascertain that the response is either from the connectivity check server or the proxy server;
wherein if the response is from the connectivity check server, concluding that there is connectivity to the third-party service; and
if the response is from the proxy server, concluding that there is no connectivity to the third-party service.

### Claim 33 (depends on 32)

The one or more computer-readable storage media of claim 32, wherein processing the response comprises comparing response data in the response with data maintained on the computing device.

### Claim 34 (depends on 32)

The one or more computer-readable storage media of claim 32, wherein processing the response comprises comparing response data in the response with data maintained on the computing device; and
if the response data matches the data maintained on the computing device, concluding that there is connectivity to the third-party service, otherwise, concluding that there is no connectivity to the third-party service.

### Claim 35 (depends on 31)

The one or more computer-readable storage media of claim 31, wherein the access determination module comprises part of the application.

### Claim 36 (depends on 31)

The one or more computer-readable storage media of claim 31, wherein the access determination module is a standalone component from the application.

### Claim 37

A computing device comprising:
one or more processors;
a touch-enabled display;
one or more computer readable storage media embodying computer-readable instructions which, when executed under the influence of the one or more processors, implement an access determination module configured to implement a method comprising:
sending a request to a third-party server to which Internet connectivity is desired by an application executing on the computing device, the third-party server being a remote source of user-specific content, the application comprising an adaptive, touch-navigable content canvas configured to enable access to the user-specific content for consumption in content-fillable containers displayed on the touch-enabled display;
ascertaining whether a response to the request is received;
responsive to not receiving a response, concluding that the third-party service is unavailable and displaying an associated user interface notification on the touch-enabled display;
responsive to receiving a response to the request, ascertaining whether the response is from the third-party service or a proxy server that is associated with wireless Internet access.
