IP Library Granted Patent US 8,195,629
Granted Patent B2
US 8,195,629 · App. 12/970,143 · Granted Jun 5, 2012

Establishing parse scope

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,195,629
App. No.
12/970,143
Granted
Jun 5, 2012
Kind
B2
Abstract

Example apparatus, methods, and computers control establishing a shared parse scope between two computers that intend to be involved in a shared de-duplication action. One example method includes, upon determining that a first de-duplication logic and a second de-duplication logic are to participate in a shared de-duplication action for an object, controlling the first de-duplication logic to establish a shared parse scope with the second de-duplication logic. Establishing the shared parse scope may include negotiations between the computers, where the negotiations transfer dialect information. The dialect information may take the form of rules. The method may also include persisting the shared parse scope.

Claims (54)

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 parse scope logic configured to determine a set of de-duplication rules shared between the apparatus and a second, different apparatus by transmitting de-duplication rule data to the second apparatus and by receiving de-duplication rule data from the second apparatus, where the apparatus and the second apparatus are both part of a de-duplication environment in which an object is to be de-duplicated; and

a de-duplication logic configured to de-duplicate the object as controlled by the set of shared de-duplication rules, where the set of de-duplication rules controls how the object is to be subdivided, and how the object is to be hashed.

2. The apparatus of claim 1 , where de-duplication rule data describes one or more of, how a layered parser is to be configured, and an acknowledgement of agreement on a de-duplication rule.

3. The apparatus of claim 1 , where the parse scope logic is configured to nest the de-duplication rule by data reducing the de-duplication rule data.

4. The apparatus of claim 1 , comprising a persistence logic configured to persist the set of de-duplication rules in one or more of, the apparatus, the second apparatus, and the object.

5. The apparatus of claim 4 , where the persistence logic is configured to selectively control the second apparatus to accept a set of de-duplication rules associated with the apparatus, where the persistence logic is configured to selectively control the apparatus to accept a set of de-duplication rules associated with the second apparatus, and where the persistence logic is configured to selectively control both the apparatus and the second apparatus to accept a set of de-duplication rules previously negotiated for the object.

6. A computer readable medium storing computer executable instructions that when executed by a computer control the computer to perform a method, the method comprising:

upon determining that a first de-duplication logic and a second de-duplication logic are to participate in a shared de-duplication action for an object,

controlling the first de-duplication logic to establish a shared parse scope with the second de-duplication logic by:

controlling the first de-duplication logic to provide dialect data to the second de-duplication logic, the dialect data comprising one or more of, a rule, a hash of the rule, a rule identifier, a plurality of rules, a hash of the plurality of rules, and a plurality of rule identifiers, where the rule comprises one or more of:

first information about a context associated with an object to be de-duplicated;

second information identifying a previously negotiated shared parse scope associated with an object;

third information identifying how an object is to be parsed;

fourth information identifying an action to be performed after an object is parsed;

fifth information identifying one or more of, a delta hash function, and a delta storage schema for an object; and

sixth information identifying balancing rules for balancing performance and reduction;

and by:

receiving feedback data from the second de-duplication logic, the feedback data being produced in response to the dialect data, the feedback data comprising one or more of,

an acceptance notification that identifies that the second de-duplication logic is aware of the dialect identified by the dialect data and agrees to use the dialect identified by the dialect data;

an update notification that identifies that the second de-duplication logic was not aware of the dialect identified by the dialect data, that the second de-duplication logic agrees to use the dialect identified by the dialect data, and that the second de-duplication logic has been updated as a function of receiving the dialect data;

a counteroffer notification comprising an alternative dialect data, where the alternative dialect data comprises one or more of, a rule, a hash of a rule, a rule identifier, a plurality of rules, a hash of the plurality of roles, and a plurality of rule identifiers, where the alternative dialect data is associated with an alternate dialect in use by the second de-duplication logic:

a request notification that identifies a hash of an item in the dialect for which a corresponding actual item is requested by the second de-duplication logic: and

an acknowledgement notification that identifies that the second de-duplication logic will participate in the shared de-duplication action as controlled by a persisted parse scope previously negotiated for the object:

persisting the shared parse scope, and

controlling the first de-duplication logic to perform a portion of the shared de-duplication action on the object as controlled by the shared parse scope.

7. The computer readable medium of claim 6 , the method comprising:

upon receiving an acknowledgement notification, establishing the persisted parse scope as the shared parse scope;

upon receiving an acceptance notification, establishing the dialect as the shared parse scope;

upon receiving an update notification, establishing the dialect as the shared parse scope; and

