Remote data collection systems and methods

• US 8,214,329 B2
• Filed: 08/26/2009
• Issued: 07/03/2012
• Est. Priority Date: 08/26/2008
• Status: Active Grant

• Current Assignee: ZeeWise, Inc.
• Original Assignee: ZeeWise, Inc.
• Inventors: Gilder, Clark S., Hix, Joshua, Zalewski, Bartosz J.
• Primary Examiner(s): Alam, Shahid
• Assistant Examiner(s): KABIR, MOHAMMAD H
• Application Number:
  US12/547,788
• Publication Number:
  US 20100179940A1
• Time in Patent Office: 1,042 Days
• Field of Search: 707/622, 707/668, 709/238
• US Class Current: 707/622
• CPC Class Codes: G06F 16/25 Integrating or interfacing systems involving database management systems
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application
• CPC Class Codes: G06F 16/254 Extract, transform and load [ETL] procedures, e.g. ETL data flows in data warehouses
• CPC Class Codes: G06F 16/256 in federated or virtual databases
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database

Abstract

The present disclosure provides remote data collection systems and methods for retrieving data including financial, sales, marketing, operational and the like data from a plurality of databases and database types remotely over a network in an automated, platform-agnostic manner. The present invention is designed to work across a plurality of LOB applications, database vendors and business models or businesses, as well as business infrastructure (various PCs, embedded devices and POS devices) and business processes while still providing the centralized ability to automatically collect data from multiple remote business sites. The present invention includes one or more central servers communicating with a plurality of remote data collection agents. The remote data collection agent is designed to overcome existing requirements or limitations as it is able to automatically collect remote data from a wide range of businesses, as well as multiple LOB applications while connecting to multiple databases vendors and formats.

Claims

1. A remote data collection system, comprising:

one or more servers coupled to one or more data sources;

a plurality of remote clients communicatively coupled to the one or more servers, each of the plurality of remote clients comprise a remote client agent communicatively coupled to one or more client data sources; and

a metadata message transport mechanism configured to coordinate, control, and replicate data between the plurality of remote clients and the one or more data sources providing real-time linkage there between for communication and control, and wherein the metadata message transport mechanism is further configured to provide communication and control between the one or more servers and the plurality of remote clients, the control comprises the one or more servers being configured to remotely control the replication of data from one of the one or more client data sources through the one of the plurality of remote clients;

wherein the one or more servers are configured to replicate and collect data from the one or more client data sources using the remote client agents on the plurality of remote clients using the metadata message transport mechanism; and

wherein the remote client agents on the plurality of remote clients and the one or more servers are configured to operate in a database independent manner relative to the plurality of data sources using abstraction layers to hide implementation details for various database types.

2. The remote data collection system of claim 1, further comprising:

a definition server communicatively coupled to each of the plurality of remote clients, wherein the definition server is configured to provide a plurality of definitions for each remote client agent, and wherein the plurality of definitions define collection rules for data in the client data source, the collection rules comprising dynamically generated extraction rules for data and subsets thereof with the extraction rules determining operation of the plurality of remote clients for the replication of data from one of the one or more client data sources.

3. The remote data collection system of claim 1, further comprising:

an update server communicatively coupled to each of the plurality of remote clients, wherein the update server is configured to provide updates to the plurality of remote client agents, wherein the updates are configured to modify the metadata message transport mechanism and associated control for the replication of data.

4. The remote data collection system of claim 1, wherein the one or more client data sources comprise data from one of a line of business application and point of sale application;

and

wherein the remote client agent comprises an abstract implementation configured to operate on a plurality of database types with the one or more client data sources comprising at least two different database types of the plurality of database types.

5. The remote data collection system of claim 1, wherein the metadata message transport mechanism comprises a plurality of message types exchanged between the plurality of remote clients and the one or more servers to remotely control the replication of data from one of the one or more client data sources;

and

wherein the metadata message transport mechanism contains formatted data that is abstracted by a remote data collection system using message handlers thereby enabling future upgrades to the message handlers to add new messages types or extend existing message types.

6. The remote data collection system of claim 5, wherein the plurality of message types comprise data messages, log messages, exception messages, update ready messages, update server online messages, update complete messages, update interrupted messages, update file messages, update configuration messages, definition request messages and definition messages.

7. The remote data collection system of claim 1, further comprising:

one or more shadow databases utilized in a data collection task, wherein, in response to the control from the metadata message transport mechanism, the data collection task copies data from one of the one or more client data sources to one of the one or more shadow databases and processes the copied data in accordance with a requested collection definition object for sending via the metadata message transport mechanism, the one or more shadow databases are used for operations in the data collection task to reconcile and collect the data.

8. The remote data collection system of claim 7, wherein the data collection task comprises a comparison function verifying copied data in the one or more shadow databases responsive to the requested collection definition object and a sending function to the one or more data sources from the one or more shadow databases.

9. A computer, comprising:

a network interface;

a connection to a data source; and

a processor communicatively coupled to the network interface and the connection, wherein the processor is configured to execute a remote data collection agent;

