Language selection

Search

Patent 2881641 Summary

Third-party information liability

Some of the information on this Web page has been provided by external sources. The Government of Canada is not responsible for the accuracy, reliability or currency of the information supplied by external sources. Users wishing to rely upon this information should consult directly with the source of the information. Content provided by external sources is not subject to official languages, privacy and accessibility requirements.

Claims and Abstract availability

Any discrepancies in the text and image of the Claims and Abstract are due to differing posting times. Text of the Claims and Abstract are posted:

  • At the time the application is open to public inspection;
  • At the time of issue of the patent (grant).
(12) Patent: (11) CA 2881641
(54) English Title: OPEN TICKETLESS TRAVEL SERVICES
(54) French Title: SERVICES OUVERTS DE VOYAGE SANS BILLET
Status: Granted and Issued
Bibliographic Data
(51) International Patent Classification (IPC):
  • G06Q 10/02 (2012.01)
(72) Inventors :
  • DUBUC, SIMON (France)
(73) Owners :
  • AMADEUS S.A.S.
(71) Applicants :
  • AMADEUS S.A.S. (France)
(74) Agent: MARTINEAU IP
(74) Associate agent:
(45) Issued: 2021-05-25
(22) Filed Date: 2015-02-12
(41) Open to Public Inspection: 2015-08-19
Examination requested: 2019-11-25
Availability of licence: N/A
Dedicated to the Public: N/A
(25) Language of filing: English

Patent Cooperation Treaty (PCT): No

(30) Application Priority Data:
Application No. Country/Territory Date
14/183,958 (United States of America) 2014-02-19
14 290 039.8 (European Patent Office (EPO)) 2014-02-19

Abstracts

English Abstract

Methods, systems, and computer program products for associating a traveler with an electronic ticket reserving a travel related service. During a booking process, the traveler may be asked to provide an identification image. The identification image provided by the traveler may be associated with the electronic ticket in an electronic ticket database. At a point-of-service, the traveler may present an image that is captured by a control system. The control system may compare the captured image to the identification image and determine if the images match. In response to the images matching, the control system may provide an indication that the traveler should receive the travel service reserved by the electronic ticket.


French Abstract

Des procédés, des systèmes et des produits de programmes informatiques permettant dassocier un voyageur à un billet électronique réservant un service associé à un voyage sont décrits. Pendant un procédé de réservation, on peut demander au voyageur de fournir une image didentification. Limage didentification fournie par le voyageur peut être associée au billet électronique dans une base de données de billets électroniques. Au niveau dun point de service, le voyageur peut présenter une image qui est capturée par un système de commande. Le système de commande peut comparer limage capturée à limage didentification et déterminer si les images correspondent. En réponse aux images correspondant, le système de commande peut fournir une indication selon laquelle le voyageur doit recevoir le service de voyage réservé par le billet électronique.

Claims

Note: Claims are shown in the official language in which they were submitted.


17
CLAIMS
1. A method comprising:
receiving, at a first computer, a request to reserve a travel service for a
traveler;
in response to the request being received, generating a reservation record for
the travel service and the traveler in a database operatively coupled to the
first computer;
receiving, at the first computer, an identification image selected for
association with the reservation record;
encrypting the identification image using an encryption algorithm;
associating the encrypted identification image with the reservation record in
the database; and
after the encrypted identification image is associated with the reservation
record in the database:
encrypting, by the first computer or a second computer, an image
presented by the traveler at a point-of-service and captured by a first
computing device at the point-of-service using the encryption algorithm;
comparing, by the first computer or the second computer, the
encrypted captured irnage and the encrypted identification image to
determine whether the encrypted captured image matches the
encrypted identification image; and
in response to determining that the encrypted captured image matches
the encrypted identification image, authorizing the traveler to use the
travel service.
2. The method of claim 1 wherein the request to reserve the travel service is
received from a third computer, and further comprising:
in response to receiving the request to reserve the travel service,
transmitting a
query from the first computer to the third computer, the query requesting the
identification image.
3. The method of claim 2 wherein the identification image is received from the
third
computer in response to the query.
Date Recue/Date Received 2020-08-27

18
4. The method of any one of claims 1 to 3, wherein the second computer
performs
the encryption of the image presented by the traveler at the point-of-service
and
captured by the first computing device at the point-of-service using the
encryption
algorithm, and further comprising:
transmitting the encrypted identification image from the first computer to the
second computer,
wherein the second computer performs the comparison of the encrypted captured
image and the encrypted identification image.
5. The method of claim 4 further cornprising:
determining an amount of time remaining before a scheduled use of the travel
service and the traveler,
wherein the encrypted identification image is automatically transmitted from
the
first computer to the second computer in response to the determined amount of
time being less than a predetermined amount of time.
6. The method of any one of claims 1 to 5 wherein the first computer is
operated by a
provider of the travel service, and the image presented by the traveler at the
point-
of service captured by the first computing device at the point-of-service by
the
presented image being scanned by the first computer.
7. The method of any one of claims 1 to 6 wherein the image presented by the
traveler is an image displayed by an electronic device of the traveler.
8. The method of any one of claims 1 to 7, wherein authorizing the traveler to
use the
travel service comprises:
automatically providing entry to the travel service to the traveler.
9. The method of claim 8, wherein automatically providing entry to the travel
service
to the traveler comprises:
automatically opening an entry barrier associated with the travel service.
10. The method of claim 9, wherein the entry barrier is a door to a hotel
room.
Date Recue/Date Received 2020-08-27

