# US 2024/0176896 A1 · Multi-Computer System for Data Privacy and Governance

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2024/0176896 A1
- Document ID: US20240176896A1
- Status: Published application
- Kind: A1
- Application number: 18/070,907
- Filed: 2022-11-29
- Published: 2024-05-30
- Earliest claimed: 2022-11-29
- Assignees: Bank of America Corporation
- Applicants: Bank of America Corporation
- Inventors: Siten Sanghvi
- Web page: https://patentgrep.com/patent/US20240176896A1

## CPC

- G06F 21/602: {Providing cryptographic facilities or services}
- G06F 21/604: {Tools and structures for managing or administering access control systems}
- G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database}
- G06Q 20/3829: {involving key management}
- G06Q 20/401: {Transaction verification}
- G06Q 20/405: {Establishing or using transaction specific rules}
- G06Q 30/0236: {Incentive or reward received by requiring registration or ID from user}
- H04L 9/0825: {using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Arrangements for providing data security control functions are provided. In some aspects, a request to process a transaction may be received. The transaction request may include identification of one or more destinations or target nodes for data, transaction details, a source of the transaction, and the like. In some examples, one or more data elements may be identified and a category of each data element may be identified. One or more rules engines may be identified and executed. Based on the application of rules in the one or more rules engines, secure data elements may be generated and encrypted. The encrypted data elements may be sent to a distributed ledger system for storage. One or more notifications may be transmitted to one or more target nodes indicating that data has been sent to the distributed ledger system. The target nodes may retrieve and decrypt the data to process the transaction.

## Claims

### Claim 1

A computing platform, comprising:
at least one processor;
a communication interface communicatively coupled to the at least one processor; and
a memory storing computer-readable instructions that, when executed by the at least one processor, cause the computing platform to:
receive, from a source node, a request for a transaction;
analyze the request for a transaction to identify a plurality of data elements within the request for the transaction;
identify, for each data element of the plurality of data elements, a category of data associated with a respective data element;
identify, based on the identified categories of data associated with the respective data elements, one or more rules engines to execute;
execute the identified one or more rules engines to generate a plurality of secure data elements corresponding to the plurality of data elements;
encrypt each secure data element of the plurality of secure data elements;
transmit, to a distributed ledger system, each encrypted secure data element of the plurality of secure data elements, wherein transmitting each secure data element to the distributed ledger system causes a distributed ledger to store each encrypted secure data element;
generate one or more notifications indicating that each encrypted secure data element has been transmitted to the distributed ledger system; and
transmit, to a plurality of target nodes, the generated one or more notifications, wherein transmitting the generated one or more notifications causes the one or more notifications to be displayed on a respective target node.

### Claim 2 (depends on 1)

The computing platform of claim 1, wherein a first notification is transmitted to a first target node and a second notification is transmitted to a second target node.

### Claim 3 (depends on 2)

The computing platform of claim 2, wherein the first notification indicates that a first portion of the plurality of secure data elements has been transmitted to the distributed ledger system and may be retrieved by the first target node.

### Claim 4 (depends on 3)

The computing platform of claim 3, wherein the first notification includes a key of a key pair to decrypt the encrypted secure data elements in the first portion of the plurality of secure data elements.

### Claim 5 (depends on 4)

The computing platform of claim 4, wherein the encrypted secure data elements in the first portion of the plurality of secure data elements are associated with a first category of data.

### Claim 6 (depends on 5)

The computing platform of claim 5, wherein the second notification indicates that a second portion of the plurality of secure data elements, different from the first portion, has been transmitted to the distributed ledger system and may be retrieved by the second target node.

### Claim 7 (depends on 6)

The computing platform of claim 6, wherein the second notification includes a key of a key pair to decrypt the encrypted secure data elements in the second portion of the plurality of secure data elements.

### Claim 8 (depends on 7)

The computing platform of claim 7, wherein the encrypted secure data elements in the second portion of the plurality of secure data elements are associated with a second category of data, different from the first category of data.

### Claim 9 (depends on 1)

The computing platform of claim 1, further including instructions that, when executed, cause the computing platform to:
prior to receiving, from the source node, the request for the transaction, receive registration data of a user associated with the source node, wherein the registration data includes user privacy and data access preferences;
generate an incentive for the user associated with the source node to modify the user privacy and data access preferences; and
transmit, to the source node, the generated incentive, wherein transmitting, to the source node, the generated incentive, causes the generated incentive to display on a display of the source node.

### Claim 10 (depends on 9)

The computing platform of claim 9, further including instructions that, when executed cause the computing platform to:
receive, from the source node, incentive response data; and
modify, based on the incentive response data, the registration data.

### Claim 11

A method, comprising:
receiving, by a computing platform, the computing platform having at least one processor, and memory and from a source node, a request for a transaction;
analyzing, by the at least one processor, the request for a transaction to identify a plurality of data elements within the request for the transaction;
identifying, by the at least one processor and for each data element of the plurality of data elements, a category of data associated with a respective data element;
identifying, by the at least one processor and based on the identified categories of data associated with the respective data elements, one or more rules engines to execute;
executing, by the at least one processor, the identified one or more rules engines to generate a plurality of secure data elements corresponding to the plurality of data elements;
encrypting, by the at least one processor, each secure data element of the plurality of secure data elements;
transmitting, by the at least one processor and to a distributed ledger system, each encrypted secure data element of the plurality of secure data elements, wherein transmitting each encrypted secure data element to the distributed ledger system causes a distributed ledger to store each encrypted secure data element;
generating, by the at least one processor, one or more notifications indicating that each encrypted secure data element has been transmitted to the distributed ledger system; and
transmitting, by the at least one processor and to a plurality of target nodes, the generated one or more notifications, wherein transmitting the generated one or more notifications causes the one or more notifications to be displayed on a respective target node.

### Claim 12 (depends on 11)

The method of claim 11, wherein a first notification is transmitted to a first target node and a second notification is transmitted to a second target node.

### Claim 13 (depends on 12)

The method of claim 12, wherein the first notification indicates that a first portion of the plurality of secure data elements has been transmitted to the distributed ledger system and may be retrieved by the first target node.

### Claim 14 (depends on 13)

The method of claim 13, wherein the first notification includes a key of a key pair to decrypt the encrypted secure data elements in the first portion of the plurality of secure data elements.

### Claim 15 (depends on 14)

The method of claim 14, wherein the encrypted secure data elements in the first portion of the plurality of secure data elements are associated with a first category of data.

### Claim 16 (depends on 15)

The method of claim 15, wherein the second notification indicates that a second portion of the plurality of secure data elements, different from the first portion, has been transmitted to the distributed ledger system and may be retrieved by the second target node.

### Claim 17 (depends on 16)

The method of claim 16, wherein the second notification includes a key of a key pair to decrypt the encrypted secure data elements in the second portion of the plurality of secure data elements.

### Claim 18 (depends on 17)

The method of claim 17, wherein the encrypted secure data elements in the second portion of the plurality of secure data elements are associated with a second category of data, different from the first category of data.

### Claim 19 (depends on 11)

The method of claim 11, further including:
prior to receiving, from the source node, the request for the transaction, receiving, by the at least one processor, registration data of a user associated with the source node, wherein the registration data includes user privacy and data access preferences;
generating, by the at least one processor, an incentive for the user associated with the source node to modify the user privacy and data access preferences;
transmitting, by the at least one processor and to the source node, the generated incentive, wherein transmitting, to the source node, the generated incentive, causes the generated incentive to display on a display of the source node;
receiving, by the at least one processor and from the source node, incentive response data; and
modifying, by the at least one processor and based on the incentive response data, the registration data.

### Claim 20

One or more non-transitory computer-readable media storing instructions that, when executed by a computing platform comprising at least one processor, memory, and a communication interface, cause the computing platform to:
receive, from a source node, a request for a transaction;
analyze the request for a transaction to identify a plurality of data elements within the request for the transaction;
identify, for each data element of the plurality of data elements, a category of data associated with a respective data element;
identify, based on the identified categories of data associated with the respective data elements, one or more rules engines to execute;
execute the identified one or more rules engines to generate a plurality of secure data elements corresponding to the plurality of data elements;
encrypt each secure data element of the plurality of secure data elements;
transmit, to a distributed ledger system, each encrypted secure data element of the plurality of secure data elements, wherein transmitting each encrypted secure data element to the distributed ledger system causes a distributed ledger to store each encrypted secure data element;
generate one or more notifications indicating that each encrypted secure data element has been transmitted to the distributed ledger system; and
transmit, to a plurality of target nodes, the generated one or more notifications, wherein transmitting the generated one or more notifications causes the one or more notifications to be displayed on a respective target node.
