Multi-source multi-tenant entitlement enforcing data repository and method of operation

• US 20060235831A1
• Filed: 12/22/2005
• Published: 10/19/2006
• Est. Priority Date: 01/14/2005
• Status: Abandoned Application

• Current Assignee: Aviv Orani, Cornelius Edward Crowley, Francis Nicholas Parr, Guerney Douglass Holloway Hunt, Jennifer Susan Gromada, Matthew Adam Rice, Max Hrabrov, Ronald Emmett Adinolfi, Sugandh Mehta, Teresa Anne Glasser
• Original Assignee: Aviv Orani, Cornelius Edward Crowley, Francis Nicholas Parr, Guerney Douglass Holloway Hunt, Jennifer Susan Gromada, Matthew Adam Rice, Max Hrabrov, Ronald Emmett Adinolfi, Sugandh Mehta, Teresa Anne Glasser
• Inventors: Orani, Aviv, Adinolfi, Ronald Emmett, Crowley, Cornelius Edward, Glasser, Teresa Anne, Gromada, Jennifer Susan, Rice, Matthew Adam, Parr, Francis Nicholas, Holloway Hunt, Guerney Douglass, Hrabrov, Max, Mehta, Sugandh
• Application Number:
  US11/318,355
• Publication Number:
  US 20060235831A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes

Abstract

Forming and maintaining a multi-source multi-tenant data repository on behalf of multiple tenants. Information in the multi-source multi-tenant data repository is received from multiple sources. Different sources and different data quality enhancement processes may yield different values for attributes of the same referred entity. Information in the multi-source multi-tenant data repository is tagged with annotations documenting the sources of the information, and any data quality processing actions applied to it. Tenants of the multi-source multi-tenant data repository have entitlement to values from some sources and to the results of some quality enhancement processes. Aspects of the method maintain this entitlement information; employ evolutionarily tracked source data tags; receive requests for information, locate the requested information, apply any sourcing preference, enforce entitlements and return entitled values to the requester. An outsourced reference data utility is one context where such a multi-source multi-tenant data repository is useful.

Claims

1. A multi-source multi-tenant data repository of data useful to requestors, comprising:

a database management system, said system managing a data base including information elements from a plurality of sources, describing at least one referred entity;

annotations of sourcing information for said elements, and entitlements of requesters to information elements based on said sourcing information;

data input apparatus for placing said information elements in said database; and

data output apparatus for providing data output based on said information elements in response to a request form a requestor, said output containing information to which said requestor is entitled based on said entitlements.

2. A repository as recited in claim 1, wherein the requestors are selected from the group comprising:

tenants, clients, sources of reference data, an agent acting on behalf of the repository;

software programs acting on behalf of a tenant; and

software programs acting on behalf of the repository.

3. A repository as recited in claim 1, further comprising means for authenticating a requestor as authorized to obtain data from said repository.

4. A repository as recited in claim 1, wherein said entitlements comprise at least one of:

entitlements to data provided by a specific data source;

entitlements to data items generated by a particular value enhancement process; and

entitlements to data from a particular process, if all values used to derive the data were from data sources to which a requester is entitled.

5. A repository as recited in claim 4, comprising a database portion for storing information concerning a set of entitlements governing outputs which a requestor associated with a tenant of the repository is entitled to receive, based on tenants contracting independently with data sources.

6. A repository as recited in claim 1, wherein said information elements comprise element types taken from a list of element types comprising:

item instances;

versioned attributes;

properties;

attribute values;

business documents;

function definitions;

rule sets;

operational information;

media documents;

descriptions of standards;

hierarchical business data;

news information;

structured documents;

configuration information; and

program code.

7. A repository as recited in claim 1, wherein a repository entity comprises at least one item instance information element, each item instance element comprising at least one versioned attribute information element.

8. A repository as recited in claim 7, wherein a repository entity has at least one property used to select said repository entity in information element selection operations.

9. A repository as recited in claim 7, wherein an item instance comprises at least one property used to select said item instance in information element selection operations.

10. A repository as recited in claim 1, wherein said repository receives from at least one item instance, process item instances or metadata for inclusion in the repository, wherein said item instance process is uniquely identified by the repository;

said repository further comprising;

means for forming at least one repository entity corresponding to at least one referred entity; and

means for associating said item instances or metadata for inclusion with at least one of said repository entities, based on reference to said at least one referred entity.