19
11. A system comprising:
one or more processors; and
a memory including instructions that, when executed by the one or more
processors, cause the system to, in response to a request to reserve a travel
service for a traveler being received at the system:
generate a reservation record for the travel service and the traveler in a
database,
in response to an identification image being selected for association with
the reservation record being received at the system, encrypt the
identification image using an encryption algorithm, and
associate the encrypted identification image with the reservation record in
the database; and
after the encrypted identification image is associated with the reservation
record in the database:
encrypt an irnage presented by the traveler at a point-of-service and
captured by a first computing device at the point-of-service using the
encryption algorithm,
compare the encrypted captured image and the encrypted identification
image to determine whether the encrypted captured image matches the
encrypted identification image, and
in response to determining that the encrypted captured image matches the
encrypted identification image, authorize the traveler to use the travel
service.
12. The system of claim 11, wherein the request initiated by the traveler to
reserve
the travel service is received from another computer, and the instructions
upon
execution further cause the system to:
transmit a query from the system to the another computer in response to the
request initiated by the traveler to reserve the travel service being
received,
wherein the query requests the identification image.
13. The system of claim 12, wherein the identification image is received from
the
another computer in response to the query.
Date Recue/Date Received 2020-08-27

20
14. The system of any one of claims 11 to 13, wherein the one or more
processors
comprise one or more first processors and one or more second processors that
differ from the one or more first processors, the instructions upon execution
cause
the one or more first processors to perforrn the generation of the reservation
record for the travel service and the traveler in the database and the
association
of the encrypted identification image with the reservation record in the
database,
the instructions upon execution cause the one or more second processors to
perform the encryption of the image presented by the traveler at the point-of-
service and captured by the first computing device at the point-of service
using the
encryption algorithm, and the instructions upon execution further cause the
system to:
transmit the encrypted identification image from the one or more first
processors
to the one or more second processors, wherein the instructions upon execution
cause the one or more second processors to perform the comparison of the
encrypted captured image and the encrypted identification image.
15. The system of claim 14, wherein the instructions upon execution further
cause
the system to:
determine an amount of time remaining before a scheduled use of the travel
service and the traveler,
wherein the encrypted identification image is automatically transmitted from
the
one or more first processors to the one or more second processors in response
to
the determined amount of time being less than a predetermined amount of time.
16. The system of any one of claims 11 to 15, wherein the instructions upon
execution further cause the system to scan, by the first computing device at
the
point-of-service, the image presented by the traveler at the point-of-service.
17. The system of claim 16, wherein the image presented by the traveler is an
image
displayed by a second computing device of the traveler.
18. The system of any one of claims 11 to 17 wherein the instructions further
cause
the system to perform the methods of any one of claims 8 to 10.
Date Recue/Date Received 2020-08-27

21
19. A computer program product comprising:
a non-transitory computer readable storage medium; and
instructions stored on the non-transitory computer readable storage medium
that,
when executed by one or more processors of a system, cause the system to:
in response to a request to reserve a travel service for a traveller being
received
at the system:
generate a reservation record for the travel service and the traveller in a
database,
in response to an identification image selected for association with the
reservation record being received at the system, encrypt the identification
image using an encryption algorithm, and
associate the encrypted identification image with the reservation record in
the
database; and
after the encrypted identification image is associated with the reservation
record in the database:
encrypt an image presented by the traveller at a point-of-service and captured
by a first computing device at the point-of service using the encryption
algorithm,
compare the encrypted captured image and the encrypted identification image
to determine whether the encrypted captured image matches the encrypted
identification image, and
in response to determining that the encrypted captured image matches the
encrypted identification image, authorize the traveller to use the travel
service.
20. The computer program product of claim 19 wherein the instructions further
cause
the processor to perform the methods of any one of claims 1 to 10.
Date Recue/Date Received 2020-08-27

Description

Note: Descriptions are shown in the official language in which they were submitted.


