Method and system for the creation, enhancement and update of remote data using persistent keys

• US 6,073,140 A
• Filed: 07/29/1997
• Issued: 06/06/2000
• Est. Priority Date: 07/29/1997
• Status: Expired due to Term

• Current Assignee: Acxiom Corporation (LiveRamp Holdings, Inc.)
• Original Assignee: Acxiom Corporation (LiveRamp Holdings, Inc.)
• Inventors: Talburt, John R., Morgan, Charles D., Roland, David B., Baker, Joy L., Cook, Joy E., Fogata, Marvin G., McLaughlin, G. Leigh, Mooney, James E.
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): RONES, CHARLES
• Application Number:
  US08/902,567
• Time in Patent Office: 1,043 Days
• Field of Search: 707/2, 707/4, 707/5, 707/10, 707/103, 707/203, 707/3, 707/8, 707/201, 395/11, 395/227, 395/705, 345/355
• US Class Current: 1/1
• CPC Class Codes: G06F 16/23 Updating
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99938 Concurrency, e.g. lock management in shared database
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

A method and system for the creation, enhancement and update of data on a customer database using data from a central database and persistent keys that are linked to each data structure is disclosed. The persistent keys allow the matching of equivalent data structures between the remote and central databases so that enhancement data from the central database can be overlaid onto the customer database. The persistent keys also make the update of data on the customer database more efficient, since key matching allows the transfer of only the data that is needed to update the customer database. The central database may physically contain all of the enhancement data, or may use a central database manager to transparently link a group of physically remote databases using the persistent keys. Data may be transferred from the central database to the customer database either in batch mode or in a near real-time mode through a direct table join. The linking feature of the persistent keys further allows the linkage of the customer database and the central database to create a multidimensional database.

Claims

1. A system for the creation, enhancement, and update of data resident at a remote location using data logically resident at a central location comprising:

(a) a central database;

(b) a customer database;

(c) a bi-directional transfer means communicatively connecting said central database and said customer database;

(d) a plurality of records resident on said central database and said customer database, each of said records comprising a plurality of fields, and each of said records that is resident on said customer database being matchable to one of said records that is resident on said central database;

(e) a plurality of persistent keys resident on said central database, the value of each of said persistent keys being independent of the physical storage location of said central records, the number of said persistent keys being equal to the number of said central records, each one of said persistent keys being linked to one of said central records, and each one of said persistent keys being permanent and distinguishable from every other one of said persistent keys.

2. A system according to claim 1, further comprising a computer-readable storage medium comprising:

(a) a persistent key list;

(b) a key field list comprising one field from each record resident on said central database; and

(c) a matching application operable to match each record on said customer database to one key field of said key field list, and link one persistent key of said persistent key list to each matched record on said customer database.

3. A system according to claim 2, wherein said matching application comprises:

(a) a first procedure that, for each record on said customer database, locates that field in each record that corresponds to the fields in said key field list;

(b) a second procedure that iteratively compares the located field with each key field in said key field list until a match is found; and

(c) a third procedure that creates on said customer database a copy of the persistent key from said persistent key list corresponding to the matched key field and links said copy with the matched record on said customer database.

4. A system according to claim 1, wherein each of said plurality of persistent keys comprises:

(a) an entity code, said entity code denoting the type of data stored in that record on said central database linked to said persistent key comprising said entity code;

(b) a unique number, said unique number distinguishing each of said persistent keys from every other one of said persistent keys;

(c) a version number, said version number incrementable each time any of said fields of said record on said central database linked to said persistent key comprising said version number is modified; and

(d) a check digit manipulable to check that said persistent key comprising said check code originated from said central database.

5. A system according to claim 4, wherein each of said plurality of persistent keys further comprises a country code, said country code denoting the country of origin for the data stored in that record on said central database linked to said persistent key comprising said country code.

6. A system according to claim 1, wherein said central database comprises:

(a) a central database manager;

(b) a plurality of linked physical databases; and

(c) a plurality of partial records resident on said plurality of linked physical databases, said partial records combinable to form records resident on said central database, and the same one of said plurality of persistent keys being linked to each of said partial records that are combinable to form a single record resident on said central database.

