Secure data communication system
View Patent ↗The description relates to a system designed to protect data exchange involved with the use of cloud computing infrastructures by services and individuals. The system is designed so that a cloud resource and its middleware access points are protected in transferring data among themselves and end users using a system designed to spread the data and then reassemble the data.
1. A method for secure data communication, the method comprising:
configuring a data file for transmission between a cloud computing architecture and at least one client device by dividing the data file into a plurality of fragments and storing the plurality of fragments on a plurality of data transfer servers, wherein each of the data transfer servers is configured to store a respective one of the fragments from among the plurality of fragments, wherein each respective fragment is different from fragments stored in the other data transfer servers, such that when any one of the data transfer servers is unavailable, the client device is unable to reassemble the data file; and
transmitting the divided data fragments to a client device for reassembly at the client device, the transmission of the divided data fragments being accomplished using the plurality of data transfer servers, each data transfer server having identifying characteristics that are not related to the other data transfer server(s).
2. The method recited in claim 1 , wherein configuring the data file comprises dividing the data file into two pieces.
3. The method recited in claim 1 , wherein each of the plurality of fragments is stored on a different data transfer server.
4. The method recited in claim 1 , wherein the identifying characteristics of the data transfer servers comprises an Internet Protocol (IP) address for each data transfer server, and wherein each data transfer server has an IP address that is unrelated to the IP addresses of the other data transfer servers.
5. The method recited in claim 4 , wherein proxy servers are used to provide the different IP addresses for each data transfer server.
6. The method recited in claim 1 , wherein the data file is divided into fragments based on an underlying file format of the data file.
7. The method recited in claim 1 , wherein transmitting the divided data fragments comprises transmitting a single data fragment over each of a plurality of data transfer servers such that each data transfer server transmits one of the divided data fragments.
8. The method recited in claim 1 , wherein configuring the data file further comprises dividing the data file into fragments using a splitter component that is compatible with a joiner component such that the joiner component is operative to reassemble data fragments divided by the splitter component.
9. The method recited in claim 1 , wherein the splitter component is resident at a middleware server and the joiner component is resident at the client device.
10. The method recited in claim 1 , wherein the splitter component is resident at the client device and the joiner component is resident at a middleware server.
11. A non-transitory computer-readable medium encoded with computer-executable instructions for secure data communication, the instructions comprising:
configuring a data file for transmission between a cloud computing architecture and at least one client device by dividing the data file into a plurality of fragments; and
transmitting the divided data plurality of fragments to a client device for reassembly at the client device, the transmission of the divided plurality of fragments being accomplished using a plurality of data transfer servers, each data transfer server having identifying characteristics that are not related to the other data transfer server(s) and each data transfer server configured to store a respective one of the fragments from among the plurality of fragments, wherein each respective fragment is different from fragments stored in the other data transfer servers, such that when any one of the data transfer servers is unavailable, the client device is unable to reassemble the data file.
12. The non-transitory computer-readable medium recited in claim 11 , wherein configuring the data file comprises dividing the data file into two pieces.
13. The non-transitory computer-readable medium recited in claim 11 , wherein each of the plurality of fragments is stored on a different data transfer server.
14. The non-transitory computer-readable medium recited in claim 11 , wherein the identifying characteristics of the data transfer servers comprises an Internet Protocol (IP) address for each data transfer server, and wherein each data transfer server has an IP address that is unrelated to the IP addresses of the other data transfer servers.
15. The non-transitory computer-readable medium recited in claim 14 , wherein proxy servers are used to provide the different IP addresses for each data transfer server.
16. The non-transitory computer-readable medium recited in claim 11 , wherein the data file is divided into fragments based on an underlying file format of the data file.
17. The non-transitory computer-readable medium recited in claim 11 , wherein transmitting the divided data fragments comprises transmitting a single data fragment over each of a plurality of data transfer servers such that each data transfer server transmits one of the divided data fragments.
18. The non-transitory computer-readable medium recited in claim 11 , wherein configuring the data file further comprises dividing the data file into fragments using a splitter component that is compatible with a joiner component such that the joiner component is operative to reassemble data fragments divided by the splitter component.
19. The non-transitory computer-readable medium recited in claim 11 , wherein the splitter component is resident at a middleware server and the joiner component is resident at the client device.
20. The non-transitory computer-readable medium recited in claim 11 , wherein the splitter component is resident at the client device and the joiner component is resident at a middleware server.