IP Library Granted Patent US 9,158,799
Granted Patent B2
US 9,158,799 · App. 13/804,694 · Granted Oct 13, 2015

Storing and retrieving context sensitive data in a management system

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 9,158,799
App. No.
13/804,694
Granted
Oct 13, 2015
Kind
B2
Abstract

A management system may include a reconciliation engine configured to reconcile a first instance of a resource object from a first data provider and a second instance of the resource object from a second data provider to obtain a reconciled resource object, and store the first instance, and second instance, and the reconciled resource object in datasets. The management system may include a context sensitive query engine configured to receive a context-sensitive query including context information identifying a source originally providing context sensitive data associated with a context-sensitive attribute, and retrieve the context sensitive data from one or more of the datasets based on the context information.

Claims (55)

1. A management system comprising:

at least one processor;

a non-transitory computer-readable storage medium including instructions executable by the at least one processor, the instructions configured to implement,

a configuration management database configured to store data in a plurality of data partitions including a first provider data partition a second provider data partition and a tar et data partition;

a reconciliation engine configured to reconcile a first instance of a resource object from a first data provider and a second instance of the resource object from a second data provider to obtain a reconciled resource object having reconciled data, the first instance and the second instance sharing a common attribute, the common attribute being marked as a context-sensitive attribute, the context-sensitive attribute of the first instance having first provider-specific data specific to the first data provider, the context-sensitive attribute of the second instance having second provider-specific data specific to the second data provider, wherein the reconciliation engine, upon determining that the common attribute is marked as the context-sensitive attribute, is configured to apply a unique reconciliation rule to the first and second instances than what is normally applied to an object without the context-sensitive attribute,

the reconciliation engine configured store the first instance in the first provider data partition associated with the first data provider, the second instance in the second provider data partition associated with the second data provider, and the reconciled resource object in the target data partition; and

a context sensitive query engine configured to receive a query including a query parameter identifying data related to the context-sensitive attribute and context information identifying one of the first data provider and the second data provider, the context sensitive query engine configured to query at least one of the data partitions in response to the query, the context sensitive query engine configured to retrieve either the first provider-specific data or the second provider-specific data from the at least one data partition based on the context information.

2. The management system of claim 1 , wherein the first and second instances of the resource object and the reconciled resource object share a common key,

wherein the context sensitive query engine is configured to query the target data partition for the reconciled resource object having the query parameter and obtain the common key from the reconciled resource object,

wherein the context sensitive query engine is configured to query the first provider data partition for the first instance using the common key when the context information specifies the first data provider, and obtain the first provider-specific data associated with the context-sensitive attribute from the first instance,

wherein the context sensitive query engine is configured to query the second provider data partition for the second instance using the common key when the context information specifies the second data provider and obtain the second provider-specific data corresponding to the context-sensitive attribute from the second instance.

3. The management system of claim 2 , wherein the common key includes a reconciliation identifier.

4. The management system of claim 1 , wherein the reconciliation engine includes a context-sensitive merging unit configured to merge the first provider-specific data and the second provider-specific data to create the reconciled data for the reconciled resource object, the reconciled data including the first provider-specific data and the second provider-specific data.

5. The management system of claim 1 , wherein the reconciled data includes the first provider-specific data, the second provider-specific data, and default data corresponding to results of a reconciliation operation on the context-sensitive attribute.

6. The management system of claim 1 ,

wherein the context sensitive query engine is configured to query the target data partition for the reconciled resource object, and obtain the first provider-specific data from the reconciled data when the context information specifies the first data provider,

wherein the context sensitive query engine is configured to query the target data partition for the reconciled resource object, and obtain the second provider-specific data from the reconciled data when the context information specifies the second data provider.

7. The management system of claim 1 , wherein the reconciliation engine includes a merging unit configured to merge the first provider-specific data and the second provider-specific from the first instance and the second instance.

8. The management system of claim 1 , wherein the reconciled data includes only one of the first provider-specific data for the first data provider and the second provider-specific data for the second data provider.

9. The management system of claim 1 , wherein the context sensitive query engine is configured to query the target data partition for the reconciled resource object to obtain a reconciliation identifier corresponding to the reconciled resource object,

