# US 2017/0374110 A1 · Device and Method for Virtual Private Network Connection Establishment

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

- Number: US 2017/0374110 A1
- Document ID: US20170374110A1
- Status: Published application
- Kind: A1
- Application number: 15/699,006
- Filed: 2017-09-08
- Published: 2017-12-28
- Earliest claimed: 2014-05-28
- Assignees: Apple Inc.
- Applicants: Apple Inc.
- Inventors: Thomas F. PAULY
- Web page: https://patentgrep.com/patent/US20170374110A1

## CPC

- H04L 65/1069: Session establishment or de-establishment
- H04L 61/4511: using domain name system [DNS]
- H04L 63/0272: {Virtual private networks}
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 69/16: Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L 61/2514: between local and global IP addresses
- H04L 63/168: {above the transport layer}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A method, client device and non-transitory computer readable storage medium for connecting to a virtual private network (VPN). A request to connect to a destination identified by a hostname is received from an application executed on the client device and a domain name system (DNS) lookup functionality is performed on the hostname, the DNS lookup functionality returning an address. It is then determined whether the returned address is a redirected address, whether a hypertext transmission protocol secure (HTTPS) probe configured for the hostname fails, or whether the returned address matches a cached route in which a transmission control protocol (TCP) connection establishment is unsuccessful. If any of the returned address is a redirected address, the HTTPS probe fails or the returned address matches the cached route and the TCP connection establishment is unsuccessful, the client device is connected to the VPN.

## Claims

### Claim at position 1

1-18. (canceled)

### Claim 19

A method for use in virtual private network (VPN) communications, the method comprising:
at a client device:
receiving, from an application executed on the client device, a request to connect to a destination identified by a hostname;
performing a domain name system (DNS) lookup functionality on the hostname, the DNS lookup functionality returning an address,
determining whether the returned address is a redirected address based on whether the returned address matches an entry in a stored list of redirected addresses;
determining whether a hypertext transmission protocol secure (HTTPS) probe configured for the hostname fails;
determining whether the returned address matches a cached route in which a transmission control protocol (TCP) connection establishment is unsuccessful; and
connecting to a VPN when:
the returned address is a redirected address;
the HTTPS probe fails; or
the returned address matches the cached route and the TCP connection establishment is unsuccessful.

### Claim 20 (depends on 19)

The method of claim 19, wherein performing the DNS lookup functionality includes,
transmitting a DNS lookup to one or more trusted servers only, and
setting a DNS lookup timeout period based at least in part on one or more measured network parameters.

### Claim 21 (depends on 19)

The method of claim 19, wherein the HTTPS probe failing is indicative of a second destination being unavailable in a public network, wherein the HTTPS probe succeeding is indicative of the second destination being publicly available on the public network.

### Claim 22 (depends on 19)

The method of claim 19, wherein the TCP connection establishment being unsuccessful is indicative of the destination being unavailable in the public network, wherein the TCP connection establishment succeeding is indicative of a connection being established with the destination on the public network.

### Claim 23 (depends on 19)

The method of claim 19, wherein determining whether the returned address is a redirected address includes:
generating, by the client device, the list of redirected addresses by:
sending a dummy hostname request;
receiving a return address in response to the dummy hostname request; and
storing, by the client device, in the list of redirected addresses, the return address received in response to the dummy hostname request.

### Claim 24 (depends on 19)

The method of claim 19, wherein the stored list of redirected addresses comprises a least one address that redirects to at least one of a landing page or a further page.

### Claim 25 (depends on 19)

The method of claim 19, wherein the stored list or redirected addresses is updated by the client device when the client device connects to a new network.

### Claim 26