7. A system according to claim 6, wherein said linked physical databases are linked by said plurality of persistent keys linked to each of said partial records resident on said plurality of linked physical databases.

8. A system according to claim 7, further comprising a customer server communicatively connected via said bi-directional transfer means between said customer database and said central database and operable to submit requests for at least one of update, enhancement, and new data to said central database.

9. A system according to claim 8, further comprising a web server that is communicatively connected via said bi-directional transfer means to said customer server and is operable to receive and process requests for at least one of update, enhancement, and new data from said customer server.

10. A system according to claim 9, further comprising an application server communicatively connected via said bi-directional transfer means between said customer server and said central database, and communicatively connected via said bi-directional transfer means to said web server, and operable to provide a direct interface between said central database and said customer database.

11. A system according to claim 8, wherein said central database manager comprises:

(a) a first batch-mode procedure whereby a persistent key of interest and a request for certain data associated with said persistent key of interest are received from said customer server;

(b) a second batch-mode procedure whereby said central database manager compares said persistent key of interest to the persistent key linked to each of said partial records to determine if each of said linked physical databases contains data associated with said persistent key of interest, and, if a match is found, returns said data from said partial record to said central database manager;

(c) a third batch-mode procedure whereby said central database manager compiles data from each of said matched partial records resident on said linked physical databases to form a full record linked to said persistent key of interest comprising said requested data; and

(d) a fourth batch-mode procedure whereby said central database manager compiles all said full records and sends that portion of said full records to said customer database that was the subject of said customer server request.

12. A system according to claim 11, wherein said second batch-mode procedure only returns said data from said partial record to said central database manager if said version number on said persistent key of interest does not match said version number on the persistent key linked to said partial record.

13. A system according to claim 8, wherein said central database manager comprises:

(a) a first near real-time mode procedure whereby a request for certain data is received from said customer server;

(b) a second near real-time mode procedure whereby said central database and said customer database are directly linked by means of a table join; and

(c) a third batch-mode procedure whereby said central database manager transmits data from each of said matched records in said central database to the corresponding record in said customer database along said table join if such data was requested by said customer server.

14. A system according to claim 13, wherein said third batch-mode procedure only transmits data along said table join if said version number on said persistent key for a particular matched record resident on said customer database does not match said version number on the persistent key linked to the matching said partial record.

15. A system according to claim 6, wherein said central database manager comprises means for allowing access to said central database as if said central database were a single physical database.

16. A system according to claim 6, wherein central database manager further comprises a means to increment said version number of that one of said persistent keys linked to a particular record resident on said central database when any field of said particular record is updated.

17. A system according to claim 1, wherein said bi-directional transfer means is a global computer communications network.

18. A system according to claim 1, wherein said bi-directional transfer means is a direct transmission line.

19. A system according to claim 1, further comprising a third-party server operable to access said customer database and said central database as an integrated multidimensional database via said bi-directional transfer means.

20. A system according to claim 19, wherein said third-party server uses matched persistent keys resident on said central database and said customer database to form said integrated multidimensional database.

21. A system according to claim 1, wherein each of said plurality of persistent keys comprises:

(a) an entity code, said entity code denoting the type of data stored in that record on said central database linked to said persistent key comprising said entity code; and

(b) a unique number, said unique number distinguishing each of said persistent keys from every other one of said persistent keys.

28. A system according to claim 21, wherein said linked physical databases are linked by said plurality of persistent keys linked to each of said partial records resident on said plurality of linked physical databases.

29. A system according to claim 28, further comprising a customer server communicatively connected via said bi-directional transfer means between said customer database and said central database and operable to submit requests for at least one of update, enhancement, and new data to said central database.

30. A system according to claim 29, further comprising a web server that is communicatively connected via said bi-directional transfer means to said customer server and is operable to receive and process requests for at least one of update, enhancement, and new data from said customer server.

31. A system according to claim 30, further comprising an application server communicatively connected via said bi-directional transfer means between said customer server and said central database, and communicatively connected via said bi-directional transfer means to said web server, and operable to provide a direct interface between said central database and said customer database.

32. A system according to claim 29, wherein said central database manager comprises:

