WO2013082151A1

WO2013082151A1 - Layover management system and method

Info

Publication number: WO2013082151A1
Application number: PCT/US2012/066850
Authority: WO
Inventors: Tatevik SHAHBAZIAN; Sargis MAKARYAN
Original assignee: Smart Layover
Priority date: 2011-11-29
Filing date: 2012-11-28
Publication date: 2013-06-06

Abstract

Method or system for reservation and booking of hotel rooms per hour, conference rooms at hotels per hour, sightseeing activities, rental cars or equipment per hour, and other services per hour (such as WIFI, SPA services at hotels nearby, etc.) for a layover (the time that available between arriving flight and boarding the next flight), or in the case of flight delays or flight cancellation, detecting such condition and sending notification to the client via email, SMS, or application push notification with suggestion of booking of aforementioned products or services.

Description

LAYOVER MANAGEMENT SYSTEM AND METHOD

BACKGROUND

Technical Field

The present disclosure relates generally to the field of travel reservations, and, more specifically, to a system and method that detects layovers at the time of and after the booking of transportation, such as commercial airline flights, with connections, flight delays or flight cancellations, and offers for the layover period at the layover location.

Description of the Related Art

Airline travel from city to city can result in a traveler having to wait between flights at the airport. In some situations a traveler may be forced to wait for several hours during the daytime and occasionally overnight. Each such extended stop on a trip is known as a layover.

Planned trips may result in interruptions, delays, or flight changes due to weather, aircraft maintenance problems, and other issues. Airlines often make schedule changes weeks in advance, although changes are sometimes made merely hours in advance, and carriers may make subsequent changes that reverse the prior changes.

Over the years, many travelers experience such layovers, and they are forced to spend time on a bench at the airport or book a hotel or other products or services by phone, generally paying the full daily rate.

BRIEF SUMMARY

In accordance with the present disclosure, a system and method is provided that detects a layover during and after the booking process and offers the user products and services commensurate with the location, time, and duration of the layover. The advantage of the method and system is it reduces travel inconvenience as much as possible when the user is booking an itinerary that involves one or more layovers, or when the user's itinerary is affected by flight delays or flight cancellation in such a way that it creates a layover at one or more airports.

The system and method are configured to detect a layover during and after a booking process of the flight ticket, or to detect the flight delays, and flight cancelations in real time. When a layover is detected, the system and method automatically offers products and services at the layover location for the duration of layover (such as a hotel room, sightseeing tours, deals at airport terminals or in the layover city, vehicle rentals, and other products and services). For each layover, in order to make a trip more convenient, the user will have the option to book or purchase offered products or services.

In accordance with another aspect of the present disclosure, the system and method scans or parses a user's emails to detect one or more layovers and to determine the location, date, time, and duration of the one or more layovers. A user may allow the system to access the user's email account or the user may provide the emails to the system for layover detection and offerings.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The foregoing and other features and advantages of the present disclosure will be more readily appreciated as the same become better understood from the following detailed description when taken in conjunction with the accompanying drawings, wherein:

Figure 1 is a data flow diagram of a system formed in accordance with the present disclosure;

Figure 2 is a block diagram illustrating a method and process of making reservations and booking travel services and identifying a layover and providing offerings of additional products and services during the layover; Figure 3 is a block diagram illustrating a method of inventory updating for integrated travel inventory providers;

Figure 4 is a block diagram illustrating a method of inventory updating for travel inventory providers that are integrated with GDS;

Figure 5 is a block diagram illustrating a method of inventory updating for non-integrated travel inventory providers; and

Figure 6 is a block diagram illustrating a method of searching for inventory when a system is integrated with GDS.

DETAILED DESCRIPTION

In the following description, certain specific details are set forth in order to provide a thorough understanding of various disclosed embodiments. However, one skilled in the relevant art will recognize that embodiments may be practiced without one or more of these specific details, or with other methods, components, materials, etc.

Unless the context requires otherwise, throughout the specification and claims which follow, the word "comprise" and variations thereof, such as, "comprises" and "comprising" are to be construed in an open, inclusive sense, that is as "including, but not limited to."

Reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

As used in this specification and the appended claims, the singular forms "a," "an," and "the" include plural referents unless the content clearly dictates otherwise. It should also be noted that the term "or" is generally employed in its broadest sense, that is as meaning "and/or" unless the content clearly dictates otherwise.

The headings and Abstract of the Disclosure provided herein are for convenience only and do not interpret the scope or meaning of the embodiments.

Throughout the description the term "user" is intended to embrace a traveler, an agent of the traveler, such as a travel agent, a travel reservation service, such as those provided by the carriers or travel services providers, and any other person, company, or entity, such as an automated service that is researching, reserving or booking travel.