wherein the context sensitive query engine is configured to query the first provider data partition when-if the context information specifies the first data provider using the reconciliation identifier and obtain the first provider-specific data from the first instance,

wherein the context sensitive query engine is configured to query the second provider data partition when the context information specifies the second data provider using the reconciliation identifier and obtain the second provider-specific data from the second instance.

10. A non-transitory computer-readable medium storing instructions that when executed cause at least one processor to:

reconcile a first instance of a resource object from a first data provider and a second instance of the resource object from a second data provider to obtain a reconciled resource object having reconciled data, the first instance and the second instance sharing a common attribute, the common attribute being marked as a context-sensitive attribute, the context-sensitive attribute of the first instance having first provider-specific data specific to the first data provider, the context-sensitive attribute of the second instance having second provider-specific data specific to the second data provider, wherein upon determining that the common attribute is marked as the context-sensitive attribute, a unique reconciliation rule is applied to the first and second instances than what is normally applied to an object without the context-sensitive attribute;

store the first instance in a first provider data partition associated with the first data provider, the second instance in a second provider data partition associated with the second data provider, and the reconciled resource object in a target data partition;

receive a query including a query parameter identifying data related to the context-sensitive attribute and context information identifying one of the first data provider and the second data provider;

query at least one data partition among a plurality of data partitions in response to the query, the plurality of data partitions including the first provider data partition, the second provider data partition, and the target data partition; and

retrieve either the first provider-specific data or the second provider-specific data from the at least one data partition based on the context information.

11. The non-transitory computer-readable medium of claim 10 , wherein the first and second instances of the resource object and the reconciled resource object share a common key, wherein the instructions further include instructions to:

query the target data partition for the reconciled resource object corresponding to the query parameter and obtain the common key from the reconciled resource object;

query the first provider data partition for the first instance using the common key when the context information specifies the first data provider, and obtain the first provider-specific data from the first instance; and

query the second provider data partition for the second instance using the common key when the context information specifies the second data provider and obtain the second provider-specific data from the second instance.

12. The non-transitory computer-readable medium of claim 11 , wherein the common key includes a reconciliation identifier.

13. The non-transitory computer-readable medium of claim 10 , wherein the instructions to reconcile include instructions to:

merge the first provider-specific data and the second provider-specific data from the first instance and the second instance to create the reconciled data including the first provider-specific data for the first data provider, and the second provider-specific data for the second data provider.

14. The non-transitory computer-readable medium of claim 10 ,

wherein the reconciled data includes the first provider-specific data, the second provider-specific data, and default data corresponding to results of a reconciliation operation on the context-sensitive attribute.

15. The non-transitory computer-readable medium of claim 10 , wherein the instructions include instructions to:

query the target data partition for the reconciled resource object, and obtain the first provider-specific data from the reconciled data when the context information specifies the first data provider; and

query the target data partition for the reconciled resource object, and obtain the second provider-specific data from the reconciled data when the context information specifies the second data provider.

16. The non-transitory computer-readable medium of claim 10 , wherein the instructions to reconcile include instructions to:

merge the first provider-specific data and the second provider-specific data from the first instance and the second instance.

17. The non-transitory computer-readable medium of claim 10 , wherein the reconciled data includes only one of the first provider-specific data for the first data provider and the second provider-specific data for the second data provider.

18. The non-transitory computer-readable medium of claim 10 , wherein the instructions include instructions to:

query the target data partition for the reconciled resource object to obtain a reconciliation identifier corresponding to the reconciled resource object;

query the first provider data partition when the context information specifies the first data provider using the reconciliation identifier and obtain the first provider-specific data from the first instance; and

query the second provider data partition when the context information specifies the second data provider using the reconciliation identifier and obtain the second provider-specific data from the second instance.

19. A method comprising:

reconciling, by at least one processor, a first instance of a resource object from a first data provider and a second instance of the resource object from a second data provider to obtain a reconciled resource object having reconciled data, the first instance and the second instance sharing a common attribute, the common attribute being marked as a context-sensitive attribute, the context-sensitive attribute of the first instance having first provider-specific data specific to the first data provider, the context-sensitive attribute of the second instance having second provider-specific data specific to the second data provider, wherein upon determining that the common attribute is marked as the context-sensitive attribute, a unique reconciliation rule is applied to the first and second instances than what is normally applied to an object without the context-sensitive attribute, wherein the reconciling includes,

