Microsoft Word Master master doc

7.6
 
Reliability 
7.6.1
 
Proxy-Relay routes messages at most once 
The service designs based on the GPRS, IMS and OSA API frameworks all use SIP as 
the protocol between sender and TMMS PR. SIP uses a CSeq header field to identify and 
order SIP transactions. 
SOAP, which is the transport protocol used by the OSA Parlay X Web Service 
framework, defines no reliability. By adding support for WS-Reliability at both the 
TMMS Client and TMMS PR WS the service can guarantee that messages are routed at 
most once. 
7.6.2
 
Service stores messages until it has been delivered 
None of the services deletes the message until it has been received by the client. 
However messages which the recipient does not accept to be charged for are deleted 
immediately after the recipient has refused to be charged for it. 
7.7
 
Billability 
7.7.1
 
Service provider must get information about chargeable operations 
All of our service designs depends on a charging controller where the TMMS PR sends 
charging information to for chargeable operations.
7.7.2
 
Message charged at most once 
The charging information in all the frameworks includes an identifier for the CDR, 
which is used to check for duplicates. 
7.7.3
 
Sender may demand that the recipient is charged for the message 
Only the IMS and the OSA Parlay X Web Services frameworks have support for this, but 
support is explicitly added in the rest of the service designs. 
7.7.4
 
Sender can not deceive receiver to pay for any messages 
None of the frameworks provides any means for this, so all of our service designs 
explicitly ask the recipient before charging it. 

---

8.1 Conclusion: : GPRS as a framework for creating end-to-end mobile services 
Page 88 of 93 
8
Conclusion 
From the discussion we can see that many of the evaluation criteria are fulfilled equally 
by all the service designs. In this chapter we will make conclusions based on our 
discussion above and our experiences with designing the services.