Microsoft Word Master master doc

8.3
 
OSA API as a framework for creating end-to-end mobile services 
The various SCFs in the OSA API framework provide a feature rich environment for the 
service provider. But it was hard to find a good way to exchange data between the client 
and the PR, except setting up a "backdoor" like in our design. 
This "backdoor" destroys the end-to-end properties of the OSA API framework, and it 
ends up very similar to the GPRS framework instead. 
In contrast to IMS, OSA API has a small, finite set of documentation which is easy to 
find. Also since it is divided into several and it is easy to see which are relevant to a 
service. 

---

8.4 Conclusion: : OSA Parlay X Web Services as a framework for creating end-to-end 
mobile services 
Page 89 of 93 
Unfortunately the authors did not spend enough research time to learn all the features of the OSA API 
framework. Therefore we acknowledge, with regret, that the service design is a little flawed since it doesn't 
use much of the OSA API features. 
8.4
 
OSA Parlay X Web Services as a framework for creating end-to-
end mobile services 
OSA Parlay X WS provides a simple subset of OSA API's features. But it is rich enough 
so the TMMS Service based on OSA Parlay X WS provides all the necessary features, 
except for immediate retrieval of messages. 
Based on WS-I Basic Profile it provides an end-to-end environment which supports all 
the security quality attributes evaluated.. Reliable messaging, however, is not provided in 
the environment. This quality attribute can be added by the service provider, but both 
the client and the PR must enable support for it. 
8.5
 
Overall 
We introduced by stating that all frameworks has their own advantages and 
disadvantages, and this has been proven correct in this thesis. Therefore we can not state 
that any framework is preferred over the other frameworks without knowing the 
constraints and requirements of the service.