| |
 |
Easily expandable data processing system and method |
| RE40520 |
Easily expandable data processing system and method
|
|
| Patent Drawings: | |
| Inventor: |
Doktor |
| Date Issued: |
September 23, 2008 |
| Application: |
11/152,835 |
| Filed: |
June 14, 2005 |
| Inventors: |
Doktor; Karol (Wheelers Hill, AU)
|
| Assignee: |
Financial Systems Technology (Intellectual Property) Pty Ltd (Malvern, Victoria, AU) |
| Primary Examiner: |
Wassum; Luke S |
| Assistant Examiner: |
|
| Attorney Or Agent: |
Allen, Dyer, Doppelt, Milbrath & Gilchrist, P.A. |
| U.S. Class: |
707/4; 707/2 |
| Field Of Search: |
707/2; 707/3; 707/101; 707/103Y |
| International Class: |
G06F 17/30 |
| U.S Patent Documents: |
|
| Foreign Patent Documents: |
WO 00/07354; WO 01/15811 |
| Other References: |
Rudolf Munz, "Design of The Well System", 1980, Noth-Holland Publishing Company, pp. 505-522. cited by examiner.
Tsichritzis, D. "LSL: A Link and Selector Language", Proceedings of the ACM-SIGMOD International Conference on Management of Data, Jun. 2-4, 1976, pp. 123-133. cited by examiner.
Munz, R. "The Well System: A Multi-User Database System Based on Binary Relationships and Graph-Pattern-Matching", Information Systems, vol. 3, 1978, pp. 99-115. cited by examiner.
Munz, R. "Design of the Well System", in Entity-Relationship Approach to Systems Analysis and Design, Proceedings of the 1st International Conference on the Entity-Relationship Approach, Chen, P. ed., 1979, pp. 502-522. cited by examiner.
Malhotra, A. et al. "Implementing an Entity-Relationship Language on a Relational Data Base", IBM Research Report 12134 (#54499), Aug. 27, 1986. cited by examiner.
Rybinski, H. "On First-Order-Logic Databases", ACM Transactions on Database Systems (TODS), vol. 12, No. 3, Sep. 1987, pp. 325-349. cited by examiner.
University of Texas "Data Modeling: the Entity-Relationship Model", downloaded from www.utexas.edu/its/archive/windows/database/datamodeling/dm/erintro.html, Feb. 29, 2004. cited by examiner.
University of Texas "Data Modeling: Primary and Foreign Keys", downloaded from www.utexas.edu/its/archive/windows/database/datamodeling/dm/keys.htm- l, Feb. 29, 2004. cited by examiner.
Curran, T. "EE221--Database Systems & Software Analysis and Design", course notes, Dublin City University, School of Electronic Engineering, downloaded from www.eeng.dcu.ie/.about.ee221-DB-2.pdf, 2007. cited by examiner.
Microsoft Corporation, "Relational Database Components", tutorial, downloaded from msdn.microsoft.com/en-us/library/aa174501(SQL.80).aspx, 2007. cited by examiner.
Korth and Silberschatz, Database System Concepts, McGraw-Hill Book Company (New York, 1986),pp. 45-105; pp. 301-323. cited by other.
"Extended Disjunctive Normal Form for Efficient Processing of Recursive Logic Queries", IBM Technical Disclosure Bulletin, vol. 30 No. 1, Jun. 1987 pp. 360-366. cited by other.
Yu et al, "Automatic Knowledge Acquisition and Maintenance For Semantic Query Optimization", IEEE Transactions on Knowledge and Data Engrn, V:1, No. 3 Sep. 1989, pp. 362-375. cited by other.
Kifer et al, "Sygraf: Implementing Logic Programs in a Database Style" IEEE Transactions on Software Engnrn. v:14, N7, Jul. 1988 pp. 92-935. cited by other.
El-Sharkawi et al, "The Architecture and Implementation of Enli: An Example-Based Natural Language Assisted Interface", Parbase 90 Intl. Conf. on Databases, Parallel Architectures & Their Applications, Mar. 7-9, 1990. cited by other.
Wilschut et al, "Pipelining in Query Execution" Parbase-90 Intl. Conf. on Databases, Parallel Architectures and Their Applications, Mar. 7-9, 1990 p. 562. cited by other.
Banerjee et al., "Data Model Issues for Object-Oriented Applications", ACM Transactions on Office Information Systems, vol. 5, No. 1, Jan. 1987, pp. 3-26. cited by other.
Blakely et al., "Experiences Buildig the Open OODB Query Optimizer", 1993, pp. 287-296. cited by other.
Markowitz et al., "Representing Extended Entity-Relationship Structures in Relational Databases: A Modular Approach", ACM Transactions on Office Information Systems, vol. 17, No. 3, Sep. 1992, pp. 423-464. cited by other.
Teorey et al., "A Logical Design Methodology for Relational Databases Using the Extended Entity-Relationship Model", Computing Surveys, vol. 18, No. 2, Jun. 1986, pp. 197-222. cited by other.
Chen, Peter, "Entity-Relationship Approach to Systems Analysis and Design", Proceedings of the International Conference in Los Angeles, Dec. 10-12, 1979, pp. 237-257. cited by other.
Blakeley et al., "Experiences Building the Open OODB Query Optimizer", 1993, pp. 287-296. cited by other.
Zand et al., "A Survey of Current Object-Oriented Databases", Data Base Advances, Feb. 1995, vol. 26, No. 1, pp. 14-29. cited by other.
Straube et al., "Queries and Query Processing in Object-Oriented Database Systems", ACM Transactions on Information Systems, vol. 8, No. 4, Oct. 1990, pp. 387-430. cited by other.
Kim et al., "Semantics and Implementation of Schema Evolution in Object-Oriented Databases", 1987, pp. 311-322. cited by other.
Kim et al., "Composite Object Support in an Object-Oriented Database System", OOPSLA '87 Proceedings, Oct. 4-8, 1987, pp. 118-125. cited by other.
Hull et al.,"Semantic Database Modeling: Survey, Applications, and Research Issues", ACM Computing Surveys, vol. 19, No. 3, Sep. 1987, pp. 201-260. cited by other.
Nixon et al., "Implementation of a Compiler for a Semantic Data Model: Experiences with Taxis", 1987, pp. 118-131. cited by other.
Codd, E., "Extending the Database Relational Model to Capture More Meaning", ACM Transactions on Database Systems, vol. 4, No. 4, Dec. 1979, pp. 397-434. cited by other.
Peckham et al., "Semantic Data Models", Acm Computing Surveys, vol. 20, No. 3, Sep. 1988, pp. 153-189. cited by other.
Tsurt et al., "An Implementation of GEM--supporting a semantic data model on a relational back-end.", 1984, pp. 286-295. cited by other.
Wilkinson et al., "The Iris Architecture and Implementation", IEEE Transactions on Knowledge and Data Engineering, vol. 2, No. 1, Mar. 1990, 27 pages. cited by other.
Gamache et al., "Addressing Techniques Used in Database Object managers O.sub.2 and Orion", SIGMOD Record, vol. 24, No. 3, Sep. 1995, pp. 50-55. cited by other.
Kim et al., "Architecture of the Orion Next-Generation Database System", IEEE, 1990, pp. 109-124. cited by other.
Klimbie et al., "Data Base Management", North-Holland Publishing Company, 1974, pp. 1-59. cited by other.
Hudson et al., "Cactis: A Self-Adaptive, Concurrent Implementation of an Object-Oriented Database Management System", ACM Transactions on Database Systems, vol. 14, No. 3, Sep. 1989, pp. 291-321. cited by other.
Annevelink et al., "Object SQL--A Language for the Design and Implementation of Object Databases", Jan. 3, 1994, pp. 1-21. cited by other.
Chen, P., "Entity-Relationship Approach to Information Modeling and Analysis", International Conference in Washington, D.C., Oct. 12-14, 1981, pp. 49-72. cited by other.
Wiederhold, G., "Database Design Appendix B", McGraw-Hill, 2001, pp. 689-698. cited by other.
Hanks, D.R., "The Payoff of Modest Price Adjustments," (Abstract only), Bank Marketing, vol. 12, No. 9, p. 13,, Sep. 1980. cited by other.
Fishman et al., "Overview of the Iris DBMS", Association for Computing Machinery, Inc., pp. 219-250. cited by other.
Halper et al., "An OODB "Part" Relationship Model", 10 pages. cited by other.
Kim et al., "Feature of the Orion Object-Oriented Database System", pp. 251-282. cited by other.
Kim et al., "Evaluation of the Object-relational DBMS Postgres .I. Administrative Data", Computing Science, Oct. 1994, pp. 1-52. cited by other.
Hendler, James A. Expert Sytems: The User Interface. Albex Publishing Corporation. Norwood, NJ. 1988. pp. 31, 46-47, 109-110, 113 and 132-134. cited by other.
Rose, Peter S., et al. Financial Institution, Understanding and Managing Financial Services, 4th Edition, Richard D. Irwin, Inc., 1993. pp. 1-217;328-356;423-446;659-792. cited by other.
Parsaye, Kamran & Chignell, Mark. Expert Systems For Experts. John Wiley & Sons, 1988. pp. 35-60, 177-178, 191-210 and 295-309. cited by other.
Howcroft, "Contemporary issues in UK bank delivery systems"., Inter. Jour. of Service Industry Management, vol. 3, No. 1, pp. 39-56, ISBN 096-4223, 1992. cited by other.
"The Smart Card's Chief Advocate", Credit Card Management, vol. 10, No. 1, p. 26+, ISBN: 0896-9329, 1992. cited by other.
Bharadwaj et al., Determinants of success in service industries: a PIMS-based empirical investigation, Journal of Service Marketing, v7n4, pp. 19-40, 1993, 23 pages from Dialog file 15, acc. # 00813287. cited by other.
Cattell, R. and Rogers, T., "Combining Object-Oriented and Relational Models of Data", 1986 International Workshop on Sep. 26, 1986, pp. 212-213. cited by other.
Rumbaugh, J., "Relations as Semantic Constructs in an Object-Oriented Language", OOPSLA '87 Proceedings, Oct. 4-8, 1987, pp. 466-481. cited by other.
Dewan et al. "Engineering the Object-Relation Database Model in O-Raid", Lecture Notes in Computer Science, 3.sup.rd International Conference--Paris, Jun. 21-23, 1989, pp. 389-403. cited by other.
Blaha et al., "Relational Database Design using an Object-Oriented Methodology", Communications of the ACM, Apr. 1988, vol. 31, No. 4, pp. 414-427. cited by other.
Wiederhold, G., "Views, Objects, and Databases" Computer Database Architecture, Dec. 1986, pp. 37-44. cited by other.
Mark et al., "Metadata Management", Computer Database Architecture, Dec. 1986, pp. 26-36. cited by other.
Osborn et al., "The Design of a relational Database System with Abstract Data Types for Domains", ACM Transactions on Database Systems, vol. 11, No. 3, Sep. 1986, pp. 357-373. cited by other.
Whang et al., "Query Optimization in a Memory-Resident Domain Relational Calculus Database System", ACM Transactions on Database Systems, vol. 15, No. 1, Mar. 1990, pp. 67-95. cited by other.
Finkelstein et al., "Physical Database Design for Relational Databases", ACM Transactions on Database Systems, vol. 13, No. 1, Mar. 1988, pp. 91-128. cited by other.
Takahashi, J., "Hybrid Relations for Database Schema Evolution", IEEE, 1990, pp. 465-470. cited by other.
Khoshaflan, S. and Copeland, G., "Object Identity", Microelectronics and Computer Technology Corporation, pp. 37-46. cited by other.
Rowe, L. and Stonebraker, M., "The POSTGRES Data Model", Computer Science Division, EECS Department, University of California, pp. 1-21. cited by other.
Stonebraker, M. and Moore, D., "Object-Relational DBMSs The Next Great Wave", Morgan Kaufman Publishers, Inc., 1996, pp. 56-61. cited by other.
Anon., "Future of European Payment Systems? Integrating the Card, ATM's, and Eurocheque," (Abstract only), World of Banking, vol. 9, No. 2, p. 19, Mach/Apr. 1990. cited by other.
Nadler, P.S. "Comment: Pitfalls of Relationship Banking," (Abstract only) American Banker, p. 4, Feb. 3, 1992. cited by other.
Stuchfield, N., et al., "Modeling of Profitability of Customer Relationships: Development and Impact of Barclays de Zoete Wedd's Beatrice," Journal of Management Information Systems, vol. 9, No. 2, p. 53, Fall 1992. cited by other.
Toby J. Teorey, et al., A Logical Design Methodology for Relational Databases Using the Extended Entity-Relationship Model, Computing Surveys, vol. 18, No. 2, Jun. 1986, pp. 197-222 ("Teorey"). cited by other.
Daniel R. Dolk, et al., A Relational Information Resource Dictionary System, Computing Practices, Communications of the ACM (Jan. 1987). cited by other.
M.M. Zloof, Query-by-Example: A Data Base Language, IBM Systems Journal, No. 4 (1977). cited by other.
Rudolph Munz, "Das WEB-Modell", (translated pages), pp. 155-156, Fig. 10.2.1, (1976) ("Munz 111"), with English translation. cited by other.
Gio Wiederhold, "Database Design Second Edition", Discloses Definition Tables, Sections 7-3-1, 7-3-7, 7-4-4,7-4-5, and 9-7-6 and Figs. 8-5, 8-7, 8-9 (1995). cited by other.
Pin-Shan Chen, The entity-relationship model--A basis for the enterprise view of data 77 (1977). cited by other.
Mark L. Gillenson, Database Step-by-step 141-42, 2d Ed. (1990). cited by other.
The IBM Dictionary of Computing Terms 87 (8th Ed. 1987). cited by other.
Webster's New World Dictionary of Computer Terms 107 (3d Ed. 1988). cited by other.
Rudolph Munz, "Das WEB-Modell" (English Translated pages), Chapter 10 (1976), 18 pages. cited by other.
Introduction to NonStop SQL, Tandem Computers, May 1988, pp. I-3-19. cited by other.
Adiba et al., "Database Snapshots", Proceedings of the 1980 International Conference on Very Large Data Bases, IEEE 1980, pgs. 86-91. cited by other.
Blakeley et al., "Join Index, Materialized View, and Hybrid-Hash Join: A Performance Analysis", Technical Report No. 280, Indiana University Computer Science Department, IEEE 1990, pgs. 256-263. cited by other.
Elmasri et al., "Fundamentals Of Database Systems", 1989. cited by other.
Hainaut, J. L., "Theoretical And Practical Tools For Data Base Design", Proceedings of the Seventh International Conference on Very Large Data Bases, IEEE 1981, pgs. 215-224. cited by other. |
|
| Abstract: |
Machine automated techniques are described for a method of data processing called Relationships Processing. A computing system is disclosed which provides for the high speed recording and extraction of data objects (entities) and for the development data representing a queried relationship between the entities. The system is expandable to handle the relatively voluminous data bases of large, commercial data repositories. A user defines set of entities and allowed relationships between the entities. The user can expand this set of allowed entities and relationships at any time during the life of the system without reprogramming or compiling of computer program code or disrupting concurrent operational use of the system. Large systems can now be built that are no longer limited to a scope of design requirements known during initial systems development. For a given set of defined relationships the system allows the user to perform complex inquiries (again without programming at the code level) that would normally require multiple nested inquiries to be coded programmatically and would not achieve the performance levels of the Relationships Processor. |
| Claim: |
What is claimed is:
1. A method for retrieving a desired entity of a desired entity type from a relational database, wherein said desired entity is related to a provided entity by a providedrelation type associating an entity type of said provided entity with said desired entity type, said method comprising: retrieving a specific relation type record defining said provided relation type from a relation definition table; retrieving aspecific relation instance record defining a relation of said provided relation type between said provided entity and said desired entity from a relation instance table corresponding to said specific relation type record; retrieving a desired entitytype record containing said desired entity type from an entity definition table, wherein said desired entity type record specifies a desired entity instance table associated with said desired entity type; and retrieving said desired entity from saiddesired entity instance table.
2. The method of claim 1, wherein said relation instance record specifies said desired entity by said desired entity type and a desired record identifier.
3. The method of claim 2, wherein said desired entity is identified by said desired record identifier in said desired entity instance table.
4. The method of claim 1, wherein said retrieving a specific relation .[.type.]. .Iadd.instance .Iaddend.record .[.defining said provided relation type from a relation definition table.]. comprises: retrieving a table identifier for saidrelation instance table from said specific relation type record; and retrieving said specific relation instance record from said relation instance table based on said specific relation type record and said provided entity.
5. The method of claim 1, further comprising retrieving data specifying said provided relation type from an inquiry table.
6. The method of claim 1, further comprising retrieving data specifying said provided entity from an inquiry table.
7. The method of claim 1, further comprising retrieving a second desired entity type record containing a second desired entity type from said entity definition table, wherein said second desired entity type record specifies a second desiredentity instance table associated with said second desired entity type.
8. The method of claim 7, further comprising retrieving a third desired entity type record containing a third desired entity type from said entity definition table, wherein said third desired entity type record specifies a third desired entityinstance table associated with said third desired entity type.
9. The method of claim 1, further comprising retrieving a second specific relation instance record defining a .[.second.]. relation of .[.said.]. .Iadd.a second .Iaddend.provided relation type between said provided entity and said desiredentity from a second relation instance table corresponding to said second .Iadd.provided .Iaddend.specific relation type .[.record.]. .
10. A relational database processing system comprising: an entity definition table containing a first entity type record defining a first entity type; .[.an.]. .Iadd.a .Iaddend.first entity instance table associated with said first entitytype; a plurality of entity instance records stored in said first entity instance table; a relation definition table containing a first relation type record defining a provided relation type; a first relation instance table associated with saidprovided relation type; and a first relation instance record of said provided relation type, said first relation instance record relating a desired entity in one of said entity instance records to a provided entity.
11. The relational database processing system of claim 10, wherein each of said entity instance records is identified by a record identifier.
12. The relational database processing system of claim 10, wherein said first relation .Iadd.instance record .Iaddend.contains a desired record identifier and a desired entity type corresponding to a desired entity instance record containingsaid desired entity.
13. The relational database processing system of claim 10, wherein said first relation type record comprises a table identifier identifying said first relation instance table.
14. The relational database processing system of claim 10, further comprising an inquiry table containing an inquiry record, wherein said inquiry record specifies said provided relation type and said provided entity.
15. The relational database processing system of claim 10 further comprising: a second entity instance table associated with a second entity type; and wherein said entity definition table contains a second entity type record containing saidsecond entity type and associating said second entity instance table with said second entity type.
16. The relational database processing system of claim .[.10.]. .Iadd.15 .Iaddend.further comprising: a third entity instance table associated with a third entity type; and wherein said entity definition table contains a third entity typerecord containing said third entity type and associating said third entity instance table with said third entity type.
17. The relational database processing system of claim 10 further comprising: a second relation instance table associated with a second .[.entity.]. .Iadd.relation .Iaddend.type; and wherein said relation definition table contains a secondrelation type record containing said second relation type and associating said second relation instance table with said second relation type.
18. The relational database processing system of claim .[.10.]. .Iadd.17 .Iaddend.further comprising: a third relation instance table associated with a third .[.entity.]. .Iadd.relation .Iaddend.type; and wherein said relation definitiontable contains a third relation type record containing said third relation type and associating said third relation instance table with said third relation type. |
| Description: |
|
|
|
|
