| CPC G06Q 20/389 (2013.01) [G06Q 20/4014 (2013.01)] | 20 Claims |
|
1. A system comprising:
one or more processors; and
a memory in communication with the one or more processors and storing instructions that, when executed by the one or more processors, are configured to cause the system to:
retrieve, via an application programming interface (API), data corresponding to a first user, the data comprising one or more first metadata snapshots corresponding to a first business purpose of the first user;
receive, from the first user, one or more first sharing preferences associated with a second user;
determine, using a machine learning model (MLM), whether the one or more first sharing preferences correspond to the retrieved data;
responsive to determining the one or more first sharing preferences do not correspond to the retrieved data, predict, via the MLM and based on at least the one or more first sharing preferences, one or more first data subsets of the data to share with the second user by associating the one or more first data subsets with the first business purpose of the first user;
extract the one or more first data subsets from the data;
generate one or more blocks of a blockchain ledger;
append the one or more first data subsets to at least a first block of the one or more blocks of the blockchain ledger;
provide the second user with access to the one or more first data subsets on the at least first block;
dynamically monitor the one or more first data subsets to detect whether any changes have been made to the one or more first data subsets;
responsive to detecting at least a first change has been made to at least one first data subset of the one or more first data subsets, provide the second user with access to the at least one first data subset by:
generating a first unique identifier corresponding to the at least one first data subset and the first change;
receiving, from the second user via a mobile application, a second unique identifier; and
determining that the first and second unique identifiers match;
retrieve one or more second metadata snapshots corresponding to the data;
determine, using the MLM, whether the one or more first sharing preferences correspond to the one or more second metadata snapshots;
responsive to determining the one or more first sharing preferences do not correspond to the one or more second metadata snapshots, predict, via the MLM and based on at least the one or more first sharing preferences, one or more second data subsets of the data to share with the second user by associating the one or more second data subsets with the first business purpose of the first user;
extract the one or more second data subsets from the one or more updates;
append the one or more second data subsets to at least a second block of the one or more blocks of the blockchain ledger;
provide the second user with access to the one or more second data subsets on the at least second block;
dynamically monitor the one or more second data subsets to detect whether any changes have been made to the one or more second data subsets; and
responsive to detecting at least a second change has been made to at least one second data subset of the one or more second data subsets, provide the second user with access to the at least one second data subset by:
generating a third unique identifier corresponding to the at least one second data subset and the second change;
receiving, from the second user via the mobile application, a fourth unique identifier; and
determining that the third and fourth unique identifiers match.
|