Collection and analysis of customer data from application programming interface usage

• US 9,218,503 B2
• Filed: 07/24/2013
• Issued: 12/22/2015
• Est. Priority Date: 07/24/2013
• Status: Active Grant

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Inventors: Counterman, Raymond C.
• Primary Examiner(s): Pwu, Jeffrey
• Assistant Examiner(s): Anderson, Michael D
• Application Number:
  US13/949,642
• Publication Number:
  US 20150033330A1
• Time in Patent Office: 881 Days
• Field of Search: 726/10, 726/20
• US Class Current: 1/1
• CPC Class Codes: G06F 21/6245 Protecting personal data, e.g. for financial or medical purposes
• CPC Class Codes: H04W 12/02 Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
• CPC Class Codes: H04W 12/08 Access security
• CPC Class Codes: H04W 12/63 Location-dependent; Proximity-dependent

Abstract

A device may receive a request for analytics information associated with a user device. The device may retrieve application programming interface (API) information associated with the request for analytics information. The API information may include information associated with providing an authorization token and with providing user device information. The device may determine demographic information based on the request for analytics information. The demographic information may be associated with a user of the user device. The device may determine the analytics information based on an analysis of the API information and the demographic information. The device may provide the analytics information.

Claims

1. A device, comprising:

one or more processors to;

receive a request for analytics information,

the request including a search query that includes one or more application programming interface (API) parameters and one or more demographic parameters for determining the analytics information,

the one or more API parameters identifying;

 

an application,

 

a type of the application,

 

a location associated with a user device that uses the application, or

 

storage information associated with the user device, and

the one or more demographic parameters identifying at least one of;

 

a user associated with the user device,

 

an age of the user,

 

a gender of the user,

 

a location associated with the user,

 

contact information associated with the user,

 

a salary associated with the user, or

 

purchase information associated with the user;

retrieve API information that identifies one or more user devices associated with the one or more API parameters included in the search query,

the API information including user device information gathered based on usage of the application by the one or more user devices;

determine demographic information associated with one or more users of the one or more user devices;

process the demographic information, based on the one or more demographic parameters included in the search query, to determine the analytics information,

the analytics information identifying at least one user device associated with a portion of the demographic information that matches the one or more demographic parameters and associated with a portion of the API information that matches the one or more API parameters; and

provide the analytics information based on determining the analytics information.

2. The device of claim 1, where the one or more processors are further to:

receive a request for authorization to access the user device information;

provide an authorization token associated with receiving access to the user device information;

store information associated with providing the authorization token; and

where the one or more processors, when retrieving the API information, are to;

retrieve the API information based on the information associated with providing the authorization token.

3. The device of claim 2, where the one or more processors are further to:

determine that consent is required from the user device based on the user device information;

receive consent from the user device; and

where the one or more processors, when providing the authorization token associated with receiving access to the user device information, are to;

provide the authorization token based on receiving consent from the user device.

4. The device of claim 1, where the one or more processors are further to:

receive another request, which includes an authorization token, for the user device information;

determine the user device information based on the other request;

provide the user device information;

store information associated with providing the user device information; and

where the one or more processors, when retrieving the API information, are to;

retrieve the API information based on the information associated with providing the user device information.

5. The device of claim 4, where the one or more processors, when determining the user device information based on the other request, are to:

determine that the user device information matches a particular result,

the particular result being associated with the request for the analytics information; and

where the one or more processors, when providing the analytics information, are to;

provide the analytics information based on determining that the user device information matches the particular result.

6. The device of claim 1, where the one or more processors are further to:

receive information associated with the usage of the application;

store the information associated with the usage of the application as stored API information; and

where the one or more processors, when retrieving the API information, are to;

retrieve the stored API information associated with the usage of the application.

7. The device of claim 1, where the one or more processors, when providing the analytics information, are to:

provide the analytics information for display.

8. The device of claim 1, where the one or more processors, when determining the demographic information, are to:

provide the API information to another device that stores the demographic information; and

receive the demographic information from the other device based on providing the API information to the other device.

9. A non-transitory computer-readable medium storing instructions, the instructions comprising:

one or more instructions that, when executed by one or more processors, cause the one or more processors to;

receive an analytics query for analytics information,