upon receiving a request notification, providing the corresponding actual item requested by the second de-duplication logic.

8. The computer readable medium of claim 7 , the method comprising:

upon receiving a counteroffer notification:

providing a dominance notification that identifies that the first de-duplication logic and the second de-duplication logic are to use the dialect identified by the dialect data;

providing an acceptance notification that identifies that the first de-duplication logic is aware of the alternate dialect identified by the alternate dialect data and agrees to use the alternate dialect identified by the alternate dialect data;

providing an update notification that identifies that the first de-duplication logic was not aware of the alternate dialect identified by the alternate dialect data, that the first de-duplication logic agrees to use the alternate dialect identified by the alternate dialect data, and that the first de-duplication logic has been updated as a function of receiving the alternate dialect data;

providing a request notification that identifies a hash of a rule associated with the alternate dialect for which a corresponding actual rule is requested by the first de-duplication logic; and

providing an acknowledgement notification that identifies that the first de-duplication logic will participate in the shared de-duplication action as controlled by a persisted parse scope previously negotiated for the object.

9. The computer readable medium of claim 6 , where the shared de-duplication action comprises data reducing the object from a first non-reduced state to a second reduced state.

10. The computer readable medium of claim 9 , the method comprising persisting the shared parse scope in one or more of, the object in the first non-reduced state, the object in the second reduced state, the first de-duplication logic, and the second de-duplication logic.

11. The computer readable medium of claim 10 , where persisting the shared parse scope comprises storing one or more of, a rule, a hash of a rule, a plurality of rules, a hash of the plurality of rules, a parse parameter, and context data concerning parsing performed according to the shared parse scope, and where establishing the shared parse scope with the second de-duplication logic can be based, at least in part, on a hash of a persisted shared parse scope.

12. The computer readable medium of claim 6 , where the shared parse scope comprises one or more de-duplication rules.

13. The computer readable medium of claim 6 , where the third information comprises one or more of, partitioning parameters comprising fixed, variable, or delimiter based partitioning parameters, hash function identifiers, and parse layering order parameters, where the partitioning parameters can be configured at one or more of, a file scope level, an object scope level, and a sub-object scope level.

14. The computer readable medium of claim 6 , where the fourth information comprises one or more of, information concerning compressing a reduced object, information concerning encrypting a reduced object, information concerning verifying the existence of an object, and information concerning transmitting an object.

15. The computer readable medium of claim 6 , where the shared de-duplication action is a security related action that includes determining a hash without transmitting the object or adding the object to a persistent data de-duplication data store.

16. The computer readable medium of claim 6 , the method comprising controlling the first de-duplication logic and the second de-duplication logic to accept a dialect associated with a replication event, where the replication event comprises distribution of an updated parse scope comprising one or more of, a rule, a hash of a rule, a rule identifier, a plurality of rules, a hash of the plurality of rules, and a plurality of rule identifiers; and where the replication event occurs independent of an intended communication between de-duplication logics.

17. A computer, comprising:

a first component configured to negotiate a set of rules by which two de-duplication logics agree to be bound with respect to performing a de-duplication action on an object;

a second component configured to perform the de-duplication action as controlled by the set of rules; and

a third component configured to persist the set of rules to control future de-duplication actions associated with the object,

where the two de-duplication logics have available two or more different approaches for subdividing the object and for hashing the object, where the set of rules controls which of the two or more different approaches are to be used for subdividing the object and for hashing the object.

Assignments (13)
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Dec 18, 2025
From: QUANTUM CORPORATION
To: U.S. BANK TRUST COMPANY, NATIONAL ASSOCIATION, AS AGENT
Reel/Frame 074024/0084 →
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 →
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 →
RELEASE OF SECURITY INTEREST Recorded Dec 27, 2018
From: TCW ASSET MANAGEMENT COMPANY LLC, AS AGENT
To: QUANTUM CORPORATION
Reel/Frame 047988/0642 →
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 25, 2016
From: QUANTUM CORPORATION
To: PNC BANK, NATIONAL ASSOCIATION
Reel/Frame 040473/0378 →
SECURITY INTEREST Recorded Oct 21, 2016
From: QUANTUM CORPORATION
To: TCW ASSET MANAGEMENT COMPANY LLC, AS AGENT
Reel/Frame 040451/0183 →
SECURITY AGREEMENT Recorded Mar 31, 2012
From: QUANTUM CORPORATION
To: WELLS FARGO CAPITAL FINANCE, LLC, AS AGENT
Reel/Frame 027967/0914 →