Systems and Methods for Decentralizing Consumer Preferences, Consent and Permissions Management with Reward and Reputation Network for Enterprises Using a Blockchain Ledger

• US 20190188411A1
• Filed: 12/19/2017
• Published: 06/20/2019
• Est. Priority Date: 12/19/2017
• Status: Abandoned Application

• Current Assignee: Vladislav Kroutik
• Original Assignee: Vladislav Kroutik
• Inventors: Kroutik, Vladislav
• Application Number:
  US15/847,717
• Publication Number:
  US 20190188411A1
• Time in Patent Office: Days
• CPC Class Codes: G06F 21/604 Tools and structures for managing or administering access control systems
• CPC Class Codes: G06F 21/6245 Protecting personal data, e.g. for financial or medical purposes
• CPC Class Codes: G06F 21/645 using a third party
• CPC Class Codes: G06Q 20/3827 Use of message hashing
• CPC Class Codes: G06Q 20/4014 Identity check for transactions
• CPC Class Codes: G06Q 2220/00 Business processing using cryptography postage metering system using cryptography G06Q2250/05
• CPC Class Codes: G06Q 2220/10 Usage protection of distributed data files
• CPC Class Codes: G06Q 50/188 Electronic negotiation
• CPC Class Codes: H04L 63/04 for providing a confidential data exchange among entities communicating through data packet networks
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 9/0894 Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage
• CPC Class Codes: H04L 9/3231 Biological data, e.g. fingerprint, voice or retina network architectures or network communication protocols for supporting authentication of entities using biometrical features in a packet data network H04L63/0861
• CPC Class Codes: H04L 9/3239 involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
• CPC Class Codes: H04L 9/3297 involving time stamps, e.g. generation of time stamps
• CPC Class Codes: H04L 9/50 using hash chains, e.g. blockchains or hash trees

Abstract

This invention relates generally to a method and an apparatus for managing consumer preferences, consent and permissions (PCP) and more specifically to a decentralized infrastructure and system including enterprise access to specific consumer PCP within reward and reputation network utilizing Blockchain ledgers.

Claims

1. An electronic system for management of personal data, preferences, consent and permissions, represented by smart contracts stored and executed on a decentralized blockchain ledger, between an enterprise and at least one of a plurality of consumers, comprising of:

a decentralized controller, having a network interface coupled to a network, in which the decentralized controller is comprised of a smart contract system configured to process, create and distribute smart contracts, as well as storing and executing smart contracts on a decentralized blockchain ledger;

a blockchain ledger, coupled to the network interfaces across the network, which is configured to stare and execute smart contracts between an enterprise and at least one of a plurality of consumers;

a consumer interface, coupled to the network interface across the network, which is configured to receive consumer input; and

an enterprise interface, coupled to the network interface across the network, which is configured to receive enterprise input.

2. The electronic system of claim 1, wherein the decentralized controller further comprises of:

a distribution system configured to process consumer requests received by the electronic system to store personal data and create smart contracts on a decentralized blockchain ledger, and to deliver one or more smart contracts in response to the enterprise input, wherein the distribution system is further configured to process execution requests received by the electronic system for smart contracts, and to deliver one or more smart contract choices in response to the execution requests;

a permission management system configured to manage consumers personal data, preferences, consent and permissions;

a clearing system configured to process financial transactions associated with the distribution of the smart contracts;

a reward management system configured to match reward offers based on consumers target interests and delivery of them through the consumer interface;

a reporting system configured to track all activities by a decentralized controller and record them for later access and reporting; and

a smart contract system configured to process requests from consumers to initiate the smart contract, store and execute the smart contract on a blockchain ledger.

3. The electronic system of claim 1, further comprising of a blockchain communication coupling which is creating a network connection between the decentralized controller and a blockchain system, wherein the blockchain system communication coupling is configured to receive smart contracts and transactions created by decentralized controllers and record them for future accesses, validations and executions.

4. The electronic system of claim 1, further comprising of a bank communication coupling via a network connection between the decentralized controller and a bank, wherein the bank communication coupling is configured to receive information validating funds from the bank.

5. The electronic system of claim 1, further comprising of a smart contract validation communication coupling connected across the network between the decentralized controller and a smart contract validation system, wherein the smart contract validation communication coupling is configured to receive information validating consumer smart contracts for compliance with consumer consent, preferences and permissions.

6. The electronic system of claim 1, wherein the decentralized controller further comprises of a membership system, a consumer database and an enterprise database, wherein the membership system is configured to authenticate the identities of at least one consumer and at least one enterprise by matching identities of consumers stored in the consumer database and by matching identities of enterprises stored in the enterprise database.

