Microsoft Word Master master doc

4.2.5.3
 
S03: New message notification 
Messages routed to the client by IMS will be picked up by the TMMS PR on the 
terminating side of the network. Then a notification event is produced and sent to 
subscribers. The subscribers may then choose to either immediately download the 
message or to download it later. In the figure below this is depicted until where the 
scenario forks. 
The next subsections describe how the NOTIFY message is handled. 

---

4.2 TMMS Service based on IMS: : Design 
Page 55 of 93 
4.2.5.3.1
 
S03.01: TMMS Client Receives MM (Immediate Retrieval) 
In this scenario the client downloads the MM immediately from the TMMS Message 
Store using the HTTP protocol. 
Figure 4-10: TMMS Client retrieves MM immediately 
4.2.5.3.2
 
S03.02: TMMS Client Receives MM (Deferred Retrieval) 
In this scenario the client defers retrieval of the MM by returning 202 (Accepted) back to 
the TMMS PR. 
Figure 4-11: TMMS Client defers retrieval of MM 

---

4.2 TMMS Service based on IMS: : Design 
Page 56 of 93 
4.2.5.4
 
S04: Deferred MM Retrieval 
If the client has deferred retrieval of a MM then it can retrieve it by sending a HTTP 
GET request to the TMMS Message Store. The Request-URI for the GET request is the 
URI which was passed to the client from the TMMS PR in the newmessage-alert 
notification. If the message exists then the TMMS Message Store will return it in the 
body of the response message. 
Figure 4-12: Deferred MM retrieval 

---

4.2 TMMS Service based on IMS: : Design 
Page 57 of 93