(a) a first batch-mode procedure whereby a persistent key of interest and a request for certain data associated with said persistent key of interest are received from said customer server;

(b) a second batch-mode procedure whereby said central database manager compares said persistent key of interest to the persistent key linked to each of said partial records to determine if each of said linked physical databases contains data associated with said persistent key of interest, and, if a match is found, returns said data from said partial record to said central database manager;

(c) a third batch-mode procedure whereby said central database manager compiles data from each of said matched partial records resident on said linked physical databases to form a full record linked to said persistent key of interest comprising said requested data; and

(d) a fourth batch-mode procedure whereby said central database manager compiles all said full records and sends that portion of said full records to said customer database that was the subject of said customer server request.

33. A system according to claim 32, wherein said second batch-mode procedure only returns said data from said partial record to said central database manager if said version number on said persistent key of interest does not match said version number on the persistent key linked to said partial record.

34. A system according to claim 29, wherein said central database manager comprises:

(a) a first near real-time mode procedure whereby a request for certain data is received from said customer server;

(b) a second near real-time mode procedure whereby said central database and said customer database are directly linked by means of a table join; and

(c) a third batch-mode procedure whereby said central database manager transmits data from each of said matched records in said central database to the corresponding record in said customer database along said table join if such data was requested by said customer server.

35. A system according to claim 34, wherein said third batch-mode procedure only transmits data along said table join if said version number on said persistent key for a particular matched customer record resident on said customer database does not match said version number on the persistent key linked to the matching said partial record.

36. A system according to claim 28, wherein said central database manager comprises means for allowing access to said central database as if said central database were a single physical database.

37. A system according to claim 28, wherein said central database manager further comprises a means to increment said version number of that one of said persistent keys linked to a particular central record when any central record field comprising said particular central record is updated.

22. A system for the creation, enhancement and update of data stored at a remote location using data logically stored at a central location comprising:

(a) a central database comprising;

(i) a plurality of central records, each comprising a plurality of central record fields, and

(ii) a plurality of persistent keys, the value of each of said persistent keys being independent of the physical storage location of said central records, the number of said plurality of persistent keys and said plurality of central records being equal, each of said plurality of persistent keys linked to one of said plurality of central records, and being permanent and distinguishable from each other;

(b) a customer database comprising a plurality of customer records, each comprising a plurality of customer record fields, and each of said plurality of customer records being matchable to one of said plurality of central records; and

(c) a bi-directional transfer means communicatively connecting said central database and said customer database.

23. A system according to claim 22, further comprising a computer-readable storage medium comprising:

(a) a persistent key list;

(b) a key central record field list comprising one central record field from each central record; and

(c) a matching application operable to match each customer record to one key central record field of said key field list, and link one persistent key of said persistent key list to each matched customer record.

24. A system according to claim 23, wherein said matching application comprises:

(a) a first procedure that, for each customer record, locates that customer record field that corresponds to the key central record fields in said key central record field list;

(b) a second procedure that iteratively compares the located central record field with each key central record field in said key central record field list until a match is found; and

(c) a third procedure that creates on said customer database a copy of the persistent key from said persistent key list corresponding to the matched key central record field and links said copy with the matched customer record.

25. A system according to claim 22, wherein each of said persistent keys comprises:

(a) an entity code, said entity code denoting the type of data stored in that central record linked to said one of said persistent keys comprising said entity code;

(b) a unique number, said unique number distinguishing each of said persistent keys from every other one of said persistent keys;

(c) a version number, said version number incrementable each time any of said central data fields of that one of said central records linked to said persistent key comprising said version number is modified; and

(d) a check digit manipulable to check that said persistent key comprising said check code originated from said central database.

26. A system according to claim 25, wherein each of said plurality of persistent keys further comprises a country code, said country code denoting the country of origin for the data stored in that record on said central database linked to said persistent key comprising said country code.

27. A system according to claim 22, wherein said central database comprises:

(a) a central database manager;

(b) a plurality of linked physical databases; and

(c) a plurality of partial records resident on said plurality of linked physical databases, said partial records combinable to form central records, and the same one of said plurality of persistent keys being linked to each of said partial records that are combinable to form a single central record.

