Software Architecture and Database for Integrated Travel Itinerary and Related Reservation System Components
First Claim
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.
3 Assignments
0 Petitions
Accused Products
Abstract
The present disclosure relates to software and database architectures and features that are adapted to VRMs and computer savvy users who would otherwise go to VRMs. In particular, it relates to an updateable itinerary data structure, method and database system. It further relates to server-side tracking of click-throughs by users presented with advertising, with options for tracking advertising impact beyond making a reservation to fulfillment. It also relates to a search engine optimized technology that integrates dynamic inventory into pages that appear to search indexing bots as static pages, thereby increasing indexing exposure. It provides a tool and method to convert HTML web pages with frames or IFrames into ASP web pages with code behind pages supporting added features.
98 Citations
33 Claims
-
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 Dependent Claims (2, 3, 4)
-
-
5. A method of persisting and updating an updatable itinerary data structure that records online negotiations between a consumer and multiple distinct travel-related vendors, including:
-
identifying a travel-related subject matter of interest;
identifying purchase categories within the travel-related subject matter;
for at least two particular purchase categories, identifying one or more relevant vendors;
in a first network session, intermediating negotiation online between a user or user'"'"'s agent (collectively referred to as the user) and at least first and second vendors in different purchase categories, the first and second vendors being distinct, including for a vendor sending the user the vendor'"'"'s offerings, including availability and pricing;
receiving the user'"'"'s selection of a particular offering;
channeling messages between the vendor and the user;
persisting, as an item in memory of an intermediator'"'"'s server, confirmation of the intermediated negotiation, the item forming part of an updatable itinerary data structure;
in a second network session with the user, accessing the updatable itinerary data structure and sending the user a formatted version of items in the updatable itinerary data structure with at least one control for adding an item;
responsive to a message indicating selection of the control for adding the item, repeating the sending, receiving, channeling and persisting actions, thereby adding to the updatable itinerary data structure, as additional items, confirmations of additional intermediated online negotiations with one or more additional vendors. - View Dependent Claims (6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 26)
-
-
25. A method of persisting and updating an updatable itinerary data structure that records online negotiations and renegotiations between a consumer and multiple independent travel-related vendors, including:
-
identifying a travel-related subject matter of interest;
identifying purchase categories within the travel-related subject matter;
for at least two particular purchase categories, identifying one or more relevant vendors;
in a first network session, intermediating negotiations online between a user or user'"'"'s agent (collectively referred to as the user) and at least first and second vendors in different purchase categories, the first and second vendors being distinct, including for a vendor sending the user the vendor'"'"'s offerings, including availability and pricing;
receiving the user'"'"'s selection of a particular offering;
channeling messages between the vendor and the user;
persisting, as an item in memory of an intermediator'"'"'s server, confirmation of the intermediated negotiation, the item forming part of an updatable itinerary data structure;
in a second network session with the user, accessing the updatable itinerary data structure and sending the user a formatted version of items in the updatable itinerary data structure with at least one control for renegotiating an item;
responsive to a message indicating selection of the control for renegotiating the item, reopening negotiation between the user and at least one vendor; and
intermediating renegotiation online by repeating the sending, receiving, channeling and persisting actions, thereby changing the renegotiated item and adding a confirmation of the renegotiation to the updatable itinerary data structure.
-
-
27. A method of tracking effective response to travel advertising through fulfillment, including:
-
receiving electronically at a web site a referral of a user in response to advertising;
determining from the electronically received referral an advertising stimulus leading to the user referral;
initiating an intermediated online negotiation between the user and a particular vendor selected in response to the advertising, including sending the selected vendor'"'"'s offerings, including availability and pricing;
receiving a selection of a particular offering;
channeling messages between the selected vendor and the user;
persisting as an item in memory of an intermediator'"'"'s server confirmation of the intermediated negotiations, the item forming part of an updatable itinerary, and an identification of the advertising stimulus;
adding to the updatable itinerary as additional items results of additional intermediated online negotiations with one or more additional vendors in additional purchase categories;
making availability via a network of the updatable itinerary to the user; and
after a date for fulfillment of the items on the updatable itinerary passes, electronically reporting fulfillment without cancellation to the vendors with the identification of the advertising stimulus. - View Dependent Claims (28, 29)
-
-
30. A dynamic webpage generation server, including:
-
at least one webpage including at least one content conveyer object contained in memory accessible to the dynamic webpage generation server, wherein parameters of the content conveyer object specify a content server and parameters to pass the content server;
a browser emulation component coupled to the webpage generation server that includes logic and resources adapted to request an HTML page from the content server specified in the content conveyer object; and
receive the HTML page from the content server;
a dynamic merge component operatively coupled to the browser emulation component and the dynamic webpage generation server that includes logic and resources adapted to strip away wrapper tags from the HTML page, leaving an HTML text; and
insert the HTML text in place of the content conveyer object in webpage, thereby producing a dynamically updated webpage; and
a publishing component operatively coupled to the browser dynamic merge component and the dynamic webpage generation server including logic and resources that, responsive to a request message, retrieve the at least one webpage, invoke the browser emulation component, invoke the dynamic merge component, and publish a dynamically updated webpage. - View Dependent Claims (32, 33)
-
-
31. A method of integrating into a web site at a first URL catalog content hosted at a second URL, including:
-
encoding a first web page of the first web site to invoke server side code responsive to a request for the first web page, the server side code adapted to dynamically update content of the first web page;
upon receiving a request for the first web page, dynamically updating content of the first web page, including invoking the server side code;
emulating a browser making a request to a catalog content server hosted at the second URL and requesting data to be returned as an HTML page;
receiving the HTML page from the second URL and removing wrapper tags, leaving the requested data in HTML format;
dynamically updating the content of the first web page by inserting the requested data in HTML format into the first web page; and
returning the dynamically updated first web page responsive to the request.
-
Specification