CA 02881641 2015-02-12
OPEN TICKETLESS TRAVEL SERVICES
TECHNICAL FIELD
[0001] The invention generally relates to computers and computer
software, and in particular
to methods, systems, and computer program products for travel planning,
reservations, and
ticketing.
BACKGROUND
[0002] Travelers on common carriers, such as railways and airlines,
typically reserve seats
for travel by purchasing tickets. Historically, tickets have been printed on
paper and presented to
the carrier by the traveler upon boarding. Paper tickets thereby formed a type
of currency that
entitled the ticket holder to board the carrier and receive services
identified by the ticket. Paper
tickets also provided the carrier with proof that the holder paid for the
travel service. The
traveler would typically purchase the ticket through a ticket office of the
carrier or through a
travel agent, who would issue the paper ticket to the traveler. For travel
involving multiple legs
or segments, tickets would sometimes be provided in the form of a booklet
containing several
separate tickets or coupons, with one coupon being redeemable for each leg of
the trip.
Typically, a portion of the paper ticket would be surrendered to the carrier
at the time of
departure or boarding, with the traveler keeping another portion of the ticket
as proof that they
were authorized to receive the service.
[0003] Electronic tickets have largely replaced paper tickets in the
travel industry. An
electronic ticket comprises a digital file located in a database of a computer
system, such as a
Computer Reservation System (CRS) or a Global Distribution System (GDS). The
carrier can
(.,
determine if the traveler is entitled services by accessing the digital file,
which provides an
electronic record of the traveler's reservation. The digital file stores
information relating to the
reserved travel service, such as dates and times when services are to be
rendered, origin and
destination locations, seat assignment, travel class, the identity of the
ticket holder, and the
current status of the electronic ticket.
[0004] In order for the traveler to receive the services reserved by
the electronic ticket, the
traveler must typically present some form of identification to the service
provider. Thus,
although electronic tickets may eliminate the need for a paper ticket, the
traveler must still carry
some form of identification so that the service provider can determine that
the traveler is
authorized to receive the service identified by the electronic ticket. This
has led to confusion

CA 02881641 2015-02-12
2
among travelers, who may be required to provide different forms of
identification depending on
the carrier and the geographic region in which the carrier is operating. In
addition, many forms
of identification include one or more printable documents, which may be easily
counterfeited or
otherwise copied, thereby creating a security issue.
[0005] Thus, improved systems, methods, and computer program products are
needed for
reserving, issuing, and authenticating electronic tickets in the travel
industry, and to provide
convenient and secure identification of ticket holders.
SUMMARY
[0006] In an embodiment of the invention, a method of associating a
traveler with a
reservation for a travel service is provided. The method includes receiving a
request to reserve
the travel service and generating a reservation record for the travel service
in a database. The
method further includes receiving a traveler-defined first image, and
associating the first image
with the reservation record in the database.
[0007] In another embodiment of the invention, a method of authorizing use
of the
reservation for the travel service by the traveler is provided. The method
includes receiving a
second image presented by the traveler. The method further includes comparing
the second
image to the first image associated with the reservation for the travel
service, and in response to
the second image matching the first image, authorizing the traveler to use the
reservation.
[0008] In another embodiment of the invention, an apparatus for associating
the traveler with
the reservation for the travel service is provided. The apparatus includes one
or more processors,
and a memory including instructions that, when executed by the one or more
processors, cause
the apparatus to receive the request to reserve the travel service and
generate the reservation
record for the travel service in the database. The instructions may further
cause the apparatus to
receive the traveler-defined first image and associate the first image with
the reservation record
in the database.
[0009] In another embodiment of the invention, an apparatus for authorizing
use of the
reservation for the travel service by the traveler is provided. The apparatus
includes one or more
processors, and a memory including instructions that, when executed by the one
or more
processors, cause the apparatus to receive the second image presented by the
traveler and
compare the second image to the first image associated with the reservation
for the travel service.

CA 02881641 2015-02-12
3
The instructions may further cause the apparatus to authorize the traveler to
use the reservation
in response to the second image matching the first image.
[0010] In another embodiment of the invention, a computer program product
is provided that
includes a non-transitory computer readable storage medium including
instructions. The
instructions may be configured, when executed by the processor, to cause the
processor to
receive the request to reserve the travel service and generate the reservation
record for the travel
service in the database. The instructions may further cause the apparatus to
receive the traveler-
defined first image and associate the first image with the reservation record
in the database.
[0011] In another embodiment of the invention, the computer program product
includes
instructions configured to cause the processor to receive the second image
presented by the
traveler and compare the second image to the first image associated with the
reservation for the
travel service. The instructions may further cause the processor to authorize
the traveler to use
the reservation in response to the second image matching the first image.
BRIEF DESCRIPTION OF THE DRAWINGS
[0012] The accompanying drawings, which are incorporated in and constitute
a part of this
specification, illustrate various embodiments of the invention and, together
with the general
description of the invention given above, and the detailed description of the
embodiments given
below, serve to explain the embodiments of the invention.
[0013] FIG. 1 is a diagrammatic view of an exemplary operating environment
including a
plurality of computer systems in communication via a network.
[0014] FIG. 2 is a diagrammatic view of an exemplary computer system of
FIG. 1.
[0015] FIG. 3 is a flow chart depicting a process that may be executed by
one or more of the
computer systems in FIG. I that includes associating an identification image
with an electronic
ticket in a database.
[0016] FIG. 4 is a flow chart depicting a process for authorizing delivery
of a service
identified by the electronic ticket by comparing a presented image to the
identification image.
DETAILED DESCRIPTION
[0017] Embodiments of the invention may be implemented by a computing
system, such as a
Global Distribution System (GDS). The computing system may provide processing
and database
functions that facilitate interconnections between indirect sellers of tickets
and a plurality of
computer reservation systems each associated with a carrier or other travel
service provider. The

CA 02881641 2015-02-12
4
computing system may be configured to allow travelers to book tickets for
travel, hotel rooms,
vehicles, or any other travel products and services (referred to herein as
simply "services")
through direct and indirect sales channels. The indirect sales channels may
include online or
traditional travel agencies or other business entities selling the services
provided by the travel
service provider.
[0018] In an embodiment of the invention, the traveler may be provided with
an option of
obtaining "open ticketless" services by providing an identification image
during a booking
process. In response to receiving the identification image from the traveler,
the system may
associate the identification image with an electronic ticket in a database. At
the time and place
where the service is to be provided, or the "point-of-service", the traveler
may be asked to
present an image. The presented image may be captured by the computing system
and compared
to the identification image in the database. If the images match, the computer
system may
authorize delivery of the service. If the images do not match, the traveler
may be denied the
service, or asked to provide some other type of proof that they are entitled
to receive the service.
[0019] Referring now to FIG. 1, an operating environment 10 in accordance
with an
embodiment of the invention may include the Global Distribution System (GDS)
12, one or more
provider systems 14, a travel agency system 16 comprising a representative
indirect seller
system, a traveler system 18, a control system 19, and an electronic ticket
database 20. Each of
the GDS 12, provider systems 14, travel agency system 16, traveler system 18,
control system
19, and electronic ticket database may communicate through a network 21. The
network 21
may include one or more private and/or public networks (e.g., the Internet)
that enable the
exchange of data.
[0020] The GDS 12 may be configured to facilitate communication between the
provider
systems 14 and travel agency system 16 by enabling travel agents, on-line
travel agencies and
other indirect sellers to book reservations on one or more provider systems 14
via the GDS 12.
To this end, the GDS 12 may maintain links to each of the provider systems 14
via the network
21. These links may allow the GDS 12 to route reservation requests from the
travel agency
system 16 to the corresponding provider system 14. The travel agency system 16
may thereby
book services from multiple service providers via a single connection to the
GDS 12. In
response to a ticket being booked, the GDS 12 may receive and store a
Passenger Name Record
(PNR). The PNR may be generated, at least in part, by the provider systems 14,
and may

CA 02881641 2015-02-12
comprise one or more reservation records that contain itinerary and traveler
information
associated with one or more booked reservations. The PNR may be stored in a
PNR database
accessible to the GDS 12, and may include data defining an itinerary for a
particular trip,
passenger, or group of passengers. The defined itinerary may include segments
from multiple
carriers (e.g., flights, bus, and or rail segments), hotel reservations,
rental car reservations, or any
other travel related services.
[0021] The GDS 12 may access the electronic ticket database 20 to store and
retrieve data
relating to electronic tickets. The electronic ticket database 20 may comprise
the PNR database,
or may be maintained as a separate database. Each electronic ticket may
comprise one or more
electronic coupons stored in the electronic ticket database 20, with each
coupon corresponding to
a travel segment or service provided by the electronic ticket. The electronic
ticket database 20
may store the electronic ticket as one or more reservation records 23. These
reservation records
23 may include or be associated with one or more images in the electronic
ticket database 20,
and may comprise at least a portion of a Total Travel Record (TTR). The Total
Travel Record
may include traditional PNR elements as well as non-GDS elements. In response
to one or more
of the electronic coupons being used, exchanged, or refunded, the GDS 12 may
update the
electronic ticket database 20 to reflect a change in status of the electronic
ticket.
[0022] Each provider system 14 may include a Computer Reservation System
(CRS) for the
respective travel service provider. Each Computer Reservation System may
include a database
for storing and retrieving data related to reserving travel services, tracking
service provider
inventory, and issuing electronic tickets for the reserved travel services.
The provider systems
14 may thereby enable the GDS 12 and/or travel agency system 16 to reserve and
pay for
services.
[0023] The travel agency system 16 may be configured to book travel through
the GDS 12.
To this end, the travel agency system 16 may include one or more applications
that allow the
travel agent access the GDS 12. The travel agency system may also include one
or more web
server applications that allow the traveler to book travel using a web browser
or other application
running on the traveler system 18. The traveler system 18 may comprise any
suitable computing
device that enables the traveler to access the travel agency system 16.
Exemplary computing
devices may include, but are not limited to a desktop computer, laptop
computer, tablet
computer, personal digital assistant, or smart phone.

CA 02881641 2015-02-12
6
[0024] The control system 19 may provide employees of the travel service
provider with
information at the point-of-service so that the employees can make informed
decisions on
whether to provide services to the traveler. For example, the control system
19 may include a
computer system or application configured to perform traveler check-in and
boarding at a
departure point, such as a railway station or airport. In the case of lodging
or other rentals, the
control system 19 may be configured to confirm or deny reservations for hotel
rooms, rental cars,
or any other services. The control system 19 is therefore not limited to
controlling the delivery
of any particular type of service.
[0025] In response to receiving data indicating that the traveler has
checked-in at the
departure point, boarded the conveyance, or received some other service, the
control system may
transmit data to GDS 12 indicating the change in status of the electronic
ticket. The GDS 12
may then update the electronic ticket database to reflect this change. The
control system 19 may
also receive data from the GDS 12 indicating whether the electronic ticket is
valid, and whether
the traveler is authorized to use the electronic ticket. Each departure point
may implement a
control system 19 so that carrier agents can perform check-in and boarding of
their passengers,
or otherwise verify that the traveler has purchased the services being
provided.
[0026] Referring now to FIG. 2, the GDS 12, provider systems 14, travel
agency system 16,
traveler system 18, and control system 19 of operating environment 10 may be
implemented on
one or more computer devices or systems, such as exemplary computer system 22.
The
computer system 22 may include at least one processor 24, a memory 26, a mass
storage memory
device 28, an input/output (I/O) interface 30, and a Human Machine Interface
(HMI) 32. The
computer system 22 may also be operatively coupled to one or more external
resources 34 and/or
scanning or imaging devices 44 via the network 21 and/or I/O interface 30.
[0027] The processor 24 may include one or more devices selected from
microprocessors,
micro-controllers, digital signal processors, microcomputers, central
processing units, field
programmable gate arrays, programmable logic devices, state machines, logic
circuits, analog
circuits, digital circuits, or any other devices that manipulate signals
(analog or digital) based on
operational instructions that are stored in the memory 26. Memory 26 may
include a single
memory device or a plurality of memory devices including but not limited to
read-only memory
(ROM), random access memory (RAM), volatile memory, non-volatile memory,
static random
access memory (SRAM), dynamic random access memory (DRAM), flash memory, cache

CA 02881641 2015-02-12
7
memory, or any other device capable of storing information. The mass storage
memory device
28 may include data storage devices such as a hard drive, optical drive, tape
drive, non-volatile
solid state device, or any other device capable of storing information.
[0028] A database 36 (e.g., the electronic ticket database 20) may reside
on the mass storage
memory device 28, and may be used to collect and organize data used by the
various systems and
modules described herein. The database 36 may include data and supporting data
structures that
store and organize the data. In particular, the database 36 may be arranged
with any database
organization and/or structure including, but not limited to, a relational
database, a hierarchical
database, a network database, and/or combinations thereof. A database
management system in
the form of a computer software application executing as instructions on the
processing 24 may
be used to access the information or data stored in records of the database 36
in response to a
query, where a query may be dynamically determined and executed by the
operating system 38,
other applications 40, and/or one or more modules.
[0029] Processor 24 may operate under the control of an operating system 38
that resides in
memory 26. The operating system 38 may manage computer resources so that
computer
program code embodied as one or more computer software applications, such as
application 40
residing in memory 26, may have instructions executed by the processor 24. In
an alternative
embodiment, the processor 24 may execute the application 40 directly, in which
case the
operating system 38 may be omitted. One or more data structures 42 may also
reside in memory
26, and may be used by the processor 24, operating system 38, and/or
application 40 to store or
manipulate data.
[0030] The I/O interface 30 may provide a machine interface that
operatively couples the
processor 24 to other devices and systems, such as the network 21, external
resource 34, and/or
imaging device 44. The application 40 may thereby work cooperatively with the
network 21,
external resource 34, and/or imaging device 44 by communicating via the I/O
interface 30 to
provide the various features, functions, and/or modules comprising embodiments
of the
invention. The application 40 may also have program code that is executed by
one or more
external resources 34, or otherwise rely on functions and/or signals provided
by other system or
network components external to the computer system 22. Indeed, given the
nearly endless
hardware and software configurations possible, persons having ordinary skill
in the art will
understand that embodiments of the invention may include applications that are
located

CA 02881641 2015-02-12
8
externally to the computer system 22, distributed among multiple computers or
other external
resources 34, or provided by computing resources (hardware and software) that
are provided as a
service over the network 21, such as a cloud computing service.
[0031] The HMI 32 may be operatively coupled to the processor 24 of
computer system 22
in a known manner to allow a user to interact directly with the computer
system 22. The HMI 32
may include video and/or alphanumeric displays, a touch screen, a speaker, and
any other
suitable audio and visual indicators capable of providing information to the
user. The HMI 32
may also include input devices and controls such as an alphanumeric keyboard,
a pointing
device, keypads, pushbuttons, control knobs, microphones, etc., capable of
accepting commands
or input from the user and transmitting the entered input to the processor 24.
The HMI 32 may
also include the imaging device 44 so that the imaging device 44 is integral
with the computer
system 22. For example, the computer system 22 may comprise a smart phone or
other portable
computing device that includes a built-in digital camera which provides the
imaging device 44.
[0032] Purchasing the electronic ticket may involve pricing, booking, and
ticketing. In
response to receiving a request from the traveler system 18, the travel agency
system 16 may
price the electronic ticket with the help of the fare engine residing in the
GDS 12. The fare
engine may determine a total fare for the ticket by calculating a fare for
each of one or more
segments that satisfy an itinerary of the electronic ticket, and summing these
fares to generate the
total fare. The resulting electronic ticket may be comprised of one or more
electronic coupons,
each corresponding to one of the segments or services of the trip. The
itinerary of the ticket may
define the segments for which the electronic ticket can be used to obtain a
boarding pass, and/or
other services that comprise the trip. Each segment defined by the itinerary
may comprise one or
more sequential legs, each leg connecting a scheduled departure station to a
scheduled arrival
station.
[0033] Booking the reservation may include checking the provider inventory
for availability
of the service, e.g., seat availability on the segments comprising the
itinerary. This check may
include sending a reservation request from the travel agency system 16 to the
GDS 12. The GDS
12 may in turn query a corresponding provider system 14 for availability of
the services
comprising the electronic ticket. If the requested services are available, the
services may be
booked, and the provider inventory decreased to reflect the booking. In
response to the traveler
approving the transaction, the traveler's account may be billed for the price
of the services.

CA 02881641 2015-02-12
9
[0034] In order for the service provider to be able to associate the
electronic ticket with the
traveler, some form of identification may be required. Identification may be
based on official
documents, such as a driver's license or passport. Basing identification of
the traveler on official
documents may provide a reasonably good level of security because this type of
identification
may be difficult to copy or abuse due to built in safeguards. However, using
official documents
to associate the traveler with the electronic ticket generally requires human
intervention from an
employee of the travel provider, such as a boarding agent, a desk agent, or a
conductor. The
traveler must also carry the official document at all times, even though they
might not otherwise
be required to do so.
[0035] Referring now to FIG. 3, a flow chart is presented that depicts a
process 50 which
may be executed by a computer system, such as the GDS 12, to generate the
electronic ticket. In
block 52, the process 50 may receive a request to reserve a travel service,
such as a flight, rail
pass, hotel room, or rental car. The request may be received from the travel
agency system 16 in
response to input by a travel agent or interaction with the traveler system
18. In any case, in
response to receiving the request, the process 50 may proceed to block 54 and
generate one or
more reservation records 23 in the electronic ticket database 20. The
reservation records 23 may
define the electronic ticket, and may include data identifying the segments
and/or services of the
trip itinerary and corresponding electronic ticket coupons, electronic ticket
coupon status (e.g.,
used or unused), traveler information (e.g., name and address), PNR data,
hotel or rental car
reservations, or any other data necessary to define the electronic ticket. The
process 50 may then
proceed to block 56.
[0036] In block 56, the process 50 may receive data from the traveler
indicting whether the
traveler would like the electronic ticket to include the open ticketless
feature. This data may be
received, for example, in response to a query transmitted to the traveler
system 18, or in response
to the traveler activating a button on a web page displayed by the traveler
system 18. In any
case, if the traveler does not select the open ticketless feature option ("NO"
branch of decision
block 56), the process 50 may proceed to block 58.
[0037] In block 58, the process 50 may assign an identification code to the
electronic ticket,
and issue the electronic ticket. The identification code may be based on data
specific to the
electronic ticket (e.g., a PNR reference number or electronic ticket number),
or data specific to
the traveler (e.g., a loyalty card number, credit card number, or other number
that identifies the

CA 02881641 2015-02-12
traveler). In either case, the traveler may have to remember which type of
identification code is
associated with the electronic ticket. At the point-of-service, the traveler
may be required to
provide the identification code to a boarding agent or enter the
identification code into a
terminal. In some cases, the traveler may also request a paper ticket be
issued, or print out the
ticket, in which case the traveler may need to present the paper ticket at the
point-of-service.
[0038] If the traveler indicates that they wish to use the open ticketless
feature ("YES"
branch of decision block 56), the process 50 may proceed to block 60. In block
60, the process
50 may request an identification image from the traveler. In response, the
traveler may for
example: (1) upload an image stored on the traveler system 18, (2) upload an
image captured by
the imaging device 44, or (3) select an image provided to the user by the
process 50 (e.g., an
image displayed on a web page used for booking the ticket). To this end, a
front end application,
such as a smart phone application or browser plug-in, may be installed on the
traveler system 18
that facilities uploading the image from the traveler system 18. The image may
be of a
document, such as an identity card or passport of the traveler, a traveler
head-shot, or any other
scene, item, or pattern having sufficient complexity to allow the
identification image to be used
to positively associate the traveler with the electronic ticket.
[0039] In response to requesting the identification image, the process 50
may proceed to
block 62 and determine if the identification image has been received. If the
identification image
has not been received ("NO" branch of decision block 62), the process 50 may
proceed to block
64 and transmit an error message to the traveler before returning to block 56.
By way of
example, the process 50 might determine that the image was not received in
response to an
excessive amount of time passing without receiving the image. The process 50
may also
determine the image was not received in response to receiving an image having
characteristics
that render the image unsuitable for associating the traveler with the
electronic ticket. For
example, an image lacking sufficient distinguishing details (e.g., an image of
an empty sky), that
is too common (e.g., an image of the Mona Lisa), or that violates a copyright
may be rejected by
the process 50.
[0040] In response to the receiving the image ("YES" branch of decision
block 62), the
process 50 may proceed to block 66. In block 66, the process 50 may associate
the electronic
ticket with the identification image in the electronic ticket database 20.
This association may
comprise storing the identification image in the electronic ticket database 20
and linking the

CA 02881641 2015-02-12
11
stored image to the reservation records comprising the electronic ticket. In
some cases, the
identification image may contain sensitive and/or personal information. For
example, the image
could include an identity card having a personal identity number, a passport,
or a credit card
number. To address this potential security issue, the process 50 may encrypt
the identification
image before associating the image with the electronic ticket in the
electronic ticket database 20.
In embodiments that encrypt the identification image, the identification image
may be stored in
an encrypted state, thereby protecting any sensitive information that may be
in the identification
image. In certain jurisdictions, this encryption may be required in order to
ensure compliance
with privacy regulations.
[0041] Referring now to FIG. 4, a flow chart is presented that depicts a
process 70 which
may be executed by a computer system, such as the control system 19, to
determine if the
traveler is entitled to receive the services reserved by the electronic
ticket. In block 72, the
process 70 may receive the identification image from the electronic ticket
database 20. The
identification image may be received as part of a transmission that includes
the reservation
records comprising the electronic ticket, the Total Travel Record, or any
other suitable data file.
The identification image may be transmitted or otherwise retrieved from the
electronic ticket
database 20 in response to the electronic ticket entering a check-in window,
and may be received
in encrypted form. The check-in window may be configured to provide a desired
lead time
before the service is to be provided so that the process 70 is properly
configured to determine
whether the traveler is entitled to receive the ticketed service.
[0042] In block 74, the process 70 may capture an image presented by the
traveler, or a
"presented image". The presented image may be captured at the point-of-
service. For example,
the traveler may present the image before boarding the conveyance, checking
into the hotel, or
picking up the rental car, by producing a smart phone or other computing
device that displays the
presented image, or by presenting a printout of the presented image. An
employee of the travel
service provider may then scan or otherwise capture the presented image using
a suitable
computing device, such as a personal digital assistant.
[0043] The control process may then proceed to block 76 and compare the
presented image
to the identification image received from the electronic ticket database 20.
To this end, the
computing device used by the employee may be in communication with the control
system 19 so
that the captured image can be transmitted to the control system 19 for
comparison. In an

CA 02881641 2015-02-12
12
alternative embodiment of the invention, the process 70 may be executed on the
computing
device of the employee. That is, the computing device of the employee may
comprise at least a
portion of the control system 19, in which case the captured image could be
compared to the
identification image in the computing device of the employee. In either case,
the process 70 may
encrypt the captured image using the same encryption algorithm that was used
to encrypt the
identification image in the electronic ticket database before comparing the
images. That is, an
encrypted version of the captured image may be compared to the encrypted
version of the
identification image.
[0044] If the images match ("YES" branch of decision block 78), the process
70 may proceed
to block 80 and authorize the travel service provider to provide the ticketed
service. That is, the
process 70 may provide an indication to the employee that the traveler is
authorized to use the
reservation defined by the electronic ticket. The traveler may then receive
the service, for
example, by boarding the conveyance, receiving access to the hotel room, or a
key to the rental
car, as the case may be. In an embodiment of the invention, the traveler may
receive the travel
service directly in response to the images matching. For example, a scanning
device on a door of
the reserved hotel room could open the door automatically in response to the
captured image
matching the identification image.
[0045] In response to the images not matching ("NO" branch of decision
block 78), the
process 70 may proceed to block 82 and provide an indication to the employee
that the ticketed
service should be refused. In the event that the ticketed service is refused,
the traveler may be
asked to provide an alternative form of identification in order to determine
if the refusal was due
to a mistake by the traveler, a system fault, or some other correctable error.
[0046] The program code embodying any of the embodiments of the invention
described
herein is capable of being individually or collectively distributed as a
program product in a
variety of different forms. In particular, the program code may be distributed
using a computer
readable media, which may include computer readable storage media and
communication media.
Computer readable storage media, which are inherently non-transitory, may
include volatile and
non-volatile, and removable and non-removable tangible media implemented in
any method or
technology for storage of information, such as computer-readable instructions,
data structures,
program modules, or other data. Computer readable storage media may further
include RAM,
ROM, erasable programmable read-only memory (EPROM), electrically erasable
programmable

CA 02881641 2015-02-12
13
read-only memory (EEPROM), flash memory or other solid state memory
technology, portable
compact disc read-only memory (CD-ROM), or other optical storage, magnetic
cassettes,
magnetic tape, magnetic disk storage or other magnetic storage devices, or any
other medium
that can be used to store the desired information and which can be read by a
computer.
Communication media may embody computer readable instructions, data
structures, or other
program modules. By way of example, and not limitation, communication media
may include
wired media such as a wired network or direct-wired connection, and wireless
media such as
acoustic, RF, infrared and other wireless media. Combinations of any of the
above may also be
included within the scope of computer readable media.
[0047] The methods described herein can be implemented by computer
program instructions
(.
supplied to the processor of any type of computer to produce a machine with a
processor that
executes the instructions to implement the functions/acts specified herein.
These computer
program instructions may also be stored in a computer readable medium that can
direct a
computer to function in a particular manner. To that end, the computer program
instructions
may be loaded onto a computer to cause the performance of a series of
operational steps and
thereby produce a computer implemented process such that the executed
instructions provide
processes for implementing the functions/acts specified herein.
[0048] In addition, program code described herein may be identified
based upon the
application or software component within which the program code is implemented
in a specific
embodiment of the invention. However, it should be appreciated that any
particular program
nomenclature that follows is used merely for convenience, and thus the
invention should not be
limited to use solely in any specific application identified and/or implied by
such nomenclature.
It should be further appreciated that the various features, applications, and
devices disclosed
herein may also be used alone or in any combination. Moreover, given the
typically endless
number of manners in which computer programs may be organized into routines,
procedures,
methods, modules, objects, and the like, as well as the various manners in
which program
functionality may be allocated among various software layers that are resident
within a typical
computing system (e.g., operating systems, libraries, APIs, applications,
applets, etc.), and/or
across one or more hardware platforms, it should be appreciated that the
invention is not limited
to the specific organization and allocation of program functionality described
herein.

CA 02881641 2015-02-12
14
[0049] The terminology used herein is for the purpose of describing
particular embodiments
only and is not intended to be limiting of the invention. As used herein, the
singular forms "a",
"an" and "the" are intended to include the plural forms as well, unless the
context clearly
indicates otherwise. It will be further understood that the terms "comprises"
and/or
"comprising," when used in this specification, specify the presence of stated
features, integers,
steps, operations, elements, and/or components, but do not preclude the
presence or addition of
one or more other features, integers, steps, operations, elements, components,
and/or groups
thereof. Furthermore, to the extent that the terms "includes", "having",
"has", "with",
"comprised of", or variants thereof are used in either the detailed
description or the claims, such
terms are intended to be inclusive in a manner similar to the term
"comprising."
[0050] The methodologies presented herein also feature the following
points.
1. A method of authorizing use of a reservation for a travel service by a
traveler, the method
comprising:
receiving, at a first computer, a first image presented by the traveler;
comparing, by one of the first computer or a second computer, the first image
to a second
image associated with the reservation for the travel service; and
in response to the first image matching the second image, authorizing the
traveler to use the
reservation.
2. The method of point 1 further comprising:
receiving, at the first computer, the second image from the second computer,
the second
image being associated with the reservation in a database operatively coupled
to the second
computer,
wherein the first computer compares the first image to the second image.
3. The method of point 1 further comprising:
transmitting the first image from the first computer to the second computer,
the second image
being associated with the reservation in a database operatively coupled to the
second
computer,
wherein the second computer compares the first image to the second image.

CA 02881641 2015-02-12
4. The method of any of points 1 to 3 wherein receiving the first image
comprises:
scanning a physical image with an imaging device operatively coupled to the
first computer;
and
saving an output of the imaging device in a memory of the first computer as
the first image.
5. The method of point 4 wherein the physical image is an image displayed
by an electronic
device or a printed image.
6. An apparatus for authorizing use of a reservation for a travel service
by a traveler, the
apparatus comprising:
one or more processors; and
a memory including instructions that, when executed by the one or more
processors, cause the
apparatus to:
receive a first image presented by the traveler;
compare the first image to a second image associated with the reservation for
the travel
service; and
in response to the first image matching the second image, authorize the
traveler to use the
reservation.
7. The apparatus of point 6 wherein the instructions further cause the
apparatus to perform
the methods of any of points 2 to 5.
8. A computer program product comprising:
a non-transitory computer readable storage medium; and
instructions stored on the non-transitory computer readable storage medium
that, when
executed by a processor, cause the processor to:
receive a first image presented by a traveler;
compare the first image to a second image associated with a reservation for a
travel service;
and
in response to the first image matching the second image, authorize the
traveler to use the
reservation.

CA 02881641 2015-02-12
16
9. The computer program product of point 8 wherein the instructions
further cause the
processor to perform the methods of any of point 2 to 5.
[0051] While embodiments of the invention have been illustrated by a
description of various
examples, and while these embodiments have been described in considerable
detail, it is not the
intention of the applicant to restrict or in any way limit the scope of the
appended claims to such
detail. Additional advantages and modifications will readily appear to those
skilled in the art.
The invention in its broader aspects is therefore not limited to the specific
details, representative
methods, and illustrative examples shown and described. Accordingly,
departures may be made
from such details without departing from the spirit or scope of applicant's
general inventive
concept.
(,

Representative Drawing
A single figure which represents the drawing illustrating the invention.
Administrative Status

2024-08-01:As part of the Next Generation Patents (NGP) transition, the Canadian Patents Database (CPD) now contains a more detailed Event History, which replicates the Event Log of our new back-office solution.

Please note that "Inactive:" events refers to events no longer in use in our new back-office solution.

For a clearer understanding of the status of the application/patent presented on this page, the site Disclaimer , as well as the definitions for Patent , Event History , Maintenance Fee  and Payment History  should be consulted.

Event History

Description Date
Inactive: Grant downloaded 2021-06-14
Inactive: Grant downloaded 2021-06-14
Letter Sent 2021-05-25
Grant by Issuance 2021-05-25
Inactive: Cover page published 2021-05-24
Pre-grant 2021-03-25
Inactive: Final fee received 2021-03-25
Notice of Allowance is Issued 2020-12-23
Letter Sent 2020-12-23
Notice of Allowance is Issued 2020-12-23
Inactive: Q2 passed 2020-12-21
Inactive: Approved for allowance (AFA) 2020-12-21
Common Representative Appointed 2020-11-07
Change of Address or Method of Correspondence Request Received 2020-08-27
Amendment Received - Voluntary Amendment 2020-08-27
Inactive: COVID 19 - Deadline extended 2020-08-19
Inactive: COVID 19 - Deadline extended 2020-08-06
Inactive: COVID 19 - Deadline extended 2020-07-16
Inactive: COVID 19 - Deadline extended 2020-07-02
Inactive: COVID 19 - Deadline extended 2020-06-10
Inactive: COVID 19 - Deadline extended 2020-05-28
Inactive: COVID 19 - Deadline extended 2020-05-14
Inactive: COVID 19 - Deadline extended 2020-04-28
Inactive: COVID 19 - Deadline extended 2020-03-29
Examiner's Report 2019-12-31
Inactive: Report - No QC 2019-12-31
Letter Sent 2019-11-28
Request for Examination Received 2019-11-25
Request for Examination Requirements Determined Compliant 2019-11-25
All Requirements for Examination Determined Compliant 2019-11-25
Early Laid Open Requested 2019-11-25
Amendment Received - Voluntary Amendment 2019-11-25
Advanced Examination Determined Compliant - PPH 2019-11-25
Advanced Examination Requested - PPH 2019-11-25
Common Representative Appointed 2019-10-30
Common Representative Appointed 2019-10-30
Inactive: IPC expired 2019-01-01
Letter Sent 2018-02-23
Maintenance Request Received 2018-02-15
Reinstatement Requirements Deemed Compliant for All Abandonment Reasons 2018-02-15
Reinstatement Request Received 2018-02-15
Deemed Abandoned - Failure to Respond to Maintenance Fee Notice 2018-02-12
Maintenance Request Received 2017-02-09
Inactive: Cover page published 2015-08-31
Application Published (Open to Public Inspection) 2015-08-19
Inactive: IPC assigned 2015-02-18
Inactive: First IPC assigned 2015-02-18
Inactive: IPC assigned 2015-02-18
Letter Sent 2015-02-17
Filing Requirements Determined Compliant 2015-02-17
Inactive: Filing certificate - No RFE (bilingual) 2015-02-17
Application Received - Regular National 2015-02-16
Inactive: QC images - Scanning 2015-02-12
Inactive: Pre-classification 2015-02-12

Abandonment History

Abandonment Date Reason Reinstatement Date
2018-02-15
2018-02-12

Maintenance Fee

The last payment was received on 2020-12-28

Note : If the full payment has not been received on or before the date indicated, a further fee may be required which may be one of the following

  • the reinstatement fee;
  • the late payment fee; or
  • additional fee to reverse deemed expiry.

Please refer to the CIPO Patent Fees web page to see all current fee amounts.

Fee History

Fee Type Anniversary Year Due Date Paid Date
Application fee - standard 2015-02-12
Registration of a document 2015-02-12
MF (application, 2nd anniv.) - standard 02 2017-02-13 2017-02-09
Reinstatement 2018-02-15
MF (application, 3rd anniv.) - standard 03 2018-02-12 2018-02-15
MF (application, 4th anniv.) - standard 04 2019-02-12 2019-02-06
Request for examination - standard 2020-02-12 2019-11-25
MF (application, 5th anniv.) - standard 05 2020-02-12 2020-01-30
MF (application, 6th anniv.) - standard 06 2021-02-12 2020-12-28
Final fee - standard 2021-04-23 2021-03-25
MF (patent, 7th anniv.) - standard 2022-02-14 2022-01-31
MF (patent, 8th anniv.) - standard 2023-02-13 2023-01-30
MF (patent, 9th anniv.) - standard 2024-02-12 2023-12-13
Owners on Record

Note: Records showing the ownership history in alphabetical order.

Current Owners on Record
AMADEUS S.A.S.
Past Owners on Record
SIMON DUBUC
Past Owners that do not appear in the "Owners on Record" listing will appear in other documentation within the application.
Documents

To view selected files, please enter reCAPTCHA code :



To view images, click a link in the Document Description column. To download the documents, select one or more checkboxes in the first column and then click the "Download Selected in PDF format (Zip Archive)" or the "Download Selected as Single PDF" button.

List of published and non-published patent-specific documents on the CPD .

If you have any difficulty accessing content, you can call the Client Service Centre at 1-866-997-1936 or send them an e-mail at CIPO Client Service Centre.


Document
Description 
Date
(yyyy-mm-dd) 
Number of pages   Size of Image (KB) 
Claims 2019-11-25 5 187
Representative drawing 2021-04-23 1 6
Description 2015-02-12 16 836
Abstract 2015-02-12 1 17
Claims 2015-02-12 3 76
Drawings 2015-02-12 3 45
Representative drawing 2015-07-22 1 7
Cover Page 2015-08-31 1 37
Claims 2020-08-27 5 198
Cover Page 2021-04-23 1 35
Filing Certificate 2015-02-17 1 179
Courtesy - Certificate of registration (related document(s)) 2015-02-17 1 103
Reminder of maintenance fee due 2016-10-13 1 114
Courtesy - Abandonment Letter (Maintenance Fee) 2018-02-23 1 172
Notice of Reinstatement 2018-02-23 1 163
Reminder - Request for Examination 2019-10-16 1 124
Courtesy - Acknowledgement of Request for Examination 2019-11-28 1 433
Commissioner's Notice - Application Found Allowable 2020-12-23 1 558
Electronic Grant Certificate 2021-05-25 1 2,527
Maintenance fee payment 2017-02-09 1 65
Reinstatement / Maintenance fee payment 2018-02-15 1 49
Request for examination / PPH request / Amendment 2019-11-25 17 645
Early lay-open request 2019-11-25 6 253
Examiner requisition 2019-12-31 6 304
Amendment / response to report 2020-01-03 1 47
Amendment 2020-08-27 13 599
Change to the Method of Correspondence 2020-08-27 3 103
Final fee 2021-03-25 2 52