Mobile Computing

1. Mobile Computing
Participents 
112323 : Inkal Patel
112329 : Jatin Patel
 Topic 
MMS [Multimedia Message Service]
Department Of Computer Science
Vidyapith

2. Agenda
• What is MMS
• Introduction
• Figures
• MMS message example
• SMIL and supported media types
• Specifications
• Network elements
• MMS service in detail
• Other issues
• Personal view
• Questions?
Department Of Computer Science
Vidyapith

3. What is MMS (1/2)
• In short: ”A method to send voice,
pictures, text and video from phone/
computer to phone/computer”
• Virtually all new phones have the
capabity to send MMS messages. (For
example all Nokia phones starting from
the new 3000 model series)
• In order to send MMS messages the
user has to configure GPRS (or other
data channel) settings to his/her phone
Department Of Computer Science
Vidyapith

4. What is MMS (2/2)
• The recipient address can be MSISDN, a
phone number or an e-mail address
• The messages are always relayed through a
MMSC (Multimedia Messaging Service Center)
• Current MMS services:
– Pictures, video, sound and text from computer/phone to
computer/phone
– ISP’s have personal accounts for users
• People can for example store pictures on an ISP’s server and then
send them as an MMS using a computer
• Future MMS services
– Every possible way of combining text, sound and pictures
Department Of Computer Science
Vidyapith

5. Introduction to MMS (2)
Department Of Computer Science
Vidyapith

6. Introduction to MMS (3)
Multimedia
Messaging
Center (MMSC)
Internet
MMS Terminal A
MMS Terminal B
Department Of Computer Science
Vidyapith

7. Comparison of MMS and SMS
• both messaging; store-and-forward, not real time.
• MMS: not size-limited, SMS: 160 char;
• MMS: rich message(video,audio..); SMS: pure text
• MMS: personalized profile(when,how send MMS). SMS: no
profile
• MMS: 2.5G, 3G. SMS: 2G+2.5G, also 3G if like.
• MMS: need storage(large). SMS: not a problem due to small
size.
• MMSC: complicated, many elements from different vendors.
SMSC: simple, monolithic
• MMS: data channel; SMS: signalling channel
Department Of Computer Science
Vidyapith

8. MMS Messaging Architecture (1)
MMSM
E
MMSS
MMS Terminal A MMS Server
MMS Proxy Relay
Internet
L
Legacy Wireless Messaging
Systems
Email Server
MMS Terminal B
MMS Terminal C
MMSR
Department Of Computer Science
Vidyapith

9. MMS Messaging Architecture (2)
• MMS Terminal: send, receive, render or create,
modify MM.
• MMS Proxy Relay: interact with MMS terminal, route
MM to target network, send notification to receiver,
communicate with MMS Server.
• MMS Server: storage. Can combined with MMS
Proxy Relay.
• MMSM: interface between client & Proxy Relay; MMSR
and MMSS: not defined yet.
Department Of Computer Science
Vidyapith

10. MMS Messaging Architecture (3)
• With legacy messaging system(i.e. SMS):
interface not defined yet; MM filtered out or
get a SMS with URL pointing to MM.
• With email system: send MM to Email server,
receive MM from Email server, fetch MM
from Email server.
Department Of Computer Science
Vidyapith

11. MMS Messaging Architecture (4)
Interface between mobile handset and MMS proxy relay
• WAP gateway provides HTTP and PUSH services.
• WSP (Wireless Service Protocol) as transport layer between client and WAP
gateway.
• SMIL (Synchornized Multimedia Intergration Language) or WML (Wireless Markup
Language) as Presentation layer.
• WAP gateway encapsulate MM as HTTP to proxy relay
• WAP gateway decapsulate traffic from proxy relay to MMS client.
Department Of Computer Science
Vidyapith

12. Figures
• In Britain 15% of sold phones have a camera by the
end of this year (Wireless World Forum)
• All major ISPs in Finland have MMS relaying
equipment. One MMS costs about 0.6 e
• Worldwide in 2002 over 580 billion users sent 430
billion SMS messages. Under 1 % of users used
MMS (Telecom Trends International)
• Wireless World Forum* predicts that MMS is worth
5.8 billion by 2006 in the Key 16 market**. This is
only 20% of the amout that analysts predict.
• ISPs do not give out information regarding the
number of sent MMS messages.
• In short: estimations are still high and it is uncertain
will MMS hit the market big time like SMS.
Department Of Computer Science
Vidyapith

13. SMIL and supported media types
• SMIL = Synchronized Multimedia Integration Language
– HTML-like language with timing capabilites
– SMIL defines when and where different MMS message
elements (i.e text, audio) are presented
– First phones offer only limited SMIL
– Altenatives for example XHTML, but it does not support
timing
– Conclusion: SMIL must be supported in the future. To help
this there are already documents concerning SMIL+XHTML
• Supported media types:
– Picture: JPEG, GIF, WBMP
– Text: UTF-8/16
– Speech: AMR (Adaptive Multi-Rate)
– Personal information Management: vCalendar and vCard
Department Of Computer Science
Vidyapith

