IP Library › Granted Patent US 12,093,421
Granted Patent B2
US 12,093,421 · App. 17/849,911 · Granted Sep 17, 2024

Systems and methods for managing tokens and filtering data to control data access

Inventors: Asanka Dissanayake (Apex, NC); Greyson Hill (Wake Forest, NC); Jeffrey Kukesh (Hingham, MA); Anil Mahalaha (Medway, MA)
Assignee: Akoya LLC
G06F21/6227G06F3/0482G06F21/602G06F2221/2141
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,093,421
App. No.
17/849,911
Filed
Jun 27, 2022
Granted
Sep 17, 2024
Kind
B2
Art Unit
2432
USPC
726/5
Abstract

Systems and methods are described for receiving at an intermediary entity a token from a data provider that enables access to a user's data at a data provider, where the token is received without an intermediary entity receiving user credentials. A request is received from a data recipient to receive data from the data provider, where the token is required to access the data. Data may be received from the data provider using the token, and the received data may be filtered based on a data directive associated with the data provider, to identify which data the data recipient is permitted to access. The identified data may be provided to the data recipient.

Claims (45)

1. A method comprising:

determining, by an intermediary entity, a list of accounts that a user has with a data provider;

determining, based on an indication from the data provider, that a particular account included in the list of accounts should not be shared with one or more data recipients;

causing a permissions dashboard to be generated for display, wherein the permissions dashboard comprises:

indications of which accounts included in the list have been shared; and

options to selectively modify which accounts included in the list are to be shared with the one or more data recipients, wherein the permissions dashboard does not allow the user to share the particular account; and

obtaining, by the intermediary entity and based on the indications of the permissions dashboard, user information data and providing the user information data to a data recipient.

2. The method of claim 1 , wherein the permissions dashboard comprises a grayed out icon indicating that the particular account is not selectable to share.

3. The method of claim 1 , wherein the permissions dashboard does include the particular account that should not be shared with one or more data recipients.

4. The method of claim 1 , wherein the list of accounts that the user has with the data provider is determined based on a token indicating that the user has been successfully authenticated by the data provider, the method further comprising:

receiving input, from the permissions dashboard, to modify whether an account has been shared; and

updating the token based on the received input.

5. The method of claim 4 , wherein the input comprises a request to begin sharing the account with one or more data recipients or a request to stop sharing the account with one or more data recipients.

6. The method of claim 4 , wherein the token is stored by the intermediary entity without personally identifiable information of the user.

7. The method of claim 1 , wherein the list of accounts that the user has with the data provider is determined based on a token indicating that the user has been successfully authenticated by the data provider, the method further comprising:

receiving input, from the permissions dashboard, to revoke access to an account that was previously shared; and

updating the token based on the received input.

8. The method of claim 1 , wherein causing the permissions dashboard to be generated for display comprises:

receiving, by the intermediary entity and from the data provider, a request for information indicating which data recipients have been granted access to one or more accounts included in the list of accounts; and

providing, to the data provider, the requested information to enable the data provider to generate for display the permissions dashboard.

9. The method of claim 8 , wherein a permission application programming interface (API) associated with the intermediary entity is utilized by the data provider to request the information and receive the requested information.

10. The method of claim 1 , wherein the permissions dashboard indicates a plurality of data recipients having been granted access to one or more accounts included in the list of accounts.

11. A system comprising:

input/output (I/O) circuitry; and

control circuitry configured to:

determine, by an intermediary entity, a list of accounts that a user has with a data provider;

determine, based on an indication from the data provider, that a particular account included in the list of accounts should not be shared with one or more data recipients;

cause a permissions dashboard to be generated for display, wherein the permissions dashboard comprises:

indications of which accounts included in the list have been shared; and

options to selectively modify which accounts included in the list are to be shared with the one or more data recipients, wherein the permissions dashboard does not allow the user to share the particular account; and

obtain, by the intermediary entity and based on the indications of the permissions dashboard, user information data and providing the user information data to a data recipient.

12. The system of claim 11 , wherein the permissions dashboard comprises a grayed out icon indicating that the particular account is not selectable to share.

13. The system of claim 11 , wherein the permissions dashboard does include the particular account that should not be shared with one or more data recipients.

14. The system of claim 11 , wherein the list of accounts that the user has with the data provider is determined based on a token indicating that the user has been successfully authenticated by the data provider, and the control circuitry is further configured to:

receive input, from the permissions dashboard, to modify whether an account has been shared; and

update the token based on the received input.

15. The system of claim 14 , wherein the input comprises a request to begin sharing the account with one or more data recipients or a request to stop sharing the account with one or more data recipients.

16. The system of claim 14 , wherein the token is stored by the intermediary entity without personally identifiable information of the user.

17. The system of claim 11 , wherein the list of accounts that the user has with the data provider is determined based on a token indicating that the user has been successfully authenticated by the data provider, and the control circuitry is further configured to:

receive input, from the permissions dashboard, to revoke access to an account that was previously shared; and

update the token based on the received input.

18. The system of claim 11 , wherein the control circuitry is further configured to cause the permissions dashboard to be generated for display by:

receiving, by the intermediary entity and from the data provider, a request for information indicating which data recipients have been granted access to one or more accounts included in the list of accounts; and

providing, to the data provider, the requested information to enable the data provider to generate for display the permissions dashboard.

19. The system of claim 18 , wherein a permission application programming interface (API) associated with the intermediary entity is utilized by the data provider to request the information and receive the requested information.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 7, 2022
From: HILL, GREYSON
To: AKOYA LLC
Reel/Frame 061674/0132 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 27, 2022
From: BABANI, DENIS; DISSANAYAKE, ASANKA; KUKESH, JEFFREY; MAHALAHA, ANIL; RUBINSTEIN, STUART
To: AKOYA LLC
Reel/Frame 060321/0227 →
Continuity (2)
Continuation 17452010 · Oct 22, 2021
Related Publication 20230129541A1 · Apr 27, 2023
Cited By (1)
US 12,634,284