wherein the remote data collection agent is configured to coordinate, control, and replicate data between the data source and a server, and wherein the remote data collection agent utilizes a metadata message transport mechanism to communicate to the server through the network interface, the metadata message transport mechanism is further configured to provide communication and control between the server and the computer providing real-time linkage there between for communication and control, wherein the control comprises the server being configured to remotely control the replication of data from the data source through the remote data collection agent, and wherein the server is configured to automatically and remotely replicate and receive the data from the data source through the remote data collection agent;

wherein the computer is configured to replicate and collect data from the data source using the remote data collection agent and using the metadata message transport mechanism; and

wherein the remote data collection agent and the server are configured to operate in a database independent manner relative to the data source using abstraction layers to hide implementation details for various database types.

10. The computer of claim 9, wherein the remote data collection agent is configured to receive a plurality of definitions defining collection rules for data in the data source from the server, the collection rules comprising dynamically generated extraction rules for data and subsets thereof in the data source, and wherein the remote data collection agent using the collection rules to automatically replicate and transmit the data from the data source to the server.

11. The computer of claim 9, wherein the remote data collection agent is configured to operate in a reconciliation phase and a collection phase, in the reconciliation phase, the remote data collection agent is configured to determine what data to extract and how to extract it from the data source using a shadow database, and in the collection phase, the remote data collection agent is configured to synchronize the data and to send the data using the shadow database.

12. The computer of claim 9, wherein the data source comprises data from one of a line of business application and point of sale application;

and

wherein the remote data collection agent comprises an abstract implementation configured to operate on a plurality of database types such that the remote data collection agent operates on the data source independent of a type of database of the data source.

13. The computer of claim 9, wherein the metadata message transports mechanism utilizes Java Message Service for secure transmission over the Internet;

wherein the metadata message transport mechanism comprises a plurality of message types exchanged between the remote data collection agent and the server to remotely control the replication of data from the data source; and

wherein the metadata message transport mechanism contains formatted data using message handlers thereby enabling future upgrades to the message handlers to add new messages types or extend existing message types.

14. The computer of claim 9, further comprising:

a shadow database utilized in a data collection task, wherein the shadow database is communicatively coupled to the processor, wherein, in response to the control from the metadata message transport mechanism, the data collection task copies data from one of the data source to one of the shadow database and processes the copied data in accordance with a requested collection definition object from the metadata message transport mechanism, the shadow database is used to perform operations on the data as defined in the requested collection definition object.

15. The computer of claim 14, wherein the data collection task comprises a comparison function verifying copied data in the shadow database responsive to the requested collection definition object and a sending function to the database from the shadow database.

16. A method of remote data collection, comprising:

receiving an agent installation package at a remote client;

initiating the agent installation package;

installing a service process that facilitates automatically starting a launcher process;

loading the launcher process thereby installing a plurality of components of a remote client agent;

communicating through a plurality of metadata messages with a server to provide defined data from a data source at the remote client to the server, wherein the plurality of metadata messages enable the server to automatically and remotely replicate the defined data using a data collection process with a reconciliation and a collection step each using a local shadow database to collect, operate on, and verify the defined data; and

using the plurality of metadata messages to control operation at the remote client providing real-time linkage to the server for communication and control and to determine subsets of the defined data to control, extract, and transport to the server;

wherein the remote client agent and the server are configured to operate in a database independent manner relative to the data source using abstraction layers to hide implementation details for various database types.

17. The method of claim 16, further comprising:

receiving collection definitions from the server;

extracting data from the data source responsive to the collection definitions;

writing the extracted data to the local shadow database;

processing the extracted data in the local shadow database based on the collection definitions;

comparing the extracted data to data in the local shadow database; and

sending data messages comprising the extracted data to the server.

18. The method of claim 17, further comprising:

extracting a table and a column definition from the collection definitions;

matching a requested table and column definition with a table and column of at least one of the data source, the local shadow database and a server data source.

19. The method of claim 16, further comprising:

sending an update number to the server;

receiving an update package from the server; and

installing the update package on the remote client to support new messages, different database types, or modify existing messages.

20. The method of claim 16, wherein the data source comprises data from one of a line of business application and point of sale application.

21. A remote data collection system comprising;

one or more network communication endpoints dynamically created to connect a plurality of remote agents to one or more central servers comprising a network namespace of endpoints which are dynamically monitored, managed and which provide a real-time linkage between remote agent and central database;

wherein the plurality of remote agents and the one or more central servers are connected in a bi-directional fashion whereby the real-time linkage is provide by a plurality of metadata messages and the real-time linkage comprises communication and control;

wherein the plurality of remote agents are communicatively coupled to a plurality of data sources;

wherein the one or more central servers are configured to replicate and collect data from the plurality of data sources using the plurality of remote agents using the one or more network communication endpoints; and

wherein the plurality of remote agents and the one or more central servers are configured to operate in a database independent manner relative to the plurality of data sources using abstraction layers to hide implementation details for various database types.