Custom digital components

• US 10,455,058 B2
• Filed: 02/02/2017
• Issued: 10/22/2019
• Est. Priority Date: 02/02/2017
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google LLC (Alphabet Inc.)
• Inventors: Dawson, Christopher, Garon, Haskell Aaron, Giles, James, Kumar, Vishal Viresh, Norum, Stephen Rhys, Levitte, George Jacob
• Primary Examiner(s): Joo, Joshua
• Application Number:
  US15/546,442
• Publication Number:
  US 20180278719A1
• Time in Patent Office: 992 Days
• Field of Search: None
• CPC Class Codes: G06F 21/602 Providing cryptographic facilities or services
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/53 using third party service providers

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.

Claims

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;

examining one or more data fields of the request, including;

identifying, within the one or more data fields, application data specifying an application that initiated the request at the client device; and

identifying, within the one or more data fields, 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 multiple real-time requests including;

identifying, based on the mapping of application data to installed SDKs in the data structure, a set of SDKs that are installed in the application that initiated the request at the client device;

including, in each real-time request, data specifying the set of SDKs that are installed in the application that initiated the request at the client device; and

including the encrypted data in a particular real-time request to a particular third-party that is authorized to decrypt the encrypted data generated by the second SDK;

transmitting, over a network, each real-time request to a corresponding third-party digital component provider; and

receiving a set of responses to the multiple real-time requests from the corresponding third party digital component providers;

selecting a particular response from the set of responses to transmit to the client device responsive to the request for the digital component; 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.

2. The system of claim 1, wherein identifying the set of SDKs that are installed in the application that initiated the request comprises:

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 particular response to the first SDK with instructions specifying which SDK installed at the client device is required to render the digital component included in the particular response comprises transmitting instructions specifying an application program interface (API) call to render the digital component included in the particular response.

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

6. The system of claim 1, wherein the operations further includes:

providing a particular custom digital component associated with the particular response for presentation by a particular SDK in an electronic document at the client device.

7. The system of claim 1, wherein:

transmitting each real-time request to a corresponding third-party digital component provider comprises not transmitting the particular real-time request to third-parties that are not authorized to decrypt the encrypted data generated by the second SDK;

receiving the set of responses to the multiple real-time requests from the corresponding third party digital component providers comprises receiving a given response in the set specifies a particular SDK, other than the first SDK, that is required to render a particular digital component included in the given response; and

transmitting the given response as the particular response, wherein the particular SDK is required to render the particular digital component included in the given 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;

examining, by one or more custom digital component servers, one or more data fields of the request, including;

identifying, within the one or more data fields, application data specifying an application that initiated the request at the client device; and

identifying, within the one or more data fields, 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 the one or more custom digital component servers, multiple real-time requests including;

identifying, based on a mapping of application data to installed SDKs in a data structure, a set of SDKs that are installed in the application that initiated the request at the client device;

including, in each real-time request, data specifying the set of SDKs that are installed in the application that initiated the request at the client device; and

including the encrypted data in a particular real-time request to a particular third-party that is authorized to decrypt the encrypted data generated by the second SDK;

transmitting, over a network by the one or more custom digital component servers, each real-time request to a corresponding third-party digital component provider; and

receiving, by the one or more custom digital component servers, a set of responses to the multiple real-time requests from the corresponding third party digital component providers;

selecting, by the one or more custom digital component servers, a particular response from the set of responses to transmit to the client device responsive to the request for the digital component; and

transmitting, by the one or more custom digital component servers, 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.

9. The method of claim 8, wherein identifying a set of SDKs that are installed in the application that initiated the request comprises:

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.

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 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 comprises transmitting instructions specifying an application program interface (API) call to render the digital component included in the particular response.

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

13. The method of claim 8, further comprising:

providing a particular custom digital component associated with the particular response for presentation by a particular SDK in an electronic document at the client device.

14. The method of claim 8, wherein:

transmitting each real-time request to a corresponding third-party digital component provider comprises not transmitting the particular real-time request to third-parties that are not authorized to decrypt the encrypted data generated by the second SDK;

receiving the set of responses to the multiple real-time requests from the corresponding third party digital component providers comprises receiving a given response in the set specifies a particular SDK, other than the first SDK, that is required to render a particular digital component included in the given response; and

transmitting the given response as the particular response, wherein the particular SDK is required to render the particular digital component included in the given 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;

examining one or more data fields of the request, including;

identifying, within the one or more data fields, application data specifying an application that initiated the request at the client device; and

identifying, within the one or more data fields, 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 multiple real-time requests including;

identifying, based on a mapping of application data to installed SDKs in a data structure, a set of SDKs that are installed in the application that initiated the request at the client device;

including, in each real-time request, data specifying the set of SDKs that are installed in the application that initiated the request at the client device; and

including the encrypted data in a particular real-time request to a particular third-party that is authorized to decrypt the encrypted data generated by the second SDK;

transmitting, over a network, each real-time request to a corresponding third-party digital component provider; and

receiving a set of responses to the multiple real-time requests from the corresponding third party digital component providers;

selecting a particular response from the set of responses to transmit to the client device responsive to the request for the digital component; 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.

16. The non-transitory computer-readable medium of claim 15, wherein identifying a set of SDKs that are installed in the application that initiated the request comprises:

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.

17. The non-transitory computer-readable medium of claim 16, 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.

18. The non-transitory computer-readable medium of claim 15, wherein 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 comprises transmitting instructions specifying an application program interface (API) call to render the digital component included in the particular response.

19. The non-transitory computer-readable medium of claim 15, wherein transmitting, over a network, each real-time request to a corresponding third party digital component provider comprises transmitting the particular real-time request to the particular third-party digital component provider without decrypting the encrypted data.

20. The non-transitory computer-readable medium of claim 15, wherein the operations further comprise:

providing a particular custom digital component associated with the particular response for presentation by a particular SDK in an electronic document at the client device.