Microsoft Word Master master doc

Figure 6-6: Send MM 
6.2.5.3
 
S03: New message notification 
When the TMMS PR WS gets a 
newmessage-alert
on behalf of the client it uses the client's 
MessageNotification
interface to notify about the new message alert. The message URI 
received in the NOTIFY request is used as the 
MessageReference
. Only deferred retrieval of 
messages is supported. 
See 3.2.5.3 for a description of the steps 1, 1.1 and 1.3 of the sequence. 

---

6.2 TMMS Service based on OSA Parlay X Web Services: : Design 
Page 78 of 93 
Figure 6-7: New message notification 
6.2.5.4
 
S04: Deferred MM Retrieval 
The TMMS PR WS fetches the message referenced in the 
GetMessageRequest
from the 
TMMS MS and returns it to the client. 
See 3.2.5.4 for a description of step 1.1 of the sequence. 
Figure 6-8: Deferred message retrieval 
6.2.5.5
 
S05: Streaming Retrieval of MM 
Streaming retrieval is accomplished using the Multimedia conference web service. 
The client starts streaming retrieval by creating a conference(step 1). It sets the name of 
the conference as the message reference which it wants the TMMS PR WS to stream 
back to it. Next it invites itself(step 2) and the TMMS PR WS(step 3) to the conference, 
respectively. When the TMMS PR WS notices that it is added to a conference it sets it up 
for streaming the message as indicated in the conference information. 
First it retrieves the conference info, where the message reference is put by the client. 
Then it gets information about the conference owner to know which codecs it supports. 
Now it is ready to setup streaming with the TMMS MS, which is described in 3.2.5.5. 
Then it adds the streaming media for the client, which will then be able to retrieve the 
message. When the client is finished it ends the conference. 
Note that all the messages the TMMS PR WS sends to itself should rather be executed 
internally, without going through the WS interface. 

---

6.2 TMMS Service based on OSA Parlay X Web Services: : Design 
Page 79 of 93