IP Library Granted Patent US 8,886,716
Granted Patent B2
US 8,886,716 · App. 13/351,183 · Granted Nov 11, 2014

Cloud-based de-duplication

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,886,716
App. No.
13/351,183
Granted
Nov 11, 2014
Kind
B2
Abstract

Example apparatus, methods, and computers support cloud-based de-duplication with transport layer transparency. One example apparatus includes a processor, a memory, and an interface to connect the processor, memory, and a set of logics. The set of logics includes a hardware identification logic for identifying networking hardware used by or available to the apparatus to interact with a cloud-based computing environment and a protocol identification logic for identifying a protocol used by or available to the apparatus to communicate messages for the cloud-based computing environment through the networking hardware. The set of logics also includes a de-duplication preparation logic for preparing a message to carry data to be de-duplicated and metadata concerning the data to be de-duplicated. The message is to be provided to the cloud-based computing environment through the networking hardware according to the protocol.

Claims (49)

1. An apparatus, comprising:

a processor;

a memory; and

an interface to connect the processor, the memory, and a set of logics, the set of logics comprising:

a hardware identification logic configured to identify networking hardware supported by the apparatus to interact with a cloud-based computing environment through a computer network;

a protocol identification logic configured to identify a protocol supported by the apparatus to communicate messages for the cloud-based computing environment through the networking hardware, the protocol comprising one or more of, a set of rules for communicating over the computer network, a set of procedure calls available for communicating over the computer network, and a set of application programming interfaces available for communicating over the computer network; and

a de-duplication preparation logic configured to prepare a collaborative data de-duplication message to carry one or more of, data to be de-duplicated, and metadata concerning the data to be de-duplicated, where the collaborative data de-duplication message is to be provided to the cloud-based computing environment through the networking hardware according to the protocol,

where the de-duplication preparation logic is configured to place the data to be de-duplicated in a first logical section of the message and to place the metadata concerning the data to be de-duplicated in a second logical section of the message,

where the data to be de-duplicated comprises one or more of, a sub-block of data, an identifier of a sub-block of data, a hash of a sub-block of data, and a sample of a sub-block of data, and

where the metadata concerning the data to be de-duplicated comprises one or more of, a boundary, a boundary character, a boundary algorithm identifier, a hash, a hash algorithm identifier, a sample, a sample algorithm identifier, and a dialect.

2. The apparatus of claim 1 ,

where the protocol identification logic is configured to identify the protocol as being one or more of, simple object access protocol (SOAP) compliant, representational state transfer (REST) compliant, hypertext transfer protocol (HTTP) compliant, and extensible markup language (XML)-compliant;

where the de-duplication preparation logic is configured to prepare the message to be one or more of, SOAP-compliant, REST-compliant, HTTP-compliant, and XML-compliant, and

where the de-duplication preparation logic is configured to place the metadata in one or more XML attributes associated with the message.

3. The apparatus of claim 1 , the set of logics comprising:

a de-duplication logic configured to sub-divide a block of data into one or more subblocks of data according to a chunking protocol and to compute de-duplication tokens associated with the one or more sub-blocks of data according to a tokenization protocol, and where the metadata concerning the data to be de-duplicated comprises one or more of, an identifier of the chunking protocol, and an identifier of the tokenization protocol.

4. The apparatus of claim 1 , the set of logics comprising:

a receipt logic configured to receive a message from the cloud-based computing environment through the networking hardware according to the protocol, and to identify the message as a de-duplication message.

5. A method for controlling a client apparatus, comprising:

controlling the client apparatus to identify an interface supported by the client apparatus to interact with a cloud-based computing environment;

controlling the client apparatus to identify a protocol supported by the client apparatus to communicate through the interface;

controlling the client apparatus to configure a de-duplication packet that conforms to the protocol and to the interface; and

controlling the client apparatus to provide the de-duplication packet to the cloud-based computing environment in a transport transparent manner through the interface according to the protocol,

where configuring the de-duplication packet includes placing data to be de-duplicated in a first logical section of the packet and placing metadata concerning the data to be de-duplicated in a second logical section of the packet,

where the data to be de-duplicated comprises one or more of, a sub-block of data, an identifier of a sub-block of data, a hash of a sub-block of data, and a sample of a sub-block of data, and

where the metadata concerning the data to be de-duplicated comprises one or more of, a boundary, a boundary character, a boundary algorithm identifier, a hash, a hash algorithm identifier, a sample, a sample algorithm identifier, and a dialect.

6. The method of claim 5 , where the de-duplication data comprises one or more of, data to be de-duplicated, an identifier of data to be de-duplicated, a hash of data to be de-duplicated, and a sample of data to be de-duplicated.

7. The method of claim 5 , where the de-duplication metadata identifies the de-duplication packet as a de-duplication packet.

8. The method of claim 5 , where the de-duplication metadata identifies one or more of, what portion of collaborative de-duplicating the client is performing, and what portion of collaborative de-duplicating the client wants to perform.

9. The method of claim 5 , where the de-duplication metadata identifies one or more of, a boundary, a boundary algorithm, a hash, a hash algorithm, an identifier, an identifier algorithm, a sample, a sample algorithm, and a de-duplication dialect.

10. The method of claim 5 , where the second portion comprises one or more extensible mark up language (XML) attributes.

11. The method of claim 5 , where the interface and protocol are representational state transfer (REST) compliant.

