sms implemantation questionaire · xml get 1. when reservation is created via travel agent or web...
TRANSCRIPT
Sell-More-Seatsreg
Inventory Synchronization WEB Service
Purpose User Impl Guide
Document Version 22
Date 17JUL12
Confidential Material - Professional Services
Confidential - Worldticket AS Page 2 | 28
Table of contents
1 GENERAL WEB SERVICE DESCRIPTION 3
11 DOCUMENT VERSION 3
12 PURPOSE 3
13 COMMUNICATION PROTOCOLS 4
14 ASSUMPTIONS AND DEPENDENCIES 4
15 INV SYNC XMLs 5
16 System Flow Diagram 5
17 SYSTEM SEQUENCE DIAGRAM 6
2 MESSAGES 7
21 login 7
22 sellSeat 8
23 releaseSeat 9
24 getAvailability 10
25 pushAvailability 11
3 DeltaPNRList 14
4 USE CASES 18
41 CREATE RESERVATION IN 1A 18
42 CANCEL RESERVATION IN 1A 21
43 REBOOK RESERVATION IN 1A 23
44 SEND PNR UPDATE TO TSRES 26
5 SMS Inventory Synchronization Overview Features 28
Confidential - Worldticket AS Page 3 | 28
1 GENERAL WEB SERVICE DESCRIPTION
11 DOCUMENT VERSION
Activities Editor Date Version
Creation PTV 07SEP09 10
Updated PTV 12SEP11 11
Updated PTV 27SEP11 20
Updated Sections
12 Added comments
13 Added recommend URLs
14 Added assumptions
15 Added system Overview
16 Added UML Sequence Diagram
PTV 21MAR12 21
Updated Info ndash Fixed wrong use of status codes
Page 9 ltreleaseSeat status=rdquoHXrdquogt ltreleaseSeat
status=rdquoHKrdquogt
Page 14 ltpushAvailability status=rdquoHXrdquogt
ltpushAvailability status=rdquoHKrdquogt
PTV 17JUL12 22
12 PURPOSE
Following document specifies the Sell-More-Seats WEB service for inventory
synchronization (SMS Sync) in a business setup with double inventory systems
The SMS Inventory Synchronization is a WEB service that enables to exchange
inventory and PNR information between a master and a secondary reservation amp
inventory system
In this connection the WorldTicket reservation and inventory system Sell-More-Seats
will be regarded as the secondary system to another master inventory system
The purpose is to add and enable more distribution channels via WorldTickets Sell-
More-Seats (SMS) sales reservation and inventory system to what an airlines
existing reservation and inventory system has today ie using SMS as a gateway to
Confidential - Worldticket AS Page 4 | 28
Global distribution systems as Amadeus (1A) Travelport (1G1V1P) andor Sabre
(1S)
13 COMMUNICATION PROTOCOLS
All exchange of data between the master and secondary will be UTF-8 encoded XML
using SSL via HTTPS posted to
Sell-More-Seats Inventory URL
httpswwwworldticketnet443[airline_name]xmli
Proposed other airlines Inventory URL
httpwww[airline_domain]xxxworldTicketServicexmlServiceaspx
14 ASSUMPTIONS AND DEPENDENCIES
1 Airlines other inventory system is master inventory
2 RBD mapping is controlled in master inventory
3 In general SSRs are supported by SMS but not supported in this INV SYNC
version via DeltaPNR except for INFT and CHLD as passenger types If needed
SSRs can be provided via PNL sending
4 PNL is merged and sent via master inventory (operating carrier side) to
Departure systems (If PNL is applicable)
5 PRLETLPFS can be sent to master inventory (operating carrier system) to
update coupon status and then the information is forwarded to secondary side
6 Maintenance of meta data (new changed of expired flights fares schedules
inventory templates equipment etc are manually maintained in all systems)
7 Uploads of changes in schedules farebasis rules are manually uploaded to
OAG and ATPCO
8 Airline provides the necessary resources for
i Development and test of master inventory interface to be
integrated to SMS SYNC
ii Defining commercial programme in SMS (schedules inventory
fares and fare rules)
iii Setup customization and test of SMS
Confidential - Worldticket AS Page 5 | 28
iv SMS daily administration
15 INV SYNC XMLs
The WEB-Service features support the following messages
1 login
2 sellSeat
3 releaseSeat
4 getAvailability
5 pushAvailability
6 deltaPNRList
16 System Flow Diagram
A typical solution could be architectured according to following System Flow
Diagram
0 GDS 1A 1G 1S could be enable as distributions channels for SMS
1 Schedules Inventory Fares etc uploaded to SMS by AL ADMIN
TS RESINV
MASTER
SMS 1A1G1S TA (1A)
OLTA
WEB
(1A)
TA
WEB
Tour
operator
Reference data
Schedules
Fares amp Rules
Sell Seat Get avail
Release seat
ATPCO OAG
Schedules
Fares
AL ADMIN
Push avail
Delta PNR
TA
WEB Tour
operator
Confidential - Worldticket AS Page 6 | 28
2 TS RESINV MASTER SYSTEM provides inventory levels via push availability
3 Reservations and Tickets are processed in Amadeus and forwarded to SMS
4 SMS forwards SellSeats to TS INVMASTER
5 SMS forwards Delta PNR to TS INVMASTER
6 AL provides PNL information to handling DCS
17 SYSTEM SEQUENCE DIAGRAM
The system sequence diagram shows the principal of the inventory integrations
between MTTRES and SMS
1 When Reservation is created via Travel Agent or WEB via TS RESINV then
MTTRES sends new total availability to SMS via the XML interface
2 When Amadeus travel agent or Amadeus enabled WEB-site searches for
routes then SMS replies with Route availability
3 When Amadeus travel agent or Amadeus enabled WEB-site makes a
reservation request via EDIFACT then if applicable SMS replies Amadeus with
a reservation confirmation
4 When Reservation is completed then SMS sends SellSeat to MTTRES via the
inventory XML interface
5 When Amadeus travel agent or Amadeus enabled WEB-site issues tickets then
SMS replies Amadeus with a ticket confirmation
TS RESINV TAWEB SMS TAWEB (1A)
Reservation
made
XML
PushAvailability
XML SellSeat
Search
RoutesAV
S
XML Delta PNR
Namelist
Reservation
requested
Ticket issued
Reservation
confirmed
XML Get
Availability
Confidential - Worldticket AS Page 7 | 28
6 SMS sends Delta Namelist via the inventory XML interface
2 MESSAGES
21 login
The purpose of this message is to get authorization from partner system to be able
to send synchronization messages
REQUEST
user
password
RESPONSE
authorizationCode
EXAMPLE
Request
ltlogin user=rdquow1rdquo password=rdquotestrdquogt
Response
ltlogin authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt
Confidential - Worldticket AS Page 8 | 28
22 sellSeat
REQUEST
authorizationCode
segment
Segment
recLoc Record locator in W1
flight Flight number
date Departure date and time from origin in airport local time
origin IATA 3 letter station code
destination IATA 3 letter station code
rbd Reservation Booking Designator
One letter code for booking class
value Number of sold seats
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
AIRIMP status codes HK or UC
errorCode Predefined codes
ErrorMessage Free text
EXAMPLE
Request
ltsellSeat authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1600rdquo origin=rdquoCPHrdquo
destination=rdquoLHRrdquo rbd=rdquoCrdquogt
3 ltsegmentgt
ltsellSeatgt
Response
ltsellSeat status=rdquoHKrdquogt
Confidential - Worldticket AS Page 9 | 28
23 releaseSeat
This message is to be used whenever a segment is cancelled or rebooked
REQUEST
authorizationCode
segment
Segment
flight Flight number
date Departure date from origin
origin IATA 3 letter station code
destination IATA 3 letter station code
rbd Reservation Booking Designator
One letter code for booking class
value Number of seats to releasecancel
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
errorCode Predefined codes
ErrorMessage Free text
EXAMPLE
Request
ltreleaseSeat
authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt ltsegment
no=rdquoW21111rdquo date=rdquo2008-12-15 1600rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt
3 ltsegmentgt
ltreleaseSeatgt
Response
ltreleaseSeat status=rdquoHKrdquogt
Confidential - Worldticket AS Page 10 | 28
24 getAvailability
This message is used for synchronizing availability
Based on the received information SMS will calculate availability as
availability = capacity + MAX(booked actual_booked)
REQUEST
authorizationCode
flight
flight
no Flight number
date Departure date from origin
RESPONSE
flight
flight
no Flight number
date Departure date from origin
segment
Segment
origin IATA 3 letter station code
destination IATA 3 letter station code
class
class
rbd Reservation Booking Designator
One letter code for booking class
capacity Number of seats authorized by TSRES in the class on the
given segment
sold Number of seats sold in the class on the given segment
according to TSRES
EXAMPLE
Request
ltgetAvailability
authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt ltflightno=rdquoW21111rdquo
date=rdquo2008-12-15 1600rdquogt
Confidential - Worldticket AS Page 11 | 28
ltgetAvailabilitygt
Response
ltgetAvailabilitygt ltflight
no=rdquoW21111rdquo date=rdquo2008-12-15 1600rdquogt
ltsegment origin=rdquoCPHrdquo
destination=rdquoLHRrdquogt ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltclass rbd=rdquoYrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt
ltsegmentgt ltsegment
origin=rdquoLHRrdquo destination=rdquoNYCrdquogt
ltclass rbd=rdquoCrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltclass rbd=rdquoYrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltsegmentgt ltsegment
origin=rdquoCPHrdquo destination=rdquoNYCrdquogt
ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltclass rbd=rdquoYrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltsegmentgt
ltflightgt ltgetAvailabilitygt
25 pushAvailability
This message is used for synchronizing availability Based on the received
information W1 will calculate availability as
Confidential - Worldticket AS Page 12 | 28
availability = capacity + MAX(booked actual_booked)
RESPONSE
authorizationCode
flight List of flights
flight
no Flight number
date Departure date from origin
segment List of segments
Segment
origin IATA 3 letter station code
destination IATA 3 letter station code
class
class
rbd Reservation Booking Designator
One letter code for booking class
capacity Number of seats authorized by TSRES in the class on the
given segment
sold Number of seats sold in the class on the given segment
according to TSRES
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
AIRIMP status codes like HK UC
errorCode Predefined codes
ErrorMessage Free text
Confidential - Worldticket AS Page 13 | 28
EXAMPLE
Request
ltpushAvailability authorizationCode=43543534sdfsdfds234234gt
ltflight date=2012-03-29 0840 no=W2901gt ltsegment destination=CPH origin=CDGgt
ltclass capacity=4 rbd=L sold=2gt ltsegmentgt
ltflightgt ltpushAvailabilitygt
or
ltpushAvailabilitygt
ltflight no=rdquoW21111rdquo
date=rdquo2008-12-15 1600rdquogt
ltsegment origin=rdquoCPHrdquo
destination=rdquoLHRrdquogt ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltclass rbd=rdquoYrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltsegmentgt
ltsegment origin=rdquoLHRrdquo
destination=rdquoNYCrdquogt ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo
sold=rdquo7rdquogt ltclass rbd=rdquoYrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltsegmentgt ltsegment
origin=rdquoCPHrdquo destination=rdquoNYCrdquogt
ltclass rbd=rdquoCrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltclass rbd=rdquoYrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltsegmentgt
ltflightgt
Confidential - Worldticket AS Page 14 | 28
ltpushAvailabilitygt
Response
ltpushAvailability status=rdquoHKrdquogt
3 DeltaPNRList
This message is used for synchronizing passenger information The message includes
all segments sold and cancelled since last sending
REQUEST
authorizationCode
add
Remove
add
coupon List of coupons issued since last update
Remove
coupon List of coupons canceled since last update
Coupon
tkne Ticket number
recLoc W1 record locator for reservation to which the coupon
belongs
status Standard IET coupon status indicator We expect that the
following should be enough
O Open for use
R Refunded
E Exchanged
segment List of segments
passenger List of passengers
price Price for pnr
Not mandatory as price maybe unknown in case of tickets
havenrsquot been issued yet
segment
flight Flight designator
date Departure date from origin
origin IATA 3 letter station code
destination IATA 3 letter station code
rbd One letter code for booking class
Confidential - Worldticket AS Page 15 | 28
passenger
type Passenger type ADT CHD INT
title Passenger title
firstName Passenger first name
Any character in UTF-8
familyName Passenger family name
Any character in UTF-8
price
fareBasis Fare basis code
nett
tax Sum of all charged taxes
fee Sum of all charged fees
total The total price including taxes and fees
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
AIRIMP status codes like HK UC
errorCode Predefined codes
ErrorMessage Free text
EXAMPLE
Request
ltdeltaPNRList
authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt
ltaddgt ltcoupon
tkne=rdquo123456789012345rdquo recLoc=rdquoZH23T6rdquo
status=rdquoordquogt ltsegment
flight=rdquoW21111rdquo date=rdquo2008-12-15 1645rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt ltpassenger
type=rdquoADTrdquo title=rdquoMRrdquo
firstName=rdquoSoslashrenrdquo
familyName=rdquoEjsingrdquo rbd=rdquoCrdquogt
Confidential - Worldticket AS Page 16 | 28
ltprice
fareBasis=rdquoCFLEX03rdquo
currency=rdquoEURrdquo nett=rdquo100000rdquo
tax=rdquo50000rdquo fees=rdquo000rdquo
total=rdquo150000rdquogt ltcoupongt
ltaddgt ltremovegt
ltcoupon tkne=rdquo123456789012345rdquo
recLoc=rdquoZH23T6rdquo status=rdquorrdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1645rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt ltpassenger
type=rdquoADTrdquo title=rdquoMRrdquo
firstName=rdquoFRANKrdquo familyName=rdquoOLSENrdquo
rbd=rdquoYrdquogt ltprice
fareBasis=rdquoYECON07rdquo currency=rdquoEURrdquo
nett=rdquo50000rdquo tax=rdquo50000rdquo
fees=rdquo1000rdquo
total=rdquo101000rdquogt ltcoupongt
ltcoupon tkne=rdquo123456789012345rdquo
recLoc=rdquoZH23T6rdquo status=rdquoerdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1645rdquo origin=rdquoCPHrdquo
destination=rdquoLHRrdquo rbd=rdquoCrdquogt
ltpassenger type=rdquoADTrdquo
title=rdquoMRSrdquo
firstName=rdquoLONErdquo
Confidential - Worldticket AS Page 17 | 28
familyName=rdquoOLSENrdquo
rbd=rdquoYrdquogt
ltprice fareBasis=rdquoYECON07rdquo
currency=rdquoEURrdquo nett=rdquo50000rdquo
tax=rdquo50000rdquo fees=rdquo1000rdquo
total=rdquo101000rdquogt ltcoupongt
ltremovegt lt deltaPNRListgt
Response
ltdeltaPNRList status=rdquoHKrdquogt
Confidential - Worldticket AS Page 18 | 28
4 USE CASES
Following basis is defined for the following use cases
TS is master system amp W1 SMS is secondary system
W1 SMS is gateway to 1A
In 1A a TS operated segment is sold as W1 hosted airline so W1 airline is
validating and marketing carrier and partner airline is operating carrier
Use case 1 Create reservation in 1A
Use case 2 Cancel reservation in 1A
Use case 3 Rebook reservation in 1A
Use case 4 Send PNR update to Master System
41 CREATE RESERVATION IN 1A
USE CASE 1
USE CASE Name Create Reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 with
TSRES as master when 1A is selling TSRES segments
Confidential - Worldticket AS Page 19 | 28
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS
POST CONDISTIONS Authorization level in W1 is in synch with assigned
authorization in TSRES
TRIGGER When TA creates a reservation in 1A on a W1 hosted airline
segment
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 On request by 1A W1 will
create a reservation on a TS
segment
2 W1 sends sellSeat
message to TS to inform that
a number of seats is sold on
specific flight event and RBD
3 TSRES confirm that
message is received and
understood
4 W1 request availability
from TSRES by flight
designator and departure
date
5 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
6 W1 updates INV with new
availability information
7 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
3a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 20 | 28
minute
5a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 21 | 28
42 CANCEL RESERVATION IN 1A
USE CASE 2
USE CASE Name Cancel reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS Reservation is already created in W1 and the sale have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Seat is release in INV and authorization level in W1 is in
synch with assigned authorization in TSRES
TRIGGER When TA cancels a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request W1 via 1A to
cancel an already confirmed
segment
Confidential - Worldticket AS Page 22 | 28
2 W1 cancel segments and
confirms cancellation to 1A
3 W1 sends releaseSeat
message to TSRES to inform
that a number of seats is
canceled on specific flight
event and RBD
4 TSRES confirm that
message is received and
understood
5 W1 request availability
from TSRES by flight
designator and departure
date
6 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
7 W1 updates INV with new
availability information
8 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 23 | 28
43 REBOOK RESERVATION IN 1A
USE CASE 3
USE CASE Name Rebook reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 25 times
PRE CONDITIONS Reservation is already created in W1 and te sell have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Request segment is rebook to another flight date or class
Availability in W1 is in synch with assigned authorization in
TSRES
TRIGGER When TA rebook a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request via 1A W1 to
rebook a specified segment
to another flight or class
Confidential - Worldticket AS Page 24 | 28
2 W1 reserve new segment
cancel old and confirms
action to 1A
3 W1 inform TSRES about
new sold segment by sending
sellSeat message
4TSRES confirm that
message is received and
understood
5 W1 informs TSRES that old
segment have been canceled
by sending releaseSeat
message
6 TSRES confirm that
message is received and
understood
7 W1 request availability
from TSRES by flight
designator and departure
date
8 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
9 W1 updates INV with new
availability information
10 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 25 | 28
minute
8a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 26 | 28
44 SEND PNR UPDATE TO TSRES
USE CASE 4
USE CASE Name Send PNR update to TSRES
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TSRES
PURPOSE To update TSRES with the daily sale in W1
LEVEL Primary
FREQUENCY Once every night
PRE CONDITIONS
POST CONDISTIONS
TRIGGER Scheduled job in W1
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 Base on schedule job W1
will generate 2 lists addition
and deletion list of all
changes since last time
TSRES were updated
2 W1 sends deltaPNRList
message to TSRES
3 TSRES confirm that
message is received and
understood
4 W1 saves timestamp for
Confidential - Worldticket AS Page 27 | 28
sending delta list
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
2a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 28 | 28
5 SMS Inventory Synchronization Overview Features
Monitoring of host transactions is logged in the ldquoSMS Host Transaction Overviewrdquo
In the same user interface are able to define filters to retrieve sent and received
transactions In the ldquoSMS Host Transaction Overview ldquo user interface you are able
to
Confidential - Worldticket AS Page 2 | 28
Table of contents
1 GENERAL WEB SERVICE DESCRIPTION 3
11 DOCUMENT VERSION 3
12 PURPOSE 3
13 COMMUNICATION PROTOCOLS 4
14 ASSUMPTIONS AND DEPENDENCIES 4
15 INV SYNC XMLs 5
16 System Flow Diagram 5
17 SYSTEM SEQUENCE DIAGRAM 6
2 MESSAGES 7
21 login 7
22 sellSeat 8
23 releaseSeat 9
24 getAvailability 10
25 pushAvailability 11
3 DeltaPNRList 14
4 USE CASES 18
41 CREATE RESERVATION IN 1A 18
42 CANCEL RESERVATION IN 1A 21
43 REBOOK RESERVATION IN 1A 23
44 SEND PNR UPDATE TO TSRES 26
5 SMS Inventory Synchronization Overview Features 28
Confidential - Worldticket AS Page 3 | 28
1 GENERAL WEB SERVICE DESCRIPTION
11 DOCUMENT VERSION
Activities Editor Date Version
Creation PTV 07SEP09 10
Updated PTV 12SEP11 11
Updated PTV 27SEP11 20
Updated Sections
12 Added comments
13 Added recommend URLs
14 Added assumptions
15 Added system Overview
16 Added UML Sequence Diagram
PTV 21MAR12 21
Updated Info ndash Fixed wrong use of status codes
Page 9 ltreleaseSeat status=rdquoHXrdquogt ltreleaseSeat
status=rdquoHKrdquogt
Page 14 ltpushAvailability status=rdquoHXrdquogt
ltpushAvailability status=rdquoHKrdquogt
PTV 17JUL12 22
12 PURPOSE
Following document specifies the Sell-More-Seats WEB service for inventory
synchronization (SMS Sync) in a business setup with double inventory systems
The SMS Inventory Synchronization is a WEB service that enables to exchange
inventory and PNR information between a master and a secondary reservation amp
inventory system
In this connection the WorldTicket reservation and inventory system Sell-More-Seats
will be regarded as the secondary system to another master inventory system
The purpose is to add and enable more distribution channels via WorldTickets Sell-
More-Seats (SMS) sales reservation and inventory system to what an airlines
existing reservation and inventory system has today ie using SMS as a gateway to
Confidential - Worldticket AS Page 4 | 28
Global distribution systems as Amadeus (1A) Travelport (1G1V1P) andor Sabre
(1S)
13 COMMUNICATION PROTOCOLS
All exchange of data between the master and secondary will be UTF-8 encoded XML
using SSL via HTTPS posted to
Sell-More-Seats Inventory URL
httpswwwworldticketnet443[airline_name]xmli
Proposed other airlines Inventory URL
httpwww[airline_domain]xxxworldTicketServicexmlServiceaspx
14 ASSUMPTIONS AND DEPENDENCIES
1 Airlines other inventory system is master inventory
2 RBD mapping is controlled in master inventory
3 In general SSRs are supported by SMS but not supported in this INV SYNC
version via DeltaPNR except for INFT and CHLD as passenger types If needed
SSRs can be provided via PNL sending
4 PNL is merged and sent via master inventory (operating carrier side) to
Departure systems (If PNL is applicable)
5 PRLETLPFS can be sent to master inventory (operating carrier system) to
update coupon status and then the information is forwarded to secondary side
6 Maintenance of meta data (new changed of expired flights fares schedules
inventory templates equipment etc are manually maintained in all systems)
7 Uploads of changes in schedules farebasis rules are manually uploaded to
OAG and ATPCO
8 Airline provides the necessary resources for
i Development and test of master inventory interface to be
integrated to SMS SYNC
ii Defining commercial programme in SMS (schedules inventory
fares and fare rules)
iii Setup customization and test of SMS
Confidential - Worldticket AS Page 5 | 28
iv SMS daily administration
15 INV SYNC XMLs
The WEB-Service features support the following messages
1 login
2 sellSeat
3 releaseSeat
4 getAvailability
5 pushAvailability
6 deltaPNRList
16 System Flow Diagram
A typical solution could be architectured according to following System Flow
Diagram
0 GDS 1A 1G 1S could be enable as distributions channels for SMS
1 Schedules Inventory Fares etc uploaded to SMS by AL ADMIN
TS RESINV
MASTER
SMS 1A1G1S TA (1A)
OLTA
WEB
(1A)
TA
WEB
Tour
operator
Reference data
Schedules
Fares amp Rules
Sell Seat Get avail
Release seat
ATPCO OAG
Schedules
Fares
AL ADMIN
Push avail
Delta PNR
TA
WEB Tour
operator
Confidential - Worldticket AS Page 6 | 28
2 TS RESINV MASTER SYSTEM provides inventory levels via push availability
3 Reservations and Tickets are processed in Amadeus and forwarded to SMS
4 SMS forwards SellSeats to TS INVMASTER
5 SMS forwards Delta PNR to TS INVMASTER
6 AL provides PNL information to handling DCS
17 SYSTEM SEQUENCE DIAGRAM
The system sequence diagram shows the principal of the inventory integrations
between MTTRES and SMS
1 When Reservation is created via Travel Agent or WEB via TS RESINV then
MTTRES sends new total availability to SMS via the XML interface
2 When Amadeus travel agent or Amadeus enabled WEB-site searches for
routes then SMS replies with Route availability
3 When Amadeus travel agent or Amadeus enabled WEB-site makes a
reservation request via EDIFACT then if applicable SMS replies Amadeus with
a reservation confirmation
4 When Reservation is completed then SMS sends SellSeat to MTTRES via the
inventory XML interface
5 When Amadeus travel agent or Amadeus enabled WEB-site issues tickets then
SMS replies Amadeus with a ticket confirmation
TS RESINV TAWEB SMS TAWEB (1A)
Reservation
made
XML
PushAvailability
XML SellSeat
Search
RoutesAV
S
XML Delta PNR
Namelist
Reservation
requested
Ticket issued
Reservation
confirmed
XML Get
Availability
Confidential - Worldticket AS Page 7 | 28
6 SMS sends Delta Namelist via the inventory XML interface
2 MESSAGES
21 login
The purpose of this message is to get authorization from partner system to be able
to send synchronization messages
REQUEST
user
password
RESPONSE
authorizationCode
EXAMPLE
Request
ltlogin user=rdquow1rdquo password=rdquotestrdquogt
Response
ltlogin authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt
Confidential - Worldticket AS Page 8 | 28
22 sellSeat
REQUEST
authorizationCode
segment
Segment
recLoc Record locator in W1
flight Flight number
date Departure date and time from origin in airport local time
origin IATA 3 letter station code
destination IATA 3 letter station code
rbd Reservation Booking Designator
One letter code for booking class
value Number of sold seats
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
AIRIMP status codes HK or UC
errorCode Predefined codes
ErrorMessage Free text
EXAMPLE
Request
ltsellSeat authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1600rdquo origin=rdquoCPHrdquo
destination=rdquoLHRrdquo rbd=rdquoCrdquogt
3 ltsegmentgt
ltsellSeatgt
Response
ltsellSeat status=rdquoHKrdquogt
Confidential - Worldticket AS Page 9 | 28
23 releaseSeat
This message is to be used whenever a segment is cancelled or rebooked
REQUEST
authorizationCode
segment
Segment
flight Flight number
date Departure date from origin
origin IATA 3 letter station code
destination IATA 3 letter station code
rbd Reservation Booking Designator
One letter code for booking class
value Number of seats to releasecancel
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
errorCode Predefined codes
ErrorMessage Free text
EXAMPLE
Request
ltreleaseSeat
authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt ltsegment
no=rdquoW21111rdquo date=rdquo2008-12-15 1600rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt
3 ltsegmentgt
ltreleaseSeatgt
Response
ltreleaseSeat status=rdquoHKrdquogt
Confidential - Worldticket AS Page 10 | 28
24 getAvailability
This message is used for synchronizing availability
Based on the received information SMS will calculate availability as
availability = capacity + MAX(booked actual_booked)
REQUEST
authorizationCode
flight
flight
no Flight number
date Departure date from origin
RESPONSE
flight
flight
no Flight number
date Departure date from origin
segment
Segment
origin IATA 3 letter station code
destination IATA 3 letter station code
class
class
rbd Reservation Booking Designator
One letter code for booking class
capacity Number of seats authorized by TSRES in the class on the
given segment
sold Number of seats sold in the class on the given segment
according to TSRES
EXAMPLE
Request
ltgetAvailability
authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt ltflightno=rdquoW21111rdquo
date=rdquo2008-12-15 1600rdquogt
Confidential - Worldticket AS Page 11 | 28
ltgetAvailabilitygt
Response
ltgetAvailabilitygt ltflight
no=rdquoW21111rdquo date=rdquo2008-12-15 1600rdquogt
ltsegment origin=rdquoCPHrdquo
destination=rdquoLHRrdquogt ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltclass rbd=rdquoYrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt
ltsegmentgt ltsegment
origin=rdquoLHRrdquo destination=rdquoNYCrdquogt
ltclass rbd=rdquoCrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltclass rbd=rdquoYrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltsegmentgt ltsegment
origin=rdquoCPHrdquo destination=rdquoNYCrdquogt
ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltclass rbd=rdquoYrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltsegmentgt
ltflightgt ltgetAvailabilitygt
25 pushAvailability
This message is used for synchronizing availability Based on the received
information W1 will calculate availability as
Confidential - Worldticket AS Page 12 | 28
availability = capacity + MAX(booked actual_booked)
RESPONSE
authorizationCode
flight List of flights
flight
no Flight number
date Departure date from origin
segment List of segments
Segment
origin IATA 3 letter station code
destination IATA 3 letter station code
class
class
rbd Reservation Booking Designator
One letter code for booking class
capacity Number of seats authorized by TSRES in the class on the
given segment
sold Number of seats sold in the class on the given segment
according to TSRES
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
AIRIMP status codes like HK UC
errorCode Predefined codes
ErrorMessage Free text
Confidential - Worldticket AS Page 13 | 28
EXAMPLE
Request
ltpushAvailability authorizationCode=43543534sdfsdfds234234gt
ltflight date=2012-03-29 0840 no=W2901gt ltsegment destination=CPH origin=CDGgt
ltclass capacity=4 rbd=L sold=2gt ltsegmentgt
ltflightgt ltpushAvailabilitygt
or
ltpushAvailabilitygt
ltflight no=rdquoW21111rdquo
date=rdquo2008-12-15 1600rdquogt
ltsegment origin=rdquoCPHrdquo
destination=rdquoLHRrdquogt ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltclass rbd=rdquoYrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltsegmentgt
ltsegment origin=rdquoLHRrdquo
destination=rdquoNYCrdquogt ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo
sold=rdquo7rdquogt ltclass rbd=rdquoYrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltsegmentgt ltsegment
origin=rdquoCPHrdquo destination=rdquoNYCrdquogt
ltclass rbd=rdquoCrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltclass rbd=rdquoYrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltsegmentgt
ltflightgt
Confidential - Worldticket AS Page 14 | 28
ltpushAvailabilitygt
Response
ltpushAvailability status=rdquoHKrdquogt
3 DeltaPNRList
This message is used for synchronizing passenger information The message includes
all segments sold and cancelled since last sending
REQUEST
authorizationCode
add
Remove
add
coupon List of coupons issued since last update
Remove
coupon List of coupons canceled since last update
Coupon
tkne Ticket number
recLoc W1 record locator for reservation to which the coupon
belongs
status Standard IET coupon status indicator We expect that the
following should be enough
O Open for use
R Refunded
E Exchanged
segment List of segments
passenger List of passengers
price Price for pnr
Not mandatory as price maybe unknown in case of tickets
havenrsquot been issued yet
segment
flight Flight designator
date Departure date from origin
origin IATA 3 letter station code
destination IATA 3 letter station code
rbd One letter code for booking class
Confidential - Worldticket AS Page 15 | 28
passenger
type Passenger type ADT CHD INT
title Passenger title
firstName Passenger first name
Any character in UTF-8
familyName Passenger family name
Any character in UTF-8
price
fareBasis Fare basis code
nett
tax Sum of all charged taxes
fee Sum of all charged fees
total The total price including taxes and fees
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
AIRIMP status codes like HK UC
errorCode Predefined codes
ErrorMessage Free text
EXAMPLE
Request
ltdeltaPNRList
authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt
ltaddgt ltcoupon
tkne=rdquo123456789012345rdquo recLoc=rdquoZH23T6rdquo
status=rdquoordquogt ltsegment
flight=rdquoW21111rdquo date=rdquo2008-12-15 1645rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt ltpassenger
type=rdquoADTrdquo title=rdquoMRrdquo
firstName=rdquoSoslashrenrdquo
familyName=rdquoEjsingrdquo rbd=rdquoCrdquogt
Confidential - Worldticket AS Page 16 | 28
ltprice
fareBasis=rdquoCFLEX03rdquo
currency=rdquoEURrdquo nett=rdquo100000rdquo
tax=rdquo50000rdquo fees=rdquo000rdquo
total=rdquo150000rdquogt ltcoupongt
ltaddgt ltremovegt
ltcoupon tkne=rdquo123456789012345rdquo
recLoc=rdquoZH23T6rdquo status=rdquorrdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1645rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt ltpassenger
type=rdquoADTrdquo title=rdquoMRrdquo
firstName=rdquoFRANKrdquo familyName=rdquoOLSENrdquo
rbd=rdquoYrdquogt ltprice
fareBasis=rdquoYECON07rdquo currency=rdquoEURrdquo
nett=rdquo50000rdquo tax=rdquo50000rdquo
fees=rdquo1000rdquo
total=rdquo101000rdquogt ltcoupongt
ltcoupon tkne=rdquo123456789012345rdquo
recLoc=rdquoZH23T6rdquo status=rdquoerdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1645rdquo origin=rdquoCPHrdquo
destination=rdquoLHRrdquo rbd=rdquoCrdquogt
ltpassenger type=rdquoADTrdquo
title=rdquoMRSrdquo
firstName=rdquoLONErdquo
Confidential - Worldticket AS Page 17 | 28
familyName=rdquoOLSENrdquo
rbd=rdquoYrdquogt
ltprice fareBasis=rdquoYECON07rdquo
currency=rdquoEURrdquo nett=rdquo50000rdquo
tax=rdquo50000rdquo fees=rdquo1000rdquo
total=rdquo101000rdquogt ltcoupongt
ltremovegt lt deltaPNRListgt
Response
ltdeltaPNRList status=rdquoHKrdquogt
Confidential - Worldticket AS Page 18 | 28
4 USE CASES
Following basis is defined for the following use cases
TS is master system amp W1 SMS is secondary system
W1 SMS is gateway to 1A
In 1A a TS operated segment is sold as W1 hosted airline so W1 airline is
validating and marketing carrier and partner airline is operating carrier
Use case 1 Create reservation in 1A
Use case 2 Cancel reservation in 1A
Use case 3 Rebook reservation in 1A
Use case 4 Send PNR update to Master System
41 CREATE RESERVATION IN 1A
USE CASE 1
USE CASE Name Create Reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 with
TSRES as master when 1A is selling TSRES segments
Confidential - Worldticket AS Page 19 | 28
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS
POST CONDISTIONS Authorization level in W1 is in synch with assigned
authorization in TSRES
TRIGGER When TA creates a reservation in 1A on a W1 hosted airline
segment
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 On request by 1A W1 will
create a reservation on a TS
segment
2 W1 sends sellSeat
message to TS to inform that
a number of seats is sold on
specific flight event and RBD
3 TSRES confirm that
message is received and
understood
4 W1 request availability
from TSRES by flight
designator and departure
date
5 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
6 W1 updates INV with new
availability information
7 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
3a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 20 | 28
minute
5a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 21 | 28
42 CANCEL RESERVATION IN 1A
USE CASE 2
USE CASE Name Cancel reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS Reservation is already created in W1 and the sale have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Seat is release in INV and authorization level in W1 is in
synch with assigned authorization in TSRES
TRIGGER When TA cancels a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request W1 via 1A to
cancel an already confirmed
segment
Confidential - Worldticket AS Page 22 | 28
2 W1 cancel segments and
confirms cancellation to 1A
3 W1 sends releaseSeat
message to TSRES to inform
that a number of seats is
canceled on specific flight
event and RBD
4 TSRES confirm that
message is received and
understood
5 W1 request availability
from TSRES by flight
designator and departure
date
6 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
7 W1 updates INV with new
availability information
8 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 23 | 28
43 REBOOK RESERVATION IN 1A
USE CASE 3
USE CASE Name Rebook reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 25 times
PRE CONDITIONS Reservation is already created in W1 and te sell have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Request segment is rebook to another flight date or class
Availability in W1 is in synch with assigned authorization in
TSRES
TRIGGER When TA rebook a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request via 1A W1 to
rebook a specified segment
to another flight or class
Confidential - Worldticket AS Page 24 | 28
2 W1 reserve new segment
cancel old and confirms
action to 1A
3 W1 inform TSRES about
new sold segment by sending
sellSeat message
4TSRES confirm that
message is received and
understood
5 W1 informs TSRES that old
segment have been canceled
by sending releaseSeat
message
6 TSRES confirm that
message is received and
understood
7 W1 request availability
from TSRES by flight
designator and departure
date
8 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
9 W1 updates INV with new
availability information
10 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 25 | 28
minute
8a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 26 | 28
44 SEND PNR UPDATE TO TSRES
USE CASE 4
USE CASE Name Send PNR update to TSRES
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TSRES
PURPOSE To update TSRES with the daily sale in W1
LEVEL Primary
FREQUENCY Once every night
PRE CONDITIONS
POST CONDISTIONS
TRIGGER Scheduled job in W1
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 Base on schedule job W1
will generate 2 lists addition
and deletion list of all
changes since last time
TSRES were updated
2 W1 sends deltaPNRList
message to TSRES
3 TSRES confirm that
message is received and
understood
4 W1 saves timestamp for
Confidential - Worldticket AS Page 27 | 28
sending delta list
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
2a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 28 | 28
5 SMS Inventory Synchronization Overview Features
Monitoring of host transactions is logged in the ldquoSMS Host Transaction Overviewrdquo
In the same user interface are able to define filters to retrieve sent and received
transactions In the ldquoSMS Host Transaction Overview ldquo user interface you are able
to
Confidential - Worldticket AS Page 3 | 28
1 GENERAL WEB SERVICE DESCRIPTION
11 DOCUMENT VERSION
Activities Editor Date Version
Creation PTV 07SEP09 10
Updated PTV 12SEP11 11
Updated PTV 27SEP11 20
Updated Sections
12 Added comments
13 Added recommend URLs
14 Added assumptions
15 Added system Overview
16 Added UML Sequence Diagram
PTV 21MAR12 21
Updated Info ndash Fixed wrong use of status codes
Page 9 ltreleaseSeat status=rdquoHXrdquogt ltreleaseSeat
status=rdquoHKrdquogt
Page 14 ltpushAvailability status=rdquoHXrdquogt
ltpushAvailability status=rdquoHKrdquogt
PTV 17JUL12 22
12 PURPOSE
Following document specifies the Sell-More-Seats WEB service for inventory
synchronization (SMS Sync) in a business setup with double inventory systems
The SMS Inventory Synchronization is a WEB service that enables to exchange
inventory and PNR information between a master and a secondary reservation amp
inventory system
In this connection the WorldTicket reservation and inventory system Sell-More-Seats
will be regarded as the secondary system to another master inventory system
The purpose is to add and enable more distribution channels via WorldTickets Sell-
More-Seats (SMS) sales reservation and inventory system to what an airlines
existing reservation and inventory system has today ie using SMS as a gateway to
Confidential - Worldticket AS Page 4 | 28
Global distribution systems as Amadeus (1A) Travelport (1G1V1P) andor Sabre
(1S)
13 COMMUNICATION PROTOCOLS
All exchange of data between the master and secondary will be UTF-8 encoded XML
using SSL via HTTPS posted to
Sell-More-Seats Inventory URL
httpswwwworldticketnet443[airline_name]xmli
Proposed other airlines Inventory URL
httpwww[airline_domain]xxxworldTicketServicexmlServiceaspx
14 ASSUMPTIONS AND DEPENDENCIES
1 Airlines other inventory system is master inventory
2 RBD mapping is controlled in master inventory
3 In general SSRs are supported by SMS but not supported in this INV SYNC
version via DeltaPNR except for INFT and CHLD as passenger types If needed
SSRs can be provided via PNL sending
4 PNL is merged and sent via master inventory (operating carrier side) to
Departure systems (If PNL is applicable)
5 PRLETLPFS can be sent to master inventory (operating carrier system) to
update coupon status and then the information is forwarded to secondary side
6 Maintenance of meta data (new changed of expired flights fares schedules
inventory templates equipment etc are manually maintained in all systems)
7 Uploads of changes in schedules farebasis rules are manually uploaded to
OAG and ATPCO
8 Airline provides the necessary resources for
i Development and test of master inventory interface to be
integrated to SMS SYNC
ii Defining commercial programme in SMS (schedules inventory
fares and fare rules)
iii Setup customization and test of SMS
Confidential - Worldticket AS Page 5 | 28
iv SMS daily administration
15 INV SYNC XMLs
The WEB-Service features support the following messages
1 login
2 sellSeat
3 releaseSeat
4 getAvailability
5 pushAvailability
6 deltaPNRList
16 System Flow Diagram
A typical solution could be architectured according to following System Flow
Diagram
0 GDS 1A 1G 1S could be enable as distributions channels for SMS
1 Schedules Inventory Fares etc uploaded to SMS by AL ADMIN
TS RESINV
MASTER
SMS 1A1G1S TA (1A)
OLTA
WEB
(1A)
TA
WEB
Tour
operator
Reference data
Schedules
Fares amp Rules
Sell Seat Get avail
Release seat
ATPCO OAG
Schedules
Fares
AL ADMIN
Push avail
Delta PNR
TA
WEB Tour
operator
Confidential - Worldticket AS Page 6 | 28
2 TS RESINV MASTER SYSTEM provides inventory levels via push availability
3 Reservations and Tickets are processed in Amadeus and forwarded to SMS
4 SMS forwards SellSeats to TS INVMASTER
5 SMS forwards Delta PNR to TS INVMASTER
6 AL provides PNL information to handling DCS
17 SYSTEM SEQUENCE DIAGRAM
The system sequence diagram shows the principal of the inventory integrations
between MTTRES and SMS
1 When Reservation is created via Travel Agent or WEB via TS RESINV then
MTTRES sends new total availability to SMS via the XML interface
2 When Amadeus travel agent or Amadeus enabled WEB-site searches for
routes then SMS replies with Route availability
3 When Amadeus travel agent or Amadeus enabled WEB-site makes a
reservation request via EDIFACT then if applicable SMS replies Amadeus with
a reservation confirmation
4 When Reservation is completed then SMS sends SellSeat to MTTRES via the
inventory XML interface
5 When Amadeus travel agent or Amadeus enabled WEB-site issues tickets then
SMS replies Amadeus with a ticket confirmation
TS RESINV TAWEB SMS TAWEB (1A)
Reservation
made
XML
PushAvailability
XML SellSeat
Search
RoutesAV
S
XML Delta PNR
Namelist
Reservation
requested
Ticket issued
Reservation
confirmed
XML Get
Availability
Confidential - Worldticket AS Page 7 | 28
6 SMS sends Delta Namelist via the inventory XML interface
2 MESSAGES
21 login
The purpose of this message is to get authorization from partner system to be able
to send synchronization messages
REQUEST
user
password
RESPONSE
authorizationCode
EXAMPLE
Request
ltlogin user=rdquow1rdquo password=rdquotestrdquogt
Response
ltlogin authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt
Confidential - Worldticket AS Page 8 | 28
22 sellSeat
REQUEST
authorizationCode
segment
Segment
recLoc Record locator in W1
flight Flight number
date Departure date and time from origin in airport local time
origin IATA 3 letter station code
destination IATA 3 letter station code
rbd Reservation Booking Designator
One letter code for booking class
value Number of sold seats
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
AIRIMP status codes HK or UC
errorCode Predefined codes
ErrorMessage Free text
EXAMPLE
Request
ltsellSeat authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1600rdquo origin=rdquoCPHrdquo
destination=rdquoLHRrdquo rbd=rdquoCrdquogt
3 ltsegmentgt
ltsellSeatgt
Response
ltsellSeat status=rdquoHKrdquogt
Confidential - Worldticket AS Page 9 | 28
23 releaseSeat
This message is to be used whenever a segment is cancelled or rebooked
REQUEST
authorizationCode
segment
Segment
flight Flight number
date Departure date from origin
origin IATA 3 letter station code
destination IATA 3 letter station code
rbd Reservation Booking Designator
One letter code for booking class
value Number of seats to releasecancel
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
errorCode Predefined codes
ErrorMessage Free text
EXAMPLE
Request
ltreleaseSeat
authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt ltsegment
no=rdquoW21111rdquo date=rdquo2008-12-15 1600rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt
3 ltsegmentgt
ltreleaseSeatgt
Response
ltreleaseSeat status=rdquoHKrdquogt
Confidential - Worldticket AS Page 10 | 28
24 getAvailability
This message is used for synchronizing availability
Based on the received information SMS will calculate availability as
availability = capacity + MAX(booked actual_booked)
REQUEST
authorizationCode
flight
flight
no Flight number
date Departure date from origin
RESPONSE
flight
flight
no Flight number
date Departure date from origin
segment
Segment
origin IATA 3 letter station code
destination IATA 3 letter station code
class
class
rbd Reservation Booking Designator
One letter code for booking class
capacity Number of seats authorized by TSRES in the class on the
given segment
sold Number of seats sold in the class on the given segment
according to TSRES
EXAMPLE
Request
ltgetAvailability
authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt ltflightno=rdquoW21111rdquo
date=rdquo2008-12-15 1600rdquogt
Confidential - Worldticket AS Page 11 | 28
ltgetAvailabilitygt
Response
ltgetAvailabilitygt ltflight
no=rdquoW21111rdquo date=rdquo2008-12-15 1600rdquogt
ltsegment origin=rdquoCPHrdquo
destination=rdquoLHRrdquogt ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltclass rbd=rdquoYrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt
ltsegmentgt ltsegment
origin=rdquoLHRrdquo destination=rdquoNYCrdquogt
ltclass rbd=rdquoCrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltclass rbd=rdquoYrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltsegmentgt ltsegment
origin=rdquoCPHrdquo destination=rdquoNYCrdquogt
ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltclass rbd=rdquoYrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltsegmentgt
ltflightgt ltgetAvailabilitygt
25 pushAvailability
This message is used for synchronizing availability Based on the received
information W1 will calculate availability as
Confidential - Worldticket AS Page 12 | 28
availability = capacity + MAX(booked actual_booked)
RESPONSE
authorizationCode
flight List of flights
flight
no Flight number
date Departure date from origin
segment List of segments
Segment
origin IATA 3 letter station code
destination IATA 3 letter station code
class
class
rbd Reservation Booking Designator
One letter code for booking class
capacity Number of seats authorized by TSRES in the class on the
given segment
sold Number of seats sold in the class on the given segment
according to TSRES
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
AIRIMP status codes like HK UC
errorCode Predefined codes
ErrorMessage Free text
Confidential - Worldticket AS Page 13 | 28
EXAMPLE
Request
ltpushAvailability authorizationCode=43543534sdfsdfds234234gt
ltflight date=2012-03-29 0840 no=W2901gt ltsegment destination=CPH origin=CDGgt
ltclass capacity=4 rbd=L sold=2gt ltsegmentgt
ltflightgt ltpushAvailabilitygt
or
ltpushAvailabilitygt
ltflight no=rdquoW21111rdquo
date=rdquo2008-12-15 1600rdquogt
ltsegment origin=rdquoCPHrdquo
destination=rdquoLHRrdquogt ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltclass rbd=rdquoYrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltsegmentgt
ltsegment origin=rdquoLHRrdquo
destination=rdquoNYCrdquogt ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo
sold=rdquo7rdquogt ltclass rbd=rdquoYrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltsegmentgt ltsegment
origin=rdquoCPHrdquo destination=rdquoNYCrdquogt
ltclass rbd=rdquoCrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltclass rbd=rdquoYrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltsegmentgt
ltflightgt
Confidential - Worldticket AS Page 14 | 28
ltpushAvailabilitygt
Response
ltpushAvailability status=rdquoHKrdquogt
3 DeltaPNRList
This message is used for synchronizing passenger information The message includes
all segments sold and cancelled since last sending
REQUEST
authorizationCode
add
Remove
add
coupon List of coupons issued since last update
Remove
coupon List of coupons canceled since last update
Coupon
tkne Ticket number
recLoc W1 record locator for reservation to which the coupon
belongs
status Standard IET coupon status indicator We expect that the
following should be enough
O Open for use
R Refunded
E Exchanged
segment List of segments
passenger List of passengers
price Price for pnr
Not mandatory as price maybe unknown in case of tickets
havenrsquot been issued yet
segment
flight Flight designator
date Departure date from origin
origin IATA 3 letter station code
destination IATA 3 letter station code
rbd One letter code for booking class
Confidential - Worldticket AS Page 15 | 28
passenger
type Passenger type ADT CHD INT
title Passenger title
firstName Passenger first name
Any character in UTF-8
familyName Passenger family name
Any character in UTF-8
price
fareBasis Fare basis code
nett
tax Sum of all charged taxes
fee Sum of all charged fees
total The total price including taxes and fees
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
AIRIMP status codes like HK UC
errorCode Predefined codes
ErrorMessage Free text
EXAMPLE
Request
ltdeltaPNRList
authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt
ltaddgt ltcoupon
tkne=rdquo123456789012345rdquo recLoc=rdquoZH23T6rdquo
status=rdquoordquogt ltsegment
flight=rdquoW21111rdquo date=rdquo2008-12-15 1645rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt ltpassenger
type=rdquoADTrdquo title=rdquoMRrdquo
firstName=rdquoSoslashrenrdquo
familyName=rdquoEjsingrdquo rbd=rdquoCrdquogt
Confidential - Worldticket AS Page 16 | 28
ltprice
fareBasis=rdquoCFLEX03rdquo
currency=rdquoEURrdquo nett=rdquo100000rdquo
tax=rdquo50000rdquo fees=rdquo000rdquo
total=rdquo150000rdquogt ltcoupongt
ltaddgt ltremovegt
ltcoupon tkne=rdquo123456789012345rdquo
recLoc=rdquoZH23T6rdquo status=rdquorrdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1645rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt ltpassenger
type=rdquoADTrdquo title=rdquoMRrdquo
firstName=rdquoFRANKrdquo familyName=rdquoOLSENrdquo
rbd=rdquoYrdquogt ltprice
fareBasis=rdquoYECON07rdquo currency=rdquoEURrdquo
nett=rdquo50000rdquo tax=rdquo50000rdquo
fees=rdquo1000rdquo
total=rdquo101000rdquogt ltcoupongt
ltcoupon tkne=rdquo123456789012345rdquo
recLoc=rdquoZH23T6rdquo status=rdquoerdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1645rdquo origin=rdquoCPHrdquo
destination=rdquoLHRrdquo rbd=rdquoCrdquogt
ltpassenger type=rdquoADTrdquo
title=rdquoMRSrdquo
firstName=rdquoLONErdquo
Confidential - Worldticket AS Page 17 | 28
familyName=rdquoOLSENrdquo
rbd=rdquoYrdquogt
ltprice fareBasis=rdquoYECON07rdquo
currency=rdquoEURrdquo nett=rdquo50000rdquo
tax=rdquo50000rdquo fees=rdquo1000rdquo
total=rdquo101000rdquogt ltcoupongt
ltremovegt lt deltaPNRListgt
Response
ltdeltaPNRList status=rdquoHKrdquogt
Confidential - Worldticket AS Page 18 | 28
4 USE CASES
Following basis is defined for the following use cases
TS is master system amp W1 SMS is secondary system
W1 SMS is gateway to 1A
In 1A a TS operated segment is sold as W1 hosted airline so W1 airline is
validating and marketing carrier and partner airline is operating carrier
Use case 1 Create reservation in 1A
Use case 2 Cancel reservation in 1A
Use case 3 Rebook reservation in 1A
Use case 4 Send PNR update to Master System
41 CREATE RESERVATION IN 1A
USE CASE 1
USE CASE Name Create Reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 with
TSRES as master when 1A is selling TSRES segments
Confidential - Worldticket AS Page 19 | 28
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS
POST CONDISTIONS Authorization level in W1 is in synch with assigned
authorization in TSRES
TRIGGER When TA creates a reservation in 1A on a W1 hosted airline
segment
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 On request by 1A W1 will
create a reservation on a TS
segment
2 W1 sends sellSeat
message to TS to inform that
a number of seats is sold on
specific flight event and RBD
3 TSRES confirm that
message is received and
understood
4 W1 request availability
from TSRES by flight
designator and departure
date
5 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
6 W1 updates INV with new
availability information
7 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
3a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 20 | 28
minute
5a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 21 | 28
42 CANCEL RESERVATION IN 1A
USE CASE 2
USE CASE Name Cancel reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS Reservation is already created in W1 and the sale have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Seat is release in INV and authorization level in W1 is in
synch with assigned authorization in TSRES
TRIGGER When TA cancels a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request W1 via 1A to
cancel an already confirmed
segment
Confidential - Worldticket AS Page 22 | 28
2 W1 cancel segments and
confirms cancellation to 1A
3 W1 sends releaseSeat
message to TSRES to inform
that a number of seats is
canceled on specific flight
event and RBD
4 TSRES confirm that
message is received and
understood
5 W1 request availability
from TSRES by flight
designator and departure
date
6 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
7 W1 updates INV with new
availability information
8 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 23 | 28
43 REBOOK RESERVATION IN 1A
USE CASE 3
USE CASE Name Rebook reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 25 times
PRE CONDITIONS Reservation is already created in W1 and te sell have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Request segment is rebook to another flight date or class
Availability in W1 is in synch with assigned authorization in
TSRES
TRIGGER When TA rebook a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request via 1A W1 to
rebook a specified segment
to another flight or class
Confidential - Worldticket AS Page 24 | 28
2 W1 reserve new segment
cancel old and confirms
action to 1A
3 W1 inform TSRES about
new sold segment by sending
sellSeat message
4TSRES confirm that
message is received and
understood
5 W1 informs TSRES that old
segment have been canceled
by sending releaseSeat
message
6 TSRES confirm that
message is received and
understood
7 W1 request availability
from TSRES by flight
designator and departure
date
8 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
9 W1 updates INV with new
availability information
10 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 25 | 28
minute
8a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 26 | 28
44 SEND PNR UPDATE TO TSRES
USE CASE 4
USE CASE Name Send PNR update to TSRES
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TSRES
PURPOSE To update TSRES with the daily sale in W1
LEVEL Primary
FREQUENCY Once every night
PRE CONDITIONS
POST CONDISTIONS
TRIGGER Scheduled job in W1
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 Base on schedule job W1
will generate 2 lists addition
and deletion list of all
changes since last time
TSRES were updated
2 W1 sends deltaPNRList
message to TSRES
3 TSRES confirm that
message is received and
understood
4 W1 saves timestamp for
Confidential - Worldticket AS Page 27 | 28
sending delta list
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
2a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 28 | 28
5 SMS Inventory Synchronization Overview Features
Monitoring of host transactions is logged in the ldquoSMS Host Transaction Overviewrdquo
In the same user interface are able to define filters to retrieve sent and received
transactions In the ldquoSMS Host Transaction Overview ldquo user interface you are able
to
Confidential - Worldticket AS Page 4 | 28
Global distribution systems as Amadeus (1A) Travelport (1G1V1P) andor Sabre
(1S)
13 COMMUNICATION PROTOCOLS
All exchange of data between the master and secondary will be UTF-8 encoded XML
using SSL via HTTPS posted to
Sell-More-Seats Inventory URL
httpswwwworldticketnet443[airline_name]xmli
Proposed other airlines Inventory URL
httpwww[airline_domain]xxxworldTicketServicexmlServiceaspx
14 ASSUMPTIONS AND DEPENDENCIES
1 Airlines other inventory system is master inventory
2 RBD mapping is controlled in master inventory
3 In general SSRs are supported by SMS but not supported in this INV SYNC
version via DeltaPNR except for INFT and CHLD as passenger types If needed
SSRs can be provided via PNL sending
4 PNL is merged and sent via master inventory (operating carrier side) to
Departure systems (If PNL is applicable)
5 PRLETLPFS can be sent to master inventory (operating carrier system) to
update coupon status and then the information is forwarded to secondary side
6 Maintenance of meta data (new changed of expired flights fares schedules
inventory templates equipment etc are manually maintained in all systems)
7 Uploads of changes in schedules farebasis rules are manually uploaded to
OAG and ATPCO
8 Airline provides the necessary resources for
i Development and test of master inventory interface to be
integrated to SMS SYNC
ii Defining commercial programme in SMS (schedules inventory
fares and fare rules)
iii Setup customization and test of SMS
Confidential - Worldticket AS Page 5 | 28
iv SMS daily administration
15 INV SYNC XMLs
The WEB-Service features support the following messages
1 login
2 sellSeat
3 releaseSeat
4 getAvailability
5 pushAvailability
6 deltaPNRList
16 System Flow Diagram
A typical solution could be architectured according to following System Flow
Diagram
0 GDS 1A 1G 1S could be enable as distributions channels for SMS
1 Schedules Inventory Fares etc uploaded to SMS by AL ADMIN
TS RESINV
MASTER
SMS 1A1G1S TA (1A)
OLTA
WEB
(1A)
TA
WEB
Tour
operator
Reference data
Schedules
Fares amp Rules
Sell Seat Get avail
Release seat
ATPCO OAG
Schedules
Fares
AL ADMIN
Push avail
Delta PNR
TA
WEB Tour
operator
Confidential - Worldticket AS Page 6 | 28
2 TS RESINV MASTER SYSTEM provides inventory levels via push availability
3 Reservations and Tickets are processed in Amadeus and forwarded to SMS
4 SMS forwards SellSeats to TS INVMASTER
5 SMS forwards Delta PNR to TS INVMASTER
6 AL provides PNL information to handling DCS
17 SYSTEM SEQUENCE DIAGRAM
The system sequence diagram shows the principal of the inventory integrations
between MTTRES and SMS
1 When Reservation is created via Travel Agent or WEB via TS RESINV then
MTTRES sends new total availability to SMS via the XML interface
2 When Amadeus travel agent or Amadeus enabled WEB-site searches for
routes then SMS replies with Route availability
3 When Amadeus travel agent or Amadeus enabled WEB-site makes a
reservation request via EDIFACT then if applicable SMS replies Amadeus with
a reservation confirmation
4 When Reservation is completed then SMS sends SellSeat to MTTRES via the
inventory XML interface
5 When Amadeus travel agent or Amadeus enabled WEB-site issues tickets then
SMS replies Amadeus with a ticket confirmation
TS RESINV TAWEB SMS TAWEB (1A)
Reservation
made
XML
PushAvailability
XML SellSeat
Search
RoutesAV
S
XML Delta PNR
Namelist
Reservation
requested
Ticket issued
Reservation
confirmed
XML Get
Availability
Confidential - Worldticket AS Page 7 | 28
6 SMS sends Delta Namelist via the inventory XML interface
2 MESSAGES
21 login
The purpose of this message is to get authorization from partner system to be able
to send synchronization messages
REQUEST
user
password
RESPONSE
authorizationCode
EXAMPLE
Request
ltlogin user=rdquow1rdquo password=rdquotestrdquogt
Response
ltlogin authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt
Confidential - Worldticket AS Page 8 | 28
22 sellSeat
REQUEST
authorizationCode
segment
Segment
recLoc Record locator in W1
flight Flight number
date Departure date and time from origin in airport local time
origin IATA 3 letter station code
destination IATA 3 letter station code
rbd Reservation Booking Designator
One letter code for booking class
value Number of sold seats
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
AIRIMP status codes HK or UC
errorCode Predefined codes
ErrorMessage Free text
EXAMPLE
Request
ltsellSeat authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1600rdquo origin=rdquoCPHrdquo
destination=rdquoLHRrdquo rbd=rdquoCrdquogt
3 ltsegmentgt
ltsellSeatgt
Response
ltsellSeat status=rdquoHKrdquogt
Confidential - Worldticket AS Page 9 | 28
23 releaseSeat
This message is to be used whenever a segment is cancelled or rebooked
REQUEST
authorizationCode
segment
Segment
flight Flight number
date Departure date from origin
origin IATA 3 letter station code
destination IATA 3 letter station code
rbd Reservation Booking Designator
One letter code for booking class
value Number of seats to releasecancel
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
errorCode Predefined codes
ErrorMessage Free text
EXAMPLE
Request
ltreleaseSeat
authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt ltsegment
no=rdquoW21111rdquo date=rdquo2008-12-15 1600rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt
3 ltsegmentgt
ltreleaseSeatgt
Response
ltreleaseSeat status=rdquoHKrdquogt
Confidential - Worldticket AS Page 10 | 28
24 getAvailability
This message is used for synchronizing availability
Based on the received information SMS will calculate availability as
availability = capacity + MAX(booked actual_booked)
REQUEST
authorizationCode
flight
flight
no Flight number
date Departure date from origin
RESPONSE
flight
flight
no Flight number
date Departure date from origin
segment
Segment
origin IATA 3 letter station code
destination IATA 3 letter station code
class
class
rbd Reservation Booking Designator
One letter code for booking class
capacity Number of seats authorized by TSRES in the class on the
given segment
sold Number of seats sold in the class on the given segment
according to TSRES
EXAMPLE
Request
ltgetAvailability
authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt ltflightno=rdquoW21111rdquo
date=rdquo2008-12-15 1600rdquogt
Confidential - Worldticket AS Page 11 | 28
ltgetAvailabilitygt
Response
ltgetAvailabilitygt ltflight
no=rdquoW21111rdquo date=rdquo2008-12-15 1600rdquogt
ltsegment origin=rdquoCPHrdquo
destination=rdquoLHRrdquogt ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltclass rbd=rdquoYrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt
ltsegmentgt ltsegment
origin=rdquoLHRrdquo destination=rdquoNYCrdquogt
ltclass rbd=rdquoCrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltclass rbd=rdquoYrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltsegmentgt ltsegment
origin=rdquoCPHrdquo destination=rdquoNYCrdquogt
ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltclass rbd=rdquoYrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltsegmentgt
ltflightgt ltgetAvailabilitygt
25 pushAvailability
This message is used for synchronizing availability Based on the received
information W1 will calculate availability as
Confidential - Worldticket AS Page 12 | 28
availability = capacity + MAX(booked actual_booked)
RESPONSE
authorizationCode
flight List of flights
flight
no Flight number
date Departure date from origin
segment List of segments
Segment
origin IATA 3 letter station code
destination IATA 3 letter station code
class
class
rbd Reservation Booking Designator
One letter code for booking class
capacity Number of seats authorized by TSRES in the class on the
given segment
sold Number of seats sold in the class on the given segment
according to TSRES
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
AIRIMP status codes like HK UC
errorCode Predefined codes
ErrorMessage Free text
Confidential - Worldticket AS Page 13 | 28
EXAMPLE
Request
ltpushAvailability authorizationCode=43543534sdfsdfds234234gt
ltflight date=2012-03-29 0840 no=W2901gt ltsegment destination=CPH origin=CDGgt
ltclass capacity=4 rbd=L sold=2gt ltsegmentgt
ltflightgt ltpushAvailabilitygt
or
ltpushAvailabilitygt
ltflight no=rdquoW21111rdquo
date=rdquo2008-12-15 1600rdquogt
ltsegment origin=rdquoCPHrdquo
destination=rdquoLHRrdquogt ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltclass rbd=rdquoYrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltsegmentgt
ltsegment origin=rdquoLHRrdquo
destination=rdquoNYCrdquogt ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo
sold=rdquo7rdquogt ltclass rbd=rdquoYrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltsegmentgt ltsegment
origin=rdquoCPHrdquo destination=rdquoNYCrdquogt
ltclass rbd=rdquoCrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltclass rbd=rdquoYrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltsegmentgt
ltflightgt
Confidential - Worldticket AS Page 14 | 28
ltpushAvailabilitygt
Response
ltpushAvailability status=rdquoHKrdquogt
3 DeltaPNRList
This message is used for synchronizing passenger information The message includes
all segments sold and cancelled since last sending
REQUEST
authorizationCode
add
Remove
add
coupon List of coupons issued since last update
Remove
coupon List of coupons canceled since last update
Coupon
tkne Ticket number
recLoc W1 record locator for reservation to which the coupon
belongs
status Standard IET coupon status indicator We expect that the
following should be enough
O Open for use
R Refunded
E Exchanged
segment List of segments
passenger List of passengers
price Price for pnr
Not mandatory as price maybe unknown in case of tickets
havenrsquot been issued yet
segment
flight Flight designator
date Departure date from origin
origin IATA 3 letter station code
destination IATA 3 letter station code
rbd One letter code for booking class
Confidential - Worldticket AS Page 15 | 28
passenger
type Passenger type ADT CHD INT
title Passenger title
firstName Passenger first name
Any character in UTF-8
familyName Passenger family name
Any character in UTF-8
price
fareBasis Fare basis code
nett
tax Sum of all charged taxes
fee Sum of all charged fees
total The total price including taxes and fees
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
AIRIMP status codes like HK UC
errorCode Predefined codes
ErrorMessage Free text
EXAMPLE
Request
ltdeltaPNRList
authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt
ltaddgt ltcoupon
tkne=rdquo123456789012345rdquo recLoc=rdquoZH23T6rdquo
status=rdquoordquogt ltsegment
flight=rdquoW21111rdquo date=rdquo2008-12-15 1645rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt ltpassenger
type=rdquoADTrdquo title=rdquoMRrdquo
firstName=rdquoSoslashrenrdquo
familyName=rdquoEjsingrdquo rbd=rdquoCrdquogt
Confidential - Worldticket AS Page 16 | 28
ltprice
fareBasis=rdquoCFLEX03rdquo
currency=rdquoEURrdquo nett=rdquo100000rdquo
tax=rdquo50000rdquo fees=rdquo000rdquo
total=rdquo150000rdquogt ltcoupongt
ltaddgt ltremovegt
ltcoupon tkne=rdquo123456789012345rdquo
recLoc=rdquoZH23T6rdquo status=rdquorrdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1645rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt ltpassenger
type=rdquoADTrdquo title=rdquoMRrdquo
firstName=rdquoFRANKrdquo familyName=rdquoOLSENrdquo
rbd=rdquoYrdquogt ltprice
fareBasis=rdquoYECON07rdquo currency=rdquoEURrdquo
nett=rdquo50000rdquo tax=rdquo50000rdquo
fees=rdquo1000rdquo
total=rdquo101000rdquogt ltcoupongt
ltcoupon tkne=rdquo123456789012345rdquo
recLoc=rdquoZH23T6rdquo status=rdquoerdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1645rdquo origin=rdquoCPHrdquo
destination=rdquoLHRrdquo rbd=rdquoCrdquogt
ltpassenger type=rdquoADTrdquo
title=rdquoMRSrdquo
firstName=rdquoLONErdquo
Confidential - Worldticket AS Page 17 | 28
familyName=rdquoOLSENrdquo
rbd=rdquoYrdquogt
ltprice fareBasis=rdquoYECON07rdquo
currency=rdquoEURrdquo nett=rdquo50000rdquo
tax=rdquo50000rdquo fees=rdquo1000rdquo
total=rdquo101000rdquogt ltcoupongt
ltremovegt lt deltaPNRListgt
Response
ltdeltaPNRList status=rdquoHKrdquogt
Confidential - Worldticket AS Page 18 | 28
4 USE CASES
Following basis is defined for the following use cases
TS is master system amp W1 SMS is secondary system
W1 SMS is gateway to 1A
In 1A a TS operated segment is sold as W1 hosted airline so W1 airline is
validating and marketing carrier and partner airline is operating carrier
Use case 1 Create reservation in 1A
Use case 2 Cancel reservation in 1A
Use case 3 Rebook reservation in 1A
Use case 4 Send PNR update to Master System
41 CREATE RESERVATION IN 1A
USE CASE 1
USE CASE Name Create Reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 with
TSRES as master when 1A is selling TSRES segments
Confidential - Worldticket AS Page 19 | 28
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS
POST CONDISTIONS Authorization level in W1 is in synch with assigned
authorization in TSRES
TRIGGER When TA creates a reservation in 1A on a W1 hosted airline
segment
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 On request by 1A W1 will
create a reservation on a TS
segment
2 W1 sends sellSeat
message to TS to inform that
a number of seats is sold on
specific flight event and RBD
3 TSRES confirm that
message is received and
understood
4 W1 request availability
from TSRES by flight
designator and departure
date
5 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
6 W1 updates INV with new
availability information
7 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
3a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 20 | 28
minute
5a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 21 | 28
42 CANCEL RESERVATION IN 1A
USE CASE 2
USE CASE Name Cancel reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS Reservation is already created in W1 and the sale have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Seat is release in INV and authorization level in W1 is in
synch with assigned authorization in TSRES
TRIGGER When TA cancels a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request W1 via 1A to
cancel an already confirmed
segment
Confidential - Worldticket AS Page 22 | 28
2 W1 cancel segments and
confirms cancellation to 1A
3 W1 sends releaseSeat
message to TSRES to inform
that a number of seats is
canceled on specific flight
event and RBD
4 TSRES confirm that
message is received and
understood
5 W1 request availability
from TSRES by flight
designator and departure
date
6 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
7 W1 updates INV with new
availability information
8 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 23 | 28
43 REBOOK RESERVATION IN 1A
USE CASE 3
USE CASE Name Rebook reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 25 times
PRE CONDITIONS Reservation is already created in W1 and te sell have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Request segment is rebook to another flight date or class
Availability in W1 is in synch with assigned authorization in
TSRES
TRIGGER When TA rebook a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request via 1A W1 to
rebook a specified segment
to another flight or class
Confidential - Worldticket AS Page 24 | 28
2 W1 reserve new segment
cancel old and confirms
action to 1A
3 W1 inform TSRES about
new sold segment by sending
sellSeat message
4TSRES confirm that
message is received and
understood
5 W1 informs TSRES that old
segment have been canceled
by sending releaseSeat
message
6 TSRES confirm that
message is received and
understood
7 W1 request availability
from TSRES by flight
designator and departure
date
8 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
9 W1 updates INV with new
availability information
10 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 25 | 28
minute
8a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 26 | 28
44 SEND PNR UPDATE TO TSRES
USE CASE 4
USE CASE Name Send PNR update to TSRES
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TSRES
PURPOSE To update TSRES with the daily sale in W1
LEVEL Primary
FREQUENCY Once every night
PRE CONDITIONS
POST CONDISTIONS
TRIGGER Scheduled job in W1
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 Base on schedule job W1
will generate 2 lists addition
and deletion list of all
changes since last time
TSRES were updated
2 W1 sends deltaPNRList
message to TSRES
3 TSRES confirm that
message is received and
understood
4 W1 saves timestamp for
Confidential - Worldticket AS Page 27 | 28
sending delta list
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
2a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 28 | 28
5 SMS Inventory Synchronization Overview Features
Monitoring of host transactions is logged in the ldquoSMS Host Transaction Overviewrdquo
In the same user interface are able to define filters to retrieve sent and received
transactions In the ldquoSMS Host Transaction Overview ldquo user interface you are able
to
Confidential - Worldticket AS Page 5 | 28
iv SMS daily administration
15 INV SYNC XMLs
The WEB-Service features support the following messages
1 login
2 sellSeat
3 releaseSeat
4 getAvailability
5 pushAvailability
6 deltaPNRList
16 System Flow Diagram
A typical solution could be architectured according to following System Flow
Diagram
0 GDS 1A 1G 1S could be enable as distributions channels for SMS
1 Schedules Inventory Fares etc uploaded to SMS by AL ADMIN
TS RESINV
MASTER
SMS 1A1G1S TA (1A)
OLTA
WEB
(1A)
TA
WEB
Tour
operator
Reference data
Schedules
Fares amp Rules
Sell Seat Get avail
Release seat
ATPCO OAG
Schedules
Fares
AL ADMIN
Push avail
Delta PNR
TA
WEB Tour
operator
Confidential - Worldticket AS Page 6 | 28
2 TS RESINV MASTER SYSTEM provides inventory levels via push availability
3 Reservations and Tickets are processed in Amadeus and forwarded to SMS
4 SMS forwards SellSeats to TS INVMASTER
5 SMS forwards Delta PNR to TS INVMASTER
6 AL provides PNL information to handling DCS
17 SYSTEM SEQUENCE DIAGRAM
The system sequence diagram shows the principal of the inventory integrations
between MTTRES and SMS
1 When Reservation is created via Travel Agent or WEB via TS RESINV then
MTTRES sends new total availability to SMS via the XML interface
2 When Amadeus travel agent or Amadeus enabled WEB-site searches for
routes then SMS replies with Route availability
3 When Amadeus travel agent or Amadeus enabled WEB-site makes a
reservation request via EDIFACT then if applicable SMS replies Amadeus with
a reservation confirmation
4 When Reservation is completed then SMS sends SellSeat to MTTRES via the
inventory XML interface
5 When Amadeus travel agent or Amadeus enabled WEB-site issues tickets then
SMS replies Amadeus with a ticket confirmation
TS RESINV TAWEB SMS TAWEB (1A)
Reservation
made
XML
PushAvailability
XML SellSeat
Search
RoutesAV
S
XML Delta PNR
Namelist
Reservation
requested
Ticket issued
Reservation
confirmed
XML Get
Availability
Confidential - Worldticket AS Page 7 | 28
6 SMS sends Delta Namelist via the inventory XML interface
2 MESSAGES
21 login
The purpose of this message is to get authorization from partner system to be able
to send synchronization messages
REQUEST
user
password
RESPONSE
authorizationCode
EXAMPLE
Request
ltlogin user=rdquow1rdquo password=rdquotestrdquogt
Response
ltlogin authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt
Confidential - Worldticket AS Page 8 | 28
22 sellSeat
REQUEST
authorizationCode
segment
Segment
recLoc Record locator in W1
flight Flight number
date Departure date and time from origin in airport local time
origin IATA 3 letter station code
destination IATA 3 letter station code
rbd Reservation Booking Designator
One letter code for booking class
value Number of sold seats
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
AIRIMP status codes HK or UC
errorCode Predefined codes
ErrorMessage Free text
EXAMPLE
Request
ltsellSeat authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1600rdquo origin=rdquoCPHrdquo
destination=rdquoLHRrdquo rbd=rdquoCrdquogt
3 ltsegmentgt
ltsellSeatgt
Response
ltsellSeat status=rdquoHKrdquogt
Confidential - Worldticket AS Page 9 | 28
23 releaseSeat
This message is to be used whenever a segment is cancelled or rebooked
REQUEST
authorizationCode
segment
Segment
flight Flight number
date Departure date from origin
origin IATA 3 letter station code
destination IATA 3 letter station code
rbd Reservation Booking Designator
One letter code for booking class
value Number of seats to releasecancel
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
errorCode Predefined codes
ErrorMessage Free text
EXAMPLE
Request
ltreleaseSeat
authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt ltsegment
no=rdquoW21111rdquo date=rdquo2008-12-15 1600rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt
3 ltsegmentgt
ltreleaseSeatgt
Response
ltreleaseSeat status=rdquoHKrdquogt
Confidential - Worldticket AS Page 10 | 28
24 getAvailability
This message is used for synchronizing availability
Based on the received information SMS will calculate availability as
availability = capacity + MAX(booked actual_booked)
REQUEST
authorizationCode
flight
flight
no Flight number
date Departure date from origin
RESPONSE
flight
flight
no Flight number
date Departure date from origin
segment
Segment
origin IATA 3 letter station code
destination IATA 3 letter station code
class
class
rbd Reservation Booking Designator
One letter code for booking class
capacity Number of seats authorized by TSRES in the class on the
given segment
sold Number of seats sold in the class on the given segment
according to TSRES
EXAMPLE
Request
ltgetAvailability
authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt ltflightno=rdquoW21111rdquo
date=rdquo2008-12-15 1600rdquogt
Confidential - Worldticket AS Page 11 | 28
ltgetAvailabilitygt
Response
ltgetAvailabilitygt ltflight
no=rdquoW21111rdquo date=rdquo2008-12-15 1600rdquogt
ltsegment origin=rdquoCPHrdquo
destination=rdquoLHRrdquogt ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltclass rbd=rdquoYrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt
ltsegmentgt ltsegment
origin=rdquoLHRrdquo destination=rdquoNYCrdquogt
ltclass rbd=rdquoCrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltclass rbd=rdquoYrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltsegmentgt ltsegment
origin=rdquoCPHrdquo destination=rdquoNYCrdquogt
ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltclass rbd=rdquoYrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltsegmentgt
ltflightgt ltgetAvailabilitygt
25 pushAvailability
This message is used for synchronizing availability Based on the received
information W1 will calculate availability as
Confidential - Worldticket AS Page 12 | 28
availability = capacity + MAX(booked actual_booked)
RESPONSE
authorizationCode
flight List of flights
flight
no Flight number
date Departure date from origin
segment List of segments
Segment
origin IATA 3 letter station code
destination IATA 3 letter station code
class
class
rbd Reservation Booking Designator
One letter code for booking class
capacity Number of seats authorized by TSRES in the class on the
given segment
sold Number of seats sold in the class on the given segment
according to TSRES
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
AIRIMP status codes like HK UC
errorCode Predefined codes
ErrorMessage Free text
Confidential - Worldticket AS Page 13 | 28
EXAMPLE
Request
ltpushAvailability authorizationCode=43543534sdfsdfds234234gt
ltflight date=2012-03-29 0840 no=W2901gt ltsegment destination=CPH origin=CDGgt
ltclass capacity=4 rbd=L sold=2gt ltsegmentgt
ltflightgt ltpushAvailabilitygt
or
ltpushAvailabilitygt
ltflight no=rdquoW21111rdquo
date=rdquo2008-12-15 1600rdquogt
ltsegment origin=rdquoCPHrdquo
destination=rdquoLHRrdquogt ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltclass rbd=rdquoYrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltsegmentgt
ltsegment origin=rdquoLHRrdquo
destination=rdquoNYCrdquogt ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo
sold=rdquo7rdquogt ltclass rbd=rdquoYrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltsegmentgt ltsegment
origin=rdquoCPHrdquo destination=rdquoNYCrdquogt
ltclass rbd=rdquoCrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltclass rbd=rdquoYrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltsegmentgt
ltflightgt
Confidential - Worldticket AS Page 14 | 28
ltpushAvailabilitygt
Response
ltpushAvailability status=rdquoHKrdquogt
3 DeltaPNRList
This message is used for synchronizing passenger information The message includes
all segments sold and cancelled since last sending
REQUEST
authorizationCode
add
Remove
add
coupon List of coupons issued since last update
Remove
coupon List of coupons canceled since last update
Coupon
tkne Ticket number
recLoc W1 record locator for reservation to which the coupon
belongs
status Standard IET coupon status indicator We expect that the
following should be enough
O Open for use
R Refunded
E Exchanged
segment List of segments
passenger List of passengers
price Price for pnr
Not mandatory as price maybe unknown in case of tickets
havenrsquot been issued yet
segment
flight Flight designator
date Departure date from origin
origin IATA 3 letter station code
destination IATA 3 letter station code
rbd One letter code for booking class
Confidential - Worldticket AS Page 15 | 28
passenger
type Passenger type ADT CHD INT
title Passenger title
firstName Passenger first name
Any character in UTF-8
familyName Passenger family name
Any character in UTF-8
price
fareBasis Fare basis code
nett
tax Sum of all charged taxes
fee Sum of all charged fees
total The total price including taxes and fees
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
AIRIMP status codes like HK UC
errorCode Predefined codes
ErrorMessage Free text
EXAMPLE
Request
ltdeltaPNRList
authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt
ltaddgt ltcoupon
tkne=rdquo123456789012345rdquo recLoc=rdquoZH23T6rdquo
status=rdquoordquogt ltsegment
flight=rdquoW21111rdquo date=rdquo2008-12-15 1645rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt ltpassenger
type=rdquoADTrdquo title=rdquoMRrdquo
firstName=rdquoSoslashrenrdquo
familyName=rdquoEjsingrdquo rbd=rdquoCrdquogt
Confidential - Worldticket AS Page 16 | 28
ltprice
fareBasis=rdquoCFLEX03rdquo
currency=rdquoEURrdquo nett=rdquo100000rdquo
tax=rdquo50000rdquo fees=rdquo000rdquo
total=rdquo150000rdquogt ltcoupongt
ltaddgt ltremovegt
ltcoupon tkne=rdquo123456789012345rdquo
recLoc=rdquoZH23T6rdquo status=rdquorrdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1645rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt ltpassenger
type=rdquoADTrdquo title=rdquoMRrdquo
firstName=rdquoFRANKrdquo familyName=rdquoOLSENrdquo
rbd=rdquoYrdquogt ltprice
fareBasis=rdquoYECON07rdquo currency=rdquoEURrdquo
nett=rdquo50000rdquo tax=rdquo50000rdquo
fees=rdquo1000rdquo
total=rdquo101000rdquogt ltcoupongt
ltcoupon tkne=rdquo123456789012345rdquo
recLoc=rdquoZH23T6rdquo status=rdquoerdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1645rdquo origin=rdquoCPHrdquo
destination=rdquoLHRrdquo rbd=rdquoCrdquogt
ltpassenger type=rdquoADTrdquo
title=rdquoMRSrdquo
firstName=rdquoLONErdquo
Confidential - Worldticket AS Page 17 | 28
familyName=rdquoOLSENrdquo
rbd=rdquoYrdquogt
ltprice fareBasis=rdquoYECON07rdquo
currency=rdquoEURrdquo nett=rdquo50000rdquo
tax=rdquo50000rdquo fees=rdquo1000rdquo
total=rdquo101000rdquogt ltcoupongt
ltremovegt lt deltaPNRListgt
Response
ltdeltaPNRList status=rdquoHKrdquogt
Confidential - Worldticket AS Page 18 | 28
4 USE CASES
Following basis is defined for the following use cases
TS is master system amp W1 SMS is secondary system
W1 SMS is gateway to 1A
In 1A a TS operated segment is sold as W1 hosted airline so W1 airline is
validating and marketing carrier and partner airline is operating carrier
Use case 1 Create reservation in 1A
Use case 2 Cancel reservation in 1A
Use case 3 Rebook reservation in 1A
Use case 4 Send PNR update to Master System
41 CREATE RESERVATION IN 1A
USE CASE 1
USE CASE Name Create Reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 with
TSRES as master when 1A is selling TSRES segments
Confidential - Worldticket AS Page 19 | 28
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS
POST CONDISTIONS Authorization level in W1 is in synch with assigned
authorization in TSRES
TRIGGER When TA creates a reservation in 1A on a W1 hosted airline
segment
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 On request by 1A W1 will
create a reservation on a TS
segment
2 W1 sends sellSeat
message to TS to inform that
a number of seats is sold on
specific flight event and RBD
3 TSRES confirm that
message is received and
understood
4 W1 request availability
from TSRES by flight
designator and departure
date
5 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
6 W1 updates INV with new
availability information
7 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
3a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 20 | 28
minute
5a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 21 | 28
42 CANCEL RESERVATION IN 1A
USE CASE 2
USE CASE Name Cancel reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS Reservation is already created in W1 and the sale have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Seat is release in INV and authorization level in W1 is in
synch with assigned authorization in TSRES
TRIGGER When TA cancels a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request W1 via 1A to
cancel an already confirmed
segment
Confidential - Worldticket AS Page 22 | 28
2 W1 cancel segments and
confirms cancellation to 1A
3 W1 sends releaseSeat
message to TSRES to inform
that a number of seats is
canceled on specific flight
event and RBD
4 TSRES confirm that
message is received and
understood
5 W1 request availability
from TSRES by flight
designator and departure
date
6 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
7 W1 updates INV with new
availability information
8 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 23 | 28
43 REBOOK RESERVATION IN 1A
USE CASE 3
USE CASE Name Rebook reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 25 times
PRE CONDITIONS Reservation is already created in W1 and te sell have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Request segment is rebook to another flight date or class
Availability in W1 is in synch with assigned authorization in
TSRES
TRIGGER When TA rebook a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request via 1A W1 to
rebook a specified segment
to another flight or class
Confidential - Worldticket AS Page 24 | 28
2 W1 reserve new segment
cancel old and confirms
action to 1A
3 W1 inform TSRES about
new sold segment by sending
sellSeat message
4TSRES confirm that
message is received and
understood
5 W1 informs TSRES that old
segment have been canceled
by sending releaseSeat
message
6 TSRES confirm that
message is received and
understood
7 W1 request availability
from TSRES by flight
designator and departure
date
8 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
9 W1 updates INV with new
availability information
10 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 25 | 28
minute
8a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 26 | 28
44 SEND PNR UPDATE TO TSRES
USE CASE 4
USE CASE Name Send PNR update to TSRES
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TSRES
PURPOSE To update TSRES with the daily sale in W1
LEVEL Primary
FREQUENCY Once every night
PRE CONDITIONS
POST CONDISTIONS
TRIGGER Scheduled job in W1
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 Base on schedule job W1
will generate 2 lists addition
and deletion list of all
changes since last time
TSRES were updated
2 W1 sends deltaPNRList
message to TSRES
3 TSRES confirm that
message is received and
understood
4 W1 saves timestamp for
Confidential - Worldticket AS Page 27 | 28
sending delta list
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
2a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 28 | 28
5 SMS Inventory Synchronization Overview Features
Monitoring of host transactions is logged in the ldquoSMS Host Transaction Overviewrdquo
In the same user interface are able to define filters to retrieve sent and received
transactions In the ldquoSMS Host Transaction Overview ldquo user interface you are able
to
Confidential - Worldticket AS Page 6 | 28
2 TS RESINV MASTER SYSTEM provides inventory levels via push availability
3 Reservations and Tickets are processed in Amadeus and forwarded to SMS
4 SMS forwards SellSeats to TS INVMASTER
5 SMS forwards Delta PNR to TS INVMASTER
6 AL provides PNL information to handling DCS
17 SYSTEM SEQUENCE DIAGRAM
The system sequence diagram shows the principal of the inventory integrations
between MTTRES and SMS
1 When Reservation is created via Travel Agent or WEB via TS RESINV then
MTTRES sends new total availability to SMS via the XML interface
2 When Amadeus travel agent or Amadeus enabled WEB-site searches for
routes then SMS replies with Route availability
3 When Amadeus travel agent or Amadeus enabled WEB-site makes a
reservation request via EDIFACT then if applicable SMS replies Amadeus with
a reservation confirmation
4 When Reservation is completed then SMS sends SellSeat to MTTRES via the
inventory XML interface
5 When Amadeus travel agent or Amadeus enabled WEB-site issues tickets then
SMS replies Amadeus with a ticket confirmation
TS RESINV TAWEB SMS TAWEB (1A)
Reservation
made
XML
PushAvailability
XML SellSeat
Search
RoutesAV
S
XML Delta PNR
Namelist
Reservation
requested
Ticket issued
Reservation
confirmed
XML Get
Availability
Confidential - Worldticket AS Page 7 | 28
6 SMS sends Delta Namelist via the inventory XML interface
2 MESSAGES
21 login
The purpose of this message is to get authorization from partner system to be able
to send synchronization messages
REQUEST
user
password
RESPONSE
authorizationCode
EXAMPLE
Request
ltlogin user=rdquow1rdquo password=rdquotestrdquogt
Response
ltlogin authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt
Confidential - Worldticket AS Page 8 | 28
22 sellSeat
REQUEST
authorizationCode
segment
Segment
recLoc Record locator in W1
flight Flight number
date Departure date and time from origin in airport local time
origin IATA 3 letter station code
destination IATA 3 letter station code
rbd Reservation Booking Designator
One letter code for booking class
value Number of sold seats
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
AIRIMP status codes HK or UC
errorCode Predefined codes
ErrorMessage Free text
EXAMPLE
Request
ltsellSeat authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1600rdquo origin=rdquoCPHrdquo
destination=rdquoLHRrdquo rbd=rdquoCrdquogt
3 ltsegmentgt
ltsellSeatgt
Response
ltsellSeat status=rdquoHKrdquogt
Confidential - Worldticket AS Page 9 | 28
23 releaseSeat
This message is to be used whenever a segment is cancelled or rebooked
REQUEST
authorizationCode
segment
Segment
flight Flight number
date Departure date from origin
origin IATA 3 letter station code
destination IATA 3 letter station code
rbd Reservation Booking Designator
One letter code for booking class
value Number of seats to releasecancel
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
errorCode Predefined codes
ErrorMessage Free text
EXAMPLE
Request
ltreleaseSeat
authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt ltsegment
no=rdquoW21111rdquo date=rdquo2008-12-15 1600rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt
3 ltsegmentgt
ltreleaseSeatgt
Response
ltreleaseSeat status=rdquoHKrdquogt
Confidential - Worldticket AS Page 10 | 28
24 getAvailability
This message is used for synchronizing availability
Based on the received information SMS will calculate availability as
availability = capacity + MAX(booked actual_booked)
REQUEST
authorizationCode
flight
flight
no Flight number
date Departure date from origin
RESPONSE
flight
flight
no Flight number
date Departure date from origin
segment
Segment
origin IATA 3 letter station code
destination IATA 3 letter station code
class
class
rbd Reservation Booking Designator
One letter code for booking class
capacity Number of seats authorized by TSRES in the class on the
given segment
sold Number of seats sold in the class on the given segment
according to TSRES
EXAMPLE
Request
ltgetAvailability
authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt ltflightno=rdquoW21111rdquo
date=rdquo2008-12-15 1600rdquogt
Confidential - Worldticket AS Page 11 | 28
ltgetAvailabilitygt
Response
ltgetAvailabilitygt ltflight
no=rdquoW21111rdquo date=rdquo2008-12-15 1600rdquogt
ltsegment origin=rdquoCPHrdquo
destination=rdquoLHRrdquogt ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltclass rbd=rdquoYrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt
ltsegmentgt ltsegment
origin=rdquoLHRrdquo destination=rdquoNYCrdquogt
ltclass rbd=rdquoCrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltclass rbd=rdquoYrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltsegmentgt ltsegment
origin=rdquoCPHrdquo destination=rdquoNYCrdquogt
ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltclass rbd=rdquoYrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltsegmentgt
ltflightgt ltgetAvailabilitygt
25 pushAvailability
This message is used for synchronizing availability Based on the received
information W1 will calculate availability as
Confidential - Worldticket AS Page 12 | 28
availability = capacity + MAX(booked actual_booked)
RESPONSE
authorizationCode
flight List of flights
flight
no Flight number
date Departure date from origin
segment List of segments
Segment
origin IATA 3 letter station code
destination IATA 3 letter station code
class
class
rbd Reservation Booking Designator
One letter code for booking class
capacity Number of seats authorized by TSRES in the class on the
given segment
sold Number of seats sold in the class on the given segment
according to TSRES
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
AIRIMP status codes like HK UC
errorCode Predefined codes
ErrorMessage Free text
Confidential - Worldticket AS Page 13 | 28
EXAMPLE
Request
ltpushAvailability authorizationCode=43543534sdfsdfds234234gt
ltflight date=2012-03-29 0840 no=W2901gt ltsegment destination=CPH origin=CDGgt
ltclass capacity=4 rbd=L sold=2gt ltsegmentgt
ltflightgt ltpushAvailabilitygt
or
ltpushAvailabilitygt
ltflight no=rdquoW21111rdquo
date=rdquo2008-12-15 1600rdquogt
ltsegment origin=rdquoCPHrdquo
destination=rdquoLHRrdquogt ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltclass rbd=rdquoYrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltsegmentgt
ltsegment origin=rdquoLHRrdquo
destination=rdquoNYCrdquogt ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo
sold=rdquo7rdquogt ltclass rbd=rdquoYrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltsegmentgt ltsegment
origin=rdquoCPHrdquo destination=rdquoNYCrdquogt
ltclass rbd=rdquoCrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltclass rbd=rdquoYrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltsegmentgt
ltflightgt
Confidential - Worldticket AS Page 14 | 28
ltpushAvailabilitygt
Response
ltpushAvailability status=rdquoHKrdquogt
3 DeltaPNRList
This message is used for synchronizing passenger information The message includes
all segments sold and cancelled since last sending
REQUEST
authorizationCode
add
Remove
add
coupon List of coupons issued since last update
Remove
coupon List of coupons canceled since last update
Coupon
tkne Ticket number
recLoc W1 record locator for reservation to which the coupon
belongs
status Standard IET coupon status indicator We expect that the
following should be enough
O Open for use
R Refunded
E Exchanged
segment List of segments
passenger List of passengers
price Price for pnr
Not mandatory as price maybe unknown in case of tickets
havenrsquot been issued yet
segment
flight Flight designator
date Departure date from origin
origin IATA 3 letter station code
destination IATA 3 letter station code
rbd One letter code for booking class
Confidential - Worldticket AS Page 15 | 28
passenger
type Passenger type ADT CHD INT
title Passenger title
firstName Passenger first name
Any character in UTF-8
familyName Passenger family name
Any character in UTF-8
price
fareBasis Fare basis code
nett
tax Sum of all charged taxes
fee Sum of all charged fees
total The total price including taxes and fees
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
AIRIMP status codes like HK UC
errorCode Predefined codes
ErrorMessage Free text
EXAMPLE
Request
ltdeltaPNRList
authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt
ltaddgt ltcoupon
tkne=rdquo123456789012345rdquo recLoc=rdquoZH23T6rdquo
status=rdquoordquogt ltsegment
flight=rdquoW21111rdquo date=rdquo2008-12-15 1645rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt ltpassenger
type=rdquoADTrdquo title=rdquoMRrdquo
firstName=rdquoSoslashrenrdquo
familyName=rdquoEjsingrdquo rbd=rdquoCrdquogt
Confidential - Worldticket AS Page 16 | 28
ltprice
fareBasis=rdquoCFLEX03rdquo
currency=rdquoEURrdquo nett=rdquo100000rdquo
tax=rdquo50000rdquo fees=rdquo000rdquo
total=rdquo150000rdquogt ltcoupongt
ltaddgt ltremovegt
ltcoupon tkne=rdquo123456789012345rdquo
recLoc=rdquoZH23T6rdquo status=rdquorrdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1645rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt ltpassenger
type=rdquoADTrdquo title=rdquoMRrdquo
firstName=rdquoFRANKrdquo familyName=rdquoOLSENrdquo
rbd=rdquoYrdquogt ltprice
fareBasis=rdquoYECON07rdquo currency=rdquoEURrdquo
nett=rdquo50000rdquo tax=rdquo50000rdquo
fees=rdquo1000rdquo
total=rdquo101000rdquogt ltcoupongt
ltcoupon tkne=rdquo123456789012345rdquo
recLoc=rdquoZH23T6rdquo status=rdquoerdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1645rdquo origin=rdquoCPHrdquo
destination=rdquoLHRrdquo rbd=rdquoCrdquogt
ltpassenger type=rdquoADTrdquo
title=rdquoMRSrdquo
firstName=rdquoLONErdquo
Confidential - Worldticket AS Page 17 | 28
familyName=rdquoOLSENrdquo
rbd=rdquoYrdquogt
ltprice fareBasis=rdquoYECON07rdquo
currency=rdquoEURrdquo nett=rdquo50000rdquo
tax=rdquo50000rdquo fees=rdquo1000rdquo
total=rdquo101000rdquogt ltcoupongt
ltremovegt lt deltaPNRListgt
Response
ltdeltaPNRList status=rdquoHKrdquogt
Confidential - Worldticket AS Page 18 | 28
4 USE CASES
Following basis is defined for the following use cases
TS is master system amp W1 SMS is secondary system
W1 SMS is gateway to 1A
In 1A a TS operated segment is sold as W1 hosted airline so W1 airline is
validating and marketing carrier and partner airline is operating carrier
Use case 1 Create reservation in 1A
Use case 2 Cancel reservation in 1A
Use case 3 Rebook reservation in 1A
Use case 4 Send PNR update to Master System
41 CREATE RESERVATION IN 1A
USE CASE 1
USE CASE Name Create Reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 with
TSRES as master when 1A is selling TSRES segments
Confidential - Worldticket AS Page 19 | 28
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS
POST CONDISTIONS Authorization level in W1 is in synch with assigned
authorization in TSRES
TRIGGER When TA creates a reservation in 1A on a W1 hosted airline
segment
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 On request by 1A W1 will
create a reservation on a TS
segment
2 W1 sends sellSeat
message to TS to inform that
a number of seats is sold on
specific flight event and RBD
3 TSRES confirm that
message is received and
understood
4 W1 request availability
from TSRES by flight
designator and departure
date
5 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
6 W1 updates INV with new
availability information
7 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
3a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 20 | 28
minute
5a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 21 | 28
42 CANCEL RESERVATION IN 1A
USE CASE 2
USE CASE Name Cancel reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS Reservation is already created in W1 and the sale have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Seat is release in INV and authorization level in W1 is in
synch with assigned authorization in TSRES
TRIGGER When TA cancels a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request W1 via 1A to
cancel an already confirmed
segment
Confidential - Worldticket AS Page 22 | 28
2 W1 cancel segments and
confirms cancellation to 1A
3 W1 sends releaseSeat
message to TSRES to inform
that a number of seats is
canceled on specific flight
event and RBD
4 TSRES confirm that
message is received and
understood
5 W1 request availability
from TSRES by flight
designator and departure
date
6 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
7 W1 updates INV with new
availability information
8 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 23 | 28
43 REBOOK RESERVATION IN 1A
USE CASE 3
USE CASE Name Rebook reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 25 times
PRE CONDITIONS Reservation is already created in W1 and te sell have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Request segment is rebook to another flight date or class
Availability in W1 is in synch with assigned authorization in
TSRES
TRIGGER When TA rebook a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request via 1A W1 to
rebook a specified segment
to another flight or class
Confidential - Worldticket AS Page 24 | 28
2 W1 reserve new segment
cancel old and confirms
action to 1A
3 W1 inform TSRES about
new sold segment by sending
sellSeat message
4TSRES confirm that
message is received and
understood
5 W1 informs TSRES that old
segment have been canceled
by sending releaseSeat
message
6 TSRES confirm that
message is received and
understood
7 W1 request availability
from TSRES by flight
designator and departure
date
8 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
9 W1 updates INV with new
availability information
10 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 25 | 28
minute
8a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 26 | 28
44 SEND PNR UPDATE TO TSRES
USE CASE 4
USE CASE Name Send PNR update to TSRES
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TSRES
PURPOSE To update TSRES with the daily sale in W1
LEVEL Primary
FREQUENCY Once every night
PRE CONDITIONS
POST CONDISTIONS
TRIGGER Scheduled job in W1
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 Base on schedule job W1
will generate 2 lists addition
and deletion list of all
changes since last time
TSRES were updated
2 W1 sends deltaPNRList
message to TSRES
3 TSRES confirm that
message is received and
understood
4 W1 saves timestamp for
Confidential - Worldticket AS Page 27 | 28
sending delta list
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
2a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 28 | 28
5 SMS Inventory Synchronization Overview Features
Monitoring of host transactions is logged in the ldquoSMS Host Transaction Overviewrdquo
In the same user interface are able to define filters to retrieve sent and received
transactions In the ldquoSMS Host Transaction Overview ldquo user interface you are able
to
Confidential - Worldticket AS Page 7 | 28
6 SMS sends Delta Namelist via the inventory XML interface
2 MESSAGES
21 login
The purpose of this message is to get authorization from partner system to be able
to send synchronization messages
REQUEST
user
password
RESPONSE
authorizationCode
EXAMPLE
Request
ltlogin user=rdquow1rdquo password=rdquotestrdquogt
Response
ltlogin authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt
Confidential - Worldticket AS Page 8 | 28
22 sellSeat
REQUEST
authorizationCode
segment
Segment
recLoc Record locator in W1
flight Flight number
date Departure date and time from origin in airport local time
origin IATA 3 letter station code
destination IATA 3 letter station code
rbd Reservation Booking Designator
One letter code for booking class
value Number of sold seats
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
AIRIMP status codes HK or UC
errorCode Predefined codes
ErrorMessage Free text
EXAMPLE
Request
ltsellSeat authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1600rdquo origin=rdquoCPHrdquo
destination=rdquoLHRrdquo rbd=rdquoCrdquogt
3 ltsegmentgt
ltsellSeatgt
Response
ltsellSeat status=rdquoHKrdquogt
Confidential - Worldticket AS Page 9 | 28
23 releaseSeat
This message is to be used whenever a segment is cancelled or rebooked
REQUEST
authorizationCode
segment
Segment
flight Flight number
date Departure date from origin
origin IATA 3 letter station code
destination IATA 3 letter station code
rbd Reservation Booking Designator
One letter code for booking class
value Number of seats to releasecancel
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
errorCode Predefined codes
ErrorMessage Free text
EXAMPLE
Request
ltreleaseSeat
authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt ltsegment
no=rdquoW21111rdquo date=rdquo2008-12-15 1600rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt
3 ltsegmentgt
ltreleaseSeatgt
Response
ltreleaseSeat status=rdquoHKrdquogt
Confidential - Worldticket AS Page 10 | 28
24 getAvailability
This message is used for synchronizing availability
Based on the received information SMS will calculate availability as
availability = capacity + MAX(booked actual_booked)
REQUEST
authorizationCode
flight
flight
no Flight number
date Departure date from origin
RESPONSE
flight
flight
no Flight number
date Departure date from origin
segment
Segment
origin IATA 3 letter station code
destination IATA 3 letter station code
class
class
rbd Reservation Booking Designator
One letter code for booking class
capacity Number of seats authorized by TSRES in the class on the
given segment
sold Number of seats sold in the class on the given segment
according to TSRES
EXAMPLE
Request
ltgetAvailability
authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt ltflightno=rdquoW21111rdquo
date=rdquo2008-12-15 1600rdquogt
Confidential - Worldticket AS Page 11 | 28
ltgetAvailabilitygt
Response
ltgetAvailabilitygt ltflight
no=rdquoW21111rdquo date=rdquo2008-12-15 1600rdquogt
ltsegment origin=rdquoCPHrdquo
destination=rdquoLHRrdquogt ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltclass rbd=rdquoYrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt
ltsegmentgt ltsegment
origin=rdquoLHRrdquo destination=rdquoNYCrdquogt
ltclass rbd=rdquoCrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltclass rbd=rdquoYrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltsegmentgt ltsegment
origin=rdquoCPHrdquo destination=rdquoNYCrdquogt
ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltclass rbd=rdquoYrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltsegmentgt
ltflightgt ltgetAvailabilitygt
25 pushAvailability
This message is used for synchronizing availability Based on the received
information W1 will calculate availability as
Confidential - Worldticket AS Page 12 | 28
availability = capacity + MAX(booked actual_booked)
RESPONSE
authorizationCode
flight List of flights
flight
no Flight number
date Departure date from origin
segment List of segments
Segment
origin IATA 3 letter station code
destination IATA 3 letter station code
class
class
rbd Reservation Booking Designator
One letter code for booking class
capacity Number of seats authorized by TSRES in the class on the
given segment
sold Number of seats sold in the class on the given segment
according to TSRES
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
AIRIMP status codes like HK UC
errorCode Predefined codes
ErrorMessage Free text
Confidential - Worldticket AS Page 13 | 28
EXAMPLE
Request
ltpushAvailability authorizationCode=43543534sdfsdfds234234gt
ltflight date=2012-03-29 0840 no=W2901gt ltsegment destination=CPH origin=CDGgt
ltclass capacity=4 rbd=L sold=2gt ltsegmentgt
ltflightgt ltpushAvailabilitygt
or
ltpushAvailabilitygt
ltflight no=rdquoW21111rdquo
date=rdquo2008-12-15 1600rdquogt
ltsegment origin=rdquoCPHrdquo
destination=rdquoLHRrdquogt ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltclass rbd=rdquoYrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltsegmentgt
ltsegment origin=rdquoLHRrdquo
destination=rdquoNYCrdquogt ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo
sold=rdquo7rdquogt ltclass rbd=rdquoYrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltsegmentgt ltsegment
origin=rdquoCPHrdquo destination=rdquoNYCrdquogt
ltclass rbd=rdquoCrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltclass rbd=rdquoYrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltsegmentgt
ltflightgt
Confidential - Worldticket AS Page 14 | 28
ltpushAvailabilitygt
Response
ltpushAvailability status=rdquoHKrdquogt
3 DeltaPNRList
This message is used for synchronizing passenger information The message includes
all segments sold and cancelled since last sending
REQUEST
authorizationCode
add
Remove
add
coupon List of coupons issued since last update
Remove
coupon List of coupons canceled since last update
Coupon
tkne Ticket number
recLoc W1 record locator for reservation to which the coupon
belongs
status Standard IET coupon status indicator We expect that the
following should be enough
O Open for use
R Refunded
E Exchanged
segment List of segments
passenger List of passengers
price Price for pnr
Not mandatory as price maybe unknown in case of tickets
havenrsquot been issued yet
segment
flight Flight designator
date Departure date from origin
origin IATA 3 letter station code
destination IATA 3 letter station code
rbd One letter code for booking class
Confidential - Worldticket AS Page 15 | 28
passenger
type Passenger type ADT CHD INT
title Passenger title
firstName Passenger first name
Any character in UTF-8
familyName Passenger family name
Any character in UTF-8
price
fareBasis Fare basis code
nett
tax Sum of all charged taxes
fee Sum of all charged fees
total The total price including taxes and fees
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
AIRIMP status codes like HK UC
errorCode Predefined codes
ErrorMessage Free text
EXAMPLE
Request
ltdeltaPNRList
authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt
ltaddgt ltcoupon
tkne=rdquo123456789012345rdquo recLoc=rdquoZH23T6rdquo
status=rdquoordquogt ltsegment
flight=rdquoW21111rdquo date=rdquo2008-12-15 1645rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt ltpassenger
type=rdquoADTrdquo title=rdquoMRrdquo
firstName=rdquoSoslashrenrdquo
familyName=rdquoEjsingrdquo rbd=rdquoCrdquogt
Confidential - Worldticket AS Page 16 | 28
ltprice
fareBasis=rdquoCFLEX03rdquo
currency=rdquoEURrdquo nett=rdquo100000rdquo
tax=rdquo50000rdquo fees=rdquo000rdquo
total=rdquo150000rdquogt ltcoupongt
ltaddgt ltremovegt
ltcoupon tkne=rdquo123456789012345rdquo
recLoc=rdquoZH23T6rdquo status=rdquorrdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1645rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt ltpassenger
type=rdquoADTrdquo title=rdquoMRrdquo
firstName=rdquoFRANKrdquo familyName=rdquoOLSENrdquo
rbd=rdquoYrdquogt ltprice
fareBasis=rdquoYECON07rdquo currency=rdquoEURrdquo
nett=rdquo50000rdquo tax=rdquo50000rdquo
fees=rdquo1000rdquo
total=rdquo101000rdquogt ltcoupongt
ltcoupon tkne=rdquo123456789012345rdquo
recLoc=rdquoZH23T6rdquo status=rdquoerdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1645rdquo origin=rdquoCPHrdquo
destination=rdquoLHRrdquo rbd=rdquoCrdquogt
ltpassenger type=rdquoADTrdquo
title=rdquoMRSrdquo
firstName=rdquoLONErdquo
Confidential - Worldticket AS Page 17 | 28
familyName=rdquoOLSENrdquo
rbd=rdquoYrdquogt
ltprice fareBasis=rdquoYECON07rdquo
currency=rdquoEURrdquo nett=rdquo50000rdquo
tax=rdquo50000rdquo fees=rdquo1000rdquo
total=rdquo101000rdquogt ltcoupongt
ltremovegt lt deltaPNRListgt
Response
ltdeltaPNRList status=rdquoHKrdquogt
Confidential - Worldticket AS Page 18 | 28
4 USE CASES
Following basis is defined for the following use cases
TS is master system amp W1 SMS is secondary system
W1 SMS is gateway to 1A
In 1A a TS operated segment is sold as W1 hosted airline so W1 airline is
validating and marketing carrier and partner airline is operating carrier
Use case 1 Create reservation in 1A
Use case 2 Cancel reservation in 1A
Use case 3 Rebook reservation in 1A
Use case 4 Send PNR update to Master System
41 CREATE RESERVATION IN 1A
USE CASE 1
USE CASE Name Create Reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 with
TSRES as master when 1A is selling TSRES segments
Confidential - Worldticket AS Page 19 | 28
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS
POST CONDISTIONS Authorization level in W1 is in synch with assigned
authorization in TSRES
TRIGGER When TA creates a reservation in 1A on a W1 hosted airline
segment
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 On request by 1A W1 will
create a reservation on a TS
segment
2 W1 sends sellSeat
message to TS to inform that
a number of seats is sold on
specific flight event and RBD
3 TSRES confirm that
message is received and
understood
4 W1 request availability
from TSRES by flight
designator and departure
date
5 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
6 W1 updates INV with new
availability information
7 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
3a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 20 | 28
minute
5a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 21 | 28
42 CANCEL RESERVATION IN 1A
USE CASE 2
USE CASE Name Cancel reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS Reservation is already created in W1 and the sale have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Seat is release in INV and authorization level in W1 is in
synch with assigned authorization in TSRES
TRIGGER When TA cancels a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request W1 via 1A to
cancel an already confirmed
segment
Confidential - Worldticket AS Page 22 | 28
2 W1 cancel segments and
confirms cancellation to 1A
3 W1 sends releaseSeat
message to TSRES to inform
that a number of seats is
canceled on specific flight
event and RBD
4 TSRES confirm that
message is received and
understood
5 W1 request availability
from TSRES by flight
designator and departure
date
6 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
7 W1 updates INV with new
availability information
8 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 23 | 28
43 REBOOK RESERVATION IN 1A
USE CASE 3
USE CASE Name Rebook reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 25 times
PRE CONDITIONS Reservation is already created in W1 and te sell have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Request segment is rebook to another flight date or class
Availability in W1 is in synch with assigned authorization in
TSRES
TRIGGER When TA rebook a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request via 1A W1 to
rebook a specified segment
to another flight or class
Confidential - Worldticket AS Page 24 | 28
2 W1 reserve new segment
cancel old and confirms
action to 1A
3 W1 inform TSRES about
new sold segment by sending
sellSeat message
4TSRES confirm that
message is received and
understood
5 W1 informs TSRES that old
segment have been canceled
by sending releaseSeat
message
6 TSRES confirm that
message is received and
understood
7 W1 request availability
from TSRES by flight
designator and departure
date
8 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
9 W1 updates INV with new
availability information
10 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 25 | 28
minute
8a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 26 | 28
44 SEND PNR UPDATE TO TSRES
USE CASE 4
USE CASE Name Send PNR update to TSRES
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TSRES
PURPOSE To update TSRES with the daily sale in W1
LEVEL Primary
FREQUENCY Once every night
PRE CONDITIONS
POST CONDISTIONS
TRIGGER Scheduled job in W1
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 Base on schedule job W1
will generate 2 lists addition
and deletion list of all
changes since last time
TSRES were updated
2 W1 sends deltaPNRList
message to TSRES
3 TSRES confirm that
message is received and
understood
4 W1 saves timestamp for
Confidential - Worldticket AS Page 27 | 28
sending delta list
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
2a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 28 | 28
5 SMS Inventory Synchronization Overview Features
Monitoring of host transactions is logged in the ldquoSMS Host Transaction Overviewrdquo
In the same user interface are able to define filters to retrieve sent and received
transactions In the ldquoSMS Host Transaction Overview ldquo user interface you are able
to
Confidential - Worldticket AS Page 8 | 28
22 sellSeat
REQUEST
authorizationCode
segment
Segment
recLoc Record locator in W1
flight Flight number
date Departure date and time from origin in airport local time
origin IATA 3 letter station code
destination IATA 3 letter station code
rbd Reservation Booking Designator
One letter code for booking class
value Number of sold seats
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
AIRIMP status codes HK or UC
errorCode Predefined codes
ErrorMessage Free text
EXAMPLE
Request
ltsellSeat authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1600rdquo origin=rdquoCPHrdquo
destination=rdquoLHRrdquo rbd=rdquoCrdquogt
3 ltsegmentgt
ltsellSeatgt
Response
ltsellSeat status=rdquoHKrdquogt
Confidential - Worldticket AS Page 9 | 28
23 releaseSeat
This message is to be used whenever a segment is cancelled or rebooked
REQUEST
authorizationCode
segment
Segment
flight Flight number
date Departure date from origin
origin IATA 3 letter station code
destination IATA 3 letter station code
rbd Reservation Booking Designator
One letter code for booking class
value Number of seats to releasecancel
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
errorCode Predefined codes
ErrorMessage Free text
EXAMPLE
Request
ltreleaseSeat
authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt ltsegment
no=rdquoW21111rdquo date=rdquo2008-12-15 1600rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt
3 ltsegmentgt
ltreleaseSeatgt
Response
ltreleaseSeat status=rdquoHKrdquogt
Confidential - Worldticket AS Page 10 | 28
24 getAvailability
This message is used for synchronizing availability
Based on the received information SMS will calculate availability as
availability = capacity + MAX(booked actual_booked)
REQUEST
authorizationCode
flight
flight
no Flight number
date Departure date from origin
RESPONSE
flight
flight
no Flight number
date Departure date from origin
segment
Segment
origin IATA 3 letter station code
destination IATA 3 letter station code
class
class
rbd Reservation Booking Designator
One letter code for booking class
capacity Number of seats authorized by TSRES in the class on the
given segment
sold Number of seats sold in the class on the given segment
according to TSRES
EXAMPLE
Request
ltgetAvailability
authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt ltflightno=rdquoW21111rdquo
date=rdquo2008-12-15 1600rdquogt
Confidential - Worldticket AS Page 11 | 28
ltgetAvailabilitygt
Response
ltgetAvailabilitygt ltflight
no=rdquoW21111rdquo date=rdquo2008-12-15 1600rdquogt
ltsegment origin=rdquoCPHrdquo
destination=rdquoLHRrdquogt ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltclass rbd=rdquoYrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt
ltsegmentgt ltsegment
origin=rdquoLHRrdquo destination=rdquoNYCrdquogt
ltclass rbd=rdquoCrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltclass rbd=rdquoYrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltsegmentgt ltsegment
origin=rdquoCPHrdquo destination=rdquoNYCrdquogt
ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltclass rbd=rdquoYrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltsegmentgt
ltflightgt ltgetAvailabilitygt
25 pushAvailability
This message is used for synchronizing availability Based on the received
information W1 will calculate availability as
Confidential - Worldticket AS Page 12 | 28
availability = capacity + MAX(booked actual_booked)
RESPONSE
authorizationCode
flight List of flights
flight
no Flight number
date Departure date from origin
segment List of segments
Segment
origin IATA 3 letter station code
destination IATA 3 letter station code
class
class
rbd Reservation Booking Designator
One letter code for booking class
capacity Number of seats authorized by TSRES in the class on the
given segment
sold Number of seats sold in the class on the given segment
according to TSRES
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
AIRIMP status codes like HK UC
errorCode Predefined codes
ErrorMessage Free text
Confidential - Worldticket AS Page 13 | 28
EXAMPLE
Request
ltpushAvailability authorizationCode=43543534sdfsdfds234234gt
ltflight date=2012-03-29 0840 no=W2901gt ltsegment destination=CPH origin=CDGgt
ltclass capacity=4 rbd=L sold=2gt ltsegmentgt
ltflightgt ltpushAvailabilitygt
or
ltpushAvailabilitygt
ltflight no=rdquoW21111rdquo
date=rdquo2008-12-15 1600rdquogt
ltsegment origin=rdquoCPHrdquo
destination=rdquoLHRrdquogt ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltclass rbd=rdquoYrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltsegmentgt
ltsegment origin=rdquoLHRrdquo
destination=rdquoNYCrdquogt ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo
sold=rdquo7rdquogt ltclass rbd=rdquoYrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltsegmentgt ltsegment
origin=rdquoCPHrdquo destination=rdquoNYCrdquogt
ltclass rbd=rdquoCrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltclass rbd=rdquoYrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltsegmentgt
ltflightgt
Confidential - Worldticket AS Page 14 | 28
ltpushAvailabilitygt
Response
ltpushAvailability status=rdquoHKrdquogt
3 DeltaPNRList
This message is used for synchronizing passenger information The message includes
all segments sold and cancelled since last sending
REQUEST
authorizationCode
add
Remove
add
coupon List of coupons issued since last update
Remove
coupon List of coupons canceled since last update
Coupon
tkne Ticket number
recLoc W1 record locator for reservation to which the coupon
belongs
status Standard IET coupon status indicator We expect that the
following should be enough
O Open for use
R Refunded
E Exchanged
segment List of segments
passenger List of passengers
price Price for pnr
Not mandatory as price maybe unknown in case of tickets
havenrsquot been issued yet
segment
flight Flight designator
date Departure date from origin
origin IATA 3 letter station code
destination IATA 3 letter station code
rbd One letter code for booking class
Confidential - Worldticket AS Page 15 | 28
passenger
type Passenger type ADT CHD INT
title Passenger title
firstName Passenger first name
Any character in UTF-8
familyName Passenger family name
Any character in UTF-8
price
fareBasis Fare basis code
nett
tax Sum of all charged taxes
fee Sum of all charged fees
total The total price including taxes and fees
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
AIRIMP status codes like HK UC
errorCode Predefined codes
ErrorMessage Free text
EXAMPLE
Request
ltdeltaPNRList
authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt
ltaddgt ltcoupon
tkne=rdquo123456789012345rdquo recLoc=rdquoZH23T6rdquo
status=rdquoordquogt ltsegment
flight=rdquoW21111rdquo date=rdquo2008-12-15 1645rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt ltpassenger
type=rdquoADTrdquo title=rdquoMRrdquo
firstName=rdquoSoslashrenrdquo
familyName=rdquoEjsingrdquo rbd=rdquoCrdquogt
Confidential - Worldticket AS Page 16 | 28
ltprice
fareBasis=rdquoCFLEX03rdquo
currency=rdquoEURrdquo nett=rdquo100000rdquo
tax=rdquo50000rdquo fees=rdquo000rdquo
total=rdquo150000rdquogt ltcoupongt
ltaddgt ltremovegt
ltcoupon tkne=rdquo123456789012345rdquo
recLoc=rdquoZH23T6rdquo status=rdquorrdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1645rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt ltpassenger
type=rdquoADTrdquo title=rdquoMRrdquo
firstName=rdquoFRANKrdquo familyName=rdquoOLSENrdquo
rbd=rdquoYrdquogt ltprice
fareBasis=rdquoYECON07rdquo currency=rdquoEURrdquo
nett=rdquo50000rdquo tax=rdquo50000rdquo
fees=rdquo1000rdquo
total=rdquo101000rdquogt ltcoupongt
ltcoupon tkne=rdquo123456789012345rdquo
recLoc=rdquoZH23T6rdquo status=rdquoerdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1645rdquo origin=rdquoCPHrdquo
destination=rdquoLHRrdquo rbd=rdquoCrdquogt
ltpassenger type=rdquoADTrdquo
title=rdquoMRSrdquo
firstName=rdquoLONErdquo
Confidential - Worldticket AS Page 17 | 28
familyName=rdquoOLSENrdquo
rbd=rdquoYrdquogt
ltprice fareBasis=rdquoYECON07rdquo
currency=rdquoEURrdquo nett=rdquo50000rdquo
tax=rdquo50000rdquo fees=rdquo1000rdquo
total=rdquo101000rdquogt ltcoupongt
ltremovegt lt deltaPNRListgt
Response
ltdeltaPNRList status=rdquoHKrdquogt
Confidential - Worldticket AS Page 18 | 28
4 USE CASES
Following basis is defined for the following use cases
TS is master system amp W1 SMS is secondary system
W1 SMS is gateway to 1A
In 1A a TS operated segment is sold as W1 hosted airline so W1 airline is
validating and marketing carrier and partner airline is operating carrier
Use case 1 Create reservation in 1A
Use case 2 Cancel reservation in 1A
Use case 3 Rebook reservation in 1A
Use case 4 Send PNR update to Master System
41 CREATE RESERVATION IN 1A
USE CASE 1
USE CASE Name Create Reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 with
TSRES as master when 1A is selling TSRES segments
Confidential - Worldticket AS Page 19 | 28
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS
POST CONDISTIONS Authorization level in W1 is in synch with assigned
authorization in TSRES
TRIGGER When TA creates a reservation in 1A on a W1 hosted airline
segment
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 On request by 1A W1 will
create a reservation on a TS
segment
2 W1 sends sellSeat
message to TS to inform that
a number of seats is sold on
specific flight event and RBD
3 TSRES confirm that
message is received and
understood
4 W1 request availability
from TSRES by flight
designator and departure
date
5 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
6 W1 updates INV with new
availability information
7 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
3a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 20 | 28
minute
5a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 21 | 28
42 CANCEL RESERVATION IN 1A
USE CASE 2
USE CASE Name Cancel reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS Reservation is already created in W1 and the sale have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Seat is release in INV and authorization level in W1 is in
synch with assigned authorization in TSRES
TRIGGER When TA cancels a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request W1 via 1A to
cancel an already confirmed
segment
Confidential - Worldticket AS Page 22 | 28
2 W1 cancel segments and
confirms cancellation to 1A
3 W1 sends releaseSeat
message to TSRES to inform
that a number of seats is
canceled on specific flight
event and RBD
4 TSRES confirm that
message is received and
understood
5 W1 request availability
from TSRES by flight
designator and departure
date
6 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
7 W1 updates INV with new
availability information
8 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 23 | 28
43 REBOOK RESERVATION IN 1A
USE CASE 3
USE CASE Name Rebook reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 25 times
PRE CONDITIONS Reservation is already created in W1 and te sell have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Request segment is rebook to another flight date or class
Availability in W1 is in synch with assigned authorization in
TSRES
TRIGGER When TA rebook a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request via 1A W1 to
rebook a specified segment
to another flight or class
Confidential - Worldticket AS Page 24 | 28
2 W1 reserve new segment
cancel old and confirms
action to 1A
3 W1 inform TSRES about
new sold segment by sending
sellSeat message
4TSRES confirm that
message is received and
understood
5 W1 informs TSRES that old
segment have been canceled
by sending releaseSeat
message
6 TSRES confirm that
message is received and
understood
7 W1 request availability
from TSRES by flight
designator and departure
date
8 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
9 W1 updates INV with new
availability information
10 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 25 | 28
minute
8a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 26 | 28
44 SEND PNR UPDATE TO TSRES
USE CASE 4
USE CASE Name Send PNR update to TSRES
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TSRES
PURPOSE To update TSRES with the daily sale in W1
LEVEL Primary
FREQUENCY Once every night
PRE CONDITIONS
POST CONDISTIONS
TRIGGER Scheduled job in W1
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 Base on schedule job W1
will generate 2 lists addition
and deletion list of all
changes since last time
TSRES were updated
2 W1 sends deltaPNRList
message to TSRES
3 TSRES confirm that
message is received and
understood
4 W1 saves timestamp for
Confidential - Worldticket AS Page 27 | 28
sending delta list
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
2a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 28 | 28
5 SMS Inventory Synchronization Overview Features
Monitoring of host transactions is logged in the ldquoSMS Host Transaction Overviewrdquo
In the same user interface are able to define filters to retrieve sent and received
transactions In the ldquoSMS Host Transaction Overview ldquo user interface you are able
to
Confidential - Worldticket AS Page 9 | 28
23 releaseSeat
This message is to be used whenever a segment is cancelled or rebooked
REQUEST
authorizationCode
segment
Segment
flight Flight number
date Departure date from origin
origin IATA 3 letter station code
destination IATA 3 letter station code
rbd Reservation Booking Designator
One letter code for booking class
value Number of seats to releasecancel
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
errorCode Predefined codes
ErrorMessage Free text
EXAMPLE
Request
ltreleaseSeat
authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt ltsegment
no=rdquoW21111rdquo date=rdquo2008-12-15 1600rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt
3 ltsegmentgt
ltreleaseSeatgt
Response
ltreleaseSeat status=rdquoHKrdquogt
Confidential - Worldticket AS Page 10 | 28
24 getAvailability
This message is used for synchronizing availability
Based on the received information SMS will calculate availability as
availability = capacity + MAX(booked actual_booked)
REQUEST
authorizationCode
flight
flight
no Flight number
date Departure date from origin
RESPONSE
flight
flight
no Flight number
date Departure date from origin
segment
Segment
origin IATA 3 letter station code
destination IATA 3 letter station code
class
class
rbd Reservation Booking Designator
One letter code for booking class
capacity Number of seats authorized by TSRES in the class on the
given segment
sold Number of seats sold in the class on the given segment
according to TSRES
EXAMPLE
Request
ltgetAvailability
authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt ltflightno=rdquoW21111rdquo
date=rdquo2008-12-15 1600rdquogt
Confidential - Worldticket AS Page 11 | 28
ltgetAvailabilitygt
Response
ltgetAvailabilitygt ltflight
no=rdquoW21111rdquo date=rdquo2008-12-15 1600rdquogt
ltsegment origin=rdquoCPHrdquo
destination=rdquoLHRrdquogt ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltclass rbd=rdquoYrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt
ltsegmentgt ltsegment
origin=rdquoLHRrdquo destination=rdquoNYCrdquogt
ltclass rbd=rdquoCrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltclass rbd=rdquoYrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltsegmentgt ltsegment
origin=rdquoCPHrdquo destination=rdquoNYCrdquogt
ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltclass rbd=rdquoYrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltsegmentgt
ltflightgt ltgetAvailabilitygt
25 pushAvailability
This message is used for synchronizing availability Based on the received
information W1 will calculate availability as
Confidential - Worldticket AS Page 12 | 28
availability = capacity + MAX(booked actual_booked)
RESPONSE
authorizationCode
flight List of flights
flight
no Flight number
date Departure date from origin
segment List of segments
Segment
origin IATA 3 letter station code
destination IATA 3 letter station code
class
class
rbd Reservation Booking Designator
One letter code for booking class
capacity Number of seats authorized by TSRES in the class on the
given segment
sold Number of seats sold in the class on the given segment
according to TSRES
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
AIRIMP status codes like HK UC
errorCode Predefined codes
ErrorMessage Free text
Confidential - Worldticket AS Page 13 | 28
EXAMPLE
Request
ltpushAvailability authorizationCode=43543534sdfsdfds234234gt
ltflight date=2012-03-29 0840 no=W2901gt ltsegment destination=CPH origin=CDGgt
ltclass capacity=4 rbd=L sold=2gt ltsegmentgt
ltflightgt ltpushAvailabilitygt
or
ltpushAvailabilitygt
ltflight no=rdquoW21111rdquo
date=rdquo2008-12-15 1600rdquogt
ltsegment origin=rdquoCPHrdquo
destination=rdquoLHRrdquogt ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltclass rbd=rdquoYrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltsegmentgt
ltsegment origin=rdquoLHRrdquo
destination=rdquoNYCrdquogt ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo
sold=rdquo7rdquogt ltclass rbd=rdquoYrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltsegmentgt ltsegment
origin=rdquoCPHrdquo destination=rdquoNYCrdquogt
ltclass rbd=rdquoCrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltclass rbd=rdquoYrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltsegmentgt
ltflightgt
Confidential - Worldticket AS Page 14 | 28
ltpushAvailabilitygt
Response
ltpushAvailability status=rdquoHKrdquogt
3 DeltaPNRList
This message is used for synchronizing passenger information The message includes
all segments sold and cancelled since last sending
REQUEST
authorizationCode
add
Remove
add
coupon List of coupons issued since last update
Remove
coupon List of coupons canceled since last update
Coupon
tkne Ticket number
recLoc W1 record locator for reservation to which the coupon
belongs
status Standard IET coupon status indicator We expect that the
following should be enough
O Open for use
R Refunded
E Exchanged
segment List of segments
passenger List of passengers
price Price for pnr
Not mandatory as price maybe unknown in case of tickets
havenrsquot been issued yet
segment
flight Flight designator
date Departure date from origin
origin IATA 3 letter station code
destination IATA 3 letter station code
rbd One letter code for booking class
Confidential - Worldticket AS Page 15 | 28
passenger
type Passenger type ADT CHD INT
title Passenger title
firstName Passenger first name
Any character in UTF-8
familyName Passenger family name
Any character in UTF-8
price
fareBasis Fare basis code
nett
tax Sum of all charged taxes
fee Sum of all charged fees
total The total price including taxes and fees
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
AIRIMP status codes like HK UC
errorCode Predefined codes
ErrorMessage Free text
EXAMPLE
Request
ltdeltaPNRList
authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt
ltaddgt ltcoupon
tkne=rdquo123456789012345rdquo recLoc=rdquoZH23T6rdquo
status=rdquoordquogt ltsegment
flight=rdquoW21111rdquo date=rdquo2008-12-15 1645rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt ltpassenger
type=rdquoADTrdquo title=rdquoMRrdquo
firstName=rdquoSoslashrenrdquo
familyName=rdquoEjsingrdquo rbd=rdquoCrdquogt
Confidential - Worldticket AS Page 16 | 28
ltprice
fareBasis=rdquoCFLEX03rdquo
currency=rdquoEURrdquo nett=rdquo100000rdquo
tax=rdquo50000rdquo fees=rdquo000rdquo
total=rdquo150000rdquogt ltcoupongt
ltaddgt ltremovegt
ltcoupon tkne=rdquo123456789012345rdquo
recLoc=rdquoZH23T6rdquo status=rdquorrdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1645rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt ltpassenger
type=rdquoADTrdquo title=rdquoMRrdquo
firstName=rdquoFRANKrdquo familyName=rdquoOLSENrdquo
rbd=rdquoYrdquogt ltprice
fareBasis=rdquoYECON07rdquo currency=rdquoEURrdquo
nett=rdquo50000rdquo tax=rdquo50000rdquo
fees=rdquo1000rdquo
total=rdquo101000rdquogt ltcoupongt
ltcoupon tkne=rdquo123456789012345rdquo
recLoc=rdquoZH23T6rdquo status=rdquoerdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1645rdquo origin=rdquoCPHrdquo
destination=rdquoLHRrdquo rbd=rdquoCrdquogt
ltpassenger type=rdquoADTrdquo
title=rdquoMRSrdquo
firstName=rdquoLONErdquo
Confidential - Worldticket AS Page 17 | 28
familyName=rdquoOLSENrdquo
rbd=rdquoYrdquogt
ltprice fareBasis=rdquoYECON07rdquo
currency=rdquoEURrdquo nett=rdquo50000rdquo
tax=rdquo50000rdquo fees=rdquo1000rdquo
total=rdquo101000rdquogt ltcoupongt
ltremovegt lt deltaPNRListgt
Response
ltdeltaPNRList status=rdquoHKrdquogt
Confidential - Worldticket AS Page 18 | 28
4 USE CASES
Following basis is defined for the following use cases
TS is master system amp W1 SMS is secondary system
W1 SMS is gateway to 1A
In 1A a TS operated segment is sold as W1 hosted airline so W1 airline is
validating and marketing carrier and partner airline is operating carrier
Use case 1 Create reservation in 1A
Use case 2 Cancel reservation in 1A
Use case 3 Rebook reservation in 1A
Use case 4 Send PNR update to Master System
41 CREATE RESERVATION IN 1A
USE CASE 1
USE CASE Name Create Reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 with
TSRES as master when 1A is selling TSRES segments
Confidential - Worldticket AS Page 19 | 28
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS
POST CONDISTIONS Authorization level in W1 is in synch with assigned
authorization in TSRES
TRIGGER When TA creates a reservation in 1A on a W1 hosted airline
segment
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 On request by 1A W1 will
create a reservation on a TS
segment
2 W1 sends sellSeat
message to TS to inform that
a number of seats is sold on
specific flight event and RBD
3 TSRES confirm that
message is received and
understood
4 W1 request availability
from TSRES by flight
designator and departure
date
5 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
6 W1 updates INV with new
availability information
7 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
3a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 20 | 28
minute
5a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 21 | 28
42 CANCEL RESERVATION IN 1A
USE CASE 2
USE CASE Name Cancel reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS Reservation is already created in W1 and the sale have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Seat is release in INV and authorization level in W1 is in
synch with assigned authorization in TSRES
TRIGGER When TA cancels a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request W1 via 1A to
cancel an already confirmed
segment
Confidential - Worldticket AS Page 22 | 28
2 W1 cancel segments and
confirms cancellation to 1A
3 W1 sends releaseSeat
message to TSRES to inform
that a number of seats is
canceled on specific flight
event and RBD
4 TSRES confirm that
message is received and
understood
5 W1 request availability
from TSRES by flight
designator and departure
date
6 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
7 W1 updates INV with new
availability information
8 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 23 | 28
43 REBOOK RESERVATION IN 1A
USE CASE 3
USE CASE Name Rebook reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 25 times
PRE CONDITIONS Reservation is already created in W1 and te sell have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Request segment is rebook to another flight date or class
Availability in W1 is in synch with assigned authorization in
TSRES
TRIGGER When TA rebook a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request via 1A W1 to
rebook a specified segment
to another flight or class
Confidential - Worldticket AS Page 24 | 28
2 W1 reserve new segment
cancel old and confirms
action to 1A
3 W1 inform TSRES about
new sold segment by sending
sellSeat message
4TSRES confirm that
message is received and
understood
5 W1 informs TSRES that old
segment have been canceled
by sending releaseSeat
message
6 TSRES confirm that
message is received and
understood
7 W1 request availability
from TSRES by flight
designator and departure
date
8 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
9 W1 updates INV with new
availability information
10 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 25 | 28
minute
8a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 26 | 28
44 SEND PNR UPDATE TO TSRES
USE CASE 4
USE CASE Name Send PNR update to TSRES
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TSRES
PURPOSE To update TSRES with the daily sale in W1
LEVEL Primary
FREQUENCY Once every night
PRE CONDITIONS
POST CONDISTIONS
TRIGGER Scheduled job in W1
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 Base on schedule job W1
will generate 2 lists addition
and deletion list of all
changes since last time
TSRES were updated
2 W1 sends deltaPNRList
message to TSRES
3 TSRES confirm that
message is received and
understood
4 W1 saves timestamp for
Confidential - Worldticket AS Page 27 | 28
sending delta list
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
2a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 28 | 28
5 SMS Inventory Synchronization Overview Features
Monitoring of host transactions is logged in the ldquoSMS Host Transaction Overviewrdquo
In the same user interface are able to define filters to retrieve sent and received
transactions In the ldquoSMS Host Transaction Overview ldquo user interface you are able
to
Confidential - Worldticket AS Page 10 | 28
24 getAvailability
This message is used for synchronizing availability
Based on the received information SMS will calculate availability as
availability = capacity + MAX(booked actual_booked)
REQUEST
authorizationCode
flight
flight
no Flight number
date Departure date from origin
RESPONSE
flight
flight
no Flight number
date Departure date from origin
segment
Segment
origin IATA 3 letter station code
destination IATA 3 letter station code
class
class
rbd Reservation Booking Designator
One letter code for booking class
capacity Number of seats authorized by TSRES in the class on the
given segment
sold Number of seats sold in the class on the given segment
according to TSRES
EXAMPLE
Request
ltgetAvailability
authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt ltflightno=rdquoW21111rdquo
date=rdquo2008-12-15 1600rdquogt
Confidential - Worldticket AS Page 11 | 28
ltgetAvailabilitygt
Response
ltgetAvailabilitygt ltflight
no=rdquoW21111rdquo date=rdquo2008-12-15 1600rdquogt
ltsegment origin=rdquoCPHrdquo
destination=rdquoLHRrdquogt ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltclass rbd=rdquoYrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt
ltsegmentgt ltsegment
origin=rdquoLHRrdquo destination=rdquoNYCrdquogt
ltclass rbd=rdquoCrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltclass rbd=rdquoYrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltsegmentgt ltsegment
origin=rdquoCPHrdquo destination=rdquoNYCrdquogt
ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltclass rbd=rdquoYrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltsegmentgt
ltflightgt ltgetAvailabilitygt
25 pushAvailability
This message is used for synchronizing availability Based on the received
information W1 will calculate availability as
Confidential - Worldticket AS Page 12 | 28
availability = capacity + MAX(booked actual_booked)
RESPONSE
authorizationCode
flight List of flights
flight
no Flight number
date Departure date from origin
segment List of segments
Segment
origin IATA 3 letter station code
destination IATA 3 letter station code
class
class
rbd Reservation Booking Designator
One letter code for booking class
capacity Number of seats authorized by TSRES in the class on the
given segment
sold Number of seats sold in the class on the given segment
according to TSRES
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
AIRIMP status codes like HK UC
errorCode Predefined codes
ErrorMessage Free text
Confidential - Worldticket AS Page 13 | 28
EXAMPLE
Request
ltpushAvailability authorizationCode=43543534sdfsdfds234234gt
ltflight date=2012-03-29 0840 no=W2901gt ltsegment destination=CPH origin=CDGgt
ltclass capacity=4 rbd=L sold=2gt ltsegmentgt
ltflightgt ltpushAvailabilitygt
or
ltpushAvailabilitygt
ltflight no=rdquoW21111rdquo
date=rdquo2008-12-15 1600rdquogt
ltsegment origin=rdquoCPHrdquo
destination=rdquoLHRrdquogt ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltclass rbd=rdquoYrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltsegmentgt
ltsegment origin=rdquoLHRrdquo
destination=rdquoNYCrdquogt ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo
sold=rdquo7rdquogt ltclass rbd=rdquoYrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltsegmentgt ltsegment
origin=rdquoCPHrdquo destination=rdquoNYCrdquogt
ltclass rbd=rdquoCrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltclass rbd=rdquoYrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltsegmentgt
ltflightgt
Confidential - Worldticket AS Page 14 | 28
ltpushAvailabilitygt
Response
ltpushAvailability status=rdquoHKrdquogt
3 DeltaPNRList
This message is used for synchronizing passenger information The message includes
all segments sold and cancelled since last sending
REQUEST
authorizationCode
add
Remove
add
coupon List of coupons issued since last update
Remove
coupon List of coupons canceled since last update
Coupon
tkne Ticket number
recLoc W1 record locator for reservation to which the coupon
belongs
status Standard IET coupon status indicator We expect that the
following should be enough
O Open for use
R Refunded
E Exchanged
segment List of segments
passenger List of passengers
price Price for pnr
Not mandatory as price maybe unknown in case of tickets
havenrsquot been issued yet
segment
flight Flight designator
date Departure date from origin
origin IATA 3 letter station code
destination IATA 3 letter station code
rbd One letter code for booking class
Confidential - Worldticket AS Page 15 | 28
passenger
type Passenger type ADT CHD INT
title Passenger title
firstName Passenger first name
Any character in UTF-8
familyName Passenger family name
Any character in UTF-8
price
fareBasis Fare basis code
nett
tax Sum of all charged taxes
fee Sum of all charged fees
total The total price including taxes and fees
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
AIRIMP status codes like HK UC
errorCode Predefined codes
ErrorMessage Free text
EXAMPLE
Request
ltdeltaPNRList
authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt
ltaddgt ltcoupon
tkne=rdquo123456789012345rdquo recLoc=rdquoZH23T6rdquo
status=rdquoordquogt ltsegment
flight=rdquoW21111rdquo date=rdquo2008-12-15 1645rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt ltpassenger
type=rdquoADTrdquo title=rdquoMRrdquo
firstName=rdquoSoslashrenrdquo
familyName=rdquoEjsingrdquo rbd=rdquoCrdquogt
Confidential - Worldticket AS Page 16 | 28
ltprice
fareBasis=rdquoCFLEX03rdquo
currency=rdquoEURrdquo nett=rdquo100000rdquo
tax=rdquo50000rdquo fees=rdquo000rdquo
total=rdquo150000rdquogt ltcoupongt
ltaddgt ltremovegt
ltcoupon tkne=rdquo123456789012345rdquo
recLoc=rdquoZH23T6rdquo status=rdquorrdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1645rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt ltpassenger
type=rdquoADTrdquo title=rdquoMRrdquo
firstName=rdquoFRANKrdquo familyName=rdquoOLSENrdquo
rbd=rdquoYrdquogt ltprice
fareBasis=rdquoYECON07rdquo currency=rdquoEURrdquo
nett=rdquo50000rdquo tax=rdquo50000rdquo
fees=rdquo1000rdquo
total=rdquo101000rdquogt ltcoupongt
ltcoupon tkne=rdquo123456789012345rdquo
recLoc=rdquoZH23T6rdquo status=rdquoerdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1645rdquo origin=rdquoCPHrdquo
destination=rdquoLHRrdquo rbd=rdquoCrdquogt
ltpassenger type=rdquoADTrdquo
title=rdquoMRSrdquo
firstName=rdquoLONErdquo
Confidential - Worldticket AS Page 17 | 28
familyName=rdquoOLSENrdquo
rbd=rdquoYrdquogt
ltprice fareBasis=rdquoYECON07rdquo
currency=rdquoEURrdquo nett=rdquo50000rdquo
tax=rdquo50000rdquo fees=rdquo1000rdquo
total=rdquo101000rdquogt ltcoupongt
ltremovegt lt deltaPNRListgt
Response
ltdeltaPNRList status=rdquoHKrdquogt
Confidential - Worldticket AS Page 18 | 28
4 USE CASES
Following basis is defined for the following use cases
TS is master system amp W1 SMS is secondary system
W1 SMS is gateway to 1A
In 1A a TS operated segment is sold as W1 hosted airline so W1 airline is
validating and marketing carrier and partner airline is operating carrier
Use case 1 Create reservation in 1A
Use case 2 Cancel reservation in 1A
Use case 3 Rebook reservation in 1A
Use case 4 Send PNR update to Master System
41 CREATE RESERVATION IN 1A
USE CASE 1
USE CASE Name Create Reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 with
TSRES as master when 1A is selling TSRES segments
Confidential - Worldticket AS Page 19 | 28
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS
POST CONDISTIONS Authorization level in W1 is in synch with assigned
authorization in TSRES
TRIGGER When TA creates a reservation in 1A on a W1 hosted airline
segment
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 On request by 1A W1 will
create a reservation on a TS
segment
2 W1 sends sellSeat
message to TS to inform that
a number of seats is sold on
specific flight event and RBD
3 TSRES confirm that
message is received and
understood
4 W1 request availability
from TSRES by flight
designator and departure
date
5 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
6 W1 updates INV with new
availability information
7 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
3a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 20 | 28
minute
5a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 21 | 28
42 CANCEL RESERVATION IN 1A
USE CASE 2
USE CASE Name Cancel reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS Reservation is already created in W1 and the sale have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Seat is release in INV and authorization level in W1 is in
synch with assigned authorization in TSRES
TRIGGER When TA cancels a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request W1 via 1A to
cancel an already confirmed
segment
Confidential - Worldticket AS Page 22 | 28
2 W1 cancel segments and
confirms cancellation to 1A
3 W1 sends releaseSeat
message to TSRES to inform
that a number of seats is
canceled on specific flight
event and RBD
4 TSRES confirm that
message is received and
understood
5 W1 request availability
from TSRES by flight
designator and departure
date
6 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
7 W1 updates INV with new
availability information
8 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 23 | 28
43 REBOOK RESERVATION IN 1A
USE CASE 3
USE CASE Name Rebook reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 25 times
PRE CONDITIONS Reservation is already created in W1 and te sell have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Request segment is rebook to another flight date or class
Availability in W1 is in synch with assigned authorization in
TSRES
TRIGGER When TA rebook a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request via 1A W1 to
rebook a specified segment
to another flight or class
Confidential - Worldticket AS Page 24 | 28
2 W1 reserve new segment
cancel old and confirms
action to 1A
3 W1 inform TSRES about
new sold segment by sending
sellSeat message
4TSRES confirm that
message is received and
understood
5 W1 informs TSRES that old
segment have been canceled
by sending releaseSeat
message
6 TSRES confirm that
message is received and
understood
7 W1 request availability
from TSRES by flight
designator and departure
date
8 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
9 W1 updates INV with new
availability information
10 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 25 | 28
minute
8a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 26 | 28
44 SEND PNR UPDATE TO TSRES
USE CASE 4
USE CASE Name Send PNR update to TSRES
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TSRES
PURPOSE To update TSRES with the daily sale in W1
LEVEL Primary
FREQUENCY Once every night
PRE CONDITIONS
POST CONDISTIONS
TRIGGER Scheduled job in W1
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 Base on schedule job W1
will generate 2 lists addition
and deletion list of all
changes since last time
TSRES were updated
2 W1 sends deltaPNRList
message to TSRES
3 TSRES confirm that
message is received and
understood
4 W1 saves timestamp for
Confidential - Worldticket AS Page 27 | 28
sending delta list
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
2a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 28 | 28
5 SMS Inventory Synchronization Overview Features
Monitoring of host transactions is logged in the ldquoSMS Host Transaction Overviewrdquo
In the same user interface are able to define filters to retrieve sent and received
transactions In the ldquoSMS Host Transaction Overview ldquo user interface you are able
to
Confidential - Worldticket AS Page 11 | 28
ltgetAvailabilitygt
Response
ltgetAvailabilitygt ltflight
no=rdquoW21111rdquo date=rdquo2008-12-15 1600rdquogt
ltsegment origin=rdquoCPHrdquo
destination=rdquoLHRrdquogt ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltclass rbd=rdquoYrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt
ltsegmentgt ltsegment
origin=rdquoLHRrdquo destination=rdquoNYCrdquogt
ltclass rbd=rdquoCrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltclass rbd=rdquoYrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltsegmentgt ltsegment
origin=rdquoCPHrdquo destination=rdquoNYCrdquogt
ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltclass rbd=rdquoYrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltsegmentgt
ltflightgt ltgetAvailabilitygt
25 pushAvailability
This message is used for synchronizing availability Based on the received
information W1 will calculate availability as
Confidential - Worldticket AS Page 12 | 28
availability = capacity + MAX(booked actual_booked)
RESPONSE
authorizationCode
flight List of flights
flight
no Flight number
date Departure date from origin
segment List of segments
Segment
origin IATA 3 letter station code
destination IATA 3 letter station code
class
class
rbd Reservation Booking Designator
One letter code for booking class
capacity Number of seats authorized by TSRES in the class on the
given segment
sold Number of seats sold in the class on the given segment
according to TSRES
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
AIRIMP status codes like HK UC
errorCode Predefined codes
ErrorMessage Free text
Confidential - Worldticket AS Page 13 | 28
EXAMPLE
Request
ltpushAvailability authorizationCode=43543534sdfsdfds234234gt
ltflight date=2012-03-29 0840 no=W2901gt ltsegment destination=CPH origin=CDGgt
ltclass capacity=4 rbd=L sold=2gt ltsegmentgt
ltflightgt ltpushAvailabilitygt
or
ltpushAvailabilitygt
ltflight no=rdquoW21111rdquo
date=rdquo2008-12-15 1600rdquogt
ltsegment origin=rdquoCPHrdquo
destination=rdquoLHRrdquogt ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltclass rbd=rdquoYrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltsegmentgt
ltsegment origin=rdquoLHRrdquo
destination=rdquoNYCrdquogt ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo
sold=rdquo7rdquogt ltclass rbd=rdquoYrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltsegmentgt ltsegment
origin=rdquoCPHrdquo destination=rdquoNYCrdquogt
ltclass rbd=rdquoCrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltclass rbd=rdquoYrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltsegmentgt
ltflightgt
Confidential - Worldticket AS Page 14 | 28
ltpushAvailabilitygt
Response
ltpushAvailability status=rdquoHKrdquogt
3 DeltaPNRList
This message is used for synchronizing passenger information The message includes
all segments sold and cancelled since last sending
REQUEST
authorizationCode
add
Remove
add
coupon List of coupons issued since last update
Remove
coupon List of coupons canceled since last update
Coupon
tkne Ticket number
recLoc W1 record locator for reservation to which the coupon
belongs
status Standard IET coupon status indicator We expect that the
following should be enough
O Open for use
R Refunded
E Exchanged
segment List of segments
passenger List of passengers
price Price for pnr
Not mandatory as price maybe unknown in case of tickets
havenrsquot been issued yet
segment
flight Flight designator
date Departure date from origin
origin IATA 3 letter station code
destination IATA 3 letter station code
rbd One letter code for booking class
Confidential - Worldticket AS Page 15 | 28
passenger
type Passenger type ADT CHD INT
title Passenger title
firstName Passenger first name
Any character in UTF-8
familyName Passenger family name
Any character in UTF-8
price
fareBasis Fare basis code
nett
tax Sum of all charged taxes
fee Sum of all charged fees
total The total price including taxes and fees
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
AIRIMP status codes like HK UC
errorCode Predefined codes
ErrorMessage Free text
EXAMPLE
Request
ltdeltaPNRList
authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt
ltaddgt ltcoupon
tkne=rdquo123456789012345rdquo recLoc=rdquoZH23T6rdquo
status=rdquoordquogt ltsegment
flight=rdquoW21111rdquo date=rdquo2008-12-15 1645rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt ltpassenger
type=rdquoADTrdquo title=rdquoMRrdquo
firstName=rdquoSoslashrenrdquo
familyName=rdquoEjsingrdquo rbd=rdquoCrdquogt
Confidential - Worldticket AS Page 16 | 28
ltprice
fareBasis=rdquoCFLEX03rdquo
currency=rdquoEURrdquo nett=rdquo100000rdquo
tax=rdquo50000rdquo fees=rdquo000rdquo
total=rdquo150000rdquogt ltcoupongt
ltaddgt ltremovegt
ltcoupon tkne=rdquo123456789012345rdquo
recLoc=rdquoZH23T6rdquo status=rdquorrdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1645rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt ltpassenger
type=rdquoADTrdquo title=rdquoMRrdquo
firstName=rdquoFRANKrdquo familyName=rdquoOLSENrdquo
rbd=rdquoYrdquogt ltprice
fareBasis=rdquoYECON07rdquo currency=rdquoEURrdquo
nett=rdquo50000rdquo tax=rdquo50000rdquo
fees=rdquo1000rdquo
total=rdquo101000rdquogt ltcoupongt
ltcoupon tkne=rdquo123456789012345rdquo
recLoc=rdquoZH23T6rdquo status=rdquoerdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1645rdquo origin=rdquoCPHrdquo
destination=rdquoLHRrdquo rbd=rdquoCrdquogt
ltpassenger type=rdquoADTrdquo
title=rdquoMRSrdquo
firstName=rdquoLONErdquo
Confidential - Worldticket AS Page 17 | 28
familyName=rdquoOLSENrdquo
rbd=rdquoYrdquogt
ltprice fareBasis=rdquoYECON07rdquo
currency=rdquoEURrdquo nett=rdquo50000rdquo
tax=rdquo50000rdquo fees=rdquo1000rdquo
total=rdquo101000rdquogt ltcoupongt
ltremovegt lt deltaPNRListgt
Response
ltdeltaPNRList status=rdquoHKrdquogt
Confidential - Worldticket AS Page 18 | 28
4 USE CASES
Following basis is defined for the following use cases
TS is master system amp W1 SMS is secondary system
W1 SMS is gateway to 1A
In 1A a TS operated segment is sold as W1 hosted airline so W1 airline is
validating and marketing carrier and partner airline is operating carrier
Use case 1 Create reservation in 1A
Use case 2 Cancel reservation in 1A
Use case 3 Rebook reservation in 1A
Use case 4 Send PNR update to Master System
41 CREATE RESERVATION IN 1A
USE CASE 1
USE CASE Name Create Reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 with
TSRES as master when 1A is selling TSRES segments
Confidential - Worldticket AS Page 19 | 28
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS
POST CONDISTIONS Authorization level in W1 is in synch with assigned
authorization in TSRES
TRIGGER When TA creates a reservation in 1A on a W1 hosted airline
segment
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 On request by 1A W1 will
create a reservation on a TS
segment
2 W1 sends sellSeat
message to TS to inform that
a number of seats is sold on
specific flight event and RBD
3 TSRES confirm that
message is received and
understood
4 W1 request availability
from TSRES by flight
designator and departure
date
5 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
6 W1 updates INV with new
availability information
7 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
3a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 20 | 28
minute
5a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 21 | 28
42 CANCEL RESERVATION IN 1A
USE CASE 2
USE CASE Name Cancel reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS Reservation is already created in W1 and the sale have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Seat is release in INV and authorization level in W1 is in
synch with assigned authorization in TSRES
TRIGGER When TA cancels a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request W1 via 1A to
cancel an already confirmed
segment
Confidential - Worldticket AS Page 22 | 28
2 W1 cancel segments and
confirms cancellation to 1A
3 W1 sends releaseSeat
message to TSRES to inform
that a number of seats is
canceled on specific flight
event and RBD
4 TSRES confirm that
message is received and
understood
5 W1 request availability
from TSRES by flight
designator and departure
date
6 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
7 W1 updates INV with new
availability information
8 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 23 | 28
43 REBOOK RESERVATION IN 1A
USE CASE 3
USE CASE Name Rebook reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 25 times
PRE CONDITIONS Reservation is already created in W1 and te sell have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Request segment is rebook to another flight date or class
Availability in W1 is in synch with assigned authorization in
TSRES
TRIGGER When TA rebook a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request via 1A W1 to
rebook a specified segment
to another flight or class
Confidential - Worldticket AS Page 24 | 28
2 W1 reserve new segment
cancel old and confirms
action to 1A
3 W1 inform TSRES about
new sold segment by sending
sellSeat message
4TSRES confirm that
message is received and
understood
5 W1 informs TSRES that old
segment have been canceled
by sending releaseSeat
message
6 TSRES confirm that
message is received and
understood
7 W1 request availability
from TSRES by flight
designator and departure
date
8 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
9 W1 updates INV with new
availability information
10 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 25 | 28
minute
8a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 26 | 28
44 SEND PNR UPDATE TO TSRES
USE CASE 4
USE CASE Name Send PNR update to TSRES
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TSRES
PURPOSE To update TSRES with the daily sale in W1
LEVEL Primary
FREQUENCY Once every night
PRE CONDITIONS
POST CONDISTIONS
TRIGGER Scheduled job in W1
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 Base on schedule job W1
will generate 2 lists addition
and deletion list of all
changes since last time
TSRES were updated
2 W1 sends deltaPNRList
message to TSRES
3 TSRES confirm that
message is received and
understood
4 W1 saves timestamp for
Confidential - Worldticket AS Page 27 | 28
sending delta list
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
2a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 28 | 28
5 SMS Inventory Synchronization Overview Features
Monitoring of host transactions is logged in the ldquoSMS Host Transaction Overviewrdquo
In the same user interface are able to define filters to retrieve sent and received
transactions In the ldquoSMS Host Transaction Overview ldquo user interface you are able
to
Confidential - Worldticket AS Page 12 | 28
availability = capacity + MAX(booked actual_booked)
RESPONSE
authorizationCode
flight List of flights
flight
no Flight number
date Departure date from origin
segment List of segments
Segment
origin IATA 3 letter station code
destination IATA 3 letter station code
class
class
rbd Reservation Booking Designator
One letter code for booking class
capacity Number of seats authorized by TSRES in the class on the
given segment
sold Number of seats sold in the class on the given segment
according to TSRES
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
AIRIMP status codes like HK UC
errorCode Predefined codes
ErrorMessage Free text
Confidential - Worldticket AS Page 13 | 28
EXAMPLE
Request
ltpushAvailability authorizationCode=43543534sdfsdfds234234gt
ltflight date=2012-03-29 0840 no=W2901gt ltsegment destination=CPH origin=CDGgt
ltclass capacity=4 rbd=L sold=2gt ltsegmentgt
ltflightgt ltpushAvailabilitygt
or
ltpushAvailabilitygt
ltflight no=rdquoW21111rdquo
date=rdquo2008-12-15 1600rdquogt
ltsegment origin=rdquoCPHrdquo
destination=rdquoLHRrdquogt ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltclass rbd=rdquoYrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltsegmentgt
ltsegment origin=rdquoLHRrdquo
destination=rdquoNYCrdquogt ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo
sold=rdquo7rdquogt ltclass rbd=rdquoYrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltsegmentgt ltsegment
origin=rdquoCPHrdquo destination=rdquoNYCrdquogt
ltclass rbd=rdquoCrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltclass rbd=rdquoYrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltsegmentgt
ltflightgt
Confidential - Worldticket AS Page 14 | 28
ltpushAvailabilitygt
Response
ltpushAvailability status=rdquoHKrdquogt
3 DeltaPNRList
This message is used for synchronizing passenger information The message includes
all segments sold and cancelled since last sending
REQUEST
authorizationCode
add
Remove
add
coupon List of coupons issued since last update
Remove
coupon List of coupons canceled since last update
Coupon
tkne Ticket number
recLoc W1 record locator for reservation to which the coupon
belongs
status Standard IET coupon status indicator We expect that the
following should be enough
O Open for use
R Refunded
E Exchanged
segment List of segments
passenger List of passengers
price Price for pnr
Not mandatory as price maybe unknown in case of tickets
havenrsquot been issued yet
segment
flight Flight designator
date Departure date from origin
origin IATA 3 letter station code
destination IATA 3 letter station code
rbd One letter code for booking class
Confidential - Worldticket AS Page 15 | 28
passenger
type Passenger type ADT CHD INT
title Passenger title
firstName Passenger first name
Any character in UTF-8
familyName Passenger family name
Any character in UTF-8
price
fareBasis Fare basis code
nett
tax Sum of all charged taxes
fee Sum of all charged fees
total The total price including taxes and fees
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
AIRIMP status codes like HK UC
errorCode Predefined codes
ErrorMessage Free text
EXAMPLE
Request
ltdeltaPNRList
authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt
ltaddgt ltcoupon
tkne=rdquo123456789012345rdquo recLoc=rdquoZH23T6rdquo
status=rdquoordquogt ltsegment
flight=rdquoW21111rdquo date=rdquo2008-12-15 1645rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt ltpassenger
type=rdquoADTrdquo title=rdquoMRrdquo
firstName=rdquoSoslashrenrdquo
familyName=rdquoEjsingrdquo rbd=rdquoCrdquogt
Confidential - Worldticket AS Page 16 | 28
ltprice
fareBasis=rdquoCFLEX03rdquo
currency=rdquoEURrdquo nett=rdquo100000rdquo
tax=rdquo50000rdquo fees=rdquo000rdquo
total=rdquo150000rdquogt ltcoupongt
ltaddgt ltremovegt
ltcoupon tkne=rdquo123456789012345rdquo
recLoc=rdquoZH23T6rdquo status=rdquorrdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1645rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt ltpassenger
type=rdquoADTrdquo title=rdquoMRrdquo
firstName=rdquoFRANKrdquo familyName=rdquoOLSENrdquo
rbd=rdquoYrdquogt ltprice
fareBasis=rdquoYECON07rdquo currency=rdquoEURrdquo
nett=rdquo50000rdquo tax=rdquo50000rdquo
fees=rdquo1000rdquo
total=rdquo101000rdquogt ltcoupongt
ltcoupon tkne=rdquo123456789012345rdquo
recLoc=rdquoZH23T6rdquo status=rdquoerdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1645rdquo origin=rdquoCPHrdquo
destination=rdquoLHRrdquo rbd=rdquoCrdquogt
ltpassenger type=rdquoADTrdquo
title=rdquoMRSrdquo
firstName=rdquoLONErdquo
Confidential - Worldticket AS Page 17 | 28
familyName=rdquoOLSENrdquo
rbd=rdquoYrdquogt
ltprice fareBasis=rdquoYECON07rdquo
currency=rdquoEURrdquo nett=rdquo50000rdquo
tax=rdquo50000rdquo fees=rdquo1000rdquo
total=rdquo101000rdquogt ltcoupongt
ltremovegt lt deltaPNRListgt
Response
ltdeltaPNRList status=rdquoHKrdquogt
Confidential - Worldticket AS Page 18 | 28
4 USE CASES
Following basis is defined for the following use cases
TS is master system amp W1 SMS is secondary system
W1 SMS is gateway to 1A
In 1A a TS operated segment is sold as W1 hosted airline so W1 airline is
validating and marketing carrier and partner airline is operating carrier
Use case 1 Create reservation in 1A
Use case 2 Cancel reservation in 1A
Use case 3 Rebook reservation in 1A
Use case 4 Send PNR update to Master System
41 CREATE RESERVATION IN 1A
USE CASE 1
USE CASE Name Create Reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 with
TSRES as master when 1A is selling TSRES segments
Confidential - Worldticket AS Page 19 | 28
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS
POST CONDISTIONS Authorization level in W1 is in synch with assigned
authorization in TSRES
TRIGGER When TA creates a reservation in 1A on a W1 hosted airline
segment
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 On request by 1A W1 will
create a reservation on a TS
segment
2 W1 sends sellSeat
message to TS to inform that
a number of seats is sold on
specific flight event and RBD
3 TSRES confirm that
message is received and
understood
4 W1 request availability
from TSRES by flight
designator and departure
date
5 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
6 W1 updates INV with new
availability information
7 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
3a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 20 | 28
minute
5a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 21 | 28
42 CANCEL RESERVATION IN 1A
USE CASE 2
USE CASE Name Cancel reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS Reservation is already created in W1 and the sale have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Seat is release in INV and authorization level in W1 is in
synch with assigned authorization in TSRES
TRIGGER When TA cancels a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request W1 via 1A to
cancel an already confirmed
segment
Confidential - Worldticket AS Page 22 | 28
2 W1 cancel segments and
confirms cancellation to 1A
3 W1 sends releaseSeat
message to TSRES to inform
that a number of seats is
canceled on specific flight
event and RBD
4 TSRES confirm that
message is received and
understood
5 W1 request availability
from TSRES by flight
designator and departure
date
6 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
7 W1 updates INV with new
availability information
8 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 23 | 28
43 REBOOK RESERVATION IN 1A
USE CASE 3
USE CASE Name Rebook reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 25 times
PRE CONDITIONS Reservation is already created in W1 and te sell have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Request segment is rebook to another flight date or class
Availability in W1 is in synch with assigned authorization in
TSRES
TRIGGER When TA rebook a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request via 1A W1 to
rebook a specified segment
to another flight or class
Confidential - Worldticket AS Page 24 | 28
2 W1 reserve new segment
cancel old and confirms
action to 1A
3 W1 inform TSRES about
new sold segment by sending
sellSeat message
4TSRES confirm that
message is received and
understood
5 W1 informs TSRES that old
segment have been canceled
by sending releaseSeat
message
6 TSRES confirm that
message is received and
understood
7 W1 request availability
from TSRES by flight
designator and departure
date
8 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
9 W1 updates INV with new
availability information
10 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 25 | 28
minute
8a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 26 | 28
44 SEND PNR UPDATE TO TSRES
USE CASE 4
USE CASE Name Send PNR update to TSRES
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TSRES
PURPOSE To update TSRES with the daily sale in W1
LEVEL Primary
FREQUENCY Once every night
PRE CONDITIONS
POST CONDISTIONS
TRIGGER Scheduled job in W1
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 Base on schedule job W1
will generate 2 lists addition
and deletion list of all
changes since last time
TSRES were updated
2 W1 sends deltaPNRList
message to TSRES
3 TSRES confirm that
message is received and
understood
4 W1 saves timestamp for
Confidential - Worldticket AS Page 27 | 28
sending delta list
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
2a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 28 | 28
5 SMS Inventory Synchronization Overview Features
Monitoring of host transactions is logged in the ldquoSMS Host Transaction Overviewrdquo
In the same user interface are able to define filters to retrieve sent and received
transactions In the ldquoSMS Host Transaction Overview ldquo user interface you are able
to
Confidential - Worldticket AS Page 13 | 28
EXAMPLE
Request
ltpushAvailability authorizationCode=43543534sdfsdfds234234gt
ltflight date=2012-03-29 0840 no=W2901gt ltsegment destination=CPH origin=CDGgt
ltclass capacity=4 rbd=L sold=2gt ltsegmentgt
ltflightgt ltpushAvailabilitygt
or
ltpushAvailabilitygt
ltflight no=rdquoW21111rdquo
date=rdquo2008-12-15 1600rdquogt
ltsegment origin=rdquoCPHrdquo
destination=rdquoLHRrdquogt ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltclass rbd=rdquoYrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltsegmentgt
ltsegment origin=rdquoLHRrdquo
destination=rdquoNYCrdquogt ltclass rbd=rdquoCrdquo
capacity=rdquo20rdquo
sold=rdquo7rdquogt ltclass rbd=rdquoYrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltsegmentgt ltsegment
origin=rdquoCPHrdquo destination=rdquoNYCrdquogt
ltclass rbd=rdquoCrdquo capacity=rdquo20rdquo
sold=rdquo7rdquogt ltclass rbd=rdquoYrdquo
capacity=rdquo20rdquo sold=rdquo7rdquogt
ltsegmentgt
ltflightgt
Confidential - Worldticket AS Page 14 | 28
ltpushAvailabilitygt
Response
ltpushAvailability status=rdquoHKrdquogt
3 DeltaPNRList
This message is used for synchronizing passenger information The message includes
all segments sold and cancelled since last sending
REQUEST
authorizationCode
add
Remove
add
coupon List of coupons issued since last update
Remove
coupon List of coupons canceled since last update
Coupon
tkne Ticket number
recLoc W1 record locator for reservation to which the coupon
belongs
status Standard IET coupon status indicator We expect that the
following should be enough
O Open for use
R Refunded
E Exchanged
segment List of segments
passenger List of passengers
price Price for pnr
Not mandatory as price maybe unknown in case of tickets
havenrsquot been issued yet
segment
flight Flight designator
date Departure date from origin
origin IATA 3 letter station code
destination IATA 3 letter station code
rbd One letter code for booking class
Confidential - Worldticket AS Page 15 | 28
passenger
type Passenger type ADT CHD INT
title Passenger title
firstName Passenger first name
Any character in UTF-8
familyName Passenger family name
Any character in UTF-8
price
fareBasis Fare basis code
nett
tax Sum of all charged taxes
fee Sum of all charged fees
total The total price including taxes and fees
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
AIRIMP status codes like HK UC
errorCode Predefined codes
ErrorMessage Free text
EXAMPLE
Request
ltdeltaPNRList
authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt
ltaddgt ltcoupon
tkne=rdquo123456789012345rdquo recLoc=rdquoZH23T6rdquo
status=rdquoordquogt ltsegment
flight=rdquoW21111rdquo date=rdquo2008-12-15 1645rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt ltpassenger
type=rdquoADTrdquo title=rdquoMRrdquo
firstName=rdquoSoslashrenrdquo
familyName=rdquoEjsingrdquo rbd=rdquoCrdquogt
Confidential - Worldticket AS Page 16 | 28
ltprice
fareBasis=rdquoCFLEX03rdquo
currency=rdquoEURrdquo nett=rdquo100000rdquo
tax=rdquo50000rdquo fees=rdquo000rdquo
total=rdquo150000rdquogt ltcoupongt
ltaddgt ltremovegt
ltcoupon tkne=rdquo123456789012345rdquo
recLoc=rdquoZH23T6rdquo status=rdquorrdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1645rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt ltpassenger
type=rdquoADTrdquo title=rdquoMRrdquo
firstName=rdquoFRANKrdquo familyName=rdquoOLSENrdquo
rbd=rdquoYrdquogt ltprice
fareBasis=rdquoYECON07rdquo currency=rdquoEURrdquo
nett=rdquo50000rdquo tax=rdquo50000rdquo
fees=rdquo1000rdquo
total=rdquo101000rdquogt ltcoupongt
ltcoupon tkne=rdquo123456789012345rdquo
recLoc=rdquoZH23T6rdquo status=rdquoerdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1645rdquo origin=rdquoCPHrdquo
destination=rdquoLHRrdquo rbd=rdquoCrdquogt
ltpassenger type=rdquoADTrdquo
title=rdquoMRSrdquo
firstName=rdquoLONErdquo
Confidential - Worldticket AS Page 17 | 28
familyName=rdquoOLSENrdquo
rbd=rdquoYrdquogt
ltprice fareBasis=rdquoYECON07rdquo
currency=rdquoEURrdquo nett=rdquo50000rdquo
tax=rdquo50000rdquo fees=rdquo1000rdquo
total=rdquo101000rdquogt ltcoupongt
ltremovegt lt deltaPNRListgt
Response
ltdeltaPNRList status=rdquoHKrdquogt
Confidential - Worldticket AS Page 18 | 28
4 USE CASES
Following basis is defined for the following use cases
TS is master system amp W1 SMS is secondary system
W1 SMS is gateway to 1A
In 1A a TS operated segment is sold as W1 hosted airline so W1 airline is
validating and marketing carrier and partner airline is operating carrier
Use case 1 Create reservation in 1A
Use case 2 Cancel reservation in 1A
Use case 3 Rebook reservation in 1A
Use case 4 Send PNR update to Master System
41 CREATE RESERVATION IN 1A
USE CASE 1
USE CASE Name Create Reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 with
TSRES as master when 1A is selling TSRES segments
Confidential - Worldticket AS Page 19 | 28
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS
POST CONDISTIONS Authorization level in W1 is in synch with assigned
authorization in TSRES
TRIGGER When TA creates a reservation in 1A on a W1 hosted airline
segment
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 On request by 1A W1 will
create a reservation on a TS
segment
2 W1 sends sellSeat
message to TS to inform that
a number of seats is sold on
specific flight event and RBD
3 TSRES confirm that
message is received and
understood
4 W1 request availability
from TSRES by flight
designator and departure
date
5 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
6 W1 updates INV with new
availability information
7 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
3a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 20 | 28
minute
5a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 21 | 28
42 CANCEL RESERVATION IN 1A
USE CASE 2
USE CASE Name Cancel reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS Reservation is already created in W1 and the sale have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Seat is release in INV and authorization level in W1 is in
synch with assigned authorization in TSRES
TRIGGER When TA cancels a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request W1 via 1A to
cancel an already confirmed
segment
Confidential - Worldticket AS Page 22 | 28
2 W1 cancel segments and
confirms cancellation to 1A
3 W1 sends releaseSeat
message to TSRES to inform
that a number of seats is
canceled on specific flight
event and RBD
4 TSRES confirm that
message is received and
understood
5 W1 request availability
from TSRES by flight
designator and departure
date
6 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
7 W1 updates INV with new
availability information
8 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 23 | 28
43 REBOOK RESERVATION IN 1A
USE CASE 3
USE CASE Name Rebook reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 25 times
PRE CONDITIONS Reservation is already created in W1 and te sell have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Request segment is rebook to another flight date or class
Availability in W1 is in synch with assigned authorization in
TSRES
TRIGGER When TA rebook a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request via 1A W1 to
rebook a specified segment
to another flight or class
Confidential - Worldticket AS Page 24 | 28
2 W1 reserve new segment
cancel old and confirms
action to 1A
3 W1 inform TSRES about
new sold segment by sending
sellSeat message
4TSRES confirm that
message is received and
understood
5 W1 informs TSRES that old
segment have been canceled
by sending releaseSeat
message
6 TSRES confirm that
message is received and
understood
7 W1 request availability
from TSRES by flight
designator and departure
date
8 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
9 W1 updates INV with new
availability information
10 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 25 | 28
minute
8a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 26 | 28
44 SEND PNR UPDATE TO TSRES
USE CASE 4
USE CASE Name Send PNR update to TSRES
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TSRES
PURPOSE To update TSRES with the daily sale in W1
LEVEL Primary
FREQUENCY Once every night
PRE CONDITIONS
POST CONDISTIONS
TRIGGER Scheduled job in W1
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 Base on schedule job W1
will generate 2 lists addition
and deletion list of all
changes since last time
TSRES were updated
2 W1 sends deltaPNRList
message to TSRES
3 TSRES confirm that
message is received and
understood
4 W1 saves timestamp for
Confidential - Worldticket AS Page 27 | 28
sending delta list
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
2a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 28 | 28
5 SMS Inventory Synchronization Overview Features
Monitoring of host transactions is logged in the ldquoSMS Host Transaction Overviewrdquo
In the same user interface are able to define filters to retrieve sent and received
transactions In the ldquoSMS Host Transaction Overview ldquo user interface you are able
to
Confidential - Worldticket AS Page 14 | 28
ltpushAvailabilitygt
Response
ltpushAvailability status=rdquoHKrdquogt
3 DeltaPNRList
This message is used for synchronizing passenger information The message includes
all segments sold and cancelled since last sending
REQUEST
authorizationCode
add
Remove
add
coupon List of coupons issued since last update
Remove
coupon List of coupons canceled since last update
Coupon
tkne Ticket number
recLoc W1 record locator for reservation to which the coupon
belongs
status Standard IET coupon status indicator We expect that the
following should be enough
O Open for use
R Refunded
E Exchanged
segment List of segments
passenger List of passengers
price Price for pnr
Not mandatory as price maybe unknown in case of tickets
havenrsquot been issued yet
segment
flight Flight designator
date Departure date from origin
origin IATA 3 letter station code
destination IATA 3 letter station code
rbd One letter code for booking class
Confidential - Worldticket AS Page 15 | 28
passenger
type Passenger type ADT CHD INT
title Passenger title
firstName Passenger first name
Any character in UTF-8
familyName Passenger family name
Any character in UTF-8
price
fareBasis Fare basis code
nett
tax Sum of all charged taxes
fee Sum of all charged fees
total The total price including taxes and fees
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
AIRIMP status codes like HK UC
errorCode Predefined codes
ErrorMessage Free text
EXAMPLE
Request
ltdeltaPNRList
authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt
ltaddgt ltcoupon
tkne=rdquo123456789012345rdquo recLoc=rdquoZH23T6rdquo
status=rdquoordquogt ltsegment
flight=rdquoW21111rdquo date=rdquo2008-12-15 1645rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt ltpassenger
type=rdquoADTrdquo title=rdquoMRrdquo
firstName=rdquoSoslashrenrdquo
familyName=rdquoEjsingrdquo rbd=rdquoCrdquogt
Confidential - Worldticket AS Page 16 | 28
ltprice
fareBasis=rdquoCFLEX03rdquo
currency=rdquoEURrdquo nett=rdquo100000rdquo
tax=rdquo50000rdquo fees=rdquo000rdquo
total=rdquo150000rdquogt ltcoupongt
ltaddgt ltremovegt
ltcoupon tkne=rdquo123456789012345rdquo
recLoc=rdquoZH23T6rdquo status=rdquorrdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1645rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt ltpassenger
type=rdquoADTrdquo title=rdquoMRrdquo
firstName=rdquoFRANKrdquo familyName=rdquoOLSENrdquo
rbd=rdquoYrdquogt ltprice
fareBasis=rdquoYECON07rdquo currency=rdquoEURrdquo
nett=rdquo50000rdquo tax=rdquo50000rdquo
fees=rdquo1000rdquo
total=rdquo101000rdquogt ltcoupongt
ltcoupon tkne=rdquo123456789012345rdquo
recLoc=rdquoZH23T6rdquo status=rdquoerdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1645rdquo origin=rdquoCPHrdquo
destination=rdquoLHRrdquo rbd=rdquoCrdquogt
ltpassenger type=rdquoADTrdquo
title=rdquoMRSrdquo
firstName=rdquoLONErdquo
Confidential - Worldticket AS Page 17 | 28
familyName=rdquoOLSENrdquo
rbd=rdquoYrdquogt
ltprice fareBasis=rdquoYECON07rdquo
currency=rdquoEURrdquo nett=rdquo50000rdquo
tax=rdquo50000rdquo fees=rdquo1000rdquo
total=rdquo101000rdquogt ltcoupongt
ltremovegt lt deltaPNRListgt
Response
ltdeltaPNRList status=rdquoHKrdquogt
Confidential - Worldticket AS Page 18 | 28
4 USE CASES
Following basis is defined for the following use cases
TS is master system amp W1 SMS is secondary system
W1 SMS is gateway to 1A
In 1A a TS operated segment is sold as W1 hosted airline so W1 airline is
validating and marketing carrier and partner airline is operating carrier
Use case 1 Create reservation in 1A
Use case 2 Cancel reservation in 1A
Use case 3 Rebook reservation in 1A
Use case 4 Send PNR update to Master System
41 CREATE RESERVATION IN 1A
USE CASE 1
USE CASE Name Create Reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 with
TSRES as master when 1A is selling TSRES segments
Confidential - Worldticket AS Page 19 | 28
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS
POST CONDISTIONS Authorization level in W1 is in synch with assigned
authorization in TSRES
TRIGGER When TA creates a reservation in 1A on a W1 hosted airline
segment
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 On request by 1A W1 will
create a reservation on a TS
segment
2 W1 sends sellSeat
message to TS to inform that
a number of seats is sold on
specific flight event and RBD
3 TSRES confirm that
message is received and
understood
4 W1 request availability
from TSRES by flight
designator and departure
date
5 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
6 W1 updates INV with new
availability information
7 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
3a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 20 | 28
minute
5a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 21 | 28
42 CANCEL RESERVATION IN 1A
USE CASE 2
USE CASE Name Cancel reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS Reservation is already created in W1 and the sale have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Seat is release in INV and authorization level in W1 is in
synch with assigned authorization in TSRES
TRIGGER When TA cancels a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request W1 via 1A to
cancel an already confirmed
segment
Confidential - Worldticket AS Page 22 | 28
2 W1 cancel segments and
confirms cancellation to 1A
3 W1 sends releaseSeat
message to TSRES to inform
that a number of seats is
canceled on specific flight
event and RBD
4 TSRES confirm that
message is received and
understood
5 W1 request availability
from TSRES by flight
designator and departure
date
6 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
7 W1 updates INV with new
availability information
8 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 23 | 28
43 REBOOK RESERVATION IN 1A
USE CASE 3
USE CASE Name Rebook reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 25 times
PRE CONDITIONS Reservation is already created in W1 and te sell have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Request segment is rebook to another flight date or class
Availability in W1 is in synch with assigned authorization in
TSRES
TRIGGER When TA rebook a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request via 1A W1 to
rebook a specified segment
to another flight or class
Confidential - Worldticket AS Page 24 | 28
2 W1 reserve new segment
cancel old and confirms
action to 1A
3 W1 inform TSRES about
new sold segment by sending
sellSeat message
4TSRES confirm that
message is received and
understood
5 W1 informs TSRES that old
segment have been canceled
by sending releaseSeat
message
6 TSRES confirm that
message is received and
understood
7 W1 request availability
from TSRES by flight
designator and departure
date
8 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
9 W1 updates INV with new
availability information
10 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 25 | 28
minute
8a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 26 | 28
44 SEND PNR UPDATE TO TSRES
USE CASE 4
USE CASE Name Send PNR update to TSRES
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TSRES
PURPOSE To update TSRES with the daily sale in W1
LEVEL Primary
FREQUENCY Once every night
PRE CONDITIONS
POST CONDISTIONS
TRIGGER Scheduled job in W1
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 Base on schedule job W1
will generate 2 lists addition
and deletion list of all
changes since last time
TSRES were updated
2 W1 sends deltaPNRList
message to TSRES
3 TSRES confirm that
message is received and
understood
4 W1 saves timestamp for
Confidential - Worldticket AS Page 27 | 28
sending delta list
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
2a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 28 | 28
5 SMS Inventory Synchronization Overview Features
Monitoring of host transactions is logged in the ldquoSMS Host Transaction Overviewrdquo
In the same user interface are able to define filters to retrieve sent and received
transactions In the ldquoSMS Host Transaction Overview ldquo user interface you are able
to
Confidential - Worldticket AS Page 15 | 28
passenger
type Passenger type ADT CHD INT
title Passenger title
firstName Passenger first name
Any character in UTF-8
familyName Passenger family name
Any character in UTF-8
price
fareBasis Fare basis code
nett
tax Sum of all charged taxes
fee Sum of all charged fees
total The total price including taxes and fees
RESPONSE
status Some kind of acknowledgement that the message is
received and understood
AIRIMP status codes like HK UC
errorCode Predefined codes
ErrorMessage Free text
EXAMPLE
Request
ltdeltaPNRList
authorizationCode=rdquo1234567890ABCDEFGHIJKLMNrdquogt
ltaddgt ltcoupon
tkne=rdquo123456789012345rdquo recLoc=rdquoZH23T6rdquo
status=rdquoordquogt ltsegment
flight=rdquoW21111rdquo date=rdquo2008-12-15 1645rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt ltpassenger
type=rdquoADTrdquo title=rdquoMRrdquo
firstName=rdquoSoslashrenrdquo
familyName=rdquoEjsingrdquo rbd=rdquoCrdquogt
Confidential - Worldticket AS Page 16 | 28
ltprice
fareBasis=rdquoCFLEX03rdquo
currency=rdquoEURrdquo nett=rdquo100000rdquo
tax=rdquo50000rdquo fees=rdquo000rdquo
total=rdquo150000rdquogt ltcoupongt
ltaddgt ltremovegt
ltcoupon tkne=rdquo123456789012345rdquo
recLoc=rdquoZH23T6rdquo status=rdquorrdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1645rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt ltpassenger
type=rdquoADTrdquo title=rdquoMRrdquo
firstName=rdquoFRANKrdquo familyName=rdquoOLSENrdquo
rbd=rdquoYrdquogt ltprice
fareBasis=rdquoYECON07rdquo currency=rdquoEURrdquo
nett=rdquo50000rdquo tax=rdquo50000rdquo
fees=rdquo1000rdquo
total=rdquo101000rdquogt ltcoupongt
ltcoupon tkne=rdquo123456789012345rdquo
recLoc=rdquoZH23T6rdquo status=rdquoerdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1645rdquo origin=rdquoCPHrdquo
destination=rdquoLHRrdquo rbd=rdquoCrdquogt
ltpassenger type=rdquoADTrdquo
title=rdquoMRSrdquo
firstName=rdquoLONErdquo
Confidential - Worldticket AS Page 17 | 28
familyName=rdquoOLSENrdquo
rbd=rdquoYrdquogt
ltprice fareBasis=rdquoYECON07rdquo
currency=rdquoEURrdquo nett=rdquo50000rdquo
tax=rdquo50000rdquo fees=rdquo1000rdquo
total=rdquo101000rdquogt ltcoupongt
ltremovegt lt deltaPNRListgt
Response
ltdeltaPNRList status=rdquoHKrdquogt
Confidential - Worldticket AS Page 18 | 28
4 USE CASES
Following basis is defined for the following use cases
TS is master system amp W1 SMS is secondary system
W1 SMS is gateway to 1A
In 1A a TS operated segment is sold as W1 hosted airline so W1 airline is
validating and marketing carrier and partner airline is operating carrier
Use case 1 Create reservation in 1A
Use case 2 Cancel reservation in 1A
Use case 3 Rebook reservation in 1A
Use case 4 Send PNR update to Master System
41 CREATE RESERVATION IN 1A
USE CASE 1
USE CASE Name Create Reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 with
TSRES as master when 1A is selling TSRES segments
Confidential - Worldticket AS Page 19 | 28
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS
POST CONDISTIONS Authorization level in W1 is in synch with assigned
authorization in TSRES
TRIGGER When TA creates a reservation in 1A on a W1 hosted airline
segment
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 On request by 1A W1 will
create a reservation on a TS
segment
2 W1 sends sellSeat
message to TS to inform that
a number of seats is sold on
specific flight event and RBD
3 TSRES confirm that
message is received and
understood
4 W1 request availability
from TSRES by flight
designator and departure
date
5 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
6 W1 updates INV with new
availability information
7 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
3a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 20 | 28
minute
5a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 21 | 28
42 CANCEL RESERVATION IN 1A
USE CASE 2
USE CASE Name Cancel reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS Reservation is already created in W1 and the sale have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Seat is release in INV and authorization level in W1 is in
synch with assigned authorization in TSRES
TRIGGER When TA cancels a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request W1 via 1A to
cancel an already confirmed
segment
Confidential - Worldticket AS Page 22 | 28
2 W1 cancel segments and
confirms cancellation to 1A
3 W1 sends releaseSeat
message to TSRES to inform
that a number of seats is
canceled on specific flight
event and RBD
4 TSRES confirm that
message is received and
understood
5 W1 request availability
from TSRES by flight
designator and departure
date
6 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
7 W1 updates INV with new
availability information
8 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 23 | 28
43 REBOOK RESERVATION IN 1A
USE CASE 3
USE CASE Name Rebook reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 25 times
PRE CONDITIONS Reservation is already created in W1 and te sell have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Request segment is rebook to another flight date or class
Availability in W1 is in synch with assigned authorization in
TSRES
TRIGGER When TA rebook a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request via 1A W1 to
rebook a specified segment
to another flight or class
Confidential - Worldticket AS Page 24 | 28
2 W1 reserve new segment
cancel old and confirms
action to 1A
3 W1 inform TSRES about
new sold segment by sending
sellSeat message
4TSRES confirm that
message is received and
understood
5 W1 informs TSRES that old
segment have been canceled
by sending releaseSeat
message
6 TSRES confirm that
message is received and
understood
7 W1 request availability
from TSRES by flight
designator and departure
date
8 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
9 W1 updates INV with new
availability information
10 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 25 | 28
minute
8a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 26 | 28
44 SEND PNR UPDATE TO TSRES
USE CASE 4
USE CASE Name Send PNR update to TSRES
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TSRES
PURPOSE To update TSRES with the daily sale in W1
LEVEL Primary
FREQUENCY Once every night
PRE CONDITIONS
POST CONDISTIONS
TRIGGER Scheduled job in W1
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 Base on schedule job W1
will generate 2 lists addition
and deletion list of all
changes since last time
TSRES were updated
2 W1 sends deltaPNRList
message to TSRES
3 TSRES confirm that
message is received and
understood
4 W1 saves timestamp for
Confidential - Worldticket AS Page 27 | 28
sending delta list
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
2a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 28 | 28
5 SMS Inventory Synchronization Overview Features
Monitoring of host transactions is logged in the ldquoSMS Host Transaction Overviewrdquo
In the same user interface are able to define filters to retrieve sent and received
transactions In the ldquoSMS Host Transaction Overview ldquo user interface you are able
to
Confidential - Worldticket AS Page 16 | 28
ltprice
fareBasis=rdquoCFLEX03rdquo
currency=rdquoEURrdquo nett=rdquo100000rdquo
tax=rdquo50000rdquo fees=rdquo000rdquo
total=rdquo150000rdquogt ltcoupongt
ltaddgt ltremovegt
ltcoupon tkne=rdquo123456789012345rdquo
recLoc=rdquoZH23T6rdquo status=rdquorrdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1645rdquo
origin=rdquoCPHrdquo destination=rdquoLHRrdquo
rbd=rdquoCrdquogt ltpassenger
type=rdquoADTrdquo title=rdquoMRrdquo
firstName=rdquoFRANKrdquo familyName=rdquoOLSENrdquo
rbd=rdquoYrdquogt ltprice
fareBasis=rdquoYECON07rdquo currency=rdquoEURrdquo
nett=rdquo50000rdquo tax=rdquo50000rdquo
fees=rdquo1000rdquo
total=rdquo101000rdquogt ltcoupongt
ltcoupon tkne=rdquo123456789012345rdquo
recLoc=rdquoZH23T6rdquo status=rdquoerdquogt
ltsegment flight=rdquoW21111rdquo
date=rdquo2008-12-15 1645rdquo origin=rdquoCPHrdquo
destination=rdquoLHRrdquo rbd=rdquoCrdquogt
ltpassenger type=rdquoADTrdquo
title=rdquoMRSrdquo
firstName=rdquoLONErdquo
Confidential - Worldticket AS Page 17 | 28
familyName=rdquoOLSENrdquo
rbd=rdquoYrdquogt
ltprice fareBasis=rdquoYECON07rdquo
currency=rdquoEURrdquo nett=rdquo50000rdquo
tax=rdquo50000rdquo fees=rdquo1000rdquo
total=rdquo101000rdquogt ltcoupongt
ltremovegt lt deltaPNRListgt
Response
ltdeltaPNRList status=rdquoHKrdquogt
Confidential - Worldticket AS Page 18 | 28
4 USE CASES
Following basis is defined for the following use cases
TS is master system amp W1 SMS is secondary system
W1 SMS is gateway to 1A
In 1A a TS operated segment is sold as W1 hosted airline so W1 airline is
validating and marketing carrier and partner airline is operating carrier
Use case 1 Create reservation in 1A
Use case 2 Cancel reservation in 1A
Use case 3 Rebook reservation in 1A
Use case 4 Send PNR update to Master System
41 CREATE RESERVATION IN 1A
USE CASE 1
USE CASE Name Create Reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 with
TSRES as master when 1A is selling TSRES segments
Confidential - Worldticket AS Page 19 | 28
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS
POST CONDISTIONS Authorization level in W1 is in synch with assigned
authorization in TSRES
TRIGGER When TA creates a reservation in 1A on a W1 hosted airline
segment
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 On request by 1A W1 will
create a reservation on a TS
segment
2 W1 sends sellSeat
message to TS to inform that
a number of seats is sold on
specific flight event and RBD
3 TSRES confirm that
message is received and
understood
4 W1 request availability
from TSRES by flight
designator and departure
date
5 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
6 W1 updates INV with new
availability information
7 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
3a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 20 | 28
minute
5a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 21 | 28
42 CANCEL RESERVATION IN 1A
USE CASE 2
USE CASE Name Cancel reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS Reservation is already created in W1 and the sale have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Seat is release in INV and authorization level in W1 is in
synch with assigned authorization in TSRES
TRIGGER When TA cancels a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request W1 via 1A to
cancel an already confirmed
segment
Confidential - Worldticket AS Page 22 | 28
2 W1 cancel segments and
confirms cancellation to 1A
3 W1 sends releaseSeat
message to TSRES to inform
that a number of seats is
canceled on specific flight
event and RBD
4 TSRES confirm that
message is received and
understood
5 W1 request availability
from TSRES by flight
designator and departure
date
6 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
7 W1 updates INV with new
availability information
8 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 23 | 28
43 REBOOK RESERVATION IN 1A
USE CASE 3
USE CASE Name Rebook reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 25 times
PRE CONDITIONS Reservation is already created in W1 and te sell have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Request segment is rebook to another flight date or class
Availability in W1 is in synch with assigned authorization in
TSRES
TRIGGER When TA rebook a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request via 1A W1 to
rebook a specified segment
to another flight or class
Confidential - Worldticket AS Page 24 | 28
2 W1 reserve new segment
cancel old and confirms
action to 1A
3 W1 inform TSRES about
new sold segment by sending
sellSeat message
4TSRES confirm that
message is received and
understood
5 W1 informs TSRES that old
segment have been canceled
by sending releaseSeat
message
6 TSRES confirm that
message is received and
understood
7 W1 request availability
from TSRES by flight
designator and departure
date
8 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
9 W1 updates INV with new
availability information
10 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 25 | 28
minute
8a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 26 | 28
44 SEND PNR UPDATE TO TSRES
USE CASE 4
USE CASE Name Send PNR update to TSRES
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TSRES
PURPOSE To update TSRES with the daily sale in W1
LEVEL Primary
FREQUENCY Once every night
PRE CONDITIONS
POST CONDISTIONS
TRIGGER Scheduled job in W1
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 Base on schedule job W1
will generate 2 lists addition
and deletion list of all
changes since last time
TSRES were updated
2 W1 sends deltaPNRList
message to TSRES
3 TSRES confirm that
message is received and
understood
4 W1 saves timestamp for
Confidential - Worldticket AS Page 27 | 28
sending delta list
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
2a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 28 | 28
5 SMS Inventory Synchronization Overview Features
Monitoring of host transactions is logged in the ldquoSMS Host Transaction Overviewrdquo
In the same user interface are able to define filters to retrieve sent and received
transactions In the ldquoSMS Host Transaction Overview ldquo user interface you are able
to
Confidential - Worldticket AS Page 17 | 28
familyName=rdquoOLSENrdquo
rbd=rdquoYrdquogt
ltprice fareBasis=rdquoYECON07rdquo
currency=rdquoEURrdquo nett=rdquo50000rdquo
tax=rdquo50000rdquo fees=rdquo1000rdquo
total=rdquo101000rdquogt ltcoupongt
ltremovegt lt deltaPNRListgt
Response
ltdeltaPNRList status=rdquoHKrdquogt
Confidential - Worldticket AS Page 18 | 28
4 USE CASES
Following basis is defined for the following use cases
TS is master system amp W1 SMS is secondary system
W1 SMS is gateway to 1A
In 1A a TS operated segment is sold as W1 hosted airline so W1 airline is
validating and marketing carrier and partner airline is operating carrier
Use case 1 Create reservation in 1A
Use case 2 Cancel reservation in 1A
Use case 3 Rebook reservation in 1A
Use case 4 Send PNR update to Master System
41 CREATE RESERVATION IN 1A
USE CASE 1
USE CASE Name Create Reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 with
TSRES as master when 1A is selling TSRES segments
Confidential - Worldticket AS Page 19 | 28
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS
POST CONDISTIONS Authorization level in W1 is in synch with assigned
authorization in TSRES
TRIGGER When TA creates a reservation in 1A on a W1 hosted airline
segment
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 On request by 1A W1 will
create a reservation on a TS
segment
2 W1 sends sellSeat
message to TS to inform that
a number of seats is sold on
specific flight event and RBD
3 TSRES confirm that
message is received and
understood
4 W1 request availability
from TSRES by flight
designator and departure
date
5 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
6 W1 updates INV with new
availability information
7 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
3a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 20 | 28
minute
5a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 21 | 28
42 CANCEL RESERVATION IN 1A
USE CASE 2
USE CASE Name Cancel reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS Reservation is already created in W1 and the sale have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Seat is release in INV and authorization level in W1 is in
synch with assigned authorization in TSRES
TRIGGER When TA cancels a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request W1 via 1A to
cancel an already confirmed
segment
Confidential - Worldticket AS Page 22 | 28
2 W1 cancel segments and
confirms cancellation to 1A
3 W1 sends releaseSeat
message to TSRES to inform
that a number of seats is
canceled on specific flight
event and RBD
4 TSRES confirm that
message is received and
understood
5 W1 request availability
from TSRES by flight
designator and departure
date
6 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
7 W1 updates INV with new
availability information
8 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 23 | 28
43 REBOOK RESERVATION IN 1A
USE CASE 3
USE CASE Name Rebook reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 25 times
PRE CONDITIONS Reservation is already created in W1 and te sell have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Request segment is rebook to another flight date or class
Availability in W1 is in synch with assigned authorization in
TSRES
TRIGGER When TA rebook a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request via 1A W1 to
rebook a specified segment
to another flight or class
Confidential - Worldticket AS Page 24 | 28
2 W1 reserve new segment
cancel old and confirms
action to 1A
3 W1 inform TSRES about
new sold segment by sending
sellSeat message
4TSRES confirm that
message is received and
understood
5 W1 informs TSRES that old
segment have been canceled
by sending releaseSeat
message
6 TSRES confirm that
message is received and
understood
7 W1 request availability
from TSRES by flight
designator and departure
date
8 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
9 W1 updates INV with new
availability information
10 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 25 | 28
minute
8a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 26 | 28
44 SEND PNR UPDATE TO TSRES
USE CASE 4
USE CASE Name Send PNR update to TSRES
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TSRES
PURPOSE To update TSRES with the daily sale in W1
LEVEL Primary
FREQUENCY Once every night
PRE CONDITIONS
POST CONDISTIONS
TRIGGER Scheduled job in W1
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 Base on schedule job W1
will generate 2 lists addition
and deletion list of all
changes since last time
TSRES were updated
2 W1 sends deltaPNRList
message to TSRES
3 TSRES confirm that
message is received and
understood
4 W1 saves timestamp for
Confidential - Worldticket AS Page 27 | 28
sending delta list
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
2a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 28 | 28
5 SMS Inventory Synchronization Overview Features
Monitoring of host transactions is logged in the ldquoSMS Host Transaction Overviewrdquo
In the same user interface are able to define filters to retrieve sent and received
transactions In the ldquoSMS Host Transaction Overview ldquo user interface you are able
to
Confidential - Worldticket AS Page 18 | 28
4 USE CASES
Following basis is defined for the following use cases
TS is master system amp W1 SMS is secondary system
W1 SMS is gateway to 1A
In 1A a TS operated segment is sold as W1 hosted airline so W1 airline is
validating and marketing carrier and partner airline is operating carrier
Use case 1 Create reservation in 1A
Use case 2 Cancel reservation in 1A
Use case 3 Rebook reservation in 1A
Use case 4 Send PNR update to Master System
41 CREATE RESERVATION IN 1A
USE CASE 1
USE CASE Name Create Reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 with
TSRES as master when 1A is selling TSRES segments
Confidential - Worldticket AS Page 19 | 28
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS
POST CONDISTIONS Authorization level in W1 is in synch with assigned
authorization in TSRES
TRIGGER When TA creates a reservation in 1A on a W1 hosted airline
segment
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 On request by 1A W1 will
create a reservation on a TS
segment
2 W1 sends sellSeat
message to TS to inform that
a number of seats is sold on
specific flight event and RBD
3 TSRES confirm that
message is received and
understood
4 W1 request availability
from TSRES by flight
designator and departure
date
5 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
6 W1 updates INV with new
availability information
7 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
3a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 20 | 28
minute
5a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 21 | 28
42 CANCEL RESERVATION IN 1A
USE CASE 2
USE CASE Name Cancel reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS Reservation is already created in W1 and the sale have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Seat is release in INV and authorization level in W1 is in
synch with assigned authorization in TSRES
TRIGGER When TA cancels a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request W1 via 1A to
cancel an already confirmed
segment
Confidential - Worldticket AS Page 22 | 28
2 W1 cancel segments and
confirms cancellation to 1A
3 W1 sends releaseSeat
message to TSRES to inform
that a number of seats is
canceled on specific flight
event and RBD
4 TSRES confirm that
message is received and
understood
5 W1 request availability
from TSRES by flight
designator and departure
date
6 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
7 W1 updates INV with new
availability information
8 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 23 | 28
43 REBOOK RESERVATION IN 1A
USE CASE 3
USE CASE Name Rebook reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 25 times
PRE CONDITIONS Reservation is already created in W1 and te sell have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Request segment is rebook to another flight date or class
Availability in W1 is in synch with assigned authorization in
TSRES
TRIGGER When TA rebook a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request via 1A W1 to
rebook a specified segment
to another flight or class
Confidential - Worldticket AS Page 24 | 28
2 W1 reserve new segment
cancel old and confirms
action to 1A
3 W1 inform TSRES about
new sold segment by sending
sellSeat message
4TSRES confirm that
message is received and
understood
5 W1 informs TSRES that old
segment have been canceled
by sending releaseSeat
message
6 TSRES confirm that
message is received and
understood
7 W1 request availability
from TSRES by flight
designator and departure
date
8 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
9 W1 updates INV with new
availability information
10 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 25 | 28
minute
8a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 26 | 28
44 SEND PNR UPDATE TO TSRES
USE CASE 4
USE CASE Name Send PNR update to TSRES
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TSRES
PURPOSE To update TSRES with the daily sale in W1
LEVEL Primary
FREQUENCY Once every night
PRE CONDITIONS
POST CONDISTIONS
TRIGGER Scheduled job in W1
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 Base on schedule job W1
will generate 2 lists addition
and deletion list of all
changes since last time
TSRES were updated
2 W1 sends deltaPNRList
message to TSRES
3 TSRES confirm that
message is received and
understood
4 W1 saves timestamp for
Confidential - Worldticket AS Page 27 | 28
sending delta list
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
2a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 28 | 28
5 SMS Inventory Synchronization Overview Features
Monitoring of host transactions is logged in the ldquoSMS Host Transaction Overviewrdquo
In the same user interface are able to define filters to retrieve sent and received
transactions In the ldquoSMS Host Transaction Overview ldquo user interface you are able
to
Confidential - Worldticket AS Page 19 | 28
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS
POST CONDISTIONS Authorization level in W1 is in synch with assigned
authorization in TSRES
TRIGGER When TA creates a reservation in 1A on a W1 hosted airline
segment
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 On request by 1A W1 will
create a reservation on a TS
segment
2 W1 sends sellSeat
message to TS to inform that
a number of seats is sold on
specific flight event and RBD
3 TSRES confirm that
message is received and
understood
4 W1 request availability
from TSRES by flight
designator and departure
date
5 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
6 W1 updates INV with new
availability information
7 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
3a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 20 | 28
minute
5a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 21 | 28
42 CANCEL RESERVATION IN 1A
USE CASE 2
USE CASE Name Cancel reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS Reservation is already created in W1 and the sale have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Seat is release in INV and authorization level in W1 is in
synch with assigned authorization in TSRES
TRIGGER When TA cancels a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request W1 via 1A to
cancel an already confirmed
segment
Confidential - Worldticket AS Page 22 | 28
2 W1 cancel segments and
confirms cancellation to 1A
3 W1 sends releaseSeat
message to TSRES to inform
that a number of seats is
canceled on specific flight
event and RBD
4 TSRES confirm that
message is received and
understood
5 W1 request availability
from TSRES by flight
designator and departure
date
6 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
7 W1 updates INV with new
availability information
8 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 23 | 28
43 REBOOK RESERVATION IN 1A
USE CASE 3
USE CASE Name Rebook reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 25 times
PRE CONDITIONS Reservation is already created in W1 and te sell have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Request segment is rebook to another flight date or class
Availability in W1 is in synch with assigned authorization in
TSRES
TRIGGER When TA rebook a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request via 1A W1 to
rebook a specified segment
to another flight or class
Confidential - Worldticket AS Page 24 | 28
2 W1 reserve new segment
cancel old and confirms
action to 1A
3 W1 inform TSRES about
new sold segment by sending
sellSeat message
4TSRES confirm that
message is received and
understood
5 W1 informs TSRES that old
segment have been canceled
by sending releaseSeat
message
6 TSRES confirm that
message is received and
understood
7 W1 request availability
from TSRES by flight
designator and departure
date
8 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
9 W1 updates INV with new
availability information
10 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 25 | 28
minute
8a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 26 | 28
44 SEND PNR UPDATE TO TSRES
USE CASE 4
USE CASE Name Send PNR update to TSRES
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TSRES
PURPOSE To update TSRES with the daily sale in W1
LEVEL Primary
FREQUENCY Once every night
PRE CONDITIONS
POST CONDISTIONS
TRIGGER Scheduled job in W1
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 Base on schedule job W1
will generate 2 lists addition
and deletion list of all
changes since last time
TSRES were updated
2 W1 sends deltaPNRList
message to TSRES
3 TSRES confirm that
message is received and
understood
4 W1 saves timestamp for
Confidential - Worldticket AS Page 27 | 28
sending delta list
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
2a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 28 | 28
5 SMS Inventory Synchronization Overview Features
Monitoring of host transactions is logged in the ldquoSMS Host Transaction Overviewrdquo
In the same user interface are able to define filters to retrieve sent and received
transactions In the ldquoSMS Host Transaction Overview ldquo user interface you are able
to
Confidential - Worldticket AS Page 20 | 28
minute
5a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 21 | 28
42 CANCEL RESERVATION IN 1A
USE CASE 2
USE CASE Name Cancel reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS Reservation is already created in W1 and the sale have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Seat is release in INV and authorization level in W1 is in
synch with assigned authorization in TSRES
TRIGGER When TA cancels a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request W1 via 1A to
cancel an already confirmed
segment
Confidential - Worldticket AS Page 22 | 28
2 W1 cancel segments and
confirms cancellation to 1A
3 W1 sends releaseSeat
message to TSRES to inform
that a number of seats is
canceled on specific flight
event and RBD
4 TSRES confirm that
message is received and
understood
5 W1 request availability
from TSRES by flight
designator and departure
date
6 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
7 W1 updates INV with new
availability information
8 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 23 | 28
43 REBOOK RESERVATION IN 1A
USE CASE 3
USE CASE Name Rebook reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 25 times
PRE CONDITIONS Reservation is already created in W1 and te sell have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Request segment is rebook to another flight date or class
Availability in W1 is in synch with assigned authorization in
TSRES
TRIGGER When TA rebook a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request via 1A W1 to
rebook a specified segment
to another flight or class
Confidential - Worldticket AS Page 24 | 28
2 W1 reserve new segment
cancel old and confirms
action to 1A
3 W1 inform TSRES about
new sold segment by sending
sellSeat message
4TSRES confirm that
message is received and
understood
5 W1 informs TSRES that old
segment have been canceled
by sending releaseSeat
message
6 TSRES confirm that
message is received and
understood
7 W1 request availability
from TSRES by flight
designator and departure
date
8 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
9 W1 updates INV with new
availability information
10 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 25 | 28
minute
8a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 26 | 28
44 SEND PNR UPDATE TO TSRES
USE CASE 4
USE CASE Name Send PNR update to TSRES
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TSRES
PURPOSE To update TSRES with the daily sale in W1
LEVEL Primary
FREQUENCY Once every night
PRE CONDITIONS
POST CONDISTIONS
TRIGGER Scheduled job in W1
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 Base on schedule job W1
will generate 2 lists addition
and deletion list of all
changes since last time
TSRES were updated
2 W1 sends deltaPNRList
message to TSRES
3 TSRES confirm that
message is received and
understood
4 W1 saves timestamp for
Confidential - Worldticket AS Page 27 | 28
sending delta list
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
2a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 28 | 28
5 SMS Inventory Synchronization Overview Features
Monitoring of host transactions is logged in the ldquoSMS Host Transaction Overviewrdquo
In the same user interface are able to define filters to retrieve sent and received
transactions In the ldquoSMS Host Transaction Overview ldquo user interface you are able
to
Confidential - Worldticket AS Page 21 | 28
42 CANCEL RESERVATION IN 1A
USE CASE 2
USE CASE Name Cancel reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 100 times
PRE CONDITIONS Reservation is already created in W1 and the sale have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Seat is release in INV and authorization level in W1 is in
synch with assigned authorization in TSRES
TRIGGER When TA cancels a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request W1 via 1A to
cancel an already confirmed
segment
Confidential - Worldticket AS Page 22 | 28
2 W1 cancel segments and
confirms cancellation to 1A
3 W1 sends releaseSeat
message to TSRES to inform
that a number of seats is
canceled on specific flight
event and RBD
4 TSRES confirm that
message is received and
understood
5 W1 request availability
from TSRES by flight
designator and departure
date
6 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
7 W1 updates INV with new
availability information
8 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 23 | 28
43 REBOOK RESERVATION IN 1A
USE CASE 3
USE CASE Name Rebook reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 25 times
PRE CONDITIONS Reservation is already created in W1 and te sell have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Request segment is rebook to another flight date or class
Availability in W1 is in synch with assigned authorization in
TSRES
TRIGGER When TA rebook a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request via 1A W1 to
rebook a specified segment
to another flight or class
Confidential - Worldticket AS Page 24 | 28
2 W1 reserve new segment
cancel old and confirms
action to 1A
3 W1 inform TSRES about
new sold segment by sending
sellSeat message
4TSRES confirm that
message is received and
understood
5 W1 informs TSRES that old
segment have been canceled
by sending releaseSeat
message
6 TSRES confirm that
message is received and
understood
7 W1 request availability
from TSRES by flight
designator and departure
date
8 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
9 W1 updates INV with new
availability information
10 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 25 | 28
minute
8a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 26 | 28
44 SEND PNR UPDATE TO TSRES
USE CASE 4
USE CASE Name Send PNR update to TSRES
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TSRES
PURPOSE To update TSRES with the daily sale in W1
LEVEL Primary
FREQUENCY Once every night
PRE CONDITIONS
POST CONDISTIONS
TRIGGER Scheduled job in W1
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 Base on schedule job W1
will generate 2 lists addition
and deletion list of all
changes since last time
TSRES were updated
2 W1 sends deltaPNRList
message to TSRES
3 TSRES confirm that
message is received and
understood
4 W1 saves timestamp for
Confidential - Worldticket AS Page 27 | 28
sending delta list
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
2a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 28 | 28
5 SMS Inventory Synchronization Overview Features
Monitoring of host transactions is logged in the ldquoSMS Host Transaction Overviewrdquo
In the same user interface are able to define filters to retrieve sent and received
transactions In the ldquoSMS Host Transaction Overview ldquo user interface you are able
to
Confidential - Worldticket AS Page 22 | 28
2 W1 cancel segments and
confirms cancellation to 1A
3 W1 sends releaseSeat
message to TSRES to inform
that a number of seats is
canceled on specific flight
event and RBD
4 TSRES confirm that
message is received and
understood
5 W1 request availability
from TSRES by flight
designator and departure
date
6 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
7 W1 updates INV with new
availability information
8 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 23 | 28
43 REBOOK RESERVATION IN 1A
USE CASE 3
USE CASE Name Rebook reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 25 times
PRE CONDITIONS Reservation is already created in W1 and te sell have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Request segment is rebook to another flight date or class
Availability in W1 is in synch with assigned authorization in
TSRES
TRIGGER When TA rebook a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request via 1A W1 to
rebook a specified segment
to another flight or class
Confidential - Worldticket AS Page 24 | 28
2 W1 reserve new segment
cancel old and confirms
action to 1A
3 W1 inform TSRES about
new sold segment by sending
sellSeat message
4TSRES confirm that
message is received and
understood
5 W1 informs TSRES that old
segment have been canceled
by sending releaseSeat
message
6 TSRES confirm that
message is received and
understood
7 W1 request availability
from TSRES by flight
designator and departure
date
8 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
9 W1 updates INV with new
availability information
10 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 25 | 28
minute
8a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 26 | 28
44 SEND PNR UPDATE TO TSRES
USE CASE 4
USE CASE Name Send PNR update to TSRES
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TSRES
PURPOSE To update TSRES with the daily sale in W1
LEVEL Primary
FREQUENCY Once every night
PRE CONDITIONS
POST CONDISTIONS
TRIGGER Scheduled job in W1
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 Base on schedule job W1
will generate 2 lists addition
and deletion list of all
changes since last time
TSRES were updated
2 W1 sends deltaPNRList
message to TSRES
3 TSRES confirm that
message is received and
understood
4 W1 saves timestamp for
Confidential - Worldticket AS Page 27 | 28
sending delta list
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
2a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 28 | 28
5 SMS Inventory Synchronization Overview Features
Monitoring of host transactions is logged in the ldquoSMS Host Transaction Overviewrdquo
In the same user interface are able to define filters to retrieve sent and received
transactions In the ldquoSMS Host Transaction Overview ldquo user interface you are able
to
Confidential - Worldticket AS Page 23 | 28
43 REBOOK RESERVATION IN 1A
USE CASE 3
USE CASE Name Rebook reservation in 1A
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TS
PURPOSE To synchronize availability between TSRES and W1 where
TSRES is the master
LEVEL Primary
FREQUENCY Daily 25 times
PRE CONDITIONS Reservation is already created in W1 and te sell have been
reported to TSRES
Successful completion of use case 1
POST CONDISTIONS Request segment is rebook to another flight date or class
Availability in W1 is in synch with assigned authorization in
TSRES
TRIGGER When TA rebook a reservation in 1A
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 TA request via 1A W1 to
rebook a specified segment
to another flight or class
Confidential - Worldticket AS Page 24 | 28
2 W1 reserve new segment
cancel old and confirms
action to 1A
3 W1 inform TSRES about
new sold segment by sending
sellSeat message
4TSRES confirm that
message is received and
understood
5 W1 informs TSRES that old
segment have been canceled
by sending releaseSeat
message
6 TSRES confirm that
message is received and
understood
7 W1 request availability
from TSRES by flight
designator and departure
date
8 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
9 W1 updates INV with new
availability information
10 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 25 | 28
minute
8a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 26 | 28
44 SEND PNR UPDATE TO TSRES
USE CASE 4
USE CASE Name Send PNR update to TSRES
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TSRES
PURPOSE To update TSRES with the daily sale in W1
LEVEL Primary
FREQUENCY Once every night
PRE CONDITIONS
POST CONDISTIONS
TRIGGER Scheduled job in W1
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 Base on schedule job W1
will generate 2 lists addition
and deletion list of all
changes since last time
TSRES were updated
2 W1 sends deltaPNRList
message to TSRES
3 TSRES confirm that
message is received and
understood
4 W1 saves timestamp for
Confidential - Worldticket AS Page 27 | 28
sending delta list
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
2a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 28 | 28
5 SMS Inventory Synchronization Overview Features
Monitoring of host transactions is logged in the ldquoSMS Host Transaction Overviewrdquo
In the same user interface are able to define filters to retrieve sent and received
transactions In the ldquoSMS Host Transaction Overview ldquo user interface you are able
to
Confidential - Worldticket AS Page 24 | 28
2 W1 reserve new segment
cancel old and confirms
action to 1A
3 W1 inform TSRES about
new sold segment by sending
sellSeat message
4TSRES confirm that
message is received and
understood
5 W1 informs TSRES that old
segment have been canceled
by sending releaseSeat
message
6 TSRES confirm that
message is received and
understood
7 W1 request availability
from TSRES by flight
designator and departure
date
8 TSRES respond with
availability for each RBD and
for each segment on
requested flight event
9 W1 updates INV with new
availability information
10 W1 sends AVS messages
to 1A
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
4a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
6a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
Confidential - Worldticket AS Page 25 | 28
minute
8a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 26 | 28
44 SEND PNR UPDATE TO TSRES
USE CASE 4
USE CASE Name Send PNR update to TSRES
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TSRES
PURPOSE To update TSRES with the daily sale in W1
LEVEL Primary
FREQUENCY Once every night
PRE CONDITIONS
POST CONDISTIONS
TRIGGER Scheduled job in W1
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 Base on schedule job W1
will generate 2 lists addition
and deletion list of all
changes since last time
TSRES were updated
2 W1 sends deltaPNRList
message to TSRES
3 TSRES confirm that
message is received and
understood
4 W1 saves timestamp for
Confidential - Worldticket AS Page 27 | 28
sending delta list
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
2a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 28 | 28
5 SMS Inventory Synchronization Overview Features
Monitoring of host transactions is logged in the ldquoSMS Host Transaction Overviewrdquo
In the same user interface are able to define filters to retrieve sent and received
transactions In the ldquoSMS Host Transaction Overview ldquo user interface you are able
to
Confidential - Worldticket AS Page 25 | 28
minute
8a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 26 | 28
44 SEND PNR UPDATE TO TSRES
USE CASE 4
USE CASE Name Send PNR update to TSRES
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TSRES
PURPOSE To update TSRES with the daily sale in W1
LEVEL Primary
FREQUENCY Once every night
PRE CONDITIONS
POST CONDISTIONS
TRIGGER Scheduled job in W1
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 Base on schedule job W1
will generate 2 lists addition
and deletion list of all
changes since last time
TSRES were updated
2 W1 sends deltaPNRList
message to TSRES
3 TSRES confirm that
message is received and
understood
4 W1 saves timestamp for
Confidential - Worldticket AS Page 27 | 28
sending delta list
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
2a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 28 | 28
5 SMS Inventory Synchronization Overview Features
Monitoring of host transactions is logged in the ldquoSMS Host Transaction Overviewrdquo
In the same user interface are able to define filters to retrieve sent and received
transactions In the ldquoSMS Host Transaction Overview ldquo user interface you are able
to
Confidential - Worldticket AS Page 26 | 28
44 SEND PNR UPDATE TO TSRES
USE CASE 4
USE CASE Name Send PNR update to TSRES
TIMESTAMP Created 18 NOV 2008 by Soslashren Ejsing
ACTOR W1 TSRES
PURPOSE To update TSRES with the daily sale in W1
LEVEL Primary
FREQUENCY Once every night
PRE CONDITIONS
POST CONDISTIONS
TRIGGER Scheduled job in W1
INCLUDES
EXTENDS
MAIN SUCCESSFUL
SCENARIO
W1 TS
1 Base on schedule job W1
will generate 2 lists addition
and deletion list of all
changes since last time
TSRES were updated
2 W1 sends deltaPNRList
message to TSRES
3 TSRES confirm that
message is received and
understood
4 W1 saves timestamp for
Confidential - Worldticket AS Page 27 | 28
sending delta list
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
2a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 28 | 28
5 SMS Inventory Synchronization Overview Features
Monitoring of host transactions is logged in the ldquoSMS Host Transaction Overviewrdquo
In the same user interface are able to define filters to retrieve sent and received
transactions In the ldquoSMS Host Transaction Overview ldquo user interface you are able
to
Confidential - Worldticket AS Page 27 | 28
sending delta list
OTHER SUCCESSFUL
SCENARIOS
Step Branching Action
2a TSRES does not respond
to message
W1 transaction is not
depending on response but
message will be resend up to
3 times with an interval of 1
minute
UNSUCCESSFUL
SCENARIOS
Conditions Actions
COMMENT
Confidential - Worldticket AS Page 28 | 28
5 SMS Inventory Synchronization Overview Features
Monitoring of host transactions is logged in the ldquoSMS Host Transaction Overviewrdquo
In the same user interface are able to define filters to retrieve sent and received
transactions In the ldquoSMS Host Transaction Overview ldquo user interface you are able
to
Confidential - Worldticket AS Page 28 | 28
5 SMS Inventory Synchronization Overview Features
Monitoring of host transactions is logged in the ldquoSMS Host Transaction Overviewrdquo
In the same user interface are able to define filters to retrieve sent and received
transactions In the ldquoSMS Host Transaction Overview ldquo user interface you are able
to