Microsoft Word Master master doc

4.2.5.5
 
S05: Streaming Retrieval of MM 
Instead of using HTTP to download the MM from the TMMS Message Store, the client 
can instead request that it is streamed to it. This scenario is shown in Figure 4-13. The 
number in brackets, e.g. [1], indicates which SIP dialog the request or response is part of. 
Figure 4-13: Streaming media retrieval of MM 

---

4.2 TMMS Service based on IMS: : Design 
Page 58 of 93 
The client sends a INVITE message to the TMMS Message Store with a SDP message in 
the body. This SDP contains information such as which message is to be streamed and 
which codecs should be used for the session. This is marked as dialog #1 in the figure, 
and is routed by the S-CSCF to the TMMS Message Store. 
Next the TMMS Message Store pulls the message from the HSS. Then, in dialog #2, the 
TMMS Message Store sends an INVITE request to the MRFC with the SDP included. 
Then the MRFC and the TMMS Client will negotiate which codecs to use for the 
streaming session before they reserve resources for it. 
After the resources have been reserved the TMMS Message Store sends an ACK request 
to the MRFC, in dialog #3. This starts the streaming session. The messages exchanged 
during the streaming session are not included here. 
When the client is finished it sends a BYE request, which is dialog #4. In dialog #5 the 
TMMS Message Store sends a BYE request to the MRFC, so it can release the resources 
reserved earlier. 
At this point the TMMS Message Store may delete the MM, since the client has viewed it. 
4.2.5.6
 
S06: TMMS Client Unregistration 
The TMMS Client unregisters from the service by unsubscribing from the newmessage-
alert event. This is done by sending the same SUBSCRIBE request as in S01: TMMS 
Client Registration, with the Expires header set to 0.