Microsoft Word Master master doc

8.6
 
Further Work 
8.6.1
 
OSA API 
It should be examined if adding a Multimedia Messaging SCF with support for TMMS 
helps to make the end-to-end service more natural. This should make it possible to 
remove the "backdoor", so the traffic between the TMMS Client and TMMS PR follows 
the normal network instead. 
8.6.2
 
Different Use Case 
Our use case, a multimedia messaging service, is very common and all of the frameworks 
have a lot of support for messaging already. This has made it hard to use all features of 
the frameworks to avoid building a messaging service upon a messaging service. The 
design of the IMS based service is closest to cross the line here. But since it adds value 
on top of the messaging features of IMS we feel that the design is legal for this 
evaluation. 
A different use case which is not directly supported by the frameworks could shed light 
on areas which have been missed in this thesis. 
8.6.3
 
Quantitative Testing 
This has been a theoretical study of the frameworks, which means it is hard to get 
quantitative data about how the services work when deployed. By implementing the 
different designs it should be easier to investigate their advantages and disadvantages. 

---

8.6 References: : Further Work 
Page 90 of 93 
9
References 
[1]
OMA-MMS-ARCH-V1_2-20031217-C, Multimedia Messaging Service, Architecture 
Overview, Open Mobile Alliance, Dec. 2003.
[2]
OMA-MMS-ENC-V1_2-20040323-C, Multimedia Messaging Service Encapsulation 
Protocol, Open Mobile Alliance, Mar. 2003. 
[3]
JSR030, Connected Limited Device Configuration Version 1.1,
Sun Microsystems, Mar. 
2003; http://jcp.org/en/jsr/detail?id=30. 
[4]
JSR068, J2ME Platform Specification
, Sun Microsystems; 
http://jcp.org/en/jsr/detail?id=68. 
[5]
J2SE, http://java.sun.com/j2se/1.5.0/index.jsp. 
[6]
JSR118, Mobile Information Device Profile 2.0 Version 2.0,
Sun Microsystems, Nov. 2002; 
http://jcp.org/en/jsr/detail?id=118
. 
[7]
R. Fielding et al., 
Hypertext Transfer Protocol – HTTP/1.1
, IETF RFC 2616, Jun. 1999;
http://www.ietf.org/rfc/rfc2616.txt
. 
[8]
JSR180, SIP API version 1.0.
1, JSR 180 Expert Group, 2004; 
http://jcp.org/en/jsr/detail?id=180 
[9]
03-03-01, Unified Modeling Language (UML)
, Object Management Group, 2003; 
http://www.omg.org/technology/documents/formal/uml.htm
. 
[10]
TS 32.152 V6.3.0, Telecommunication management; Integration Reference Point (IRP) 
Information Service (IS) Unified Modeling Language (UML) repertoire,
3GPP, Jun. 2005; 
http://www.3gpp.org/ftp/Specs/html-info/32152.htm
. 
[11]
T.Berners-Lee et al., 
Uniform Resource Locators (URL)
, IETF RFC 1738, Dec. 1994; 
http://www.ietf.org/rfc/rfc1738.txt
. 
[12]
H. Schulzrinne, A. Rao, R. Lanphier, 
Real Time Streaming Protocol (RTSP)
, IETF RFC 
2326, Apr. 1998; 
http://www.ietf.org/rfc/rfc2326.txt
. 
[13]
L. Bass, P. Clements and Rick Kazman, 
Software Architecture in Practice
, 2nd ed. 
Addison-Wesley, Reading, MA., 2003; pp. 294-295. 
[14]
Rosenberg et al., 
Session Initiation Protocol
, IETF RFC 3261, Jun. 2002; 
http://www.ietf.org/rfc/rfc3261.txt
. 
[15]
M. O’Dell et al., 
A Simple Network Protocol (SNMP)
, IETF RFC 1157, May 1990; 
http://www.ietf.org/rfc/rfc1157.txt
. 
[16]
H. Schultzrinne et al.,