the analytics query identifying an application programming interface (API) parameter and a demographic parameter,

the API parameter identifying at least one of;

 

an application associated with an API,

 

a type of the application,

 

a location associated with a user device that uses the application, or

 

storage information associated with the user device, and

the demographic parameter identifying;

 

a user associated with the user device,

 

an age range of the user,

 

a gender of the user,

 

a location associated with the user,

 

contact information associated with the user,

 

a salary range associated with the user, or

 

purchase information associated with the user;

retrieve API information associated with the API parameter identified in the analytics query,

the API information being derived based on usage of the API,

the API information identifying one or more user devices;

determine demographic information associated with one or more users of the one or more user devices;

process the demographic information, using the demographic parameter, to determine the analytics information,

the analytics information identifying at least one user device associated with a portion of the demographic information that matches the demographic parameter and associated with a portion of the API information that matches the API parameter; and

provide the analytics information.

10. The non-transitory computer-readable medium of claim 9, where the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:

receive a request for authorization to access user device information associated with the user device of the one or more user devices;

provide an authorization token associated with receiving access to the user device information;

store information associated with providing the authorization token; and

where the one or more instructions, that cause the one or more processors to retrieve the API information, are to;

retrieve the API information based on the information associated with providing the authorization token.

11. The non-transitory computer-readable medium of claim 10, where the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:

request, from the user device, consent to provide authorization for access to the user device information;

receive consent from the user device; and

where the one or more instructions, that cause the one or more processors to provide the authorization token associated with receiving access to the user device information, cause the one or more processors to;

provide the authorization token based on receiving the consent from the user device.

12. The non-transitory computer-readable medium of claim 10, where the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:

receive another request, which includes the authorization token, to use the API;

determine the user device information based on the other request;

provide the user device information via the API; and

where the one or more instructions, that cause the one or more processors to retrieve the API information, cause the one or more processors to;

retrieve the API information based on providing the user device information via the API.

13. The non-transitory computer-readable medium of claim 9, where the one or more instructions, that cause the one or more processors to provide the analytics information, cause the one or more processors to:

provide the analytics information to another device for display.

14. The non-transitory computer-readable medium of claim 9, where the one or more instructions, that cause the one or more processors to determine the demographic information, cause the one or more processors to:

determine the demographic information based on subscriber information stored by a home subscriber server (HSS).

15. A method, comprising:

receiving, by a device, a request for analytics information,

the request including an application programming interface (API) parameter and a demographic parameter,

the API parameter identifying at least one of;

an application associated with an API,

a type of the application,

a location associated with a user device that uses the application, or

storage information associated with the user device, and

the demographic parameter identifying at least one of;

a user associated with the user device,

an age or an age range of the user,

a gender of the user,

a location associated with the user,

contact information associated with the user,

a salary or a salary range associated with the user, or

purchase information associated with the user;

determining, by the device, API information derived from usage of the API by a plurality of user devices,

the API information identifying the plurality of user devices;

determining, by the device, demographic information corresponding to a plurality of users of the plurality of user devices;

processing, by the device, the demographic information using the demographic parameter;

determining, by the device, the analytics information based on processing the demographic information,

the analytics information identifying at least one user device associated with a portion of the demographic information that matches the demographic parameter and associated with a portion of the API information that matches the API parameter; and

providing, by the device, the analytics information.

16. The method of claim 15, further comprising:

identifying the plurality of user devices based on the API parameter matching a parameter associated with the usage of the API by the plurality of user devices; and

where determining the API information comprises;

determining the API information based on identifying the plurality of user devices.

17. The method of claim 15, where the API information includes information associated with the user device, of the plurality of user devices, when the user device is using the application associated with the API.

18. The method of claim 15, further comprising:

determining that the user device, of the plurality of user devices, is using the application associated with the API;

storing information, associated with the usage of the application by the user device, as stored API information; and

where retrieving the API information comprises;

retrieving the stored API information associated with the usage of the application by the user device.

19. The method of claim 15, where receiving the request for the analytics information comprises:

receiving the request for the analytics information from a particular device; and

where providing the analytics information comprises;

providing the analytics information to the particular device.

20. The method of claim 15, where providing the analytics information comprises:

providing the analytics information to another device.