 |
|
|
| Welcome |
|
Welcome to the main Web-site for the OpenMMS-project. The aim of this project is to design an MMSC
which can provide an alternative to commercial MMSC (Multimedia Messaging Service Center).
The MMSC (as it is most commonly referred to)
is being developed, first and foremost, for the sending of multimedia messages between mobile phones.
The chosen programming platform for development is JAVA, using Java Servlets and EJB. You can read about the different
technologies being used by clicking on the links in botton of the page. These technologies have been chosen to make the system as
“versatile” as possible, i.e. not dependent on any given operative system or database.
Take your time and visit our
developmentsite at sourceforge.net
|
| About MMSC |
MMSC is an abbreviation for Multimedia Messaging Service Center and is an internet based server interface
for the transferring of multimedia between mobile phones.
A multimedia message (MM), when sent from a mobile phone,
is directed via a WAP-gateway, to the server. During this process the WAP-gateway converts the messages from the
WAP-protocol binary format to HTTP-protocol. An MMSC can be facilitated with a wide range of services for mobile users,
as illustrated in the figure of an MMSC.
The MMS traffic highways are mostly controlled by telephone companies and multimedia giants, who are cashing in on
this “sought after” service, through their own MMSC’s. OpenMMS is interested in making the facility of an MMSC available
to a wider scope of service providers, of whom, not all posses the resources to invest in producing their own MMSC,
or renting from another service provider.
|
Click on picture to enlarge
|
|
| About OpenMMS |
|
Open source MMSC is being built in compliance with the functional specifications described by
WAP Forum and 3GPP:
You need to have Acrobat Reader installed in order to view these documents!
Visit Adobe and download Acrobat Reader for free, by clicking on the links below.
3GPP TS 22.140 V5.4.0, Technical Specification, stage 1
3GPP TS 23.140 V6.0.0, Technical Specification, stage 2
OMA-WAP-MMS-ARCH-v1_1-20021101-C, Architecture Overview, Version 1.1, 01-November-
2002
OMA-WAP-MMS-CTR-v1_1-20021031-C, Client Transactions, Version 1.1, 31-October-2002
OMA-MMS-ENC-v1_1-20021030-C, Encapulation Protocol, Version 1.1, 31-October-2002
The MMSC has been divided into two main entities, which are: Relay and Server.
As the names suggest, InRelay is the component which receives the MMS-messages and sends them to the server,
and OutRelay fetches the MMS-message from the server and sends it to the MMS-recipient.
The Server uses Java Beans functionality to process the MMS-messages and provide an interface for persistent storage.
|
Click on picture to enlarge
|
|
| Get Involved
|
|
If you are interested in this project and would like to participate in some way, then why not
sign up and join us.
If you'd like more details about the MMS-specifictations, as given out by 3GPP
and OMA(Open Mobile Alliance),
then click on the link in the above section.
|
| Logo
|
|
The chosen logo for OpenMMS is that of the humming bird, nature’s smallest
and most colourful bird. With its glittering feather coat, comprised of all
the colours of the rainbow, the humming bird is also referred to by some as
Nature’s Jewel. It is the only bird in the world capable of as many as 200
wing beats per second, thus creating the humming sound which has given the
bird its common name. There are many different species of humming bird,
varying in colour and size, the smallest of these measuring no more than
2,5cm in length.
|
|
For us the colourful content of multimedia is represented by the humming
birds many colours, whereas its swift reaction speed captures the idea of
rapid message transfer. The size of this colourful bird illustrates too, how
little it takes to spread colour in motion.
|
|
|
|
