LOW COST TRAVEL TICKETING

• US 20150134373A1
• Filed: 11/13/2013
• Published: 05/14/2015
• Est. Priority Date: 11/13/2013
• Status: Abandoned Application

• Current Assignee: Amadeus S.A.S. (Amadeus Global Travel Distribution S.A.)
• Original Assignee: Amadeus S.A.S. (Amadeus Global Travel Distribution S.A.)
• Inventors: Le Marier, Mathieu, Regnault, Julien, Geoffroy, Emmanuelle, Epiard, Damien, Ramon, Carolina
• Application Number:
  US14/079,035
• Publication Number:
  US 20150134373A1
• Time in Patent Office: Days
• US Class Current: 705/5
• CPC Class Codes: G06Q 10/02 Reservations, e.g. for tickets, services or events
• CPC Class Codes: G06Q 50/14 Travel agencies

Abstract

Methods, systems, and computer program products for managing low cost carrier travel inventory items. A booking request for a travel record is received at a reservation system. Responsive to determining that the booking request corresponds to a travel inventory item of a low cost carrier, a light ticketing document number is generated for the travel inventory item based at least in part on the low cost carrier and a type of the travel inventory item. A transaction request including form of payment information and contact information is communicated to a low cost carrier inventory system for the travel inventory item. Responsive to a transaction response received from the low cost carrier inventory system indicating successful booking and successful payment for the travel inventory item, the travel record is updated to include a confirmed booking for the travel inventory item including the light ticketing document number.

Claims

1. A method for managing low cost carrier travel inventory items, the method comprising:

receiving a booking request associated with a passenger name record from a travel reservation device at a reservation system;

in response to determining that the booking request corresponds to a travel inventory item of a low cost carrier, generating, with at least one processor of the reservation system, a light ticketing document number associated with the travel inventory item based at least in part on an identity of the low cost carrier and a type associated with the travel inventory item;

communicating a transaction request for the travel inventory item to an inventory system for the low cost carrier, the transaction request including form of payment information and contact information; and

in response to receiving a transaction response from the inventory system for the low cost carrier indicating a successful booking and a successful payment for the travel inventory item, updating, with the at least one processor, the passenger name record to include a confirmed booking for the travel inventory item including the light ticketing document number.

2. The method of claim 1, further comprising:

in response to not receiving a transaction response from the inventory system for the low cost carrier at the reservation system;

updating, with the at least one processor, the passenger name record to indicate that a transaction was initiated and not completed;

updating the passenger name record to include the light ticketing document number; and

locking the passenger name record such that only a get booking status request corresponding to the travel inventory item may be communicated to the inventory system of the low cost carrier for the passenger name record.

3. The method of claim 1, further comprising:

generating an interface record for a reservation agent associated with the booking request based at least in part on the confirmed booking and including the light ticketing document number; and

communicating the interface record to an accounting system associated with the reservation agent.

4. The method of claim 1, wherein generating, with the at least one processor of the reservation system, the light ticketing document number associated with the travel inventory item based at least in part on the low cost carrier and the type associated with the travel inventory item comprises:

selecting a first subset of numbers of the light ticketing document number based at least in part on the identity of the low cost carrier; and

selecting a second subset of numbers of the light ticketing document number based at least on part on the type associated with the travel inventory item.

5. The method of claim 1, further comprising:

prior to communicating the transaction request, determining an interface platform associated with the inventory system of the low cost carrier; and

generating the transaction request based at least in part on the booking request and the interface platform associated with the inventory system of the low cost carrier.

6. The method of claim 1, further comprising:

in response to updating the passenger name record associated with the booking request, communicating a confirmation to the travel reservation device indicating the confirmed booking and the successful payment.

7. The method of claim 1, wherein the light ticketing document number is stored in a ticket number element associated with the confirmed booking.

8. The method of claim 1, the method further comprising:

prior to communicating a reissue request to the inventory system of the low cost carrier corresponding to the travel inventory item, determining changes between the passenger name record and a previous image of the passenger name record that corresponds to booking the travel inventory item; and

communicating a transaction request for a reissue corresponding to the travel inventory item that includes the determined changes.

9. The method of claim 8, further comprising:

