Data transmission using smart clusters

• US 10,810,231 B2
• Filed: 02/05/2019
• Issued: 10/20/2020
• Est. Priority Date: 02/05/2019
• Status: Active Grant

• Current Assignee: Bank of America Corp.
• Original Assignee: Bank of America Corp.
• Inventors: Lakshminarayanan, Balamurali, Ahmed, Mubashshir Ahmed Nazir, Nelakuditi, Srinath, Pallapolu, Kalyan Chakravarthy
• Primary Examiner(s): Al-Hashemi, Sana A
• Application Number:
  US16/267,844
• Publication Number:
  US 20200250204A1
• Time in Patent Office: 623 Days
• Field of Search: 707607, 707609, 707687, 707705, 707769, 707790, 707813, 707821
• CPC Class Codes: G06F 16/122 using management policies backup systems G06F11/1446; file migration policies for HSM systems G06F16/185
• CPC Class Codes: G06F 16/182 Distributed file systems
• CPC Class Codes: G06F 16/2228 Indexing structures
• CPC Class Codes: G06F 16/278 Data partitioning, e.g. horizontal or vertical partitioning
• CPC Class Codes: G06F 16/907 Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/61 taking into account QoS or priority requirements

Abstract

A smart transmission system is configured to upload data from a plurality of sources to a target application hosted in a cloud environment. A server receives a data stream from the plurality of sources. Using a priority algorithm, the server analyzes the data stream to determine which files and accounts are most critical for the target application'"'"'s function. The files and their associated accounts are partitioned into tranches, and the tranches are uploaded to the target application in order of priority.

Claims

1. A system for clustered data uploads, comprising:

a memory configured to store a database of account settings, wherein the account settings includes at least one static factor related to data significance;

a processor, communicatively coupled to a cloud server, the processor configured to;

receive a data stream from a plurality of sources, wherein the data stream is composed of a plurality of files and each file in the data stream is associated with one of a plurality of accounts;

implement a priority engine, configured to;

read, for each of the plurality of accounts that has a related file in the data stream, a set of static factors related to the file'"'"'s significance to a target application and a set of dynamic factors related to file usage and associated account updates, wherein the static and dynamic factors are located in metadata of the files associated with each account or in the database of account settings;

for a first account comprised of a first set of files, assign;

a priority value for each of a set of the static factors; and

a priority value for each of a set of the dynamic factors;

for a second account comprised of a second set of files, assign;

a priority value for each of the set of static factors; and

a priority value for each of the set of the dynamic factors;

implement an aggregation engine, configured to compute, using a priority algorithm;

a first cumulative priority value for the first account based on the priority values generated by the priority engine; and

a second cumulative priority value for the second account based on the priority values generated by the priority engine, wherein the second cumulative priority value is greater than the first cumulative priority value;

implement a data clustering engine, configured to;

assemble a first tranche, wherein the first tranche includes the second account and the files from the data stream that are associated with the second account;

assemble a second tranche, wherein the second tranche includes the first account and the files from the data stream that are associated with the first account;

implement a cloud connector engine, configured to;

connect with a target application located in the cloud server;

send, to the target application, the first tranche;

send, after the first tranche is uploaded to the target application, the second tranche to the target application.

2. The system of claim 1, wherein the memory is further configured to store a table of rules for assigning priority values, and wherein assigning priority values comprises comparing the static and dynamic factors associated with an account to a set of rules for assigning priority values for each factor.

3. The system of claim 1, wherein the account settings include at least one selected from the group of data source, customer type, customer contact info, customer opt out consent, and customer relationship.

4. The system of claim 1, wherein the target application is a customer relationship management application.

5. The system of claim 1, wherein the static factors include at least one selected from the group of data source, customer type, customer contact info, customer opt out consent, and customer relationship.

6. The system of claim 1, wherein the dynamic factors include at least one selected from the group of opportunity create date, appointment due date, follow-up task due date, interaction created date, and customer behavior indicator.