11. A repository as recited in claim 1, wherein said database management system comprises:

means for storing in said database as at least one property of at least one item instance, information identifying-an item instance process yielding said item instance;

means for storing in said database in the form of at least one evolutionarily tracked source data tag at least one event in a history of said item instance, said at least one event comprised of temporal information, sources and agents of said at least one event as received from at least one item instance process;

means for storing in the form of at least one evolutionarily tracked source data tag event in a history of versioned attributes of said item instance, said at least one event comprised of temporal information, sources and agents of said at least one event as received from an item instance process;

means for storing metadata for each said item instance;

means for storing metadata for each repository entity; and

means for storing metadata for each said versioned attribute.

12. A repository as recited in claim 10, wherein said database management system comprises at least one of:

means for storing in at least one evolutionarily tracked source data tag at least one event reflecting operations involving item instances, said at least one event comprised of temporal information, sources and agents of said at least one event;

means for creating new item instances;

means for affecting existing item instances;

means for providing composite processing of a plurality of item instances;

means for supplying an item instance with attribute values for a repository entity received from a source dataset;

means for supplying an item instance with attribute values for a repository entity resulting from quality assurance and enhancement of values received from a single source dataset; and

means for supplying an item instance with attribute values for a repository entity resulting from comparison and selection between values from a plurality of source datasets relating to the same attribute of the same referred entity.

13. A repository as recited in claim 1, wherein said database management system comprises:

means for interpreting a request to produce at least one request specification;

means for selecting requested information elements in the repository based on said request specification to form a return dataset;

means for filtering said return dataset to include only the information elements to which said requester is entitled to form a filtered return dataset; and

means for supplying said filtered return dataset to said data output apparatus.

14. A repository as recited in claim 13, wherein the means for interpreting yields a request specification comprising a plurality of aspects taken from a group of aspects comprising:

identification of the requester;

a selection predicate governing selection of the information elements to be returned; and

a sourcing preference comprising prioritization of said at least one preference of a requester when multiple information elements from separate sources are available satisfying said information element selection predicate.

15. A repository as recited in claim 12, wherein the means for selecting comprises at least one taken from a group comprising:

means for selecting any repository entity matching said request specification;

means for selecting any item instance belonging to said repository entities matching said request specification;

means for selecting any attribute value forming said item instances matching said request specification;

means for selecting any metadata associated with said any repository entity matching said request specification;

means for selecting any metadata associated with said any item instance matching said request specification;

means for selecting any metadata associated with said any attribute value matching said request specification; and

means for applying specified requester sourcing preference to form a return dataset comprising;

said item instances, said attribute values belonging to said item instances, and said metadata.

16. A repository as recited in claim 12, wherein the means for filtering comprises at least one from a group comprising:

means for ensuring the entitlement of said at least one requester to any item instance process responsible for generating any of the item instances selected;

means for ensuring the entitlement of said at least one requester to any attribute value selected, wherein said requester is entitled to receive said any attribute value only if said requester is entitled to at least one source providing said attribute value; and

means for removing from the return dataset any information element to which the requester is not entitled.

17. An information processing apparatus including means for maintaining a multi-source multi-tenant data repository, wherein the means for maintaining comprises:

means for forming said multi-source multi-tenant data repository to include information elements from a plurality of sources, describing at least one referred entity;

means for annotating a plurality of elements from said information elements in the multi-source multi-tenant data repository with sourcing information; and

means for maintaining information about entitlement of requesters to information elements based on said sourcing information.

18. A multi-source multi-tenant reference data repository, comprising:

means for inputting into said repository information about business instrument information, corporate hierarchy information, corporate news information and other information from multiple sources;

means for annotating changes to said business instrument information, corporate hierarchy information, corporate news information, and other information, and sources of each change;

means for maintaining information about entitlement of requesters to obtain said business instrument information, corporate hierarchy information, corporate news information, and other information, based on entitlement to the sources and processes which have provided or modified this information; and

means for responding to at least one request from at least one requester to return at least a subset of said business instrument information, corporate hierarchy information, corporate news information, and other information, based on requester-specified selection and sourcing preferences and subject to said entitlements.

19. A repository apparatus comprising:

means for forming the repository with information element structures in place;

means for inserting arriving information elements into a store of said the repository;

means for annotating each information element with annotations describing evolutionary history of said each information element in forming an evolutionarily tracked source data tag for said each information element;

