SYSTEMS AND METHODS FOR MANAGING PERMISSIONS FOR INFORMATION OWNERSHIP IN THE CLOUD
First Claim
1. A method comprising:
- receiving, via at least one server connected to a communication network, a rule set, wherein said rule set comprises at least one explicit permission to allow customer information to be transferred to at least one community of interest;
associating said rule set with a unique identifier, wherein said unique identifier is associated with an identifiable customer;
receiving, via said at least one server, from a requestor, a request for customer information associated with said unique identifier;
determining, via said at least one server, based on said rule set associated with said unique identifier, whether requestor has permission to receive said requested customer information; and
transferring said requested customer information to said requestor, if said requestor is determined to have permission to receive said requested customer information.
2 Assignments
0 Petitions
Accused Products
Abstract
The present invention relates to a central (root) directory and the synchronization of unique identifiers associated with a payment addresses and permission preferences at different institutions. In a preferred embodiment, each unique identifier associates an account owner'"'"'s permissions preference for the release of personal identifying information without the need for transaction-by-transaction explicit permissions or blanket implicit permissions. An asset transfer deposit account (for information and/or monetary assets) may be set up as a deposit only account. In this way, the present invention can be effective in eliminating many privacy concerns of account owners and security requirements of an information asset repository.
-
Citations
60 Claims
-
1. A method comprising:
-
receiving, via at least one server connected to a communication network, a rule set, wherein said rule set comprises at least one explicit permission to allow customer information to be transferred to at least one community of interest; associating said rule set with a unique identifier, wherein said unique identifier is associated with an identifiable customer; receiving, via said at least one server, from a requestor, a request for customer information associated with said unique identifier; determining, via said at least one server, based on said rule set associated with said unique identifier, whether requestor has permission to receive said requested customer information; and transferring said requested customer information to said requestor, if said requestor is determined to have permission to receive said requested customer information. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15)
-
-
16. A method comprising:
-
receiving, via at least one server connected to a communication network, transaction information associated with a unique identifier, wherein said unique identifier is associated with an identifiable customer; storing said transaction information associated with said unique identifier; and transferring said transaction information in response to a requestor'"'"'s request for information associated with said unique identifier, if said requestor is determined to have permission to receive said requested transaction information. - View Dependent Claims (17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30)
-
-
31. A system comprising:
at least one server, connected to a communication network, comprising executable programming contained on a non-transitory storage medium, said programming when executed operable to; receive a rule set, wherein said rule set comprises at least one explicit permission to allow customer information to be transferred to at least one community of interest; associate said rule set with a unique identifier, wherein said unique identifier is associated with an identifiable customer; receive from a requestor, a request for customer information associated with said unique identifier; determine based on said rule set associated with said unique identifier, whether requestor has permission to receive said requested customer information; and transfer said requested customer information to said requestor, if said requestor is determined to have permission to receive said requested customer information. - View Dependent Claims (32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45)
-
46. A system comprising:
at least one server, connected to a communication network, comprising executable programming contained on a non-transitory storage medium, said programming when executed operable to; receive transaction information associated with a unique identifier, wherein said unique identifier is associated with an identifiable customer; store said transaction information associated with said unique identifier; and transfer said transaction information in response to a requestor'"'"'s request for information associated with said unique identifier, if said requestor is determined to have permission to receive said requested transaction information. - View Dependent Claims (47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60)
Specification