identifying the previous image of the passenger name record that corresponds to booking the travel inventory item based at least in part on an envelope number associated with the received transaction response.

10. The method of claim 1, wherein the transaction response is a first transaction response, the method further comprising:

in response to a second transaction response received from the inventory system for the low cost carrier indicating that booking was not successful for the travel inventory item, communicating an error message to the travel reservation device.

11. A reservation system comprising:

at least one processor; and

program code configured to be executed by the at least one processor and upon execution to cause the at least one processor to;

receive a booking request associated with a passenger name record from a travel reservation device at the reservation system;

responsive to determining that the booking request corresponds to a travel inventory item of a low cost carrier, generate a light ticketing document number associated with the travel inventory item based at least in part on an identity of the low cost carrier and a type associated with the travel inventory item;

communicate a transaction request for the travel inventory item to an inventory system for the low cost carrier, the transaction request including form of payment information and contact information; and

responsive to a transaction response received from the inventory system for the low cost carrier indicating a successful booking and a successful payment for the travel inventory item, update the passenger name record to include a confirmed booking for the travel inventory item including the light ticketing document number.

12. The reservation system of claim 11, wherein the program code is further configured upon execution to cause the processor to:

responsive to not receiving a transaction response from the inventory system for the low cost carrier at the reservation system, update the passenger name record to indicate that a transaction was initiated and not completed, update the passenger name record to include the light ticketing document number, and lock the passenger name record such that only a get booking status request corresponding to the travel inventory item may be communicated to the inventory system of the low cost carrier for the passenger name record.

13. The reservation system of claim 11, wherein the program code is further configured upon execution to cause the processor to:

generate an interface record for a reservation agent associated with the booking request based at least in part on the confirmed booking and including the light ticketing document number, and

communicate the interface record to an accounting system associated with the reservation agent.

14. The reservation system of claim 11, wherein the program code being configured upon execution to generate the light ticketing document number associated with the travel inventory item based at least in part on the low cost carrier and the type associated with the travel inventory item comprises:

the program code being configured upon execution to cause the processor to select a first subset of numbers of the light ticketing document number based at least in part on the identity of the low cost carrier, and select a second subset of numbers of the light ticketing document number based at least on part on the type associated with the travel inventory item.

15. The reservation system of claim 11, wherein the program code is further configured upon execution to cause the processor to:

determine an interface platform associated with the inventory system of the low cost carrier prior to communicating the transaction request, and generate the transaction request based at least in part on the booking request and the interface platform associated with the inventory system of the low cost carrier.

16. The reservation system of claim 11, wherein the program code is further configured upon execution to cause the processor to:

communicate a confirmation to the travel reservation device indicating the confirmed booking and the successful payment responsive to updating the passenger name record associated with the booking request.

17. The reservation system of claim 11, wherein the light ticketing document number is stored in a ticket number element associated with the confirmed booking.

18. The reservation system of claim 11, wherein the program code is further configured upon execution to cause the processor to:

determine changes between the passenger name record and a previous image of the passenger name record that corresponds to booking the travel inventory item prior to communicating a reissue request to the inventory system of the low cost carrier corresponding to the travel inventory item, and

communicate a transaction request for a reissue corresponding to the travel inventory item that includes the determined changes.

19. The reservation system of claim 18, wherein the program code is further configured upon execution to cause the processor to:

identify the previous image of the passenger name record that corresponds to booking the travel inventory item based at least in part on an envelope number associated with the received transaction response.

20. A program product comprising:

a computer readable storage medium; and

program code stored on the computer readable storage medium and configured, upon execution, to cause at least one processor to;

receive a booking request associated with a passenger name record from a travel reservation device at a reservation system;

responsive to determining that the booking request corresponds to a travel inventory item of a low cost carrier, generate a light ticketing document number associated with the travel inventory item based at least in part on an identity of the low cost carrier and a type associated with the travel inventory item;

communicate a transaction request for the travel inventory item to an inventory system for the low cost carrier, the transaction request including form of payment information and contact information; and

responsive to a transaction response received from the inventory system for the low cost carrier indicating a successful booking and a successful payment for the travel inventory item, update the passenger name record to include a confirmed booking for the travel inventory item including the light ticketing document number.