Two-layer data architecture for reservation management systems
First Claim
1. A reservation management information processing system, comprising:
- at least one processing node comprising a memory and a processor, wherein the at least one processing node further comprises a set of reservation processing and transaction modules that manage and process reservation requests and inquiries;
at least one general purpose database communicatively coupled to the at least one processing node, wherein the at least one general purpose database comprises a set of pre-allocated tables of fixed length records, wherein the set of pre-allocated tables are pre-populated with fixed length records prior to being populated with data, wherein the fixed length records are independently accessible by the set of reservation processing and transaction modules and are independently lockable by the general purpose database, wherein the general purpose database is configured to store reservation related information within one or more of the fixed length records based on receiving a record update operation from the set of reservation processing and transaction modules, and wherein the set of reservation processing and transaction modules are configured to track which of the fixed length records are being utilized to store reservation related information; and
at least one persistent storage device communicatively coupled to the at least one processing node, wherein the general purpose database persistently stores the set of pre-allocated tables of fixed length records on the at least one persistent storage device,wherein the at least one processing node is configured to perform a method comprisingdetermining that at least one user is interacting with at least one reservation inventory resource stored in a first fixed length record of at least a first of the set of pre-allocated tables;
identifying at least a second fixed length record in at least a second of the set of pre-allocated tables that is available for use, wherein the second fixed length record is absent reservation related information; and
temporarily moving, via an update record transaction, the at least one reservation inventory resource from the first fixed length record to the second fixed length record for a given amount of time, wherein at least one of a set of reservation processing and transaction modules prevents the second fixed length record from being associated with another user.
1 Assignment
0 Petitions
Accused Products
Abstract
A reservation management system includes at least one processing node that includes a memory and a processor. The at least one processing node further includes a set of reservation processing and transaction modules that manage and process reservation requests and inquiries. At least one general purpose database is communicatively coupled to the at least one processing node. The at least one general purpose database includes a set of pre-allocated tables of fixed length records. At least one persistent storage device is communicatively coupled to the at least one processing node. The general purpose database persistently stores the set of pre-allocated tables of fixed length records on the at least one persistent storage device.
-
Citations
24 Claims
-
1. A reservation management information processing system, comprising:
-
at least one processing node comprising a memory and a processor, wherein the at least one processing node further comprises a set of reservation processing and transaction modules that manage and process reservation requests and inquiries; at least one general purpose database communicatively coupled to the at least one processing node, wherein the at least one general purpose database comprises a set of pre-allocated tables of fixed length records, wherein the set of pre-allocated tables are pre-populated with fixed length records prior to being populated with data, wherein the fixed length records are independently accessible by the set of reservation processing and transaction modules and are independently lockable by the general purpose database, wherein the general purpose database is configured to store reservation related information within one or more of the fixed length records based on receiving a record update operation from the set of reservation processing and transaction modules, and wherein the set of reservation processing and transaction modules are configured to track which of the fixed length records are being utilized to store reservation related information; and at least one persistent storage device communicatively coupled to the at least one processing node, wherein the general purpose database persistently stores the set of pre-allocated tables of fixed length records on the at least one persistent storage device, wherein the at least one processing node is configured to perform a method comprising determining that at least one user is interacting with at least one reservation inventory resource stored in a first fixed length record of at least a first of the set of pre-allocated tables; identifying at least a second fixed length record in at least a second of the set of pre-allocated tables that is available for use, wherein the second fixed length record is absent reservation related information; and temporarily moving, via an update record transaction, the at least one reservation inventory resource from the first fixed length record to the second fixed length record for a given amount of time, wherein at least one of a set of reservation processing and transaction modules prevents the second fixed length record from being associated with another user. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9)
-
-
10. A computer implemented method for continuously and persistently managing a reservation system, the computer implemented method comprising:
-
pre-allocating, by a processor using a general purpose database, a set of tables of fixed length records, wherein the set of tables are pre-populated with fixed length records prior to being populated with data, wherein the fixed length records are configured to store reservation related information based on record update operations, and wherein the fixed length records are independently accessible by a reservation processing module and are independently lockable by the general purpose database, wherein the reservation processing module is independent from the general purpose database; designating, by a processor, at least a first table in the set of pre-allocated tables to store user reservation dialog state information; designating, by a processor, at least a second table in the set of pre-allocated tables to store inventory information; tracking, by the reservation processing module, which of the fixed length records are currently being utilized to store reservation related information; receiving, by a processor using the reservation processing module, a request for a reservation from a user; identifying, based on the receiving and the tracking, at least one fixed length record in the first table that is available for use, wherein the first fixed length record is absent reservation related information; storing, by a processor using the reservation processing module, a set of information associated with a user reservation dialog state in the at least one fixed length record that has been identified in the first table as an update to the first table, wherein the storing at least comprises temporarily storing, via an update record transaction, at least one reservation inventory resource from a fixed length record of the second table in the at least one fixed length record that has been identified for a given amount of time; and managing, by a processor using the reservation processing module, the request from the user based on a set of reservation state information within the set of tables comprising at least inventory information in the second table. - View Dependent Claims (11, 12, 13, 14, 15)
-
-
16. A computer implemented method for continuously and persistently managing a reservation system, the computer implemented method comprising:
-
pre-allocating, by a processor using a general purpose database, a set of tables of uniquely identified fixed size records, wherein the set of tables are pre-populated with uniquely identified fixed size records prior to being populated with data wherein the uniquely identified fixed size records are configured to store reservation related information based on record update operations, and wherein the uniquely identified fixed size records are independently accessible by a reservation processing module and are independently lockable by the general purpose database, wherein the reservation processing module is independent from the general purpose database; managing, by a processor using the reservation processing module, the uniquely identified fixed size records, wherein the managing comprises at least tracking which of the uniquely identified fixed size records are currently being utilized to store reservation related information; receiving, by a processor using the reservation processing module, a request from a user for a reservation; identifying, based on the receiving, at least one uniquely identified fixed size record in a first of the set of tables that is available for use, wherein the uniquely identified fixed size record is absent reservation related information; updating via an update record transaction, by a processor using the reservation processing module, the at least one uniquely identified fixed size record that has been identified with a set of user reservation dialog information, wherein the set of user reservation dialog information comprises at least user identification information and a set of inventory resources from one or more uniquely identified fixed size records in a second of the set of tables, wherein the set of user reservation dialog information is temporarily stored within the at least one record that has been identified for a given amount of time; persistently storing, based on the updating, the at least one uniquely identified fixed size record that has been identified on at least one persistent storage device at one or more given intervals of time; updating via an update record transaction, by a processor using the reservation processing module, the one or more uniquely identified fixed size records in the second of the set of tables based on updating the at least one uniquely identified fixed size record in the first of the set of tables; and persistently storing the one or more uniquely identified fixed size records from the second of the set of tables on at least one persistent storage device, at one or more given intervals of time. - View Dependent Claims (17, 18, 19, 20, 21, 22, 23, 24)
-
Specification