Microsoft Word Master master doc

B3: Sender may demand that the recipient is charged for the message
Yes. Uses private charging field. 
B4: Sender can not deceive receiver to pay for any messages
 
No support. 

---

5.1 TMMS Service based on OSA API: : Overview 
Page 64 of 93 
5
TMMS Service based on OSA API 
In this chapter we will first give a brief introduction of OSA. A more detailed reading 
about OSA can be found in [43]. The end-to-end mobile service designed in this chapter 
is based on OSA API. We continue this chapter presenting to service, before we end this 
chapter with an evaluation of the service based on the criteria and scenarios in 2.5. 
5.1
 
Overview 
Earlier the circuit switched telecommunication networks where separate from the packet 
switched computer networks. In the last few years this has changed and these networks 
have converged. This makes it possible to create new kinds of service, and has brought 
forward a need for a standard interface to create services. With no standard interface it 
becomes harder to deploy a service in networks from different providers, and in 
computer networks it has been common to have such a standard interface, for example 
the Portable Operating system Interface (POSIX) and the Common Object Request 
Broker Architecture (CORBA), but this is quite new for telecommunication networks. 
The OSA interface is jointly developed by 3GPP, The Third Generation Partnership 
Project 2 (3GPP2), European Telecommunication Standards Institution (ETSI) and the 
Parlay Group to be such an interface. Through the OSA interface applications gets 
access to network functionality, and makes applications independent from the underlying 
network technology. 
From [TS23.198-100], the OSA consists of three parts: 
ƒ
Applications 
Implemented in one or more Application Server(s) and makes use of the 
other parts. The MMS as discussed later in this paper is one such 
application.