Parallel Data Transmission

• US 20180359059A1
• Filed: 06/08/2017
• Published: 12/13/2018
• Est. Priority Date: 06/08/2017
• Status: Active Grant

• Current Assignee: Bank of America Corp.
• Original Assignee: Bank of America Corp.
• Inventors: Kurian, Manu J.
• Granted Patent: US 10,461,898 B2
• Time in Patent Office: Days
• CPC Class Codes: H04L 1/0006 by adapting the transmission format
• CPC Class Codes: H04L 1/08 by repeating transmission, e.g. Verdan system H04L1/1858 and H04L1/189 take precedence
• CPC Class Codes: H04L 1/22 using redundant apparatus to increase reliability
• CPC Class Codes: H04L 2001/0096 Channel splitting in point-to-point links
• CPC Class Codes: H04L 63/0227 Filtering policies mail message filtering H04L51/212
• CPC Class Codes: H04L 63/1483 service impersonation, e.g. phishing, pharming or web spoofing detection of rogue wireless access points H04W12/12

Abstract

An example embodiment includes a first, second, and third subsystem, each in different locations, where the first subsystem receives a request to deliver data to the third subsystem, sends a first subset of the data to the second subsystem, and sends, through first nodes, a first data stream containing a second subset of the data different from the first subset to the third subsystem. The second subsystem receives the first subset from the first subsystem, and sends, through second nodes that differ from the first nodes, a second data stream containing the first subset to the third subsystem. Furthermore, the third subsystem receives the first and second data streams, determines that the first and second data streams, in combination, contain the data, builds a data set containing the data based on the first and second data streams, and sends the data set to a downstream component of the third subsystem.

Claims

1. A system, comprising:

a first subsystem located in a first location, a second subsystem located in a second location, and a third subsystem located in a third location, wherein the first, second, and third locations correspond to different geographical locations and wherein;

the first subsystem comprises a first analytics engine and a first delivery engine, the first analytics engine configured to;

receive a request to deliver data to the third subsystem, the data comprising a plurality of packets; and

inform the first delivery engine of the request;

the first delivery engine configured to;

send a first subset of the plurality of packets to the second subsystem; and

send, through a first combination of nodes, a first data stream to the third subsystem, the first data stream comprising a second subset of the plurality of packets, wherein the second subset of the plurality of packets is different from the first subset of the plurality of packets;

the second subsystem comprises a second analytics engine and a second delivery engine, the second analytics engine configured to;

receive the first subset of the plurality of packets from the first subsystem; and

inform the second delivery engine to deliver the first subset of the plurality of packets to the third subsystem;

the second delivery engine configured to;

send, through a second combination of nodes that differ from the first combination of nodes, a second data stream to the third subsystem, the second data stream comprising the first subset of the plurality of packets;

the third subsystem comprising a data stream processor, the data stream processor configured to;

receive the first and second data streams;

determine that the first and second data streams, in combination, comprise each of the plurality of packets;

build a data set based on the first and second data streams, wherein the data set comprises the plurality of packets; and

send the data set to a downstream component of the third subsystem.

2. The system of claim 1, wherein the data comprises a cloud object.

3. The system of claim 1, wherein the analytics engine is further configured to determine that the data is to be sent in parallel, such that the first subset of the plurality of packets is to be sent from the second subsystem and the second subset of the plurality of packets is to be sent from the first subsystem.

4. The system of claim 1, wherein the data stream processor is further configured to discard at least some packets from one of the first data stream and the second data stream, wherein the at least some packet are packets that are common to both the first data stream and the second data stream.

5. The system of claim 1, wherein the data stream processor is further configured to build the data set based on one or more rebuilding rules.

6. The system of claim 5, wherein the one or more rebuilding rules are received by the data stream processor from the downstream component of the third subsystem.

7. The system of claim 5, wherein the one or more rebuilding rules are received by the data stream processor from an entity that is different from any entity operating at least one of the first subsystem, the second subsystem, and the third subsystem.

8. A front-end system, comprising:

a data receiving engine configured to;

receive, from a first subsystem, a first data stream sent to a third subsystem, wherein the first data stream comprises a first subset of data comprising a plurality of packets;

receive, from a second subsystem that is in a different geographical location than the first subsystem, a second data stream sent to the third subsystem, wherein the second data stream comprises a second subset of the data, wherein the second subset of the data is different from the first subset of the data; and

send the first and second data streams to a data stream processor; and

the data stream processor configured to;

receive the first and second data streams;

determine that the first and second data streams, in combination, comprise each of the plurality of packets;

build a data set based on the first and second data streams, wherein the data set comprises the plurality of packets; and

send the data set to a downstream component of the third subsystem.

9. The system of claim 8, wherein the data comprises a cloud object.

10. The system of claim 8, wherein the data stream processor is further configured to discard at least some packets from one of the first data stream and the second data stream.

11. The system of claim 8, wherein the data stream processor is further configured to build the data set based on one or more rebuilding rules.

12. The system of claim 11, wherein the one or more rebuilding rules are received by the data stream processor from the downstream component of the third subsystem.

13. The system of claim 11, wherein the one or more rebuilding rules are received by the data stream processor from an entity that is different from any entity operating at least one of the first subsystem, the second subsystem, and the third subsystem.

14. A method, comprising:

receiving, by a first subsystem, a request to deliver data to a third subsystem, the data comprising a plurality of packets; and

sending, by the first subsystem, a first subset of the plurality of packets to a second subsystem;

sending, by the first subsystem, through a first combination of nodes, a first data stream to the third subsystem, the first data stream comprising a second subset of the plurality of packets, wherein the second subset of the plurality of packets is different from the first subset of the plurality of packets;

receiving, by the second subsystem, the first subset of the plurality of packets from the first subsystem;

sending, by the second subsystem, through a second combination of nodes that differ from the first combination of nodes, a second data stream to the third subsystem, the second data stream comprising the first subset of the plurality of packets;

receiving, by the third subsystem, the first and second data streams;

determining, by the third subsystem, that the first and second data streams, in combination, comprise each of the plurality of packets;

building, by the third subsystem, a data set based on the first and second data streams, wherein the data set comprises the plurality of packets; and

sending, by the third subsystem, the data set to a downstream component of the third subsystem;

wherein the first subsystem is located in a first location, the second subsystem located in a second location, and the third subsystem located in a third location, wherein the first, second, and third locations correspond to different geographical locations.

15. The method of claim 14, wherein the data comprises a cloud object.

16. The method of claim 14, further comprising determining, by the first subsystem, that the data is to be sent in parallel, such that the first subset of the plurality of packets is to be sent from the second subsystem and the second subset of the plurality of packets is to be sent from the first subsystem.

17. The method of claim 14, further comprising discarding, by the third subsystem, at least some packets from one of the first data stream and the second data stream, wherein the at least some packet are packets that are common to both the first data stream and the second data stream.

18. The method of claim 14, further comprising building the data set based on one or more rebuilding rules.

19. The method of claim 18, wherein the one or more rebuilding rules are received by the data stream processor from the downstream component of the third subsystem.

20. The method of claim 18, wherein the one or more rebuilding rules are received by the data stream processor from an entity that is different from any entity operating at least one of the first subsystem, the second subsystem, and the third subsystem.