means for maintaining source based entitlement information for authorized requesters of repository information and data sources to which each authorized requester is entitled; and

means for employing said evolutionarily tracked source data tag together with source based entitlements in a process providing entitlement enforced controlled access to information included in the repository.

20. A method for maintaining a multi-source multi-tenant data repository of data useful to requestors, comprising:

forming said multi-source multi-tenant data repository to include information elements from a plurality of sources, describing at least one referred entity;

annotating a plurality of said elements with sourcing information; and

maintaining information about entitlement of requesters to information elements based on said sourcing information.

21. A method as recited in claim 20, wherein said entitlements comprise at least one of:

entitlements to data provided by a specific data source;

entitlements to data items generated by a particular value enhancement process; and

entitlements to data from a particular process, if all values used to derive the data were from data sources to which a requestor is entitled.

22. A method as recited in claim 21, wherein tenants of the repository contract independently with data sources, and data enhancement process owners to determine a set of entitlements governing data which requesters associated with tenants are entitled to receive.

23. A method as recited in claim 20, further comprising responding to at least one request from at least one requester to return a set of information elements based on requester-specified selection predicates and sourcing preferences and subject to said entitlement of said at least one requester.

24. A method as recited in claim 20, wherein the step of responding comprises:

receiving at least one request from at least one requester;

interpreting said at least one request to produce at least one request specification;

selecting requested information elements in the multi-source multi-tenant data repository based on said request specification to form a return dataset;

filtering said return dataset include only the information elements to which said requester is entitled to form a filtered return dataset; and

returning said filtered return dataset to said requester.

25. A method as recited in claim 24, wherein the step of interpreting yields a request specification comprising a plurality of aspects taken from a group of aspects comprising:

identification of the requester;

a selection predicate governing selection of the information elements to be returned; and

a sourcing preference comprising prioritarization of said at least one requester'"'"'s preference when multiple information elements from separate sources are available satisfying said information element selection predicate.

26. A method as recited in claim 24, wherein the step of selecting comprises at least one step taken from a group comprising:

selecting any repository entity matching said request specification;

selecting any item instance belonging to said repository entities matching said request specification;

selecting any attribute value forming said item instances matching said request specification;

selecting any metadata associated with said any repository entity matching said request specification;

selecting any metadata associated with said any item instance matching said request specification;

selecting any metadata associated with said any attribute value matching said request specification; and

applying specified requester sourcing preference to form a return dataset comprising;

said item instances, said attribute values belonging to said item instances, and said metadata.

27. A method as recited in claim 24, wherein the step of filtering comprises at least one step taken from a group of steps comprising:

ensuring the entitlement of said at least one requester to any item instance process responsible for generating any of the item instances selected;

ensuring the entitlement of said at least one requester to any attribute value selected, wherein said requester is entitled to receive said any attribute value only if said requester is entitled to at least one source providing said attribute value; and

removing from the return dataset any information element to which the requester is not entitled.

28. A method as recited in claim 20, wherein said multi-source multi-tenant data repository comprises a plurality of information element types taken from a list of information element types comprising:

item instances;

versioned attributes;

properties;

attribute values;

business documents;

function definitions;

rule sets;

operational information;

media documents;

descriptions of standards;

hierarchical business data;

news information;

structured documents;

configuration information; and

program code.

29. A method as recited in claim 20, wherein a repository entity has at least one item instance information element, each item instance comprising at least one versioned attribute information element.

30. A method as recited in claim 29, wherein a repository entity comprises at least one property used to select said repository entity in information element selection operations.

31. A method as recited in claim 29 wherein an item instance comprises at least one property used to select said item instance in information element selection operations.

32. A method as recited in claim 20, wherein the forming comprises at least one step taken from a group of steps comprising:

said multi-source multi-tenant data repository receiving from at least one item instance process item instances or metadata for inclusion in the repository, wherein said item instance process is uniquely identified by the repository;

said repository forming at least one repository entity corresponding to at least one referred entity; and

said repository associating said item instances or metadata for inclusion with at least one of said repository entities based on reference to said at least one referred entity.

33. A method as recited in claim 20, wherein the annotating comprises at least one step taken from a group of steps comprising:

storing as at least one property of at least one item instance, information identifying-an item instance process yielding said item instance;

storing in the form of at least one evolutionarily tracked source data tag at least one event in a history of said item instance, said at least one event comprised of temporal information, sources and agents of said at least one event as received from at least one item instance process;

