Microsoft Word Master master doc

 
TMMS Client 
The client may use the standard JAD-based deployment, as explained in 3.2.2.1. In 
addition a push-based deployment method is also possible, because the TMMS PR can 
obtain the client's address from the Via-header of its initial SIP REGISTER request. 
The TMMS PR acts as a PI and requests version information for the TMMS Client from 
the client. If it is not installed or a newer version is available then TMMS PR will send a 
push request to the client. 
4.2.2.2
 
TMMS Proxy-Relay 
The service is deployed to a SIP Application Server. For the service to be available to a 
user its Service Profile GUP component and initial Filter Criteria (iFC) must be updated 
to include the TMMS PR. 

---

4.2 TMMS Service based on IMS: : Design 
Page 51 of 93 
The figure below shows how the TMMS PR updates these elements. 
Figure 4-5: Create service profile of PUI 
First the service operator uses the discovery service to get the address of the GUP Server 
and an authorization token for the Create request. Next the Create request is sent to the 
GUP Server with the authorization token. Service information included in the Create 
request includes service information: 
ƒ
Authorization token, from the Discovery Service 
ƒ
PUI to give service access to. 
ƒ
iFC component for the service. 
The specification for this is currently a bit unfinished, so a complete example of this can 
not be included here. An example of the iFC added to the Service Profile is given in 
Appendix F:InitialFilterCriteria.xml. The trigger point used in the example has two 
Service Point Triggers (SPT) in an AND condition, which are explained below. 
ƒ
SIP Method MESSAGE 
The service will only trigger on MESSAGE requests. 
ƒ