IP Library Granted Patent US 8,271,477
Granted Patent B2
US 8,271,477 · App. 11/957,398 · Granted Sep 18, 2012

Methods and systems for accessing data

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,271,477
App. No.
11/957,398
Granted
Sep 18, 2012
Kind
B2
Abstract

Some embodiments of the invention provide a user interface that allows a user to specify one or more attributes that should be included in a master reference data set, and identify which of these attributes should serve as enterprise specified identifiers that can be used to identify the particular master reference data set in an enterprise data storage. Some embodiments of the invention provide a method that allows the master reference data set to be accessed and updated in the data storage through the use of the enterprise specified identifiers.

Claims (38)

1. A method of accessing data related to an entity associated with an enterprise, said method comprising:

displaying a plurality of reference data attributes for use in defining a master reference data set that is (i) for identifying the entity and (ii) for accessing data stored regarding the entity, said

master reference data set representing a most reliable reference data set maintained for the entity by the enterprise;

receiving a user identification of a set of different attributes from the plurality of reference data attributes;

designating each identified attribute in the set of different attributes as a first unique identifier for uniquely identifying the master reference data set;

receiving different queries that are based on said set of different attributes, each particular query including reference data associated with an attribute designated as the first unique identifier; and

processing each particular query by (i) using the reference data associated with the attribute included in the query to uniquely identify, in a first data storage, the master reference data set for the entity, the master reference data set comprising a second unique identifier, (ii) cross-correlating, by accessing a cross-correlation table that stores one or more other unique identifiers associated with the entity in different data storages, the second unique identifier to a third unique identifier associated with the entity in a second data storage different from the first data storage, and (iii) retrieving data relating to the entity from the second data storage using the third unique identifier.

2. The method of claim 1 , wherein the designating comprises specifying the set of different attributes of said master reference data set as different unique keys for accessing the master reference data set.

3. The method of claim 1 , wherein the set of different attributes comprises a business identifier for the entity, wherein said business identifier for the entity is an identifier that is stored in a plurality of the different data storages and that uniquely identifies reference data for the entity in each of the plurality of the different data storages.

4. The method of claim 1 , wherein the designating comprises providing access to said master reference data set using each attribute in the set of different attributes.

5. The method of claim 4 , wherein the second unique identifier is an internally generated default access key and the reference data associated with the attribute is not an internally generated key, the method further comprising providing access to the master reference data set using the default access key.

6. The method of claim 1 , wherein the data related to the entity comprise relationship data related to the entity, said relationship data for providing a composite view of the entity's relationship to other entities associated with the enterprise.

7. The method of claim 1 , wherein the data related to the entity comprise transactional data related to interactions of the entity with the enterprise.

8. The method of claim 7 , wherein said master reference data set is stored in the first data storage, and the transactional data related to the entity are stored in the second data storage in the enterprise that is at a different physical location apart from the first data storage.

9. The method of claim 1 , wherein at least one of the different queries is based on a previously stored attribute value that is not a current value stored for the entity.

10. The method of claim 1 , wherein the data relating to the entity are stored in a plurality of the different data storages, said method further comprising enabling cross-reference correlation for updating the data of the entity in the plurality of the different data storages in response to an update to the master reference data set.

11. The method of claim 1 , wherein displaying the plurality of reference data attributes comprises displaying the plurality of reference data attributes in a user interface (“UI”) that includes corresponding user-selectable items for receiving selection of the set of different attributes to be designated as unique identifiers for accessing the entity data.

12. An apparatus for accessing data related to an entity associated with an enterprise, the apparatus comprising:

a user interface module (i) to display a plurality of reference data attributes for use in defining a master reference data set that represents a most reliable reference data set maintained by the enterprise for identifying the entity and for accessing data stored regarding the entity, and (ii) to receive user identification of different sets of attributes as different sets of unique identifiers for uniquely identifying the master reference data set;

a master reference manager (i) to receive a plurality of reference data sets relating to the entity, and (ii) to consolidate the received reference data sets into the master reference data set in a first data storage; and

a data retrieval module (i) to receive different queries that are based on said different sets of unique identifiers, each particular query including reference data associated with an attribute in the different sets of attributes, and (ii) to process each particular query by (a) using the reference data associated with the attribute included in the query to uniquely identify, in the first data storage, the master reference data set for the entity, the master reference data set comprising a first unique identifier, (b) cross-correlating, by accessing a cross-correlation table that stores one or more other unique identifiers associated with the entity in different data storages, the first unique identifier to a second unique identifier associated with the entity in a second data storage different from the first data storage, and (c) retrieving data related to the entity from at least the second data storage using the second unique identifier.

13. A method of providing access to data related to an entity associated with an enterprise, said data stored in a plurality of different data storages that are accessible by a plurality of different applications to retrieve the data related to the entity, the method comprising:

consolidating reference data sets that are related to the entity and stored in the different data storages into a master reference data set representing a most reliable reference data set maintained by the enterprise for identifying the entity, said master reference data set defined by a plurality of reference attributes;