storing in the form of at least one evolutionarily tracked source data tag event in a history of versioned attributes of said item instance, said at least one event comprised of temporal information, sources and agents of said at least one event as received from an item instance process;

storing metadata for each said item instance;

storing metadata for each repository entity; and

storing metadata for each said versioned attribute.

34. A method as recited in claim 32, wherein said repository item instance process comprises at least one step taken from a group of steps comprising:

storing in at least one evolutionarily tracked source data tag at least one event reflecting operations involving item instances, said at least one event comprised of temporal information, sources and agents of said at least one event;

employing a process that creates new item instances;

employing a process that affects existing item instances;

employing a composite process comprised of a plurality of item instance processes;

supplying an item instance with attribute values for a repository entity received from a source dataset;

supplying an item instance with attribute values for a repository entity resulting from quality assurance and enhancement of values received from a single source dataset; and

supplying an item instance with attribute values for a repository entity resulting from comparison and selection between values from a plurality of source datasets relating to the same attribute of the same referred entity.

35. A method as recited in claim 20, wherein said requester is taken from a group of requesters comprising:

an agent acting on behalf of a repository tenant, an agent acting on behalf of the repository;

software programs acting on behalf of a repository tenant; and

software programs acting on behalf of the repository.

48. A computer usable medium having computer readable program code means embodied therein, the computer readable program code means being for causing a computer to effect the method of claim 20.

36. A method for maintaining a multi-source multi-tenant reference data repository, comprising:

forming said multi-source multi-tenant reference data repository to include information about business instrument information, corporate hierarchy information, corporate news information and other information from multiple sources;

annotating changes to said business instrument information, corporate hierarchy information, corporate news information, and other information, and sources of each change;

maintaining information about entitlement of requesters to obtain said business instrument information, corporate hierarchy information, corporate news information, and other information, based on entitlement to the sources and processes which have provided or modified this information; and

responding to at least one request from at least one requester to return at least a subset of said business instrument information, corporate hierarchy information, corporate news information, and other information, based on requester-specified selection and sourcing preferences and subject to said entitlements.

37. A method as recited in claim 36, wherein said at least one requester is a client of at least one service provider.

38. A method as recited in claim 36, wherein said business instrument information is financial information.

39. A method as recited in claim 38, wherein said source is from a group of sources comprising:

providers of business data;

providers of financial data;

providers of ratings data;

providers of corporate news data; and

providers of corporate hierarchy data.

40. A method as recited in claim 38, wherein said financial information includes data taken from a group of data comprising at least one of:

stock instruments;

bond instruments;

derivative instruments;

fixed income instruments;

mortgage-backed instruments;

counterparty information;

financial transaction information;

corporate events information;

financial trade information;

financial settlement information;

financial documents;

other financial instruments; and

other financial data.

41. A method as recited in claim 36, wherein the forming comprises keeping distinct versions of historical states of said business instrument information, corporate hierarchy information, corporate news information and other information.

49. A computer usable medium having computer readable program code means embodied therein, the computer readable program code means being for causing a computer to effect the method of claim 36.

42. A data repository method comprising:

forming the repository with information element structures in place;

inserting arriving information elements into a store of said the repository;

annotating each information element with annotations describing evolutionary history of said each information element in forming an evolutionarily tracked source data tag for said each information element;

maintaining source based entitlement information for authorized requesters of repository information and data sources to which each authorized requester is entitled; and

employing said evolutionarily tracked source data tag together with source based entitlements in a process providing entitlement enforced controlled access to information included in the repository.

43. A method as recited in claim 42, further comprising retrieval requests arriving as input;

and the process of providing comprising forming retrieval responses being returned as output for this processing.

44. A method as recited in claim 43, further comprising employing the repository to store other items that reside in a data store, said other items comprising at least one of:

business value added functions, business documents, functional rule sets;

operational rule sets, functional log records, and operational log records.

45. A method as recited in claim 42, further comprising associating the evolutionarily tracked source data tags with at least one information element in the repository;

and the step annotating comprises recording sourcing information to provide traceability to sources that contributed to creation of an information element value.

46. A method as recited in claim 42, wherein the maintaining comprises updating entitlement information received as input.

47. A method as recited in claim 42, wherein a step in maintaining is performed by a service provider.

50. A computer usable medium having computer readable program code means embodied therein, the computer readable program code means being for causing a computer to effect the method of claim 42.