Microsoft Word Master master doc

3.2.2
 
Deployment view 
The following figure depicts how the TMMS Service is deployed with the GPRS 
framework. 
Figure 3-2 Deployment of GPRS based service 
3.2.2.1
 
TMMS Client 
The service operator must provide the customer with an URL which directs the client to 
a Java Application Descriptor (JAD) document. A JAD contains all information 
necessary for the customer's UE to retrieve and download the MIDP client application. 
This JAD document can be seen in "Appendix E: TMMSClient-IMS.jad". The client 
does not enlist for Push registration in the JAD document because it must subscribe to 
the newmessage-event, as explained below, before it can use the service. 
It needs to know the network's TMMS PR before it can access it. This can be 
accomplished in two ways: 
ƒ
Option one is to set the TMMS PR IP address manually, where the 
service operator gives the IP address to the client. 

---

3.2 TMMS Service based on GPRS: : Design 
Page 32 of 93 
ƒ
The second option is to use a DNS SVR which a client can retrieve from 
a DNS server to discover the local TMMS PR's address. 
3.2.3
 
Component view 
3.2.3.1
 
TMMS Client 
The client application uses the Generic Communication Framework [xx] to communicate 
with the TMMS PR. Support for the HTTP protocol comes from MIDP, and support 
for the SIP protocol is specified in [8]. 
In addition to the components described in 2.4 Case description: TMMS Service above 
adds this solution the package TMmsClient.Communication.Gprs which gives an 
implementation of the TMmsClient.Communication.Messaging interface. This 
implementation is used by the startup class TMmsClient.TMmsClient for 
communication.