Custom digital components

Patent metadata

Field	Value
Publication number	US-11375044-B2
Application number	US-202017089124-A
Country	US
Kind code	B2
Filing date	Nov 4, 2020
Priority date	Feb 2, 2017
Publication date	Jun 28, 2022
Grant date	Jun 28, 2022

Abstract

Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for processing requests for digital components. A method includes receiving a request from a client device for a digital component generated by a first SDK installed at a client device, examining data fields of the request by servers, generating real-time requests by the servers, and transmitting each real-time request to a third-party digital component provider by the servers. The method further includes receiving responses to the real-time requests from the third party digital component provider by the servers, selecting a particular response to transmit to the client device responsive to the request for the digital component by the servers, and transmitting the particular response to the first SDK with instructions specifying which SDK installed at the client device is required to render a digital component included in the particular response by the servers.

First claim

The invention claimed is:

1. A system, comprising:
a front-end server that receives, from a client device, a first request for a digital component that was generated by a first SDK installed at the client device; and
a custom digital component server that processes the first request by performing operations comprising:
receiving, from the front end server, the first request for the digital component that was generated by the first SDK installed at the client device;
identifying, within one or more data fields of the first request, data (i) corresponding to a set of other SDKs installed at the client device and (ii) included in the first request generated by the first SDK;
generating a second request that includes data specifying one or more SDKs from the set of other SDKs that are installed at the client device that initiated the first request;
transmitting, over a network, the second request to a third-party digital component provider;
receiving a response to the second request from the third party digital component provider; and
transmitting, responsive to the first request generated by the first SDK, instructions specifying which SDK from among the set of other SDKs installed at the client device is required to render a digital component specified by the response to the second request.

2. The system of claim 1 , wherein the operations further comprise:
accessing a mapping of application data to installed SDKs; and
identifying, within the mapping, an application specified in the application data and a version of the application that initiated the first request, wherein:
identifying the set of other SDKs installed at the client device comprises identifying the set of other SDKs that are mapped to the application and the version of the application that initiated the first request.

3. The system of claim 2 , wherein the operations further comprise generating the mapping of application data to installed SDKs, including:
identifying, from a response log stored in a data structure, previous responses that were previously provided to the version of the application in response to previous requests that were initiated by the version of the application;
identifying, from the previous responses, a set of multiple different SDKs that were specified in the previous responses; and
mapping each SDK in the set of multiple different SDKs to the version of the application in the data structure.

4. The system of claim 1 , wherein transmitting the instructions specifying which SDK installed at the client device is required to render the digital component specified by the response to the second request comprises transmitting instructions specifying an application program interface (API) call to render the digital component specified by the response to the second request.

5. The system of claim 1 , wherein transmitting, over a network, the second request to the third party digital component provider comprises transmitting a real-time request to the third-party digital component provider without decrypting the data corresponding to the set of other SDKs installed at the client device.

6. The system of claim 1 , wherein the operations further comprise providing a custom digital component specified by the response to the second request for presentation by a particular SDK in an electronic document at the client device.

7. The system of claim 1 , wherein receiving the response to the second request from the third party digital component provider comprises receiving the response to the second request specifying a particular SDK, other than the first SDK, that is required to render a particular digital component specified by the response to the second request.

8. A non-transitory computer readable medium storing instructions that, upon execution, cause one or more data processing apparatus to perform operations comprising:
receiving, from a client device, a first request for a digital component that was generated by a first SDK installed at the client device;
identifying, within one or more data fields of the first request, data (i) corresponding to a set of other SDKs installed at the client device and (ii) included in the first request generated by the first SDK;
generating a second request that includes data specifying one or more SDKs from the set of other SDKs that are installed at the client device that initiated the first request;
transmitting, over a network, the second request to a third-party digital component provider;
receiving a response to the second request from the third party digital component provider; and
transmitting, responsive to the first request generated by the first SDK, instructions specifying which SDK from among the set of other SDKs installed at the client device is required to render a digital component specified by the response to the second request.

9. The non-transitory computer readable medium of claim 8 , wherein the operations further comprise:
accessing a mapping of application data to installed SDKs; and
identifying, within the mapping, an application specified in the application data and a version of the application that initiated the first request, wherein:
identifying the set of other SDKs installed at the client device comprises identifying the set of other SDKs that are mapped to the application and the version of the application that initiated the first request.

10. The non-transitory computer readable medium of claim 9 , wherein the operations further comprise generating the mapping of application data to installed SDKs, including:
identifying, from a response log stored in a data structure, previous responses that were previously provided to the version of the application in response to previous requests that were initiated by the version of the application;
identifying, from the previous responses, a set of multiple different SDKs that were specified in the previous responses; and
mapping each SDK in the set of multiple different SDKs to the version of the application in the data structure.

11. The non-transitory computer readable medium of claim 8 , wherein transmitting the instructions specifying which SDK installed at the client device is required to render the digital component specified by the response to the second request comprises transmitting instructions specifying an application program interface (API) call to render the digital component specified by the response to the second request.

12. The non-transitory computer readable medium of claim 8 , wherein transmitting, over a network, the second request to the third party digital component provider comprises transmitting a real-time request to the third-party digital component provider without decrypting the data corresponding to the set of other SDKs installed at the client device.

13. The non-transitory computer readable medium of claim 8 , wherein the operations further comprise providing a custom digital component specified by the response to the second request for presentation by a particular SDK in an electronic document at the client device.

14. The non-transitory computer readable medium of claim 8 , wherein receiving the response to the second request from the third party digital component provider comprises receiving the response to the second request specifying a particular SDK, other than the first SDK, that is required to render a particular digital component specified by the response to the second request.

15. A method, comprising:
receiving, from a client device, a first request for a digital component that was generated by a first SDK installed at the client device;
identifying, within on

Assignees

• Google Llc

Inventors

• Dawson Christopher
• Garon Haskell Aaron
• Giles James
• Kumar Vishal Viresh
• Norum Stephen Rhys
• Levitte George Jacob

Classifications

• H04L67/53

  using third party service providers · CPC title

• G06F21/602

  Providing cryptographic facilities or services · CPC title

• H04L67/34 Primary

  involving the movement of software or configuration parameters  (network booting or remote initial program loading [RIPL] G06F9/4416) · CPC title

• G06F9/451 Primary

  Execution arrangements for user interfaces · CPC title

• G06Q30/018

  Certifying business or products · CPC title