12. The method of claim 5 , where the interface and protocol are one or more of, HTTP compliant, and XML compliant.

13. The method of claim 5 , the method being transparent to a transport layer associated with one or more of, the interface, and the protocol.

14. The method of claim 13 , where being transparent to a transport layer comprises having the packet pass through the interface according to the protocol without generating an interface exception and without generating a protocol exception.

15. The method of claim 5 , comprising:

controlling the client apparatus to sub-divide a block of data on the client apparatus into one or more sub-blocks of data according to a de-duplication sub-dividing protocol, and where the de-duplication metadata comprises a de-duplication sub-dividing protocol identifier.

16. The method of claim 15 , comprising:

controlling the client apparatus to hash a sub-block of data according to a de-duplication hashing protocol, and where the de-duplication metadata comprises a de-duplication hashing protocol identifier.

17. The method of claim 5 , comprising:

controlling the client apparatus to identify a received packet as a de-duplication packet, the received packet being received from the cloud-based computing environment through the interface according to the protocol.

18. The method of claim 17 , comprising controlling the client apparatus to selectively transmit an additional related message as a function of metadata included in the received packet.

19. The method of claim 18 , where the additional related message includes data to be de-duplicated.

20. A method, comprising:

controlling a client apparatus to identify an interface used by the client apparatus to interact with a server in a cloud-based computing environment; and

controlling the client apparatus to configure a transport layer transparent de-duplication packet to be used in cloud-based collaborative data de-duplication to conform to the interface,

where configuring the transport layer transparent de-duplication packet includes placing data to be de-duplicated in a first logical section of the packet and placing metadata concerning the data to be de-duplicated in a second logical section of the packet,

where the data to be de-duplicated comprises one or more of, a sub-block of data, an identifier of a sub-block of data, a hash of a sub-block of data, and a sample of a sub-block of data, and

where the metadata concerning the data to be de-duplicated comprises one or more of, a boundary, a boundary character, a boundary algorithm identifier, a hash, a hash algorithm identifier, a sample, a sample algorithm identifier, and a dialect.

Assignments (13)
TERMINATION AND RELEASE OF INTELLECTUAL PROPERTY SECURITY AGREEMENT AT REEL/FRAME NO. 40473/0378 Recorded Oct 8, 2025
From: PNC BANK, NATIONAL ASSOCIATION, AS AGENT
To: QUANTUM CORPORATION
Reel/Frame 073061/0454 →
TERMINATION AND RELEASE OF AMENDED AND RESTATED INTELLECTUAL PROPERTY SECURITY AGREEMENT AT REEL/FRAME NO. 48029/0525 Recorded Aug 19, 2025
From: PNC BANK, NATIONAL ASSOCIATION, AS AGENT
To: QUANTUM CORPORATION
Reel/Frame 072542/0594 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 24, 2025
From: BLUE TORCH FINANCE LLC, AS AGENT FOR THE SECURED PARTIES
To: ALTER DOMUS (US) LLC, AS AGENT FOR THE SECURED PARTIES
Reel/Frame 071019/0850 →
RELEASE OF SECURITY INTEREST Recorded Aug 10, 2021
From: U.S. BANK NATIONAL ASSOCIATION
To: QUANTUM CORPORATION; QUANTUM LTO HOLDINGS, LLC
Reel/Frame 057142/0252 →
SECURITY INTEREST Recorded Aug 5, 2021
From: QUANTUM CORPORATION; QUANTUM LTO HOLDINGS, LLC
To: BLUE TORCH FINANCE LLC, AS AGENT
Reel/Frame 057107/0001 →
SECURITY INTEREST Recorded Jan 8, 2019
From: QUANTUM CORPORATION
To: PNC BANK, NATIONAL ASSOCIATION
Reel/Frame 048029/0525 →
RELEASE OF SECURITY INTEREST Recorded Dec 27, 2018
From: TCW ASSET MANAGEMENT COMPANY LLC, AS AGENT
To: QUANTUM CORPORATION
Reel/Frame 047988/0642 →
SECURITY INTEREST Recorded Dec 27, 2018
From: QUANTUM CORPORATION, AS GRANTOR; QUANTUM LTO HOLDINGS, LLC, AS GRANTOR
To: U.S. BANK NATIONAL ASSOCIATION, AS AGENT
Reel/Frame 049153/0518 →
SECURITY INTEREST Recorded Oct 25, 2016
From: QUANTUM CORPORATION
To: PNC BANK, NATIONAL ASSOCIATION
Reel/Frame 040473/0378 →
RELEASE OF SECURITY INTEREST Recorded Oct 25, 2016
From: WELLS FARGO CAPITAL FINANCE, LLC, AS AGENT
To: QUANTUM CORPORATION
Reel/Frame 040474/0079 →
SECURITY INTEREST Recorded Oct 21, 2016
From: QUANTUM CORPORATION
To: TCW ASSET MANAGEMENT COMPANY LLC, AS AGENT
Reel/Frame 040451/0183 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 7, 2016
From: TOFANO, JEFFREY VINCENT
To: QUANTUM CORPORATION
Reel/Frame 039963/0054 →
SECURITY AGREEMENT Recorded Mar 31, 2012
From: QUANTUM CORPORATION
To: WELLS FARGO CAPITAL FINANCE, LLC, AS AGENT
Reel/Frame 027967/0914 →