HIGH SPEED PARALLEL DATA EXCHANGE WITH RECEIVER SIDE DATA HANDLING

• US 20120079001A1
• Filed: 09/27/2010
• Published: 03/29/2012
• Est. Priority Date: 09/27/2010
• Status: Active Grant

• Current Assignee: Z124 LLC (Flexis)
• Original Assignee: Flextronics Innovative Development Limited (Flextronics International Limited)
• Inventors: Chincisan, Octavian
• Granted Patent: US 8,788,576 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: H04L 12/40013 Details regarding a bus controller

Abstract

Systems and methods for transfer of data including establishing two separate connections, the two separate connections including a high speed connection and a high integrity connection. Blocks of data are exchanged over the high speed connection while the high integrity connection facilitates communication of descriptor data regarding data received over the high speed connection. As such, the data transfer speed of the high speed connection is utilized while communication via the high integrity connection allows for data reliability features not provided by the high speed connection. The systems and methods may include receiver side data handling such that data received chronologically out of order may be ordered at the receiver.

Claims

1. A method of writing data received at a destination device from a source device into a memory at the destination device, comprising:

receiving a descriptor at the destination device from the source device, the descriptor including information regarding blocks of data transferred from the source device to the destination device, wherein the descriptor is received via a high reliability connection and the data is obtained via a high speed connection;

determining, at least partially based on the descriptor, a corresponding location in memory to which each block of data received is to be written.

2. The method of claim 1, wherein the determining further includes calculating an offset from a known location in memory for each block of data at least partially based the identity of the block.

3. The method of claim 1, wherein a plurality of blocks are substantially simultaneously received at the destination device and the plurality of blocks are non-adjacent.

4. The method of claim 3, wherein the non-adjacent blocks are written to memory at corresponding non-adjacent locations thereof based at least partially on the identity of each of the non-adjacent blocks at least partially as determined by the descriptor.

5. The method of claim 4, wherein the non-adjacent blocks each belong to a different one of at least two portions of blocks and each of said at least two portions of blocks include a corresponding descriptor.

6. The method according to claim 1, wherein the at least two portions of blocks comprise part of a file.

7. The method according to claim 6, wherein the descriptor includes bits, and each bit corresponds to a different one of the plurality of blocks.

8. The method according to claim 7, wherein the method further comprises toggling at least one bit in response to receipt of a corresponding block of the first portion at the destination device.

9. The method according to claim 8, further comprising transmitting the descriptor having toggled bits to the source device via the high integrity connection.

10. The method according to claim 1, wherein the at least one high speed connection employs a User Datagram Protocol (UDP).

11. The method according to claim 10, wherein the at least one high integrity connection employs a Transmission Control Protocol (TCP).

12. The method according to claim 1, wherein the source device is a server and the destination device is a client device.

13. The method according to claim 12, wherein the client device is a handheld computing device.

14. The method according to claim 1, wherein the source device and the destination device are both servers.

15. The method according to claim 1, wherein the method is initiated by the source device.

16. The method according to claim 1, wherein the method is initiated by the destination device.