VERIFYING AD REQUESTS

• US 20170032413A1
• Filed: 07/31/2015
• Published: 02/02/2017
• Est. Priority Date: 07/31/2015
• Status: Active Grant

• Current Assignee: WideOrbit
• Original Assignee: WideOrbit
• Inventors: McCartney, Steve
• Granted Patent: US 10,460,340 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 21/64 Protecting data integrity, e.g. using checksums, certificates or signatures
• CPC Class Codes: G06Q 30/0241 Advertisements
• CPC Class Codes: G06Q 30/0248 Avoiding fraud
• CPC Class Codes: G06Q 30/0275 Auctions
• CPC Class Codes: H04L 63/123 received data contents, e.g. message integrity
• CPC Class Codes: H04L 9/14 using a plurality of keys or algorithms
• CPC Class Codes: H04L 9/3247 involving digital signatures
• CPC Class Codes: H04L 9/3297 involving time stamps, e.g. generation of time stamps

Abstract

A method for verifying an ad request includes verifying a signature including the ad request using symmetric or asymmetric keys. Using symmetric keys, after an ad request having a first signature is received, a signature generation algorithm is executed to generate a second signature. If the first signature matches the second signature, then the ad request is determined to be verified. Using asymmetric keys, after an ad request having a signature is received, a signature verification algorithm is executed to determine if the signature matches the ad request. If so, then the ad request is determined to be verified.

Claims

1. A method comprising:

receiving an ad request and a first signature;

executing a signature generation algorithm using the ad request to generate a second signature;

determining if the first signature matches the second signature; and

responsive to determining the first signature matches the second signature, transmitting a verification message corresponding to the ad request,

wherein the method is executed by at least one device including a hardware processor.

2. The method of claim 1, wherein the ad request comprises a Uniform Resource Locator (URL), and wherein executing the signature generation algorithm comprises applying the signature generation algorithm to the URL.

3. The method of claim 1, wherein the ad request comprises a Uniform Resource Locator (URL), and wherein a modification of the URL within the ad request results in a corresponding modification of any signature generated by executing the signature generation algorithm using the ad request.

4. The method of claim 1, wherein the ad request comprises a user identifier, and wherein a modification of the user identifier within the ad request results in a corresponding modification of any signature generated by executing the signature generation algorithm using the ad request.

5. The method of claim 1, wherein executing the signature generation algorithm using the ad request comprises applying the signature generation algorithm to a first portion of the ad request without applying the signature generation algorithm to a second portion of the ad request.

6. The method of claim 1, wherein executing the signature generation algorithm using the ad request comprises applying the signature generating algorithm to all portions of the ad request.

7. The method of claim 1, wherein the executing operation is performed by a particular device executing one or more software modules associated with a Supply Side Platform (SSP).

8. The method of claim 1, wherein the executing operation is performed by a particular device executing one or more software modules associated with an ad exchange.

9. The method of claim 1, wherein the executing operation is performed by a particular device executing one or more software modules associated with a Demand Side Platform (DSP).

10. The method of claim 1, transmitting the verification message is further responsive to:

determining a timestamp included in the ad request is within a particular time window from a current time.

11. The method of claim 1, transmitting the verification message is further responsive to:

identifying a nonce included in the ad request; and

determining the nonce included in the ad request does not match any nonce included in a previously received ad request.

12. The method of claim 1, wherein the first signature is generated by executing the signature generation algorithm that was used to generate the second signature.

13. A method comprising:

receiving an ad request and a first signature;

executing a signature generation algorithm using the ad request to generate a second signature;

determining if the first signature matches the second signature; and

responsive to determining the first signature matches the second signature, forwarding the ad request as a verified ad request,

wherein the method is executed by at least one device including a hardware processor.

14. The method of claim 13, wherein the ad request comprises a Uniform Resource Locator (URL), and wherein executing the signature generation algorithm comprises applying the signature generation algorithm to the URL.

15. A method, comprising:

receiving a public key;

receiving an ad request and a signature;

executing a signature verification method by applying the public key to the ad request and the signature to determine if the signature matches the ad request; and

responsive to determining that the signature matches the ad request;

determining that the ad request is verified,

wherein the method is executed by at least one device including a hardware processor.

16. The method of claim 15, further comprising:

responsive to determining that the ad request is verified;

forwarding the ad request as a verified ad request.

17. The method of claim 15, further comprising:

responsive to determining that the ad request is verified;

placing a bid for the ad request.

18. The method of claim 15, wherein the signature is generated by executing a signature generation algorithm using a private key different than the public key.

19. The method of claim 15, wherein determining that the ad request is verified is further responsive to:

determining a timestamp included in the ad request is within a particular time window from a current time.

20. The method of claim 15, wherein determining that the ad request is verified is further responsive to:

identifying a nonce included in the ad request; and

determining the nonce included in the ad request does not match any nonce included in a previously received ad request.