Techniques for in-app user data authorization
AssigneeFacebook, Inc.
InventorsEdward Kenneth O'Neill, Vladamir Fedorov
Life of this patent
Estimating the term…
Abstract
Techniques for in-app user data authorization are described. An apparatus may comprise a processor circuit, a permissions component, and a token component. The permissions component may be operative on the processor circuit to receive a request from an application to perform a task on a device and to return a response to the request to the application based on active permissions for the application. The token component may be operative on the processor circuit to manage a token database and to determine the active permissions for the application based on the token database. Other embodiments are described and claimed.
Claims12
An apparatus, comprising:
- a processor circuit;
- a permissions component operative on the processor circuit to receive a request from an application to perform a task on a device and to return a response to the request to the application based on active permissions for the application;
- a token component operative on the processor circuit to manage a token database, to retrieve a token from the token database, to determine the active permissions for the application based on the retrieved token, and to update existing permissions to the active permissions according to a user response;
- and
- a dialog component operative on the processor circuit to determine a permission bucket corresponding to the request from the application, to retrieve a dialog template corresponding to the determined permission bucket, to construct a dialog for display to a user based on the retrieved dialog template and the request, to send the dialog to a user interface component, to receive a user response from the user interface component, and to send the user response to the token component.
A computer-implemented method, comprising:
- receiving, by a permissions component, a request from an application to perform a task on a device;
- retrieving, by a token component, a token from a token database;
- determining, by the token component, active permissions for the application based on the retrieved token;
- returning, by the permissions component, a response to the request to the application based on active permissions for the application;
- determining, by a dialog component, a permission bucket corresponding to the request from the application;
- retrieving, by the dialog component, a dialog template corresponding to the determined permission bucket;
- constructing, by the dialog component, a dialog for display to a user based on the retrieved dialog template and the request;
- displaying, by the dialog component, the dialog to the user;
- receiving, by the dialog component, a user response;
- and
- updating, by the token component, existing permissions to the active permissions according to the user response.
At least one non-transitory computer-readable storage medium comprising instructions that, when executed, cause a system to:
- receive, by a permissions component, a request from an application to perform a task on a device;
- retrieve, by a token component, an existing token from a token database;
- determine, by the token component, existing permissions based on the existing token;
- determine, by a dialog component, a permission bucket corresponding to the request from the application;
- retrieve, by the dialog component, a dialog template corresponding to the determined permission bucket;
- construct, by the dialog component, a dialog for display to a user based on the retrieved dialog template and the request;
- display, by the dialog component, the dialog to the user;
- receive, by the dialog component, a user response;
- create, by the token component, an active token based on the user response to update the existing permissions;
- store, by the token component, the active token in the token database;
- determine, by the token component, active permissions for the application according to the active token;
- and
- return, by the permissions component, a response to the request to the application based on the active permissions for the application.
Dependencies are inferred from the claim text.