Click detection method, apparatus and system

• US 8,856,207 B2
• Filed: 07/10/2008
• Issued: 10/07/2014
• Est. Priority Date: 10/26/2007
• Status: Active Grant

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Blackberry Limited
• Inventors: Owen, Russell, Brown, Michael, Little, Herbert
• Primary Examiner(s): Eskandarnia, Arvin
• Application Number:
  US12/170,750
• Publication Number:
  US 20090112978A1
• Time in Patent Office: 2,280 Days
• Field of Search: 709/203
• US Class Current: 709/203
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: G06Q 30/0246 Traffic
• CPC Class Codes: H04L 63/0421 Anonymous communication, i.e. the party's identifiers are hidden from the other party or parties, e.g. using an anonymizer

Abstract

A click detection method, apparatus and system is provided. An embodiment includes a method that receives a request from a client destined for a server and a unique identifier for the client. The method of the method also includes generating a representation of the unique identifier, and forwarding the unique identifier and the request to the server.

Claims

1. A method for modifying requests from a client device for a server comprising:

receiving a request from said client device for said server;

receiving a unique identifier for said client device;

generating a representation of said unique identifier by;

obtaining a numerical string representing a current date;

concatenating said numerical string with said unique identifier; and

applying a hashing operation to said unique identifier and said numerical string;

forwarding said representation and said request to said server;

receiving a plurality of further requests from said client device; and

generating and forwarding further representations of said unique identifier for each of said further requests using further current dates, without storing said current date or said further current dates, such that when said further current dates are equal to said current date, said further representations are equal to said representation, and when said further current dates are different from said current date, said further representations are different from said representation.

2. The method of claim 1 wherein said representation is anonymous such that said unique identifier cannot be recovered from said representation.

3. The method of claim 2 wherein applying a hashing operation comprises performing said hashing operation on said concatenated unique identifier and numerical string to produce a message digest;

said representation incorporating said message digest.

4. The method of claim 1 wherein said numerical string identifies one or more of a current month, a current week, a current day, a current half-day, and a current hour.

5. The method of claim 4 wherein said numerical string identifies the current year, the current month and the current day.

6. The method of claim 1 wherein the numerical string is a random number that is associated with the current date.

7. The method of claim 1 wherein said request is for a web-page generated from a web-browser on said client device.

8. The method of claim 7 wherein said request is generated by selecting a link on one web-page hosted on an additional server other than said server.

9. The method of claim 1 further comprising:

prior to said generating, receiving an indication from said client device whether said client device request desires anonymity;

if said indication indicates said client device does not desire anonymity, then as part of said generating, setting said representation to equal said unique identifier such that during said forwarding said request and said unique identifier are forwarded to said server.

10. A computer comprising a processor which connects to a persistent storage device and a volatile storage device via a bus;

said processor also connected to a network interface for communicating with a client device;

said processor configured to receive a request of a client device for a server;

said processor further configured to receive a unique identifier of said client device;

said processor further configured to generate a representation of said unique identifier by;

obtaining a numerical string representing a current date;

concatenating said numerical string with said unique identifier; and

applying a hashing operation to said unique identifier and said numerical string;

said processor further configured to forward said request and said representation for further processing by said server; and

said processor further configured to receive a plurality of further requests from said client device, and to generate and forward further representations of said unique identifier for each of said further requests using further current dates, without storing said current date or said further current dates, such that when said further current dates are equal to said current date, said further representations are equal to said representation, and when said further current dates are different from said current date, said further representations are different from said representation.

11. The computer of claim 10 wherein said representation is anonymous such that said unique identifier cannot be recovered from said representation.

12. The computer of claim 11 wherein applying a hashing operation comprises performing said hashing operation on said unique identifier and said numerical string to produce a message digest;

said representation incorporating said message digest.

13. The computer of claim 10 wherein said numerical string identifies one or more of a current month, a current week, a current day, a current half-day, and a current hour.

14. The computer of claim 13 wherein said numerical string identifies the current year, the current month and the current day.

15. The computer of claim 10 wherein said request is for a web-page generated from a web-browser on said client device.

16. The computer of claim 10 wherein said request is generated by selecting a link on one web-page hosted on an additional server other than said server.

17. The computer of claim 10 wherein said request is for a web-service.

18. The computer of claim 10 wherein said computer is independent of said client and said server.

19. A non-transitory computer readable medium storing a plurality of programming instructions;

said programming instructions configured to execute on a computer;

said programming instructions configured to render a processor on said computer operable to;

receive a request from said client device for said server;

receive a unique identifier for said client device;

generate a representation of said unique identifier by;

obtaining a numerical string representing a current date;

concatenating said numerical string with said unique identifier; and

applying a hashing operation to said unique identifier and said numerical string;

forward said representation and said request to said server;

receive a plurality of further requests from said client device; and

generate and forward further representations of said unique identifier for each of said further requests using further current dates, without storing said current date or said further current dates, such that when said further current dates are equal to said current date, said further representations are equal to said representation, and when said further current dates are different from said current date, said further representations are different from said representation.

20. A method of processing requests comprising:

receiving a request and a unique identifier from a client device;

generating a representation of said unique identifier by;

obtaining a numerical string representing a current date;

concatenating said numerical string with said unique identifier; and

applying a hashing operation to said unique identifier and said numerical string;

recording said representation and said request;

receiving a plurality of further requests from said client device; and

generating and recording further representations of said unique identifier for each of said further requests using further current dates, without storing said current date or said further current dates, such that when said further current dates are equal to said current date, said further representations are equal to said representation, and when said further current dates are different from said current date, said further representations are different from said representation.

21. The method of claim 20 further comprising:

if said recording step is performed less than a predetermined number of times, generating a charge associated with said request.

22. A method of processing requests comprising:

receiving a request for content and a unique identifier at a service provider engine from a client device;

generating a representation of said unique identifier at said service provider engine by;

obtaining a numerical string representing a current date;

concatenating said numerical string with said unique identifier; and

applying a hashing operation to said unique identifier and said numerical string;

forwarding said request for content and said representation to a first content server;

said content being hosted on an additional content server other than said first content server;

recording said representation and said request for content at said first content server; and

receiving a plurality of further requests at said service provider engine from said client device; and

generating and forwarding further representations of said unique identifier for each of said further requests using further current dates, without storing said current date or said further current dates, such that when said further current dates are equal to said current date, said further representations are equal to said representation, and when said further current dates are different from said current date, said further representations are different from said representation.

23. The method of claim 22 further comprising:

if said recording step is performed less than a predetermined number of times, generating a charge to an entity hosting said content associated with said request.

24. The method of claim 22 further comprising:

returning a redirect address to said service provider engine from said first content server;

said redirect address including an identifier for said content.

25. The method of claim 24 further comprising:

returning said redirect address to said client device from said service provider engine.

26. The method of claim 25 further comprising:

using said redirect address to connect with said additional content server.