The present disclosure relates generally to travel selling systems such as Internet Distribution Systems and services (e.g., Online Travel

Agencies, Travel supplier's websites) and Travel Management Companies. More specifically, the present disclosure relates to a method for performing data processing operations to manage a user's itinerary involving layovers of varying duration and offering products and services for the layover location and duration.

A computerized system for detecting layovers is provided that is configured to offer to users different products and services, such as hotel room per hour, car rental per hour, etc., which will allow a user to book or purchase the afore-mentioned products and services during the booking process or post booking, or if delay or flight cancellation has been detected in the itinerary. These offerings can be obtained from the system database, directly from the providers of the products and services, or from a combination of the system database and the providers.

In accordance with one aspect of the present disclosure, the system and method automates offers of hotel room per hour, car and other product rentals, as well as purchasing other products and services during layover to improve user experience and lower inconvenience if one or more layovers occur in the itinerary. During or after or both during and after the travel reservation process, such as for flights, one or more travel seller systems send information about the potential itinerary and user preferences, and where applicable the group of users, to the layover system. The layover system then accurately determines the layover location, date, time, and duration of the layover. Based on that information and any information about the user (or traveler if the user is not the traveler), the layover system uses a database to match all offerings based on rules and availability at the layover location. The matching results are then sent to the user electronically for display, print out, or forwarding. Users may select one or more of the offerings and proceed with checkout.

In accordance with one aspect of the present disclosure, the system can also track flight changes in the real time. If the flight changes result in changes to any of the product and service offerings, the system updates the offerings. In accordance with one aspect of the present disclosure, the system notifies the vendors and service providers about the change, and the

notification will generate a revised list or new list of product and service offerings at the layover location.

In accordance with a further aspect of the present disclosure, the system can also scan emails of the user (either forwarded by the user or by accessing email electronically) and detect layover details. Based on the detected information (such as each layover location, date, time, and duration) and any information about the user, the layover system uses a database to match all offerings based on rules and availability at the layover location. The matching results are then sent to the user electronically for display, print out, or forwarding. Users may select one or more of the offerings and proceed with checkout.

The system operates internally on a travel inventory model (hotel or motel rooms, vehicles, equipment, event tickets, deals and discount offerings, etc.), which receives accurate revisions, updates, and new offerings on a continuous or continual basis with respect to fares, pricing, availability, and business rules. Business can include, without limitation, rules regarding discounts, number of persons, length of stay, membership requirements and benefits, redemption of points and coupons, and the like. In the context of this disclosure, "continual" means on a periodic bases, and "continuous" means without cessation.

The process utilizes the following subsystems: A first subsystem is responsible for replication and storage in an electronic database a travel inventory that includes availability, description, price (for example, lodging (hotels, motels, room rentals), vehicle rentals (such as without limitation auto, moped, motorcycle, bicycle, truck, motor home, and watercraft), and service providers). It is also configured to detect any availability changes in order to prevent errors such as double booking of a product or service. This subsystem also connects directly to external interfaces provided by third party inventory suppliers or providers, which allows accessing current travel inventory in real time without storing the data in a database that is local to the system.

A second subsystem receives layover information, user preferences, and number of users traveling together, applies additional business rules to determine window of opportunities for offerings during layover and it manages reservation and booking, manages the existing reservation of hotel rooms, product rentals or services, and finally issues or re-issues a new reservation and notifies the user as well as service provider (aka vendor).

A third subsystem is configured to detect any real-time flight changes that creates a new layover for travelers or affects the time and duration of the planned layover of the traveler. The system then acts on that updated or revised data to modify the offerings.

A fourth subsystem is configured to analyze emails of the user and detect layover information in the emails. This subsystem is configured to access a user's email account that is linked with the email or to receive emails directly from the user and detect the layover information in the emails. The technology for analyzing emails and building an itinerary therefrom is known, such as the online Triplt system offered by Concur Technologies, Inc. However, this system merely builds an itinerary and does not identify the location, date, time, and duration of layovers and produce product offerings related to the layover or enable a user to reserve, rent, or purchase products and services therefrom.

The third and fourth subsystems described above are optional or alternative embodiments and are not required for the first and second

subsystems to operate together and provide the offers to the user.

Hence, in summary, in accordance with one aspect of the present disclosure, the system includes a first subsystem configured to receive and store in an electronic database at least one travel provider's schedule data; receive and store in the electronic database at least one provider's offering of products and services; and a second subsystem configured to: detect at least one layover in a user's travel itinerary; determine the at least one layover location, date, time, and duration; search the electronic database and

identifying products and services available during the at least one layover; and provide information to the user about products and services identified as available during the at least one layover.

In accordance with other aspects of the foregoing system, (1 ) the third subsystem is configured to detect in real-time flight changes that create at least one new layover or that affect the time and duration of an existing at least one layover; (2) the first subsystem is configured to detect any availability changes in the identified products and services in order to prevent double booking of at least one product or service; (3) the first subsystem is configured to detect flight information during flight booking process that create at least one layover; and (4) the second subsystem is configured to: obtain user

preferences; identify number of users traveling together; apply additional business rules to determine at least one window of opportunity for products and services during the at least one layover; manage reservation and booking of travel and other services; and notify the user and product and service providers. In accordance with the present disclosure, a computer system is provided that is configured to: detect at least one layover in a user's travel itinerary; determine the at least one layover location, date, time, and duration; search for and identifying products and services available during the at least one layover; and provide information to the user about products and services identified as available during the at least one layover.

The foregoing computer system can further be configured to perform one or more of the following: (1 ) detect changes in the user's travel itinerary and, when changes in the user's travel itinerary are detected, to notify the user of changes in the user's travel itinerary; (2) detect changes in the at least one layover location, date, time, and duration resulting from changes detected in the user's travel itinerary to determine at least one new layover, and to search for and identify products and services available during the at least one new layover; (3) initially create an inventory of products and services, and to store at least a portion of the inventory of products and services in a database; (4) contact providers of products and services on at least a continual basis to update the inventory of products and services; (5) receive an email from a user, and identify from the email the user's travel itinerary; and (6) link electronically to a user's email account, and check the user's email account to detect the user's travel itinerary in the user's email.

As will be understood from the following, a method is provided that includes: detecting at least one layover in a user's travel itinerary;

determining the at least one layover location, date, time, and duration;

searching for and identifying products and services available during the at least one layover; and providing information to the user about products and services identified as available during the at least one layover.

Other aspects of the foregoing method can include one or more of the following: (1 ) providing an interface for the user to book or otherwise purchase products and services identified as available to the user during the at least one layover; (2) detecting changes in the user's travel itinerary and, when changes in the user's travel itinerary are detected, notifying the user of changes in the user's travel itinerary; (3) detecting changes in the at least one layover location, date, time, and duration resulting from changes detected in the user's travel itinerary to determine at least one new layover, and searching for and identifying products and services available during the at least one new layover; (4) initially creating an inventory of products and services and saving at least a portion of the inventory of products and services in a database; (5) as part of the searching, contacting providers of products and services on at least a continual basis to update the inventory of products and services in the database; (6) as part of the searching, electronically communicating with providers of products and services ( such as via the internet to the websites of the providers) to obtain real time information for product and service offerings; (7) the providing information includes providing information regarding at least one from among hotel or motel or room rentals, travel services, vehicle rental, taxi services, public transportation, events, personal services, sightseeing, special offers, and coupons; (8) the detecting the at least one layover includes receiving an email from a user, and identifying from the received email the user's itinerary; and (9) the detecting the at least one layover includes linking electronically to a user's email account, and periodically checking the user's email account to detect the user's itinerary.

Preferably the method is implemented via computer system as described and illustrated in this disclosure. Communications are via digital means between a user's computer, PDA, Smartphone, or other communication device, and the system of the present disclosure using conventional

communication platforms, as illustrated more fully in Figure 1 and as described more fully below.

The computer system uses commercially available hardware configured to perform the method of the present disclosure. This hardware includes communication equipment (wireless and hard wired) configured to communicate with the service providers to obtain product and service offerings and solely from which an offering of products and services is compiled. The hardware can include an electronic database for storing product and service offerings, including the identification and contact information for service providers, solely from which the system assembles an offering of products and services. The hardware can be further configured to enable searching of the database for products and services commensurate with the layover location and period as well as to communicate directly with the providers to obtain real time product and service offerings commensurate with the layover location and period, and to then assemble the offering of products and services based on both the search of the database and the communication with the providers of the products and services.

Below are descriptions of scenarios describing how the method and system of the present disclosure is utilized by users. In this description, the term "users" can include without limitation, customers, consumers, travel agencies, reservation and booking centers, resorts, and travel providers such as airlines, cruise lines, and the like. It is to be understood that while the present system and method are described in the context of booking flights, it can be utilized in other industries, such as cruise lines, railroads, bus lines, freight shipping via trucks and ships, and other industries where a layover is experienced.

User Scenarios

Scenario 1 - Booking a flight by a user

A user accesses and utilizes an online reservation system to book a flight. Booking a flight can include, without limitation, merely saving a preferred flight for future payment and actually making payment to secure the flight reservation. The system then detects or determines if the user's itinerary includes a layover of determined duration, for example several hours layover, at one or more airports. A booking system using the layover system is configured to detect the layover location, date, time, and duration. Based on that determination, the system creates a list of offerings, such as hotel rooms offered at a per hour rate at airport hotels (or vehicle rental or other products). The system can be configured to use the user's frequent flyer or other membership information, such as American Auto Club, to prioritize a list of offerings. The list of offerings is then sent to the user for display, printing, saving or forwarding or a combination of two or more of the foregoing.

When the booking process is used with the system and method of the present disclosure, it allows a user to book not only the flight (or other form of transportation such as a cruise that may involve a layover) but other products and services available during the layover or layovers. Hence, the list of offerings is provided to the user preferably before the user books the flight. The user can select offered services and products as part of the booking process, meaning the user may also book a product or a service or both while at the same time the user is booking the flight.

Upon completion of the booking, the booking confirmation of any products and services that have been booked or purchased is sent to the user along with the flight booking information or itinerary. More particularly, in addition to the itinerary information, the booking information will also include details on a booked hotel and any product and services purchased at the layover location or locations. The product and service providers are notified about layover related purchases via preferred channels of communication between the system and the providers.

Scenario 2- A User has booked a flight

After a customer utilizes any online reservation system to book a flight to include layover, usually an email with itinerary information is sent to the user. The system is configured to scan or parse the email and detect or determine if the user's itinerary includes a layover. If a layover is detected, the system is further configured to determine the location, date, time, and duration, for example several hours layover at one or more airports. If layover information is identified, the layover system creates a list of offerings, such as, without limitation, hotel rooms offered at a per hour rate at airport hotels or vehicle rental on an hourly basis or other products. The list of matching products and services is communicated to the user, and the user can select and book or purchase the products or services through the system of the present disclosure.

Scenario 3- Flight has been delayed or canceled

In some circumstances, a user's flight will be delayed for several hours or canceled. While waiting in the airport for the flight or even while in the air, the user will receive a notification from the layover system via one of the following channels (e-mail, SMS, voice call, call by call agent or application push notification) that the flight has been delayed or canceled. In order to minimize the level of inconvenience, the notification includes list of offerings of lodging (such as rooms per hour), vehicle rental, off-airport transportation, as well as other product and services based on the user's location and the other layover listed above.

Scenario 4- User missed a flight

Although infrequent, a user may miss a flight. This can occur for a variety of reasons, such as an in-flight delay of a connecting flight, traffic delays on the ground, security delays, and the like. The system is configured to detect that the user did not board a flight and notify a the user or user via channels described in scenario 2 about alternative flight options, which include a new flight to the same destination and services at the current location during the layover. Notification preferences can be provided that enables users to have the system send notifications to a travel agent, business associate, relative, and other designated individuals, groups, businesses, and government agencies. 1 . Introduction

This document provides a Software Requirement Specification (SRS) that will explain all the details to build a software system that will utilize the aforementioned method. 1 .1 . Goals

The goal is to build a system that:

• Detects the layovers in the itinerary and offers products or services at the layover location for the date, time, and duration of layover or layovers.

· The system is driven by business rules that are provided by the system administration as well as by travel inventory suppliers.

• The system allows integration with PMS and OTA systems.

• The system is configured to integrate with flight status tracking systems to identify in real-time new layovers and track the changes.

· The system allows integration with Mobile applications and

Websites.

• The system is scalable and extendable.

In addition to the foregoing, the system will be able to detect and extract the itinerary from user emails, as well as interface with providers of products and products, including travel services, and to save in a database some or all of the products and services that are offered by providers, which is updated at least periodically. From this database as well as from real-time communications with providers, the system will identify and offer products and services to the user commensurate with the location, date, time, and duration of the layover or layovers.

1 .2. Definitions, Acronyms, and Abbreviations

• GDS - Global Distribution System - e.g., Amadeus, Saber, Travelport (Galileo & Worldspan). • PMS - Property Management System.

• OTA - Online Travel Agency.

• TMC - Travel Management Companies - e.g., American

Express. 2. General Description

2.1 . Product Perspective

The system can work as integrated system with travel seller website systems, as well as can be used as a separate service that provides interface to other systems, websites, applications or services. 2.2. Product Functions

1 . The system exposes standard interfaces {e.g., GDS) that provide a connection to Travel Inventory Suppliers.

2. The system is configured to receive real-time and offline updates on fares, availability, schedules, rules, booking, ticketing, and other information.

3. The system is configured to receive flight status changes in real time.

4. The system is configured to detect changes in the itinerary, including change in layover location, date, time, duration, and conditions (such as weather, labor, financial, governmental, and other unforeseen events at the layover location).

5. The system is configured to notify Travel Inventory

Suppliers about reservations, changes in flight status and flight cancellations.

6. The system is further configured to generate the new offerings and send the same to the user as directed by the notification preferences when the itinerary changes. 7. The system is configured to store the data received from the Travel Inventory providers in its own database.

8. The internal database in replicated or backed up for high availability.

9. The system is also configured to expose web portal for

Travel Inventory Suppliers so they can manually update their inventory, availability, schedulers, fares, rules, etc.

10. The system is further configured to accept as an input the description of products and services, including without limitation ratings, reviews, availability information, schedules, fares and rules for calculating hourly price based on the daily price. Rules may include conditions concerning setting an hourly rate, providing a minimum period for rent, or some advanced rules such as for 1 -3 hours a price of $X; for 3-5 hours, a price of $Y, and for 5-

8 hours, a price of $Z.

1 1 . The system is preferably configured to handle service and product availability and pricing in real time to accommodate for changes.

12. Based on the itinerary, the system determines the layover location, date, time, duration, user's preferences (such as memberships, earned discounts, etc., as set up in a profile) and group size.

13. Based on the information retrieved from the itinerary and a user profile, the system is configured to find and generate a list of offerings of products and services and returns the list to the user.

14. A user can select desired products and services from the offerings and proceed to checkout.

15. The system is configured to provide a user with an advanced feature to search offers at layover location based on the criteria such as a keyword, a hotel user rating, etc.

16. The system is configured to receive user's emails and detect layover information within the emails. 17. The system can be linked with user email accounts in order to detect layover information in the user's emails.

2.3. User Characteristics

• The user of the system can be either a user who interacts with the system through the website or application, or it can be another system such as an Internet Distribution Service.

• Travel inventory suppliers may use automatic connectivity via standard published protocols, such as those used by GDS or it may use an online portal to update the inventory related data

· The system is configured to process booking cancellation fees, refunds, exchanges, etc.

• The system supports rules that will drive the logic of picking up the matching offering, scheduling, and price logic.

2.4. User Email Interface

Three scenarios below identify possible options for obtaining the user's itinerary from the user's email. These options can be used solely or in combinations of two or more as desired.

Option 1 :

1 . A user forwards to the system an email with the itinerary embedded in or attached to the email.

2. The system receives the email and searches for the user's records in the system's database.

3. The system checks the email to identify itinerary related emails associated with the user's email.

4. The system scans the body of the email and finds flight information and detects the layover information (e.g., one or more of location, date, time, and duration). 5. The system prepares and transmits to the user an offering of products and services commensurate for the layover based on the layover information obtained in step 4 above.

Note: the product and service offering can be sent to the user by different notification channels (e.g. email, app push up notification or SMS)

Option 2:

1 . A user allows linking his/her email account with the system.

2. The system access the user email account and scans user emails periodically and identifies itinerary related emails.

3. The system scans the body and attachments of each itinerary-related email and finds flight information from which the system detects the layover information (e.g., one or more of location, date, time, and duration).

4. Smart Layover System offers products and services for the layover period for layover location based on Layover information and user information

Note: The offer can be sent to the user by different notification channels (e.g. email, app push up notification or SMS)

Option 3:

1 . A user installs a system application on the device

(laptop/tablet/mobile, etc.) that can access the user's email.

2. The user allows the installed mobile app to access the user's email.

3. The mobile app scans the user's emails periodically and identifies itinerary related emails.

4. The app scans the body and attachments of the email and finds flight information from which it detects the layover information (e.g., one or more of location, date, time, and duration) within the email 5. When the layover information is detected, the mobile app sends the layover information to the system server.

6. The system sends offers for products and services commensurate with the for the layover information, i.e., the layover period for the layover location.

2.5. General Constraints

• The system is compliant with security, privacy, and local and international government regulations.

3. Specific Requirements

3.1 . External Interface Requirements

• The system is exposing standard web interfaces for communication, such as JSON, XML, etc. 3.1 .1 . User Interfaces

• The system can be accessible via a Web portal.

• The system employs a Ul interface for Travel Inventory suppliers (aka portal).

• The system also includes a Ul for Administrative operations (such as to update the business rules, etc.).

3.1 .2. Hardware Interfaces

• The system software is capable of being hosted on standalone servers, as well as hosted in the cloud {e.g., Amazon EC2, Microsoft Windows Azure, etc.). 3.1 .3. Software Interfaces

• The system software utilizes interfaces with other well-known published protocols, such as GDS, and others

3.1 .4. Communications Interfaces

· The system software implements well-known published connectivity protocols, such as GDS Software that has a proprietary communication interface to be used only by the system Administrator.

3.2. Use Cases

3.2.1 . Use Case - Updating Inventory for integrated systems

1 . A Travel Inventory provider connects their property management system to the layover system via a published interface (similar to GDS).

2. On real time basis travel inventory updates are sent to the layover system, including without limitation inventory availability, description, price, etc.

3.2.2. Use Case - Updating Inventory for non-integrated systems

1 . A Travel Inventory provider that does not have ability to connect the property management system to the layover system via a published interface will have an option to use a web portal in order to access and update the inventory one by one or to do a bulk update.

2. Each Travel Inventory provider can access the layover system portal and update the inventory at a desired frequency.

3. In order to prevent double booking, inventory providers may have to block the inventory submitted to the layover system so it is available only to be booked by the layover system. 3.2.3. Use Case - Updating the Business rules for travel inventory

1 . The layover system is driven by business rules. Each service provider may choose a program with a level of rule complexity that can be applied to the inventory.

2. Example of rules include without limitation:

• Minimal booking period {e.g., 1 hour).

• Price rules, either flat rule that take a percentage of the full day price, or have a special range that says if user booking room for 1 -3 hours, the price will be $X; for 3-5 hours, the price is $Y; and for 6-8 hours, the price is $Z, etc.

• When the layover crosses a predetermined or selected time of day, such as 9:00 pm, then the price of $A will be used.

• The business rule can include restrictions {e.g., No pets, No children, Non Smoking, Max parties allowed, and the like). 3.2.4. Use Case - Updating the Business rules for calculating a window of opportunity

1 . The layover system will allow administrator to update business rules for calculating window of opportunities for each type of product or service

2. Once the business rule will be uploaded to the system, the layover system will apply these rules during analyzing the layover period.

3.2.5. Use Case - Cancellation or reservation

1 . The layover system permits cancellation of reservations with all necessary steps such as refund, cancelation confirmation to the user, and notification to the service or product provider. 3.2.6. Use Case - Modification of existing reservation

1 . The layover system allows modification of existing reservation based on changes in the flight status or as triggered by the user.

3.3.6. Use Case - Search of the available services

1 . The system accepts input from the user or another system.

2. Input includes:

_ Location (airport Code, or city name), and

_ Date and Time.

3. The system is configured to perform a search in the inventory database based on the input provided by the user.

4. The system applies business rules, and based on the rules will generate a list of the offerings

5. Each offering will have price information calculated based on the fares rules. 3.2.7. Use Case - Advanced Search of the available services

1 . The system is configured to allow the user to perform advanced search for products and services provided during layover

2. The search can be refined by category (type of service), name, hotel star rating, etc. 3.2.8. Use Case - Booking itinerary

1 . The user of the system provides potential itinerary details. (In case of air travel the itinerary details includes list of flights, airports, date time etc. In the case of cruises, it includes ports of embarkation/debarkation, date, time, durations, and the like.)

2. The system detects layovers/stopovers in the itinerary.

3. The system performs searches in the database for a lodging, vehicle rental, and other product or service offerings based on the layover location, date, time, duration of layover, number of users, age of users, and user profile and preferences.

4. The system search takes into account service and product availability information, and it retrieves prices from the database and applies business rules for filtering offerings and calculating hourly rate based on the daily price.

5. The system returns a result (list of offerings and prices) after some filtering for display, printing, forwarding, saving, and other use by the end user.

6. The user selects the desired product or service from the list and proceeds with a checkout process.

7. The checkout process is performed by standard methods employed in the industry, including conventional security provisions.

8. The end user or system receives a notification about the purchased product and services.

9. The providers of the purchased product and services are notified via preferred standard channels.

3.2.9. Use Case - Change in itinerary

1 . The system detects the change to the itinerary due to flight delay or cancellation or other reasons.

2. The system triggers a search of the new offerings base on the new layover location, date, time, and duration.

3. The user is notified via notification preference channels such as email, SMS, app push notification, etc., about new products and services.

4. A user can go online or call to a call center agent to make a change to the reservation.

5. Once a reservation is complete, the end user or system receives a notification about the purchased product and services. 6. The product and service provider are notified via preferred standard channels.

3.3. Non Functional requirements

• The system should be highly available.

· The response time of the system is reasonable and does not introduce a long waiting time for users and systems that are using it.

• The system handles the incoming traffic without affecting

SLAs.

• The system is scalable.

· All data stored in the local databases will have a backup for failure recovery.

• The internal database structure can be updated based on the requirements of the Travel Inventory Suppliers.

• Interfaces with the software are dependent on the industry standards in such a way that it enables integrating with major PMS software and connecting with Global Distribution Service (GDS) Amadeus, Sabre

(Abacus, Infiniti, Axess, Travelport (Galileo & Worldspan), etc.

• The system can run on servers in data centers, as well as can be hosted in the cloud or may run on the premise of the Travel Seller Company. Identification of User's needs during layover

• Lodging, such as rooms for several hours in order to obtain sleep or rest or to have a private area to work, exercise, clean, change clothes, and relax. For travelers with small children, this can provide a time for naps and play time.

· Services at hotel facilities, SPA, rent a conference room.

• At Airport, obtain an Internet connection (WIFI), entrance to clubs, and the like. • Transportation & Tours, including Taxi, Limo by an hour, Rent- A-Car by an hour, Sightseeing tour.

Online Flight booking Systems

The following are major GDS Systems and Internet Travel Sites for which the system is configured to interface are identified below:

GDS Travel Agent Systems:

• Sabre (US, CA, EU)

• Amadeus (AU, EU, SA, US)

• Apollo (US, CA)

· Galileo (AU, EU, NZ)

• Abacus (South East Asia)

• WorldSpan (EU, US, Middle East)

• System One (US, Canada)

• Pegasus (Online Distribution)

Internet Travel Systems:

Travelocity (Sabre)

Expedia (WorldSpan)

Travel Now (Sabre)

Orbitz (Pegasus)

AOL Travel (Sabre)

Yahoo Travel (Sabre)

Lodging.com (Galileo)

Travel.com (Travel Now)

TravelWeb (Pegasus)

Cheap Ticket (Pegasus)

Hotels.com (Sabre)

1 ,000's More (Pegasus) Referring next to Figure 1 , shown therein is a data flow diagram for different possible options of offering products and services to a user during at least one layover. The columns across the top of Figure 1 identify the five main aspects of the system, which are from the left "End User," "Travel Sellers," "Inventory for Layover," "Connectivity and Distribution," and "Travel & Other Inventor Suppliers."

The End User portion identifies the functionality in the form of a website portal or Application for mobile or desktop devices or both. The End User in this diagram is either a traveler for business (corporate) of for pleasure (leisure). The user will have either one or more of a computer, PDA or

Smartphone, or Tablet or slate.

The Travel Sellers column includes Online Travel Agencies (OTA's), Internet Distribution Services (IDS), a Supplier Website, such as KLM.com, Delta.com, Hilton.com, etc. Travel Management Companies (TMC's) such as American Express and Carlson Wagon are shown.

The system web portal identified as Smart Layover Web Portal is shown connected to the Internet and to a backend system in the third column (described below). The OTA's, IDS's, TMC's, and the Supplier Websites are all connected to the Internet and thence to the user via the user's computer, PDA or Smartphone, or to a user's Tablet or slate.

In the third column entitled "Inventory for Layover," is shown the Smart Layover Backend System coupled to each of the sellers in column two. The backend system includes the Smart Layover Web Service, such as SOAP, XML, ISON, etc. The third column also includes a Smart Layover Database Server that is connected to the Smart Layover Web Service.

The fourth column is for exchange and management. This includes PRN, fares, schedules, availability, booking, ticketing, refund, interline management, settlement (ARC, BSP), reporting and ancillary services,

(upgrades, baggage, lounge passes, in-flight services), deals for Restaurants and Retail Stores, Virtual points, miles or virtual casino money, coupons, etc. In this column is shown a Global Distribution Service (GDS), such as Amadeus, Sabre (Abacus, Infiniti, Axess, Travelport (Galileo & Worldspan). Also shown is a box for GDS New Entrants such as Farelogix, a box for Direct, which is Proprietary Direct Connect Platform, e.g., AA's Direct Connect, and Groupon, etc., and finally a box for the system's Smart Layover Direct Connector for Inventory and Availability. All of the foregoing are coupled to the Smart Layover Database Server as shown in column three.

Finally, the fifth column has a Reservation System (PMS, CRS, ARS) coupled to all of the exchange and management systems, except the Smart Layover Direct Connector, identified above with respect to column four. The Reservation System is coupled to lodging providers (such as hotels), airlines, cruise lines, as well as transportation vendors (taxi cabs, limos, trains, and buses, for example), and auto and equipment rentals. Also shown are providers of deals and special products, services and activities vendors, and private hotels, all of which are only coupled to the Smart Layover Direct

Connector.

Hence, in accordance with one aspect of the present disclosure the system includes all of the features and connections shown in Figure 1 .

Alternatively, as shown in Figure 1 , certain boxes are cross-hatched, i.e., the Smart Layover Web Portal in column two, the Smart Layover Backend System in column three, and the Smart Layover Direct Connector shown in column four. These three components cooperate together to form a system that cooperate with the other systems and features shown in Figure 1 to provide the layover identification and offerings described herein.

Referring next to Figure 2, shown therein is an Itinerary

Reservation process 10 formed in accordance with the present disclosure. This process is designed for use with one or more OTAs (online travel agency).

The first box 12 is the start of the process. From the start box 12, the process moves to the second step 12 where a user accesses a Travel Seller website (box 14), after which the user enters criteria for a flight search in box 14. The Travel Seller website returns a list of flight matching the user's search criteria (box 18), after which the user selects the flight for his itinerary, such as adding it to a "Shopping Cart" (box 20). The user's flight details are then sent to the system of the present disclosure and processed as describe herein to detect a layover (box 22). Decision box 24 has a "Yes" path and a "No" path. The "No" path leads to box 26, in which the system displays the trip information or itinerary to the user for review and confirmation. If the user does not confirm (box 28), the "No" path from that decision box 26 returns to the list of flights (box 18). If the user confirms, the "Yes" path leads to three conclusion boxes 30, in which the first box 32 is the transmission of the reservation to the Travel Supplier, the second box 34 is sending of the confirmation to the user, and the last box 36 is transfer of payment to the providers.

Returning to decision box 24, if the decision is a "Yes," this leads to the system generating a list of offerings for the layover location and the layover period (start and end date and start and end times) (box 38). After that the generated list is sent to the user for display, saving, forwarding, or printing (box 40).

The next decision box 42 is whether the user selects one or more offerings. If not, the "No" path returns to box 26 to display the trip information for review and confirmation. If "Yes," the path leads to box 44 where selected products and services are added to a "shopping cart." Following that, the system returns to box 26 to display the trip information for the review and confirmation steps 30. The process terminates at the "End" 38.

Figures 3-6 illustrate several update approaches for inventory providers and a search process. More particularly, the first method illustrated in Figure 3 is an inventory update 50 for integrated travel inventory providers. Following the start step 52, the travel inventory provider's system is configured to be connected to the system of the present disclosure (box 54), followed by sending of updates on a real time basis (box 56). The system then sends an acknowledgment status that indicates the updates are processed (box 58), at which point the process ends (box 59).

In situations where travel providers are integrated with GDS, the system provides an update process 60 shown in Figure 4 that includes, following the start box 62, having the travel inventory provider configured to be connected to the GDS (box 64). The provider then publishes the inventory with "special" rates for the system users (box 66), and the inventory is stored in the GDS and available for the system consumption (box 68). The process then ends (box 79).

An alternative update process 70 is shown in Figure 5 for travel inventory providers without integration. Here, after the start (box 72), the travel inventory provider accesses the system portal (box 74) and logs in with secure credentials (box 76). The travel inventory provider then updates the inventory details, such as price and availability (box 77), and then logs out (box 78), and the process ends (box 79).

Finally, a process for searching the inventor when the system is integrated with GDS is provided in Figure 6. Here the search process 80 begins at the start (box 81 ), followed by receiving layover information as an input to the system (that includes layover location, date, start time, and end time) (box 82). The system then applies Rules and identifies what rate to search for in the GDS (box 84), and makes a query to the GDS to retrieve available inventory (box 86). The inventory is then processed with some rules applied (box 87), and the applicable inventory is returned to the requestor and available for standard booking (box 88). The process then ends (box 89).

As will be readily appreciated from the foregoing, the system and method of the present disclosure addresses a need to provide a traveler with information related to a layover period. The system and method can utilize a database, such as the system database, in which of the available offerings of products and services are stored or it can obtain offerings directly from the providers of the products and services, or it can be a combination of direct access to providers and the system database.

The various embodiments described above can be combined to provide further embodiments. Aspects of the embodiments can be modified, if necessary to employ concepts of the various patents, applications and publications to provide yet further embodiments. Hence, although the present disclosure refers to layovers between two or more flights, the disclosed method and system is applicable to layovers between trains, ships and other public or private transportation.

These and other changes can be made to the embodiments in light of the above-detailed description. In general, in the following claims, the terms used should not be construed to limit the claims to the specific embodiments disclosed in the specification and the claims, but should be construed to include all possible embodiments along with the full scope of equivalents to which such claims are entitled. Accordingly, the claims are not limited by the disclosure.

Claims

1 . A method for offering products and services during a travel layover, the method comprising:

detecting at least one layover in a user's travel itinerary;

determining the at least one layover location, date, time, and duration;

searching for and identifying products and services available during the at least one layover; and

providing information to the user about products and services identified as available during the at least one layover.

2. The method of claim 1 , further comprising providing an interface for the user to book or otherwise purchase products and services identified as available to the user during the at least one layover.

3. The method of claim 1 , further comprising detecting changes in the user's travel itinerary and, when changes in the user's travel itinerary are detected, notifying the user of changes in the user's travel itinerary.

4. The method of claim 3, further comprising detecting changes in the at least one layover location, date, time, and duration resulting from changes detected in the user's travel itinerary to determine at least one new layover, and searching for and identifying products and services available during the at least one new layover.

5. The method of claim 1 , comprising initially creating an inventory of products and services and saving at least a portion of the inventory of products and services in a database.

6. The method of claim 5, wherein the searching comprises contacting providers of products and services on at least a continual basis to update the inventory of products and services in the database.

7. The method of claim 1 wherein the searching comprises electronically communicating with providers of products and services to obtain real time information for product and service offerings or searching information stored on a system database for products and services applicable to the at least one layover or a combination of electronically communicating with providers of products and services to obtain real time information for product and service offerings and searching information stored on a system database for products and services applicable to the at least one layover.

8. The method of claim 1 , wherein the providing information includes providing information regarding at least one from among lodging (hotel or motel or room rentals), travel services, vehicle rental, taxi and limousine services, public transportation, events, personal services, sightseeing, special offers, and coupons.

9. The method of claim 1 , wherein the detecting the at least one layover comprises:

receiving an email from a user;

identifying from the received email the user's itinerary.

10. The method of claim 1 , wherein the detecting the at least one layover comprises:

linking electronically to a user's email account; and periodically checking the user's email account to detect the user's itinerary.

1 1 . A system, comprising:

a first subsystem configured to:

receive and store in an electronic database at least one travel provider's schedule data;

receive and store in the electronic database at least one provider's offering of products and services; and

a second subsystem configured to:

detect at least one layover in a user's travel itinerary;

determine the at least one layover location, date, time, and duration;

search the electronic database and identifying products and services available during the at least one layover; and

provide information to the user about products and services identified as available during the at least one layover.

12. The system of claim 1 1 , wherein the first subsystem is configured to detect in real-time flight changes that create at least one new layover or that affect the time and duration of an existing at least one layover.

13. The system of claim 1 1 , wherein the first subsystem is configured to detect any availability changes in the identified products and services in order to prevent double booking of at least one product or service.

14. The system of claim 1 1 , wherein the first subsystem is configured to detect flight information during a flight booking process that creates at least one layover.

15. The system of claim 1 1 , wherein the second subsystem is configured to:

obtain user preferences;

identify number of users traveling together;

apply additional business rules to determine at least one window of opportunity for products and services during the at least one layover;

manage reservation and booking of travel and other services; and notify the user and product and service providers.

16. The system of claim 1 1 , wherein the second subsystem is configured to electronically communicate with providers of products and services to obtain real time information for product and service offerings or to search information stored on the electronic database for products and services applicable to the at least one layover or a combination of electronically communicating with providers of products and services to obtain real time information for product and service offerings and searching information stored on the electronic database for products and services applicable to the at least one layover.

17. A system, comprising:

a computer system configured to:

detect at least one layover in a user's travel itinerary;

determine the location, date, time, and duration of the least one layover;

search for and identifying products and services available during the at least one layover; and

18. The system of claim 17, wherein the computer system is further configured to detect changes in the user's travel itinerary and, when changes in the user's travel itinerary are detected, to notify the user of changes in the user's travel itinerary.

19. The system 17, wherein the computer system is configured to detect changes in the at least one layover location, date, time, and duration resulting from changes detected in the user's travel itinerary to determine at least one new layover, and to search for and identify products and services available during the at least one new layover.

20. The system of claim 17, wherein the computer system is configured to initially create an inventory of products and services, and to store at least a portion of the inventory of products and services in a database.

21 . The system of claim 17, wherein the computer system is configured to contact providers of products and services on at least a continual basis to update the inventory of products and services.

22. The system of claim 17, wherein the computer system is configured to:

receive an email from a user; and

identify from the email the user's travel itinerary.

23. The system of claim 17, wherein the computer system is configured to:

link electronically to a user's email account; and

check the user's email account to detect the user's travel itinerary in the user's email.

24. The system of claim 17, wherein the computer system includes a database, and wherein the system is configured to:

electronically communicate with providers of products and services to obtain real time information for product and service offerings; or search information stored on the database for products and services applicable to the at least one layover; or

perform a combination of electronically communicating with providers of products and services to obtain real time information for product and service offerings and searching information stored on a system database for products and services applicable to the at least one layover.