×

Software Architecture and Database for Integrated Travel Itinerary and Related Reservation System Components

  • US 20070260495A1
  • Filed: 10/23/2006
  • Published: 11/08/2007
  • Est. Priority Date: 10/21/2005
  • Status: Abandoned Application
First Claim
Patent Images

1. A travel reservation database and system, including:

  • a dynamic web page generation server coupled to a network, including logic and resources adapted to respond to a user request by generating web pages that present descriptions of a unit or a travel service without loading the unit or travel-related service descriptions into frame or IFrame web page structures;

    a hub server coupled by the dynamic web page generation server to the user, the hub server including logic and resources to retrieve unit and travel-related service descriptions and to persist a reservation item for the unit or the travel-related service in an updatable itinerary data structure, responsive to user requests;

    a unit availability database, including at least unit descriptions and availability, coupled to the hub server;

    a VRM unit maintenance server that provides a plurality of different VRM operators access to the unit availability database, including logic and resources to populate the unit availability database with the unit descriptions of units operated by the VRM operators;

    one or more reservation connector components that couple the hub server to a plurality of distinct data sources that list travel-related services and accept reservations for the listed travel-related services;

    an updatable itinerary database, coupled to the hub server, in which the hub server persists confirmations of reservation items for the units and travel-related services, using the updatable itinerary data structure; and

    an updatable itinerary access server, coupled between the network and the updatable itinerary database, including logic and resources to generate a user interface page including a formatted version of items in a particular updatable itinerary data structure, with at least one control for adding an item to the particular updatable itinerary data structure; and

    invoke the hub server in a session separate from when reservation items originally were persisted in the particular updatable itinerary data structure, responsive to a message indicating user selection of the control for adding the item, the hub server adding additional reservation items to the particular updatable itinerary data structure.

View all claims
  • 3 Assignments
Timeline View
Assignment View
    ×
    ×