Method and system for counting web access requests

US 8,606,900 B1
Filed: 04/12/2000
Issued: 12/10/2013
Est. Priority Date: 06/07/1995
Status: Expired due to Fees

- Alert
- Pin

Associated Cases

Associated Defendants

First Claim

Patent Images

1. A method of tracking web page requests received at a web server from a plurality of clients, comprising:

generating a plurality of session identifiers at the web server, each of the plurality of session identifiers having information associated with a particular client making a web page request to the web server;

storing the session identifiers at a plurality of web browsers operated by the clients;

receiving web page requests at the web server, each web page request including a session identifier associated with a particular client making the web page request;

storing information regarding the web page requests at the web server, the information including the requested web page and the session identifier associated with the request; and

tracking the web page requests by evaluating the information stored at the web server and by counting the number of requests for particular web pages exclusive of repeated requests from a particular client utilizing information associated with a particular client.

View all claims

10 Assignments

Timeline View

Assignment View

Litigations

0 Petitions

Accused Products

Abstract

Service requests from a client to a server system through a network are processed. A session identifier is appended to requests for information. The server responds to the requests from the client by returning the requested information to the client. Requests to particular information are counted, exclusive of repeated requests from a common client.

231 Citations

22 Claims

1. A method of tracking web page requests received at a web server from a plurality of clients, comprising:
- generating a plurality of session identifiers at the web server, each of the plurality of session identifiers having information associated with a particular client making a web page request to the web server;
  
  storing the session identifiers at a plurality of web browsers operated by the clients;
  
  receiving web page requests at the web server, each web page request including a session identifier associated with a particular client making the web page request;
  
  storing information regarding the web page requests at the web server, the information including the requested web page and the session identifier associated with the request; and
  
  tracking the web page requests by evaluating the information stored at the web server and by counting the number of requests for particular web pages exclusive of repeated requests from a particular client utilizing information associated with a particular client.
- View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11)
- - 2. The method of claim 1, wherein the web page requests comprise Uniform Resource Locator (URL) requests, the URL requests being stored at the web server along with the session identifier associated with the request.
  - 3. The method of claim 2, wherein the session identifier is appended to the URL request.
  - 4. The method of claim 2, wherein the session identifier is embedded in the URL request.
  - 5. The method of claim 1, wherein the counting step excludes repeated requests from a particular client that occur during a predetermined period of time, and thereafter counts a repeated request for the same web page from the particular client.
  - 6. The method of claim 1, wherein the session identifier is cryptographically generated.
  - 7. The method of claim 1, wherein the information associated with a particular client includes a user identifier for the client.
  - 8. The method of claim 1, wherein the information associated with a particular client includes an IP address for the client.
  - 9. The method of claim 1, wherein the information associated with a particular client includes an unforgeable digital signature.
  - 10. The method of claim 1, wherein repeated requests from a particular client are identified by the web server using the stored session identifiers associated with the web page requests.
  - 11. The method of claim 1, wherein the counting step enables an operator of the web server to determine the merits of information presented through the requested web pages for ratings purposes by avoiding distortions in the counting process through the exclusion of the repeated requests from a particular client.

12. A web server for tracking web page requests received from a plurality of clients, comprising:
- means for generating a plurality of session identifiers, each of the plurality of session identifiers having information associated with a particular client making a web page request to the web server;
  
  means for receiving web page requests, each web page request including a session identifier associated with a particular client making the web page request;
  
  a database for storing information regarding the web page requests, the information including the requested web page and the session identifier associated with the request; and
  
  means for tracking the web page requests by evaluating the information stored in the database and by counting the number of requests for particular web pages exclusive of repeated requests from a particular client utilizing information associated with a particular client.
- View Dependent Claims (13, 14, 15, 16, 17, 18, 19, 20, 21, 22)
- - 13. The web server of claim 12, wherein the web page requests comprise Uniform Resource Locator (URL) requests, the URL requests being stored in the database along with the session identifier associated with the request.
  - 14. The web server of claim 13, wherein the session identifier is appended to the URL request.
  - 15. The web server of claim 13, wherein the session identifier is embedded in the URL request.
  - 16. The web server of claim 12, wherein the tracking means excludes repeated requests from a particular client that occur during a predetermined period of time, and thereafter counts a repeated request for the same web page from the particular client.
  - 17. The web server of claim 12, wherein the session identifier is cryptographically generated.
  - 18. The web server of claim 12, wherein the information associated with a particular client includes a user identifier for the client.
  - 19. The web server of claim 12, wherein the information associated with a particular client includes an IP address for the client.
  - 20. The web server of claim 12, wherein the information associated with a particular client includes an unforgeable digital signature.
  - 21. The web server of claim 12, wherein repeated requests from a particular client are identified by the web server using the stored session identifiers associated with the web page requests.
  - 22. The web server of claim 12, wherein the tracking means enables an operator of the web server to determine the merits of information presented through the requested web pages for ratings purposes by avoiding distortions in the counting process through the exclusion of the repeated requests from a particular client.

Specification

Resources

Litigation Campaign Assessment

Litigation Data

Current Assignee
Soverain IP, LLC
Original Assignee
Soverain Software LLC
Inventors
Payne, Andrew C., Treese, George Winfield, Levergood, Thomas Mark, Stewart, Lawrence C., Morris, Stephen Jeffrey
Primary Examiner(s)
WINDER, PATRICE L

Application Number

US09/548,237
Time in Patent Office

4,990 Days
Field of Search

709/203, 709217-219, 709/224, 709/226
US Class Current

709/224
CPC Class Codes

H04L 63/10 for controlling access to d...

Method and system for counting web access requests

First Claim

10 Assignments

Litigations

0 Petitions

Accused Products

Abstract

231 Citations

22 Claims

Specification

Solutions

Use Cases

Quick Links

Method and system for counting web access requests

First Claim

10 Assignments

Subscription Required

Subscription Required

Litigations

0 Petitions

Subscription Required

Accused Products

Subscription Required

Abstract

231 Citations

22 Claims

Specification

Subscription Required

Solutions

Use Cases

Quick Links