IP Library Granted Patent US 11,962,619
Granted Patent B2
US 11,962,619 · App. 17/374,518 · Granted Apr 16, 2024

Systems and methods for electronic signing of electronic content requests

Inventors: Lachlan A. Maxwell (Ashburn, VA); Andrew Braksator (Herndon, VA); George Fletcher (Round Hill, VA)
Assignee: Yahoo Assets LLC
H04L63/1483H04L9/0894H04L9/14H04L9/30H04L9/3247H04L63/0428H04L63/10H04L63/126H04L2209/60
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,962,619
App. No.
17/374,518
Granted
Apr 16, 2024
Kind
B2
Abstract

Systems and methods are disclosed for cryptographic signing of content requests. One method includes receiving, at a content network, a content request from a publisher website, the publisher website purporting to be associated with a publisher domain. At the content network, a public key may be received associated with the publisher domain. At the content network, at least one policy may be received associated with the publisher domain. It may be determined whether the content request comprises a cryptographic signature. If it is determined that the content request does not comprise a cryptographic signature, content may or may not be provided to the publisher website according to the policy from the publisher domain. If it is determined that the content request comprises a cryptographic signature, the cryptographic signature of the request may be validated using the public key. Upon successfully validating the cryptographic signature of the content request, content maybe provided to the publisher website according to the content request.

Claims (60)

1. A method for validating an identity of publisher websites, the method including:

receiving a content request from a publisher website purporting to be associated with a publisher domain;

receiving a policy associated with the publisher domain, the policy comprising a signature requirement;

upon determining that the received content request does not include a digital signature,

determining how to provide content to the publisher website according to the policy associated with the publisher domain;

upon determining that the received content request includes a digital signature validating the digital signature using a key provided by the publisher domain; and

upon successful validation, providing content to the publisher website according to the content request.

2. The method of claim 1 , further comprising:

prompting the publisher domain to add digital signatures to content requests.

3. The method of claim 1 , further comprising:

upon determining that the content request does not comprise a digital signature, forwarding information associated with the content request to the publisher domain.

4. The method of claim 1 , further comprising:

upon determining that the content request does not comprise a digital signature, forwarding the content request to the publisher domain with a request for a corresponding digital signature.

5. The method of claim 1 , further comprising:

providing content to the publisher website for additional content requests from the publisher website without validation.

6. The method of claim 1 , further comprising:

receiving a plurality of content requests from the publisher domain; and

validating digital signatures associated with the content requests in a batch.

7. The method of claim 1 , further comprising:

determining that the content policy associated with the publisher domain requires all content requests associated with the publisher domain to be digitally signed; and

upon determining that the content request does not comprise a validated digital signature, denying the content request.

8. The method of claim 1 , wherein a publisher key is received from a Domain Name Server associated with the publisher domain.

9. A system for validating an identity of publisher websites, the system including:

at least one data storage device storing instructions for validating the identity of publisher websites; and

at least one processor configured to execute the instructions to perform a method comprising:

receiving a content request from a publisher website purporting to be associated with a publisher domain;

receiving a policy associated with the publisher domain, the policy comprising a signature requirement;

upon determining that the received content request does not include a digital signature;

determining how to provide content to the publisher website according to the policy associated with the publisher domain;

upon determining that the received content request includes a digital signature, validating the digital signature using a key provided by the publisher domain; and

upon successful validation, providing content to the publisher website according to the content request.

10. The system of claim 9 , further comprising:

prompting the publisher domain to add digital signatures to content requests.

11. The system of claim 9 , the method further comprising:

upon determining that the content request does not comprise a digital signature, forwarding information associated with the content request to the publisher domain.

12. The system of claim 9 , the method further comprising:

upon determining that the content request does not comprise a digital signature, forwarding the content request to the publisher domain with a request for a corresponding digital signature.

13. The system of claim 9 , the method further comprising:

providing content to the publisher website for additional content requests from the publisher website without validation.

14. The system of claim 9 , the method further comprising:

receiving a plurality of content requests from the publisher domain; and

validating digital signatures associated with the content requests in a batch.

15. The system of claim 9 , the method further comprising:

determining that the content policy associated with the publisher domain requires all content requests associated with the publisher domain to be digitally signed; and

upon determining that the content request does not comprise a validated digital signature, denying the content request.

16. The system of claim 9 , wherein a publisher key is received from a Domain Name Server associated with the publisher domain.

17. A non-transitory computer-readable medium storing instructions that, when executed by a computer, cause the computer to perform operations validating an identity of publisher websites, the operations comprising:

receiving a content request from a publisher website purporting to be associated with a publisher domain;

receiving a policy associated with the publisher domain, the policy comprising a signature requirement;

upon determining that the received content request does not include a digital signature,

determining how to provide content to the publisher website according to the policy associated with the publisher domain;

upon determining that the received content request includes a digital signature, validating the digital signature using a key provided by the publisher domain; and

upon successful validation, providing content to the publisher website according to the content request.

18. The computer-readable medium of claim 17 , the operations further comprising:

upon determining that the content request does not comprise a digital signature, forwarding the content request to the publisher domain with a request for a corresponding digital signature.

19. The computer-readable medium of claim 17 , the operations further comprising:

providing content to the publisher website for additional content requests from the publisher website without validation.

20. The computer-readable medium of claim 17 , the operations further comprising:

receiving a plurality of content requests from the publisher domain; and

validating digital signatures associated with the content requests in a batch.

Assignments (8)
PATENT SECURITY AGREEMENT Recorded Mar 18, 2025
From: RPX CORPORATION
To: BARINGS FINANCE LLC, AS COLLATERAL AGENT
Reel/Frame 070551/0860 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 4, 2025
From: YAHOO ASSETS LLC; YAHOO AD TECH LLC
To: RPX CORPORATION
Reel/Frame 070402/0873 →
NOTICE OF RELEASE OF SECURITY INTEREST IN SPECIFIEDPATENTS Recorded Dec 27, 2024
From: ROYAL BANK OF CANADA, AS COLLATERAL AGENT
To: YAHOO ASSETS LLC
Reel/Frame 069792/0193 →
PATENT SECURITY AGREEMENT (FIRST LIEN) Recorded Sep 29, 2022
From: YAHOO ASSETS LLC
To: ROYAL BANK OF CANADA, AS COLLATERAL AGENT
Reel/Frame 061571/0773 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 16, 2021
From: YAHOO AD TECH LLC (FORMERLY VERIZON MEDIA INC.)
To: YAHOO ASSETS LLC
Reel/Frame 058982/0282 →
CHANGE OF NAME Recorded Jul 15, 2021
From: AOL INC.
To: OATH INC.
Reel/Frame 056886/0022 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 15, 2021
From: OATH INC.
To: VERIZON MEDIA INC.
Reel/Frame 056886/0654 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 15, 2021
From: MAXWELL, LACHLAN A.; BRAKSATOR, ANDREW; FLETCHER, GEORGE
To: AOL INC.
Reel/Frame 056864/0716 →
Continuity (3)
Continuation 16742521 · Jan 14, 2020
Continuation 15633289 · Jun 26, 2017
Related Publication 20210344712A1 · Nov 4, 2021