Information exchange engine providing a critical infrastructure layer and methods of use thereof

• US 8,099,435 B2
• Filed: 07/31/2010
• Issued: 01/17/2012
• Est. Priority Date: 12/20/1999
• Status: Expired due to Fees

• Current Assignee: PlanetID, LLC
• Original Assignee: Ajit S. Shah, Dave Hu, Joyce Thom, Madhukar Thakur
• Inventors: Thom, Joyce, Hu, Dave, Thakur, Madhukar, Shah, Ajit S.
• Primary Examiner(s): Woo, Isaac M
• Application Number:
  US12/848,166
• Publication Number:
  US 20100293138A1
• Time in Patent Office: 535 Days
• Field of Search: 707600-831
• US Class Current: 707/791
• CPC Class Codes: G06F 16/00 Information retrieval; Database structures therefor; File system structures therefor
• CPC Class Codes: G06F 16/21 Design, administration or maintenance of databases
• CPC Class Codes: G06F 16/22 Indexing; Data structures therefor; Storage structures
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database
• CPC Class Codes: G06F 16/284 Relational databases
• CPC Class Codes: G06F 16/285 Clustering or classification
• CPC Class Codes: G06F 16/288 Entity relationship models
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A virtual record manager and a data exchange engine are provided for dynamically defining data records in a database and for dynamically allocating instances of defined data records. These components are capable of mediating between the database and application and client interface layers to facilitate exchange of information over a network. Embodiments are configured to allow complex data records having a plurality of related fields, and to allow management and exchange of information at both the data field level and data record level.

Claims

1. A data exchange engine for use with a database, comprising:

a virtual record manager coupled to the database and configured to manage the storage of at least one data record in the database, the data record being managed at an individual data field level;

a data exchange engine coupled to the database and configured to support an exchange of the information in at least one data field between at least two parties, the exchange being based on a relationship between the parties, the relationship being represented in the database;

wherein the virtual record manager is configured to utilize a virtual object to manage the storage of the data record, the virtual object defining a data record structure being a logical grouping of individual data fields, the virtual object being described as a virtual object type whereby the virtual object type is configured to provide a description of the data record structure; and

wherein utilization of the virtual object allows a unique type of data record to be created substantially instantaneous.

2. The engine of claim 1 wherein the virtual record manager is configured to support a complex data record, the complex data record comprising a plurality of related data fields.

3. The engine of claim 2 wherein the data exchange engine is configured to support the exchange of the information in the complex data record.

4. The engine of claim 1 wherein the virtual record manager is configured to allow a unique type of data record to be created substantially instantaneous.

5. The engine of claim 1 wherein the virtual record manager is configured to allow an instance of the data record to be allocated to the database substantially instantaneous.

6. The engine of claim 1 wherein the virtual record manager is configured to assign each data field a unique identifier.

7. The engine of claim 1 wherein the virtual record manager is configured to associate each data field with a data record type and to manage each data field according to the data record type.

8. The engine of claim 1 wherein utilization of the virtual object allows an instance of the data record to be allocated to the database substantially instantaneous.

9. The engine of claim 1 wherein the virtual record manager and the data exchange engine are configured to provide a means for a party to exchange specific data fields with all other parties with which the party has a relationship.