Microsoft Word Master master doc

7.3.4
 
Client registration 
GPRS and OSA API has the same registration procedure, and it is the most complex 
procedure. First the client must send a SIP REGISTER request to the TMMS PR to 
register its contact information. Next the client must subscribe to the newmessage-alert 
event. 
In IMS only the last step, event subscription, is necessary from the TMMS Service's point 
of view. 
Similar to the IMS design, in the Parlay X WS design the client only subscribes to 
notifications about new messages. 
7.3.5
 
Client unregistration 
All the unregistration procedures are similar to the registration procedures. 
7.4
 
Modifiability 
7.4.1
 
Add more servers to achieve better scalability 
All of the designs use DNS to access the TMMS PR, which means they can all achieve 
better scalability through normal DNS based network load balancing techniques. 
The IMS design, which use IMS' HSS node as user- and message store benefits from the 
scalability 3GPP has designed for this node. 

---

7.5 Discussion: : Interoperability 
Page 86 of 93 
7.4.2
 
Extend the service to support new media types 
All of the service designs use MIME types to describe the media types used. This makes 
the media type transparent to the TMMS PR. Only the streaming media server and the 
client application must be upgraded to support new media types. 
7.4.3
 
Restrict the media types supported by the service 
In all the service designs the TMMS PR may filter the media type of a message based on 
the Content-Type header. Additionally a content negotiation scheme, like the HTTP 
Accept header, can be added.