ALGORITHM FOR CLASSIFICATION OF BROWSER LINKS

• US 20100153539A1
• Filed: 12/15/2008
• Published: 06/17/2010
• Est. Priority Date: 12/15/2008
• Status: Abandoned Application

• Current Assignee: Taproot Systems Incorporated
• Original Assignee: Taproot Systems Incorporated
• Inventors: Zarroli, Gregory Thomas, Barton, Matthew Erling, Spivey, Anthony Wayne
• Application Number:
  US12/334,662
• Publication Number:
  US 20100153539A1
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: G06F 16/951 Indexing; Web crawling techniques
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/535 Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34
• CPC Class Codes: H04L 67/564 Enhancement of application control based on intercepted application data

Abstract

A method or algorithm for classifying downloaded links or URL'"'"'s based on the reason behind the download. Downloads are classified into categories, for example, a “visited” URL or an “embedded” URL. Categorizing these downloads allows other applications to collect information for storage, upload, or other action. This algorithm uses information from the browser history and packet streams to obtain and categorize the links or URL'"'"'s for classification.

Claims

1. A method for determining whether an HTTP (HyperText Transfer Protocol) request to a Uniform Resource Locator (URL) comprises an actual visit to a web page (Visited URL) designated by the URL or a visit to a web page containing the URL embedded in that web page (Embedded URL), the method comprising the steps of:

intercepting packets of data from a user;

analyzing the packets of data to locate URLs in the packets of data to determine whether the packet contains an HTTP request;

if a packet contains an HTTP request, analyzing the HTTP request to locate a requested URL, a corresponding domain (defined by a Host field), and the presence of a Referer field in the HTTP request; and

determining whether an HTTP request to a URL comprises Visited URL or an Embedded URL based upon the presence or absence of the Referer field.

2. The method of claim 1, wherein:

if the HTTP request is a first HTTP request in the packets of data from a user, the HTTP request is assumed to be a Visited URL and the HTTP request is classified as a Visited URL, then the method further includes the steps of;

updating a Visited URL database to include information as to the Visited URL, and

storing the domain represented in the Host field as a stored domain.

3. The method of claim 2, wherein:

if the requested URL is not the first HTTP request in the packets of data from the user, the domain in the HTTP request is compared against a stored domain; and

if the stored domain is the same as the domain in the HTTP request, and the requested URL is not in the browser history, then it is determined that the requested URL is an Embedded URL; and

the Embedded URL database is updated to include information as to the Embedded URL.

4. The method of claim 3, wherein:

if the requested URL is in the browser history, then the requested URL is classified as a Visited URL, and the Visited URL database is updated to include information as to the Visited URL.

5. The method of claim 4, wherein if the domain of the requested URL is different from the stored domain, and the Referer field is detected, then content of the Refer field is examined to determine whether the URL is a Visited URL or an Embedded URL.

6. The method of claim 5, wherein if the Referer field does not exist in the HTTP request, and the requested URL appears in the browser history, then the URL is classified as a Visited URL and the Visited URL database is updated to include information as to the Visited URL.

7. The method of claim 6, wherein if the Referer field doesn'"'"'t exist in the HTTP request and the requested URL is not in the browser history, then the URL is classified as an Embedded URL and the Embedded URL database is updated to include information as to the Embedded URL.

8. The method of claim 7, wherein if the Referer field exists in the HTTP request, then the domain of the Referer is compared against the “

stored domain” and

if the domain of the Referer is the same as the stored domain, and the requested URL is in the browser history, then the URL is classified as a Visited URL and the Visited URL database is updated to include information as to the Visited URL.

9. The method of claim 8, wherein if the “

stored domain” and

the domain of the Referer are the same, but the requested URL is not in the browser history, then the URL is classified as an Embedded URL and the Embedded URL database is updated to include information as to the Embedded URL.

10. The method of claim 1, wherein determination of whether an HTTP request to a URL comprises an actual visit to a web page designated by the URL or a visit to a web page containing an the URL embedded in that web page determines advertising hit rates for an advertiser advertising on a web page.

11. The method of claim 10, wherein an advertiser is charged a first rate for Visited URLs and a second rate for Embedded URLs.

12. The method of claim 1, wherein determination of whether an HTTP request to a URL comprises an actual visit to a web page designated by the URL or a visit to a web page containing an the URL embedded in that web page determines whether a user can access a restricted web site.

13. The method of claim 12, wherein if the URL is a visited URL, the visited URL is compared to a list of restricted URLs and the user is denied access to the visited URL if the visited URL is on the list of restricted URLs.

14. The method of claim 13, wherein if the URL is a embedded URL, is granted access to a page having the embedded URL.

15. The method of claim 14, wherein if the if the URL is an embedded URL, the embedded URL is compared to a list of restricted URLs and the web page with the embedded URL is flagged for review.