7. The electronic system of claim 2, further comprising of a smart contract database which is accessible by the decentralized controller which is upon receiving personal data from the consumer interface, is configured to invoke the smart contract system to create a plurality of smart contracts corresponding to the consumers personal data and preferences and reward offer settings and to store them in the smart contract database.

8. The electronic system of claim 7, wherein the decentralized controller, upon receiving a request from the enterprise interface, is configured to invoke the smart contract system to retrieve one or more smart contracts from the smart contracts database, associate a consumer with the one or more smart contract, and to deliver the consumer information to the enterprise interface.

9. The electronic system of claim 8, further comprising of a plurality of databases which are accessible by the decentralized controller, the plurality of databases comprising of at least a smart contract database for storing execution commitments of the smart contracts, and a transaction database for storing transaction data relating to the smart contracts.

10. The electronic system of claim 9, wherein the decentralized controller, upon receiving a execution commitment from the enterprise interface, is configured to invoke the smart contract system to generate an identifier specifying at least one financial account, the identifier being associated with the execution commitment, and to store the execution commitment and the identifier in the smart contract database.

11. The electronic system of claim 10, wherein the decentralized controller, upon the execution of the smart contract stored in the smart contract database, is configured to invoke the clearing system to transfer funds from an enterprise account to consumer account based on a reward structure which is stored in the smart contract and record the execution of a smart contract on a decentralized blockchain ledger.

12. The electronic system of claim 9, further comprising of a plurality of databases, containing at least a permissions database, a reward offer database, a reputation database, a rewards database, a payment database, an audit database, an escrow database, and a smart contract database.

13. A method for management of personal data, preferences, consent and permissions, represented by smart contracts, stored and executed on a decentralized blockchain ledger, between an enterprise and at least one of a plurality of consumers, the method comprising the steps of:

providing a networked, electronic change apparatus having a decentralized controller, in which the decentralized controller is comprising of;

a smart contract management system configured to process requests received by the networked, electronic exchange apparatus for smart contracts, and to deliver one or more smart contracts in response to the requests;

a blockchain ledger configured to store and execute smart contracts between au enterprise and at least one of a plurality of consumers;

a permission system configured to process requests by consumers to store personal data, preferences, consent and permissions;

a reputation management system configured to maintain feedback records of decentralized controller transactions;

a clearing system configured to process financial transactions associated with the rewards of the smart contracts;

a reporting system configured to maintain a record of decentralized controller transactions and consumer data accesses;

a consumer interface; and

an enterprise interface;

receiving personal data from the consumer interface, the personal data comprising at least an email, name, permissions, consent, and preferences;

generating a smart contract associated with the personal data;

delivering the smart contract to the enterprise interface; and

storing and executing the smart contract on a decentralized blockchain ledger.

14. The method of claim 13, wherein the smart contract corresponds to a consumer personal data, further comprising the step of a partial sharing of personal data, consent to the reward for engagement with at least one of the plurality of enterprises.

15. The method of claim 13, further comprising of the steps to:

receive at least one smart contract from the consumer interface in response to the step of delivering the reward offer;

receive at least one execution commitment from the enterprise response to the step of delivering the smart contract;

receive an electronic financial account identifier associated with each execution commitment from the enterprise interface; and

execute an electronic transfer of funds via the electronic financial account identifier; and

execute and record a smart contract on a decentralized blockchain ledger.

16. The method of claim 15, wherein the smart contract comprises of at least the personal data shared, consent, list of preferences, permission to access personal data, a reward value, and a contract expiration date.

17. The method of claim 15, further comprising of the step to receive a guarantee for reward payments upon execution of the smart contract, wherein the guaranteed reward is comprised of either a digital currency, cash, reward points or a combination thereof.

18. The method of claim 15, further comprising of the step of determining whether a smart contract duration has expired prior to the execution commitment.

19. The method of claim 15, further comprising of the steps of validating the personal data and validating the at least one execution commitment.

20. The method of claim 15, further comprising the steps of:

delivering at least one smart contract to the consumer interface upon receiving the personal data;

receiving additional personal data, consent, permissions and preferences from the consumer interface

generating, electronically, a first counteroffer and delivering the first counteroffer to the enterprise interface;

executing at least one smart contract upon receiving the at least one execution commitment;

executing and recording a smart contract on a decentralized blockchain ledger;

receiving additional personal data details from the consumer interface; and

generating, electronically, a follow-up counteroffer and delivering the counteroffer to the enterprise interface.