38. A system according to claim 22, wherein said bi-directional transfer means is a global computer communications network.

39. A system according to claim 22, wherein said bi-directional transfer means is a direct transmission line.

40. A system for the creation, enhancement, and update of data, comprising:

(a) a plurality of databases;

(b) a plurality of data structures resident on each of said plurality of databases, each of said plurality of data structures representing an entity; and

(c) a plurality of persistent keys, each linked to one of said data structures stored on one of said plurality of databases, the value of each of said persistent keys being independent of the physical storage location of that one of said data structures to which said persistent key is linked, and each of said persistent keys being permanent and distinguishable from every other one of said persistent keys that is linked to one of said data structures that does not represent the same entity as that one of said data structures that is linked to that one of said persistent keys.

41. A system according to claim 40, wherein an updated version of each of said plurality of persistent keys is permanently maintained on one of said plurality of databases.

42. A plurality of persistent keys each linked to a data structure stored on a database, each of said plurality of persistent keys comprising:

(a) an entity code, said entity code denoting the type of data stored in said data structure linked to said persistent key;

(b) a unique number, said unique number distinguishing each of said plurality of persistent keys from every other one of said plurality of persistent keys that have an identical said entity code;

(c) a version number, said version number incrementable each time said data stored in said data structure linked to said persistent key comprising said version number is modified; and

(d) a check digit manipulable to check that said persistent key comprising said check code is authentic.

43. A system according to claim 42, wherein each of said plurality of persistent keys further comprises a country code, said country code denoting the country of origin for said data stored in said data structure linked to said persistent key comprising said country code.

44. A method for the creation, enhancement and update of data stored at a remote location using data logically stored at a central location comprising the steps of:

(a) storing on a central database a plurality of records, each comprising a plurality of fields;

(b) creating and linking to each said record a persistent key, each said persistent key being permanent and distinguishable from every other said persistent key, and the value of each of said persistent key being independent of the physical storage location of each said record;

(c) copying each of said persistent keys and a key field found in said record linked to each said persistent key from said central database to a computer-readable medium;

(d) interfacing said computer-readable medium with a customer database, said customer database comprising a plurality of said records;

(e) for each record on said customer database, overlaying onto the record that one persistent key linked to said key field resident on said computer-readable medium whose data matches the corresponding field in said record on said customer database;

(f) compiling a list of persistent keys resident on said customer database;

(g) sending said list to said central database;

(h) sending a data request to said central database, said data request specifying the type of update or enhancement required for said records on said customer database;

(i) matching each persistent key of said list with the corresponding persistent key resident on said central database;

(j) for each matched persistent key on said central database, retrieving the data requested from the record on said central database linked to each matched persistent key; and

(k) compiling all data requested and sending the data to said customer database.

45. A method according to claim 44, wherein each persistent key comprises a version number, and step (j) is replaced with the step of, for each matched persistent key on said central database, retrieving the data requested from the record on said central database linked to each matched persistent key only if said version number of the matched persistent key on said central database is not identical to said version number of the matched persistent key from said list.

46. A method according to claim 44, wherein step (e) comprises the substeps of:

(a) for each record on said customer database, iteratively comparing each key field stored on said computer-readable medium to the corresponding field of each record on said customer database until a match is found;

(b) copying the persistent key stored on said computer-readable medium that is linked to the matched key field onto said customer database; and

(c) linking the copied persistent key to the matched record on said customer database.

47. A method according to claim 44, wherein step (k) is accomplished by means of a direct table join between said customer database and said central database.

50. A method according to claim 44, wherein steps (i) and (j) comprise the substeps of:

(aa) using a central database manager of which said central database is comprised, for each persistent key in said persistent key list sent by said customer database, polling each of a plurality of physically remote databases comprising said central database, each said physically remote database comprising partial records and a persistent key linked to each partial record, to determine if, for each said physically remote database, any of said partial records resident on said physically remote database are linked to a persistent key matching each of said list of persistent keys;

(bb) for each said partial record so matched, compiling data in said partial record with data from every other partial record from other said physically remote databases that is also linked to a persistent key resident on that said physically remote database that also matches said one persistent key from said persistent key list; and

