13:53 -

Wireless transaction Protocol (WTP)

Wireless transaction Protocol (WTP)
• WTP is on top of either WDP or, if security is required, WTLS.

• WTP has been designed to run on very thin clients, such as mobile phones.

Advantages of WTP:

• Improved reliability over datagram services

• Improved efficiency over connection-oriented services

• Support for transaction-oriented services such as web browsing.

13:53 -=

Three classes of WTP transaction service:

Class O provides unreliable message transfer without any result message.

Classes I provides reliable message transfer without any result message.

Class 2 provides reliable message transfer with one reliable result message.

WTP achieves reliability using:

Duplicate removal

Retransmission

Acknowledgements

Unique transaction identifiers.

No class requires any connection set-up or tear-down phase. This avoids unnecessary overhead on the communication link.
WTP allows for

• Asynchronous transactions

• Abort of tra nsactions

• Concatenation of messages

• Report success or fai lure of reliable messages.

The three service primitives offered by WTP are:

• TR-Invoke - to initiate a new transaction

• TR-Result - to send back the result of a previously initiated transaction

• TR-Abort - to abort an existing transaction.

Types of WTP PDU:

• Invoke POU - used to convey a request from an initiator to a responder

• ACK POU - used to acknowledge an Invoke or Result POU □

• Result POU - used to convey response of the server to the client

• Abort POU - used to abort a transaction

• Segmented invoke POU and segmented result POU - used for segmentation and reassembly

• Negative acknowledgment POU - used to indicate that some packets did not arrive
13:53 -

WTP Class O : Unreliable Message Transfer without result message

In this class the responder does not ACK & initiator does not perform any
retransmission.

The transaction is stateless and cannot be aborted.

ilillD ~
Requested with TR-lnvoke.req primitive. TR-SAP TR.SAP
TR-n1a1<•11q
Parameters are: (SA, SP, DA, DP, A, UD, C=O, H) (SA. SP DA. DP.A. !Al. C,0, H) ~ TR-ffl'l0ie Ind
- •. ~P~ (SA.SP, DA, OP A,UO.C-0. H')
SA - source address, DA - destination address

SP - source port, DP - destination port

A - acknowledgement nag, if the responder WTP should generate an ACK or ~ ~ ' '"' IWl'Nwl
QOH (t,J,ll
If a user acknowledgement is used.
H: HNI (IOOtl 1111)

UD - User data 13asic Transaction: WTP class 0

C - class type which is O for this class.

H - handle simple index to uniquely identify the transaction

13:53 -

• WTP Class 1 : Reliable Message Transfer

without result message
• Sender send a TR-lnvoke.req
m- - --~1
TR-SAP

(SA.SP.DA.DP.A.uo.c- 1. 111
~ --cnl
1~

I .'°' :
TR-SAP

m.-...,
(SA. SP, DA. DP ... uo, c.•. '2
• Parameters are: (SA, SP, DA, A, UD, C=l, I ,4 •

H)
f '
Basic Transaction, WTP class 1, no user 1cknowled1ement
• C is class type which is 1 for this class.
ind111tor r-.ponder
• Responder signals the incoming TR- TR-8.AP TR-SAP
Invoke.ind & ACK automatically
m.-...,
;.;_";;".;..,ciP...,uo.c-, '!~ ~.Pei,_ (SA,
• Sender on receipt of ACK will close the
connection.
• Responder maintains the connection for
sometime in case it receives the duplicate
TR-- c n l
~
,ol
~ - .
i-lH

f
---
SP, DA. DP. A. UO. Co I . Hl

~1_ _ _ _ __

TR-lnvoke.req indicating the loss of ACK. Basic. transaction, WTP class 1, w ith user
acknowled1ement
13:53 -

WTP Class 2 : Reliable Message Transfer with one result message

Reliable reqoost/respond transacllon.

Depending on user requirements, many different scenarios are possible for

Initiator/responder lnteracllon

WTP dass 2 transaction, No user Ack & No hold on:

I. Initiator requests the service using TR-lnvoke.req and the WTP entity sends
the Invoke POU to the responder.
TR--SP. DA.
(SA. OP. 'I, UO. c.>. '!_,
-
,....._ "Ill,
T A-sAP

TR-- Ind
~ (SA. SP:~ DP, A. UD. Cs2,

TR-~.,.q
HJ
TR-i.woi...a,f pl)) (Ul)", H I
2. Responder request with the TR-Invoke.Ind.
~~ ....-!-
3. The responder sent back the result POU to the Initiator using TRResult.req. TR-..und
IU0", 11
◄
4. The Initiator Indicate the suacessful transmission of the invoke message and TR--
the result with the two service primitives:

TR-lnvoke.cnf
"
TR-Resultlnd. ' y
Fig. Baile tran11ctlon or cla11 2 without-user acltnowlecle:ement
5. A user respond with TR-Resultres.

6. An acknowledgement POU is then generated which finally trigger5 the TR-

Result.01f primitive on the responder.
WTP class 2 transaction, user Ack:

1. The responder explicitly responds to the Invoke POU

IOlhGt or ,_,_
using the TRinvoke.res. TRSI\P TA·SI\P
TR-ltwokereq
(SA. SP, DA, OP, A. UO, C-2, H)
2. Then the initiator triggers the TR-Invoke.cnf via
7 !'!"<>Ire Pot, TR lrwok• Ind •
, • .._ (SA. SP, DA. OP, A. UO, C 2, HJ_
TR-tnvoktt,..
an Ack POU. TR-lfwol\emr (H1

-----------i~·
(H)

TR- - . . n d - -• ."" ~
TR-RNUltreq
(UO', H1
(UD' H) ,_...-

TR-Roault.-
(H) ___ J.., ~ Pot, TR-RMUh cnf

·1 . . , . (H") ----

'
Basic transcatlon, WTP class2, with user Ack
13:53 ~.,.

WTP class 2 transaction, hold on & no user Ack:

• If the calculation of the result takes some time,

the responder can put the initiator

on "hold on" to prevent a retransmission. :.._~;,,..tiP.

TR-lnvol<acnf
(H)
A UO. C 2.
""""'°'
i '" " •
TR SAP

Po
• U
,__

,-p,.p(ll)
• -
i
TR-SAP

TR Invoke.ind
(SA. SP DA, DP, A. UO, c-2, H')

TR - . t t mq
- ►

◄ _. (UD' H )
TR-- i n d ~ - pO\.l ◄
...
(Uo- ,n .....
TR--..it.r.o
(H)

l
.•"""' . ..,~I
Po(J TR-RetulLcnl

' '
WTP cla ss 2 t r11ns11ctlon w ith " hold o n", no use r A ck