Copy offload for disparate offload providers

• US 9,071,585 B2
• Filed: 12/12/2012
• Issued: 06/30/2015
• Est. Priority Date: 12/12/2012
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Green, Dustin L.
• Primary Examiner(s): WASEL, MOHAMED A
• Application Number:
  US13/711,637
• Publication Number:
  US 20140164571A1
• Time in Patent Office: 930 Days
• Field of Search: 709217-219
• US Class Current: 1/1
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70

Abstract

Aspects of the subject matter described herein relate to offload technology. In aspects, a source offload provider may transfer bulk data to a destination offload provider even if the offload providers are different and independent from each other and have no prior knowledge of each other. In preparation for transferring bulk data, trust may be extended to the offload providers. After authentication, the offload providers may transfer all or a portion of the bulk data over a secure channel without the data traversing the initiator of the transfer.

Claims

1. A method implemented at least in part by a computer, the method comprising:

sending, by an initiator, a request for a token that represents immutable data as long as the token is valid;

in response to the request, receiving the token from a source offload provider;

providing the token to a destination offload provider with an instruction to copy at least a portion of the immutable data from the source offload provider to the destination offload provider, the source offload provider and the destination offload provider being independent of each other; and

extending trust of the initiator to the source offload provider and to the destination offload provider such that the source offload provider trusts the destination offload provider as the source offload provider trusts the initiator and such that the destination offload provider trusts the source offload provider as the destination offload provider trusts the initiator.

2. The method of claim 1, further comprising receiving a secret from the source offload provider in response to the request for a token, the secret to be used in the extending trust of the initiator to the source offload provider and to the destination offload provider.

3. The method of claim 1, further comprising sending, by the initiator, a secret to the source offload provider in conjunction with sending the request for the token, the secret to be used in the extending trust of the initiator to the source offload provider and to the destination offload provider.

4. The method of claim 1, further comprising providing a Kchannel key with which to secure a communications channel between the source offload provider and the destination offload provider.

5. The method of claim 4, further comprising generating the Kchannel key by the initiator.

6. The method of claim 5, further comprising generating an additional Kchannel key for each additional destination offload provider to which data represented by the token is to be copied.

7. The method of claim 4, wherein the Kchannel key is generated by the source offload provider.

8. The method of claim 1, wherein providing the token to a destination offload provider comprises providing the token to an offload write initiator that, in response, sends the token to a destination storage stack to provide to the destination offload provider.

9. The method of claim 1, further comprising providing a network address of the source offload provider to the destination offload provider by embedding the network address in the token.

10. The method of claim 1, further comprising providing a network address of the source offload provider to the destination offload provider by embedding in the token a lookup key usable to find the network address.

11. In a computing environment, a system, comprising:

a destination offload provider comprised of one or more computers and one or more storage devices, the destination offload provider configured to execute actions indicated by computer code, the actions comprising;

receiving, from an initiator, a token that represents immutable data as long as the token is valid, the token generated by a source offload provider that ensures immutability of the data as long as the token is valid, the destination offload provider and the source offload provider being independent of each other; and

receiving, from the initiator, trust data, the trust data for extending trust of the initiator to the source offload provider and to the destination offload provider such that the source offload provider trusts the destination offload provider as the source offload provider trusts the initiator and such that the destination offload provider trusts the source offload provider as the destination offload provider trusts the initiator.

12. The system of claim 11, wherein the destination offload provider receives the token and the trust data in a single message from the initiator.

13. The system of claim 11, wherein the destination offload provider is further configured to execute additional actions indicated by computer code, the additional actions comprising receiving a Kchannel key with which to secure a communications channel between the destination offload provider and the source offload provider.

14. The system of claim 11, wherein the destination offload provider is further configured to execute additional actions indicated by computer code, the additional actions comprising authenticating the source offload provider using the secret.

15. The system of claim 11, wherein the destination offload provider is further configured to execute additional actions indicated by computer code, the additional actions comprising:

receiving a network address of the source offload provider; and

using the network address to establish a communication channel with the source offload provider.

16. The system of claim 11, further comprising the source offload provider configured to authenticate the destination offload provider via an operation that uses the secret.

17. A computer storage device having computer-executable instructions, which when executed perform actions, comprising:

receiving, from an initiator, a request for a token that represents immutable data as long as the token is valid; and

in response to the request, from a source offload provider, sending the token to be provided to a destination offload provider with an instruction and trust data, the instruction to copy at least a portion of the immutable data from the source offload provider to the destination offload provider, the source offload provider and the destination offload provider being independent of each other, the trust data for extending trust of the initiator to the source offload provider and to the destination offload provider such that the source offload provider trusts the destination offload provider as the source offload provider trusts the initiator and such that the destination offload provider trusts the source offload provider as the destination offload provider trusts the initiator.

18. The computer storage device of claim 17, further comprising generating the trust data by the source offload provider and providing the trust data to the initiator.

19. The computer storage device of claim 17, further comprising receiving the trust data from the destination offload provider and in response creating a secure channel with the destination offload provider.

20. The computer storage device of claim 17, further comprising receiving a network address of the destination offload provider and initiating, by the source offload provider, establishment of a communication channel with the destination offload provider.