Microsoft Word Master master doc

Chan
ge
 S
ervice 
Difficult because of the IMS framework. 

---

4.3 TMMS Service based on IMS: : Evaluation 
Page 63 of 93 
4.3.4
 
Interoperability 
Table 4-4: Evaluation of Interoperability quality attribute for TMMS Service based on IMS 
4.3.5
 
Reliability 
Table 4-5: Evaluation of Reliability quality attribute for TMMS Service based on IMS 
4.3.6
 
Billability 
Table 4-6: Evaluation of Billability quality attribute for TMMS Service based on IMS 
I1: Send and receive messages with GSM SMS clients
 
If A TMMS message contains media types that a GSM SMS client doesn’t 
support, an ENUM translation needs to be performed.The TMMS gets routed 
based on the translation result. A TMMS message which only contains plain text 
isn't converted since the GSM SMS client supports text. 
R1: Proxy-Relay routes messages at most once
IMS supports forking so messages can be routed to more then one destination. 
R2: Service stores messages until it has been delivered
 
(The message store does not confirm if the HTTP response with the message is 
received by the client). When user has retrieved message, the service deletes 
message from message store. 
B1: Service provider must get information about chargeable operations
IMS specific. The TMMS PR sends charging information to the CDF in offline 
charging and OCS in online charging.. CDF and OCS handle charging on behalf 
of the service provider. 
B2: Message charged at most once
IMS specific. The IMS network elements mark the ACR/CCR messages with a T-
flag if duplicate messages are to be sent. A check is done based on Session-ID 
and CC-Request number AVP pairs.