Peer data transfer orchestration

• US 7,490,140 B2
• Filed: 05/12/2005
• Issued: 02/10/2009
• Est. Priority Date: 05/12/2005
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Goodman, Brian D., Rooney, John W.
• Primary Examiner(s): Pwu; Jeffrey
• Assistant Examiner(s): Sciacca; Scott M
• Application Number:
  US11/128,100
• Publication Number:
  US 20060259573A1
• Time in Patent Office: 1,370 Days
• Field of Search: 709/203, 709/204, 709217-219, 709/226, 709/227, 709/231, 709/238
• US Class Current: 709/219
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/108 characterised by resources being split in blocks or fragments
• CPC Class Codes: H04L 67/1091 Interfacing with client-server systems or between P2P systems

Abstract

A system, method, service, and program storage device implementing a method of transferring data, wherein the method comprises arranging a plurality of peer systems in a computer network; coupling at least one data server preferably comprises data to the plurality of peer systems, wherein the plurality of peer systems comprise a first peer system and at least one second peer system; the first peer system instructing the at least one second peer system to collaboratively transfer the data from the at least one data server to the first peer system; and the at least one second peer system transferring the data from the at least one data server to the first peer system. The plurality of peer systems is preferably grid enabled.

Claims

1. A method of orchestrating peer data transfer, said method comprising:

arranging a first peer system and a plurality of second peer systems in a computer local area network (LAN), said first peer system being a destination of said orchestrated peer data transfer;

coupling to each of said plurality of second peer systems, at least one data server that stores target data to be transferred to said first peer system,

wherein said plurality of second peer systems is grid enabled, and

wherein communication between said first peer system and said plurality of second peer systems occurs through web services;

using, by said first peer system, a peer directory to connect said first peer and said plurality of second peer systems to one another;

identifying, by said first peer system, data resources and transfer bandwidth capabilities of each of said plurality of second peer system systems;

creating, by said first peer system, an orchestrated peer data transfer plan,

wherein said orchestrated peer data transfer plan comprises a uniform resource identifier (URI) to said target data, a peer identifier, and a byte range associated with each of said plurality of second peer system systems,

wherein said byte range identifies a requested portion of said target data which each second peer system of the plurality of second peer systems is requested to transfer, and

wherein said first peer system sends—

said data transfer plan to each of said plurality of second peer systems and each of said plurality of second peer systems provides a status message to said first peer system;

upon receiving said data transfer plan, said plurality of second peer systems collaboratively retrieving the requested portion of said target data from said at least one data server;

transferring, by each of said plurality of second systems, the requested portion of said target data to said first peer system; and

reconstituting, by said first peer system, said data transferred by said orchestrated peer data transfer plan.