receiving different data access requests from the plurality of different applications, at least two requests utilizing two different reference attributes as unique identifiers for the entity, each particular request including reference data associated with a reference attribute that uniquely identifies the master reference data set; and

processing each particular request by (i) using the reference data associated with the reference attribute included in the request to uniquely identify the master reference data set for the entity from a first data storage, the master reference data set comprising a first unique identifier (ii) cross-correlating, by accessing a cross-correlation table that stores one or more other unique identifiers associated with the entity in the different data storages, the first unique identifier to a second unique identifier associated with the entity in a second data storage different from the first data storage, and (iii) retrieving data related to the entity from at least the second data storage using the second unique identifier.

14. The method of claim 13 , wherein at least one of the different data access requests utilizes a previous data value that is not a current value of said reference attribute to identify the master reference data set.

15. The method of claim 13 further comprising updating the master reference data set using at least one other data value in one of the data access requests.

16. The method of claim 15 , wherein the second data storage is at a different physical location apart from the first data storage, wherein the method further comprises updating the retrieved data stored in the second data storage.

17. The method of claim 13 , wherein the retrieved data comprises transactional data related to the entity, wherein retrieving the transactional data comprises sending a distributed query across the plurality of data storages to retrieve the transactional data related to the entity.

18. The method of claim 13 further comprising retrieving relationship data related to the entity, said relationship data for providing a composite view of the entity's relationship to other entities associated with the enterprise.

19. The method of claim 13 further comprising identifying a particular reference attribute as a particular identifier that is designated as a key for accessing the master reference data set.

20. For an enterprise, an apparatus for integrating entity data stored in a plurality of different data storages, said enterprise comprising a plurality of different applications that generate requests to access the entity data, said apparatus comprising:

a master reference manager for (i) receiving a plurality of reference data sets relating to an entity, and (ii) consolidating, in a first data storage, the received reference data sets into a master reference data set, said master reference data set representing a most reliable reference data set maintained by the enterprise for uniquely identifying the entity; and

a data access module for (i) receiving, from the plurality of different applications, different data access requests regarding the entity that include a set of different attributes, each attribute in the set of different attributes designated as a first unique identifier that uniquely identifies the master reference data set, and (ii) processing each particular request by (a) using the attribute included in the request to uniquely identify a second unique identifier for the master reference data set, (b) cross-correlating, by accessing a cross-correlation table that stores one or more other unique identifiers associated with the entity in the different data storages, the second unique identifier to at least a third unique identifier associated with the entity in a second data storage different from the first data storage, and (c) retrieving data relating to the entity from the second data storage using the third identifier.

21. The apparatus of claim 20 further comprising a user interface module for (i) displaying a plurality of master reference data attributes for use in defining the master reference data set that is for identifying the entity and for accessing data stored regarding the entity, and (ii) receiving user identification of the set of different attributes as different unique identifiers for uniquely identifying the master reference data set.

22. The apparatus of claim 21 , wherein receiving the user identification comprises receiving a selection of the set of different attributes used to retrieve the data relating to the entity stored in the second data storage.

23. The apparatus of claim 12 , wherein the data related to the entity comprise relationship data related to the entity, said relationship data for providing a composite view of the entity's relationship to other entities associated with the enterprise.

24. The apparatus of claim 12 , wherein the data related to the entity comprise transactional data related to interactions of the entity with the enterprise.

Assignments (10)
RELEASE OF SECURITY INTEREST Recorded Nov 18, 2025
From: JPMORGAN CHASE BANK, N.A.
To: INFORMATICA LLC
Reel/Frame 073597/0722 →
SECURITY INTEREST Recorded Oct 29, 2021
From: INFORMATICA LLC
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 057973/0568 →
RELEASE OF SECURITY INTEREST Recorded Oct 29, 2021
From: NOMURA CORPORATE FUNDING AMERICAS, LLC
To: INFORMATICA LLC
Reel/Frame 057973/0496 →
RELEASE OF SECURITY INTEREST Recorded Oct 29, 2021
From: NOMURA CORPORATE FUNDING AMERICAS, LLC
To: INFORMATICA LLC
Reel/Frame 057973/0507 →
SECURITY INTEREST Recorded Feb 26, 2020
From: INFORMATICA LLC
To: NOMURA CORPORATE FUNDING AMERICAS, LLC
Reel/Frame 052022/0906 →
NOTICE OF SUCCESSION OF AGENCY Recorded Feb 25, 2020
From: BANK OF AMERICA, N.A.
To: NOMURA CORPORATE FUNDING AMERICAS, LLC
Reel/Frame 052018/0070 →
SECURITY AGREEMENT Recorded Aug 6, 2015
From: INFORMATICA CORPORATION
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 036294/0701 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 5, 2011
From: SIPERIAN LLC
To: INFORMATICA CORPORATION
Reel/Frame 027019/0872 →
CHANGE OF NAME Recorded Oct 5, 2011
From: SIPERIAN, INC.
To: SIPERIAN LLC
Reel/Frame 027021/0121 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 18, 2008
From: SOOD, MANISH; QIAN, XIAOFENG
To: SIPERIAN, INC.
Reel/Frame 021851/0610 →