Microsoft Word Master master doc

5.2
 
Design 
5.2.1
 
Introduction 
5.2.2
 
Deployment view 
The figure below depicts how the nodes are deployed in an IMS network. 
Figure 5-1: Deployment of OSA API based service in IMS network environment 
The 
OSA API
interface of the OSA AS is used by TMMS PR to use OSA SCFs, such as 
the Charging SCF which is used for charging of service usage. The 
SIP
interface is used 
to communicate with the client.
The next sections will describe in detail how the TMMS Client and the TMMS PR 
applications are deployed. 
5.2.2.1
 
TMMS Client 
The TMMS Client is deployed as in the GPRS based solution, as explained in 3.2.2.1. 
5.2.2.2
 
TMMS Proxy-Relay 
The TMMS PR is deployed at an AS. The kind of AS and how it is deployed there is an 
implementation detail which is out of scope for this report. This AS can either be located 
in the client's home network or at an external service platform. 

---

5.2 TMMS Service based on OSA API: : Design 
Page 67 of 93 
Before the TMMS PR can access OSA services it needs to establish a service agreement 
with the OSA service provider. The procedure for establishing a service agreement may 
include an offline provider specific part which is not included here. There are multiple 
steps which needs to be executed to establish the service agreement which is described in 
the subsections below. 
5.2.2.2.1
 
Initial Access 
First TMMS PR must initialize with the OSA Framework and agree on which API 
version which should be used. Figure 5-2 shows this part of the scenario. 
Figure 5-2: Establish service agreement - Initial Access