Microsoft Word Master master doc

7.3
 
Usability 
7.3.1
 
Distribution of the client application 
All of the designs provide a manual distribution mechanism, where the client must start 
to download the client application itself. 

---

7.4 Discussion: : Modifiability 
Page 85 of 93 
IMS, in addition, can also support a push-based distribution. This comes from the fact 
that the TMMS PR is notified when clients registers to IMS. Note that the iFC for the 
service must also be setup correctly for this to work. 
As described push-based distribution depends on that the TMMS PR is notified when 
clients register to the network. For the GPRS based service this information should be 
possible with support from a CAMEL application. Using the Presence and Availability 
Management (PAM) SCF of the OSA API and the Presence WS of the OSA Parlay X, 
respectively, it should also be possible to do this on those frameworks too. 
But it seems much easier to accomplish this feature on IMS since the service provider 
only need to add another part to the iFC of the client PUI's service profile. This 
compared to e.g. developing a CAMEL application. 
7.3.2
 
Which parameters are necessary for the client to communicate with 
the Proxy-Relay 
All of the designs has a similar parameter set. 
7.3.3
 
Address handling (GSM SMS vs. TMMS addresses) 
All of the service designs do address handling similar, SIP URIs are used to identify 
TMMS clients and TEL URIs are used to identify GSM SMS clients. 
Except for the IMS based service, the TMMS PR of the services must look after TEL 
URIs and relay them to GSM SMS clients itself. In IMS, with the IP-MESSAGE-GW 
node present, messages sent to GSM SMS clients will be routed to the recipients with no 
influence from the TMMS PR.