merging the first provider-specific data and the second provider-specific data from the first instance and the second instance to create the reconciled data, the reconciled data including the first provider-specific data for the first data provider, and the second provider-specific data for the second data provider;

storing, by the at least one processor, the first instance in a first provider data partition associated with the first data provider, the second instance in a second provider data partition associated with the second data provider, and the reconciled resource object in a target data partition;

receiving, by the at least one processor, a context-sensitive query, the context-sensitive query including a query parameter related to the context-sensitive attribute and context information identifying one of the first data provider and the second data provider;

querying, by the at least one processor, the target data partition for the reconciled resource object, and obtaining the first provider-specific data from the reconciled data when the context information specifies the first data provider; and

querying, by the at least one processor, the target data partition for the reconciled resource object, and obtaining the second provider-specific data from the reconciled data when the context information specifies the second data provider.

20. The method of claim 19 , wherein the reconciled data includes the first provider-specific data, the second provider-specific data, and default data corresponding to results of a reconciliation operation on the context-sensitive attribute.

Assignments (14)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 7, 2025
From: BMC SOFTWARE, INC.
To: BMC HELIX, INC.
Reel/Frame 070442/0197 →
GRANT OF FIRST LIEN SECURITY INTEREST IN PATENT RIGHTS Recorded Nov 13, 2024
From: BMC SOFTWARE, INC.; BLADELOGIC, INC.
To: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT
Reel/Frame 069352/0628 →
GRANT OF SECOND LIEN SECURITY INTEREST IN PATENT RIGHTS Recorded Nov 13, 2024
From: BMC SOFTWARE, INC.; BLADELOGIC, INC.
To: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT
Reel/Frame 069352/0568 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (052854/0139) Recorded Aug 6, 2024
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
To: BMC SOFTWARE, INC.; BLADELOGIC, INC.
Reel/Frame 068339/0617 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (052844/0646) Recorded Aug 6, 2024
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
To: BMC SOFTWARE, INC.; BLADELOGIC, INC.
Reel/Frame 068339/0408 →
OMNIBUS ASSIGNMENT OF SECURITY INTERESTS IN PATENT COLLATERAL Recorded Mar 4, 2024
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS RESIGNING COLLATERAL AGENT
To: GOLDMAN SACHS BANK USA, AS SUCCESSOR COLLATERAL AGENT
Reel/Frame 066729/0889 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS Recorded Feb 1, 2024
From: ALTER DOMUS (US) LLC
To: BMC SOFTWARE, INC.; BLADELOGIC, INC.
Reel/Frame 066567/0283 →
GRANT OF SECOND LIEN SECURITY INTEREST IN PATENT RIGHTS Recorded Sep 30, 2021
From: BMC SOFTWARE, INC.; BLADELOGIC, INC.
To: ALTER DOMUS (US) LLC
Reel/Frame 057683/0582 →
SECURITY INTEREST Recorded Jun 4, 2020
From: BMC SOFTWARE, INC.; BLADELOGIC, INC.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
Reel/Frame 052844/0646 →
SECURITY INTEREST Recorded Jun 4, 2020
From: BMC SOFTWARE, INC.; BLADELOGIC, INC.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
Reel/Frame 052854/0139 →
RELEASE OF PATENTS Recorded Oct 5, 2018
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: BMC SOFTWARE, INC.; BLADELOGIC, INC.; BMC ACQUISITION L.L.C.
Reel/Frame 047198/0468 →
SECURITY INTEREST Recorded Oct 2, 2018
From: BMC SOFTWARE, INC.; BLADELOGIC, INC.
To: CREDIT SUISSE, AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 047185/0744 →
SECURITY INTEREST Recorded Jul 27, 2017
From: BMC SOFTWARE, INC.; BLADELOGIC, INC.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 043351/0189 →
SECURITY INTEREST Recorded Jul 27, 2017
From: BMC SOFTWARE, INC.; BLADELOGIC, INC.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 043351/0231 →