×

Two-layer data architecture for reservation management systems

  • US 8,805,711 B2
  • Filed: 12/22/2009
  • Issued: 08/12/2014
  • Est. Priority Date: 12/22/2009
  • Status: Expired due to Fees
First Claim
Patent Images

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.

View all claims
  • 1 Assignment
Timeline View
Assignment View
    ×
    ×