A client device, comprising:
communications circuitry; and
a processor,
wherein the processor and communications circuitry are configured to establish a connection to a virtual private network (VPN) by:
receiving, from an application executed on the client device, a request to connect to a destination identified by a hostname;
performing a domain name system (DNS) lookup functionality on the hostname, the DNS lookup functionality returning an address,
determining whether the returned address is a redirected address based on whether the returned address matches an entry in a stored list of redirected addresses;
determining whether a hypertext transmission protocol secure (HTTPS) probe configured for the hostname fails;
determining whether the returned address matches a cached route in which a transmission control protocol (TCP) connection establishment is unsuccessful; and
connecting to a VPN when:
the returned address is a redirected address;
the HTTPS probe fails; or
the returned address matches the cached route and the TCP connection establishment is unsuccessful.

### Claim 27 (depends on 26)

The client device of claim 26, wherein performing the DNS lookup functionality includes the processor and the communications circuitry;
transmitting a DNS lookup to one or more trusted servers only, and
setting a DNS lookup timeout period based at least in part on one or more measured network parameters.

### Claim 28 (depends on 26)

The client device of claim 26, wherein the HTTPS probe failing is indicative of a second destination being unavailable in a public network, wherein the HTTPS probe succeeding is indicative of the second destination being publicly available on the public network.

### Claim 29 (depends on 26)

The client device of claim 26, wherein the TCP connection establishment being unsuccessful is indicative of the destination being unavailable in the public network, wherein the TCP connection establishment succeeding is indicative of a connection being established with the destination on the public network.

### Claim 30 (depends on 26)

The client device of claim 26, wherein the processor and the communications circuitry is further configured to:
generate the list of redirected addresses by:
send a dummy hostname request;
receive a return address in response to the dummy hostname request, wherein the memory arrangement stores in the list of redirected addresses, the return address received in response to the dummy hostname request.

### Claim 31 (depends on 26)

The client device of claim 26, wherein the stored list of redirected addresses comprises a least one address that redirects to at least one of a landing page or a further page.

### Claim 32 (depends on 26)

The client device of claim 26, wherein the stored list or redirected addresses is updated by the client device when the client device connects to a new network.

### Claim 33

A non-transitory computer readable storage medium with an executable program stored thereon, wherein the program instructs a microprocessor to perform operations comprising:
receiving, from an application executed on a client device, a request to connect to a destination identified by a hostname;
performing a domain name system (DNS) lookup functionality on the hostname, the DNS lookup functionality returning an address,
determining whether the returned address is a redirected address based on whether the returned address matches an entry in a stored list of redirected addresses;
determining whether a hypertext transmission protocol secure (HTTPS) probe configured for the hostname fails;
determining whether the returned address matches a cached route in which a transmission control protocol (TCP) connection establishment is unsuccessful; and
connecting to a VPN when:
the returned address is a redirected address;
the HTTPS probe fails; or
the returned address matches the cached route and the TCP connection establishment is unsuccessful.

### Claim 34 (depends on 33)

The non-transitory computer readable storage medium of claim 33, wherein performing the DNS lookup functionality includes the microprocessor performing operations comprising;
transmitting a DNS lookup to one or more trusted servers only, and
setting a DNS lookup timeout period based at least in part on one or more measured network parameters.

### Claim 35 (depends on 33)

The non-transitory computer readable storage medium of claim 33, wherein the HTTPS probe failing is indicative of a second destination being unavailable in a public network, wherein the HTTPS probe succeeding is indicative of the second destination being publicly available on the public network.

### Claim 36 (depends on 33)

The non-transitory computer readable storage medium of claim 33, wherein the TCP connection establishment being unsuccessful is indicative of the destination being unavailable in the public network, wherein the TCP connection establishment succeeding is indicative of a connection being established with the destination on the public network.

### Claim 37 (depends on 33)

The non-transitory computer readable storage medium of claim 33, wherein the microprocessor further performs operations comprising:
generating the list of redirected addresses by:
sending a dummy hostname request;
receiving a return address in response to the dummy hostname request, and
storing, in the list of redirected addresses, the return address received in response to the dummy hostname request.

### Claim 38 (depends on 33)

The non-transitory computer readable storage medium of claim 33, wherein the stored list of redirected addresses comprises a least one address that redirects to at least one of a landing page or a further page.
