Custom digital components

Patent metadata

Field	Value
Publication number	US-10862999-B2
Application number	US-201916570130-A
Country	US
Kind code	B2
Filing date	Sep 13, 2019
Priority date	Feb 2, 2017
Publication date	Dec 8, 2020
Grant date	Dec 8, 2020

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 data structure storing a mapping of application data to installed software development kits (SDKs) that are installed in various applications;
a front-end server that receives, from a client device, a 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 request by performing operations including:
receiving, from the client device, the 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 request, encrypted data that was generated and encrypted by a second SDK installed at the client device and included in the request generated by the first SDK;
generating a real-time request that includes data specifying a set of SDKs that are installed in an application that initiated the request at the client device;
transmitting, over a network, the real-time request to a third-party digital component provider that is authorized to decrypt the encrypted data generated by the second SDK;
receiving a response to the real-time request from the third party digital component provider; and
transmitting the response to the first SDK with instructions specifying which SDK installed at the client device is required to render a digital component specified by the response.

2. The system of claim 1 , wherein the operations further comprises identifying a set of SDKs that are installed in the application that initiated the request by:
accessing the mapping of application data to installed SDKs;
identifying, within the mapping, the application specified in the application data and a version of the application that initiated the request;
identifying the set of SDKs that are mapped to the application and the version of the application that initiated the 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 the 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 response to the first SDK with instructions specifying which SDK installed at the client device is required to render the digital component specified by the response comprises transmitting instructions specifying an application program interface (API) call to render the digital component specified by the response.

5. The system of claim 1 , wherein transmitting, over a network, the real-time request to the third party digital component provider comprises transmitting the real-time request to the third-party digital component provider without decrypting the encrypted data.

6. The system of claim 1 , wherein the operations further includes: providing a custom digital component associated with the response 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 real-time request from the third party digital component provider comprises receiving the response specifies a particular SDK, other than the first SDK, that is required to render a particular digital component specified by the response.

8. A method, comprising:
receiving, from a client device, a request for a digital component that was generated by a first software development kit (SDK) installed at the client device;
identifying, within one or more data fields of the request, encrypted data that was generated and encrypted by a second SDK installed at the client device and included in the request generated by the first SDK;
generating, by one or more custom digital component servers, a real-time request that includes data specifying a set of SDKs that are installed in an application that initiated the request at the client device;
transmitting, over a network by the one or more custom digital component servers, the real-time request to a third-party digital component provider that is authorized to decrypt the encrypted data generated by the second SDK;
receiving, by the one or more custom digital component servers, a response to the real-time request from the third party digital component provider; and
transmitting, by the one or more custom digital component servers, the response to the first SDK with instructions specifying which SDK installed at the client device is required to render a digital component specified by the response.

9. The method of claim 8 , wherein the operations further comprise identifying a set of SDKs that are installed in the application that initiated the request by:
accessing a mapping of application data to installed SDKs;
identifying, within the mapping, the application specified in the application data and a version of the application that initiated the request;
identifying the set of SDKs that are mapped to the application and the version of the application that initiated the request.

10. The method of claim 9 , further comprising 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 method of claim 8 , wherein transmitting the response to the first SDK with instructions specifying which SDK installed at the client device is required to render a digital component specified by the response comprises transmitting instructions specifying an application program interface (API) call to render the digital component specified by the response.

12. The method of claim 8 , wherein transmitting, over a network by the one or more custom digital component servers, the real-time request to the third party digital component provider comprises transmitting the real-time request to the third-party digital component provider without decrypting the encrypted data.

13. The method of claim 8 , further comprising: providing a custom digital component associated with the response for presentation by a particular SDK in an electronic document at the client device.

14. The method of claim 8 , wherein:
receiving the response to the real-time request from the third party digital component provider comprises receiving the response specifies a particular SDK, other than the first SDK, that is required to render the digital component specified by the response.

15. A non-transitory computer storage medium encoded with a computer program, the program comprising instructions that when executed by data processing apparatus cause the data processing apparatus to perform operations comprising:
receiving, from a client device, a request for a digital component that was generated by a first software development kit (SDK) installed at the client device;
identifying, within one or more data fields of the request, encrypted

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

• G06Q30/018

  Certifying business or products · CPC title

• G06F21/602

  Providing cryptographic facilities or services · CPC title

• G06F9/451 Primary

  Execution arrangements for user interfaces · 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