(cc) creating from said compiled data a record on said central database that contains all said data from each of said matched partial records and is linked to said persistent key that was linked to each of said matched partial records.

48. A method for the creation, enhancement and update of data stored at a remote location using data logically stored at a central location comprising the steps of:

(a) storing on a central database a plurality of records, said records comprising a plurality of fields;

(b) creating and linking to each said record a persistent key, each said persistent key being permanent and distinguishable from every other said persistent key, and the value of each of said persistent key being independent of the physical storage location of each said record;

(c) sending a data request to said central database from a customer database, said data request specifying the type of said records required for inclusion on said customer database;

(d) searching each said record on said central database for the data requested in said data request;

(e) compiling all said records containing the data requested in said data request;

(f) sending said compiled records to said customer database, along with that one of said persistent keys linked to each of said compiled records on said central database; and

(g) storing said compiled records with said linked persistent keys on said customer database.

49. A method according to claim 48, wherein step (f) is accomplished by means of a direct table join between said customer database and said central database.

51. A method for the creation, enhancement and update of data stored at a remote location using data logically stored at a central location comprising the steps of:

(a) storing on a central database a plurality of records, said records comprising a plurality of fields;

(b) creating and linking to each said record a persistent key, each said persistent key being permanent and distinguishable from every other said persistent key, and the value of each of said persistent key being independent of the physical storage location of each said record;

(c) copying each of said persistent keys and a key field found in said record linked to each said persistent key from said central database to a computer-readable medium;

(d) interfacing said computer-readable medium with a customer server, said customer server communicatively connected to a customer database, said customer database comprising a plurality of said records;

(e) using said customer server, for each record on said customer database, overlaying onto said record that one persistent key linked to said key field resident on said computer-readable medium whose data matches the corresponding field in said record on said customer database;

(f) using said customer server, compiling a list of said persistent keys resident on said customer database;

(g) sending said list of persistent keys from said customer server to an application server communicatively connected to said central database and said customer server;

(h) sending a data request from said customer server to a web server, said web server being communicatively connected to said application server and said customer server, said data request specifying the type of update or enhancement required for said records on said customer database;

(i) interpreting said data request using said web server, and passing said data request to said application server;

(j) using said application server, matching each of said list of persistent keys from said customer database with the corresponding said persistent key resident on said central database;

(k) using said application server, for each said matched persistent key on said central database, retrieving the data requested in said data request from the record on said central database linked to each said matched persistent key;

(l) compiling all said requested data and sending said compiled requested data from said application server to said customer server; and

(m) using said customer server, integrating said requested data into said customer database.

52. A method according to claim 51, wherein all information sent between said customer database and said central database is sent via a global computer communications network.

53. A method according to claim 51, wherein all information sent between said customer database and said central database is sent via a direct transmission line.

54. A method for the analysis and summation of information stored at physically remote databases, comprising the steps of:

(a) using a bi-directional transfer means, establishing a connection between a third-party server and a central database, said central database comprising a plurality of records, each of said plurality of records on said central database being linked to a persistent key, each one of said persistent keys being permanent and distinguishable from all other said persistent keys resident on said central database, and the value of each of said persistent key being independent of the physical storage location of each said record;

(b) using said bi-directional transfer means, establishing a connection between said third-party server and a customer database, said customer database comprising a plurality of records, each of said plurality of records being linked to a persistent key, each of said persistent keys being matchable to a persistent key resident on said central database that is linked to a record that contains data related to that data in said record on said customer database to which that one of said persistent keys is linked; and

(c) using said persistent keys resident on said central database and said customer database, matching said records linked to said persistent keys to form a single multidimensional database accessible by said third-party server.

55. A plurality of persistent keys each linked to a data structure stored on a database, wherein each of said plurality of persistent keys is permanent and distinguishable from all other said persistent keys, the value of each of said persistent keys is independent of the physical storage location of each said data structure, and each of said plurality of persistent keys comprising:

(a) an entity code, said entity code denoting the type of data stored in said data structure linked to said persistent key; and

(b) a unique number, said unique number distinguishing each of said plurality of persistent keys from every other one of said plurality of persistent keys that have an identical entity code.