Reduction in redirect navigation latency via speculative preconnection

• US 9,729,654 B1
• Filed: 10/31/2014
• Issued: 08/08/2017
• Est. Priority Date: 10/25/2011
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Roskind, James
• Primary Examiner(s): Maung, Zarni
• Application Number:
  US14/529,301
• Time in Patent Office: 1,012 Days
• Field of Search: 709217, 709203, 709218, 709223-229, 709250
• CPC Class Codes: G06F 16/9566 URL specific, e.g. using aliases, detecting broken or misspelled links
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

Methods, systems, and computer storage mediums for reducing navigation redirect latency by using speculative preconnection. A redirect speculation value is retrieved in response to a request for a source Uniform Resource Locator (URL), where the redirect speculation value is based on the source URL. The redirect speculation value includes the source URL, a target URL, and a probability factor. A preconnection to the target URL'"'"'s hostname is then initiated based on the probability factor. Next, a response from the request to the source URL is received, where the response includes a redirect URL. Finally, the preconnection is used to process the redirect URL when the redirect URL is similar to the target URL.

Claims

1. A computer-implemented method for reducing navigation redirect latency by using speculative preconnection comprising:

retrieving, in response to a request for a source Uniform Resource Locator (URL), a first redirect speculation value based on the source URL, wherein the first redirect speculation value includes the source URL, a target URL, and a first probability factor;

initiating a preconnection to the target URL'"'"'s hostname when the first probability factor exceeds a threshold;

receiving a response to the request for the source URL, wherein the response includes a redirect URL; and

using the preconnection to process the redirect URL when the redirect URL is similar to the target URL.

2. The computer-implemented method of claim 1, wherein the initiating the preconnection further comprises:

performing a first preconnection action when the first probability factor exceeds a first threshold; and

performing a second preconnection action when the first probability factor exceeds a second threshold.

3. The computer-implemented method of claim 2, wherein the first preconnection action comprises resolving the target URL'"'"'s hostname via a Domain Name System (DNS).

4. The computer-implemented method of claim 2, wherein the second preconnection action comprises initiating a TCP/IP connection to the target URL'"'"'s hostname.

5. The computer-implemented method of claim 1, further comprising:

creating a second redirect speculation value when the redirect URL is not similar to the target URL, wherein the second redirect speculation value includes the source URL, the redirect URL, and a second probability factor; and

storing the second redirect speculation value.

6. The computer-implemented method of claim 1, further comprising:

modifying the first probability factor based on a similarity between the redirect URL and the target URL.

7. The computer-implemented method of claim 1, further comprising:

modifying the first probability factor by a value based on navigating to the redirect URL.

8. The computer-implemented method of claim 1, further comprising:

receiving the first probability factor from a third-party provider.

9. A system for reducing navigation redirect latency by using speculative preconnection comprising:

a redirect speculation module, implemented on at least one processor, configured to retrieve, in response to a request for a source Uniform Resource Locator (URL), a first redirect speculation value based on the source URL, wherein the first redirect speculation value includes the source URL, a target URL, and a first probability factor;

a preconnect module configured to initiate a preconnection to the target URL'"'"'s hostname when the first probability factor exceeds a threshold; and

a connect module configured to;

receive a response from the request to the source URL, wherein the response includes a redirect URL; and

use the preconnection to process the redirect URL when the redirect URL is similar to the target URL.

10. The system of claim 9, the preconnection module is further configured to:

perform a first preconnection action when the first probability factor exceeds a first threshold; and

perform a second preconnection action when the first probability factor exceeds a second threshold.

11. The system of claim 10, wherein the first preconnection action comprises resolving the target URL'"'"'s hostname via a Domain Name System (DNS).

12. The system of claim 10, wherein the second preconnection action comprises initiating a TCP/IP connection to the target URL'"'"'s hostname.

13. The system of claim 9, the redirect speculation module is further configured to:

create a second redirect speculation value when the redirect URL is dissimilar to the target URL, wherein the second redirect speculation value includes the source URL, the redirect URL, and a second probability factor; and

store the second redirect speculation value.

14. The system of claim 9, wherein the redirect speculation module is further configured to modify the first probability factor based on a similarity between the redirect URL and the target URL.

15. A non-transitory computer-readable medium storing instructions executable by at least one processor for reducing navigation redirect latency by using speculative preconnection, the instructions configured to cause the at least one processor to:

retrieve, in response to a request for a source Uniform Resource Locator (URL), a first redirect speculation value based on the source URL, wherein the first redirect speculation value includes the source URL, a target URL, and a first probability factor;

initiate a preconnection to the target URL'"'"'s hostname when the first probability factor exceeds a threshold;

receive a response from the request to the source URL, wherein the response includes a redirect URL; and

use the preconnection to process the redirect URL when the redirect URL is similar to the target URL.

16. The computer-readable medium of claim 15, wherein the initiate the preconnection further comprises:

perform a first preconnection action when the first probability factor exceeds a first threshold; and

perform a second preconnection action when the first probability factor exceeds a second threshold.

17. The computer-readable medium of claim 16, wherein the first preconnection action comprises resolving the target URL'"'"'s hostname via a Domain Name System (DNS).

18. The computer-readable medium of claim 16, wherein the second preconnection action comprises initiating a TCP/IP connection to the target URL'"'"'s hostname.

19. The computer-readable medium of claim 15, wherein the instructions are further configured to:

create a second redirect speculation value when the redirect URL is dissimilar to the target URL, wherein the second redirect speculation value includes the source URL, the redirect URL, and a second probability factor; and

store the second redirect speculation value.

20. The computer-readable medium of claim 15, wherein the instructions are further configured to:

modify the first probability factor based on a similarity between the redirect URL and the target URL.