14. MMS example (1/4)
Department Of Computer Science
Vidyapith

15. MMS example (2/4)
• Header
– X-Mms-Message-Type: m-retrieve-conf (required)
– X-Mms-Transaction-Id: text-string
– X-Mms-Version: 1.0
– Message-Id: text-string (usually x@x format)
– Date: HTTP-date-format
– From: address@domain or +InternationalPhoneNumber/TYPE=PLMN (Address-
present-token is assumed)
– To: address@domain or +InternationalPhoneNumber/TYPE=PLMN (use multiple
headers for multiple recipients)
– Cc: (same format as To)
– Bcc: (same format as To)
– Subject: text-string
– X-Mms-Message-Class: Personal, Advertisement, Informational or Auto (default is
Personal)
– X-Mms-Priority: Low, Normal or High (default is Normal)
– X-Mms-Delivery-Report: Yes or No (default is No)
– X-Mms-Read-Reply: Yes or No (default is No)
– Content-type: MIME-Type (default is application/vnd.wap.multipart.related,
override default with caution!)X-NowMMS-Content-Location: filename;content-
type (optional, use multiple headers for multiple files)
Department Of Computer Science
Vidyapith

16. MMS example (3/4)
• SMIL part
<?XML version="1.0" ?>
<!DOCTYPE SMIL PUBLIC "-//W3C//DTD SMIL 2.0 Basic//EN"
"http://www.w3.org/TR/REC-smil/2000/SMIL20Basic.dtd">
<smil>
<head>
<layout> <!-- This is a "landscape" screen -->
<root-layout width="352" height="144"/>
<region id="Image" width="176" height="144" left="0" top="0"/>
<region id="Text" width="176" height="144" left="176" top="0"/>
</layout>
</head>
<body>
<par dur="8s">
<img src="FirstImage.jpg" region="Image" alt="First image" begin="1s" end="6s"/>
<text src="FirstText.txt" region="Text"/>
<audio/>
</par>
</body>
</smil> Department Of Computer Science
Vidyapith

17. MMS example (4/4)
• <smil>: smil part
• <par>: parallel -- happens in parallel. The
par-tag can have dur=” XXms” as an attribute
• <exce>: only one can be selected, a button
for example (not shown here)
• <seq>: elements played in a sequence (not
shown here)
Department Of Computer Science
Vidyapith

18. Specifications
• 3GPP has published two MMS related
specifications
– TS 22.140 Service Aspects
• System requirements at a general level
– TS 23-140 Functional Description
• Detailed version which descibes various architectural
elements that are a part of MMS
• In addition to these 3GPP has five WAP MMS
specifications that describe
– Architecture overview
– Client Transaction
– Encapsulation Protocol
– Two Wireless Session Protocol Spesifications
Department Of Computer Science
Vidyapith

19. Network elements (1/2)
Department Of Computer Science
Vidyapith

20. Network elements (2/2)
• E-mail Server/Gateway
– MMS to E-mail
• Legacy support
– Server where to store the message before user fetches it
• Subscriber database
– Helps MMSC to decide what content to deliver
• Content server
– If a user’s mobile phone does not support sent media,
content server converts it
• Voicemail
– Voice can be encapsulated to MMS messages
• Foreign MMSC
– Must be used when MMS is sent to other carrier’s network
• These are just the basic elements, the future will show us
many more
Department Of Computer Science
Vidyapith

21. MMS service in detail
1. Originator addresses a message
2. Mobile device contains information about MMSC
and initializes a connection and sends the message
3. MMSC accepts the message
4. MMSC sends the message to the receiver
5. The receiver gets information about the message
from MMSC
• Receiver can decide when to get the message
1. MMS message in sent to the user
2. Receiver acknowledges the message
3. MMSC informs the originator that the message was
delivered
Department Of Computer Science
Vidyapith

22. MMS Capable Mobilephones
Nokia 7650
Nokia 7210
Nokia 3510
Sony Ericsson
T300
Ericsson T68/ie
Sony Ericsson
P800
Motorola A820
Nokia 3315
Nokia 6610
Nokia 6100
Nokia 5100
Nokia 3650
Nokia 3530
Sony EricssonP802
Department Of Computer Science
Vidyapith

23. Other important issues
• Terminolgy
– Synchronous: only one message can be
handled at a time
– Asynchronous: several messages can be
handled at a time
• MMSC center uses standard HTTP
headers
• Security: SSL can be used in MMSC
• Charging: external applications may
send charging information to MMSC
Department Of Computer Science
Vidyapith

24. Questions?
• Thank you!
Department Of Computer Science
Vidyapith

25. Personal view
• MMS looks like a killer application, but it
will not ”kill” until the price is reasonable
• MMS will definately belong to the future
of mobile communication
• Streaming and MMS could offer big
revenues
Department Of Computer Science
Vidyapith

26. References
• Course book
• www.w2forum.com
• http://www.ihub.com/MMS%20Messages.htm
• http://www.symbian.com/developer/techlib/v70
• http://www.forum.nokia.com/html_reader
/main/1,4997,2090,00.html?page_nbr=1
Department Of Computer Science
Vidyapith