7. The system of claim 1, wherein the priority algorithm is a Gini Index formula.

8. A method for clustered data uploads, comprising:

reading for each of a plurality of accounts that has a related file in a data stream, by a first processor, a set of static factors related to the file'"'"'s significance to a target application and a set of dynamic factors related to file usage and associated account updates, wherein the static and dynamic factors are located in metadata of the files associated with each account or in a database of account settings;

for a first account comprised of a first set of files, assigning, by the first processor;

a priority value for each of a set of the static factors; and

a priority value for each of a set of the dynamic factors;

for a second account comprised of a second set of files, assigning, by the first processor;

a priority value for each of the set of static factors; and

a priority value for each of the set of the dynamic factors;

computing, using a priority algorithm implemented on the first processor;

a first cumulative priority value for the first account; and

a second cumulative priority value for the second account, wherein the second cumulative priority value is greater than the first cumulative priority value;

assemble, by the first processor;

a first tranche, wherein the first tranche includes the second account and the files from the data stream that are associated with the second account; and

a second tranche, wherein the second tranche includes the first account and the files from the data stream that are associated with the first account;

send, by the first processor;

the first tranche to the target application located in a cloud server; and

after the first tranche is uploaded to the target application, the second tranche to the target application.

9. The method of claim 8, wherein the account settings include at least one selected from the group of data source, customer type, customer contact info, customer opt out consent, and customer relationship.

10. The method of claim 8, wherein assigning priority values comprises comparing the static and dynamic factors associated with an account to a set of rules for assigning priority values for each factor.

11. The method of claim 8, wherein the target application is a customer relationship management application.

12. The method of claim 8, wherein the static factors include at least one selected from the group of data source, customer type, customer contact info, customer opt out consent, and customer relationship.

13. The method of claim 8, wherein the dynamic factors include at least one selected from the group of opportunity create date, appointment due date, follow-up task due date, interaction created date, and customer behavior indicator.

14. The method of claim 8, wherein the priority algorithm is a Gini Index formula.

15. A data clustering device, comprising one or more processors configured to implement:

a priority engine, configured to;

read in the files'"'"' metadata, for each of the plurality of accounts that has a related file in the data stream, a set of static factors related to the file'"'"'s significance to a target application and a set of dynamic factors related to file usage and associated account updates;

for a first account comprised of a first set of files, assign;

a priority value for each of a set of the static factors; and

a priority value for each of a set of the dynamic factors;

for a second account comprised of a second set of files, assign;

a priority value for each of the set of static factors; and

a priority value for each of the set of the dynamic factors;

an aggregation engine, configured to compute, using a priority algorithm;

a first cumulative priority value for the first account based on the priority values generated by the priority engine; and

a second cumulative priority value for the second account based on the priority values generated by the priority engine, wherein the second cumulative priority value is greater than the first cumulative priority value;

a data clustering engine, configured to;

assemble a first tranche, wherein the first tranche includes the second account and the files from the data stream that are associated with the second account;

assemble a second tranche, wherein the second tranche includes the first account and the files from the data stream that are associated with the first account;

a cloud connector engine, configured to;

connect with a target application located in the cloud server;

send, to the target application, the first tranche;

send, after the first tranche is uploaded to the target application, the second tranche to the target application.

16. The device of claim 15, wherein the priority engine is further operably configured to determine the set of static factors based on a database of account settings, wherein the account settings include at least one selected from the group of data source, customer type, customer contact info, customer opt out consent, and customer relationship.

17. The device of claim 15, wherein assigning priority values comprises comparing the static and dynamic factors associated with an account to a set of rules for assigning priority values.

18. The device of claim 15, wherein the dynamic factors include at least one selected from the group of opportunity create date, appointment due date, follow-up task due date, interaction created date, and customer behavior indicator.

19. The device of claim 15, wherein the priority algorithm is a Gini Index formula.

20. The device of claim 15, wherein the target application is a customer relationship management application.