Systems and Methods to Provide Data Services

• US 20110264567A1
• Filed: 04/25/2011
• Published: 10/27/2011
• Est. Priority Date: 04/23/2010
• Status: Abandoned Application

• Current Assignee: Visa USA, Inc. (Visa, Inc.)
• Original Assignee: Visa USA, Inc. (Visa, Inc.)
• Inventors: Clyne, Andrew
• Application Number:
  US13/093,618
• Publication Number:
  US 20110264567A1
• Time in Patent Office: Days
• US Class Current: 705/30
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: G06Q 40/12 Accounting

Abstract

In one aspect, a computing apparatus includes: a transaction handler configured to process transactions; a data warehouse configured to store meta data and first data including transaction data recording the transactions and information generated based on the transaction data; an intranet coupled between the data warehouse and the transaction handler; an input engine coupled between the intranet and a plurality of data sources outside the intranet, where the input engine is controlled by the meta data to access the data sources to provide second data; and a broker engine coupled between the intranet and a plurality of data consuming devices outside the intranet, where the broker engine is controlled by the meta data to control access of the data consuming devices to the first data and the second data.

Claims

1. A system, comprising:

a transaction handler configured to process transactions, each of the transactions being processed to make a payment from an issuer to an acquirer via the transaction handler in response to an account identifier of a customer, as issued by the issuer, being submitted by a merchant to the acquirer, the issuer to make the payment on behalf of the customer, the acquirer to receive the payment on behalf of the merchant;

a data warehouse configured to store meta data and first data, the first data including transaction data recording the transactions and information generated based on the transaction data;

an intranet coupled between the data warehouse and the transaction handler;

an input engine coupled between the intranet and a plurality of data sources outside the intranet, the input engine controlled by the meta data to access the data sources to provide second data; and

a broker engine coupled between the intranet and a plurality of data consuming devices outside the intranet, the broker engine controlled by the meta data to control access of the data consuming devices to the first data and the second data.

2. The system of claim 1, wherein the input engine is configured to measure usage of the plurality of data sources based on the meta data and generate account payable information for the plurality of data sources based on the usage measured by the input engine;

and the broker engine is configured to measure data usage by the plurality of data consuming devices based on the meta data and generate account receivable information for the plurality of data consuming devices.

3. The system of claim 2, wherein the meta data comprises a plurality of meta data portions corresponding to the plurality of data sources, each respective portion of the meta data portions controlling the input engine to access a respective data source in the plurality of data sources;

and wherein the plurality of data sources use a plurality of different data management systems.

4. The system of claim 3, wherein the respective data source is addable into a dataset accessible via the broker engine via addition of the respective portion of the meta data without modifying the input engine or the broker engine.

5. The system of claim 2, wherein the meta data comprises a plurality of meta data portions corresponding to the plurality of data consuming devices, each respective portion of the meta data portions controlling the broker engine in providing a respective data consuming device of the plurality of data consuming devices with data access to the first data and the second data.

6. The system of claim 5, wherein the respective data consuming device is allowed to access a dataset accessible via the broker engine via addition of the respective portion of the meta data without modifying the input engine or the broker engine.

7. The system of claim 6, wherein the respective portion of the meta data identifies a first portion of the dataset that is accessible to the respective consuming device and a second portion of the dataset that is not accessible to the respective consuming device.

8. The system of claim 2, wherein the account receivable information and the account payable information are based on a plurality of different billing models.

9. The system of claim 1, further comprising:

a profile generator configured to generate transaction profiles summarizing transactions of respective consumers;

wherein the information generated based on the transaction data includes the transaction profiles of the respective consumers.

10. The system of claim 9, wherein at least a portion of the first data is generated based on the transaction data stored in the data warehouse and a portion of the second data provided by the input engine.

11. A system, comprising:

a data warehouse storing transaction data and meta data; and

an input engine coupled with the data warehouse, the input engine to interface with a plurality of external data sources based on the meta data specified for the plurality of external data sources.

12. The system of claim 11, wherein the input engine provides access to data in the plurality of external data sources via a uniform interface.

13. The system of claim 12, wherein the input engine measures usage of the data in the plurality of external data sources to generate account payable information according to the meta data.

14. The system of claim 13, wherein the meta data indicate that the plurality of external data sources use different billing models for different data.

15. The system of claim 11, further comprising:

an intranet to couple the data warehouse and the input engine to integrate access to the transaction data and the data in the plurality of external data sources, wherein the plurality of external data sources are external to the intranet.

16. A system, comprising:

at least one data source storing meta data; and

a broker engine coupled with the at least one data source, the broker engine to interface with a plurality of data consuming devices based on the meta data specified for the plurality of data consuming devices.

17. The system of claim 16, wherein the broker engine selectively provides access to data in the at least one data source based on the meta data.

18. The system of claim 17, wherein the broker engine measures usage of the data in the at least one data source to generate account receivable information according to the meta data.

19. The system of claim 18, wherein the meta data indicate that the plurality of data consuming devices are billed via different models for different data.

20. The system of claim 16, wherein the at least one data source comprises a data warehouse storing transaction data and meta data and a plurality of external data sources, the system further comprising:

an input engine to interface with the plurality of external data sources; and

an intranet to couple the data warehouse, the input engine, and the broker engine;

wherein the broker engine is to provide a uniform interface to access data in the at least one data source; and

the plurality of external data sources and the data consuming devices are external to the intranet.