Microsoft Word Master master doc

Con
fi
den
ti
ality 
On top of OSA API security, TMMS PR WS ensures confidentiality by either 
using a Virtual Private Network (VPN) which gets administrated independent of 
the Web Service implementation, or to use HTTP over TLS0

---

6.3 TMMS Service based on OSA Parlay X Web Services: : Evaluation 
Page 82 of 93 
6.3.2
 
Usability 
Table 6-2: Evaluation of Usability quality attribute for TMMS Service based on OSA Parlay X Web 
Services 
6.3.3
 
Modifiability 
Table 6-3: Evaluation of Modifiability quality attribute for TMMS Service based on OSA Parlay X 
Web Services 
U1: Distribution of the client application 
Client must retrieve the client application manually. 
U2: Which parameters are necessary for the client to communicate with the 
Proxy-Relay
Client need to know what SOAP binding the TMMS PR WS supports, address to 
web service. 
U3: Address handling (GSM SMS vs. TMMS addresses)
 Term
in
al
 In
tegr
at
io
n 
SIP URIs are used to address TMMS Clientsclients, and TEL URIs are used to 
address GSM SMS clients. 
U4: Client registration 
TMMS PR WS performs a SIP registration on behalf of the client. 
U5: Client un-registration
Re
gis
tr
at
io
n 
The TMMS PR WS performs a un-registration on behalf of the client.
M1: Add more servers to achieve better scalability
Scalability 
Since the TMMS PR is addressed through DNS is it possible to use normal DNS 
based network load balancing techniques to add more servers. 
M2: Extend the service to support new media types 
The service uses MIME types to describe the media types of the message body. 
Only the client application must be upgraded to present new media types to the 
user. 
M3: Restrict the media types supported by the service 
The TMMS PR may filter the media types in a message, based on the Content-
Type, to restrict which media types are allowed to be sent between the clients. 
M4: Support new Carrier Access Network (CAN) 
Yes. 
M5: Port the service to a different framework