Multimedia Messaging Service: Difference between revisions
KMaster888 (talk | contribs) ce |
|||
(550 intermediate revisions by more than 100 users not shown) | |||
Line 1: | Line 1: | ||
{{short description|Standard way to send messages}} |
|||
{{dablink|For the Microsoft Media Server (MMS) protocol, see [[Microsoft Media Services]].}} |
|||
[[File:Ic mms 48px.svg|thumb|110x110px|MMS icon as it appears under an older version of Google Android]] |
|||
{{Cleanup|date=May 2008}} |
|||
'''Multimedia Messaging Service''' ('''MMS''') is a standard way to send messages that include [[multimedia]] content to and from a [[mobile phone]] over a [[cellular network]]. Users and providers may refer to such a message as a '''PXT''', a '''picture message''', or a '''multimedia message'''.<ref name=":1" /> The MMS standard extends the core [[SMS]] (Short Message Service) capability, allowing the exchange of text messages greater than 160 characters in length. Unlike text-only SMS, MMS can deliver a variety of media, including up to forty seconds of video, one image, a [[slide show|slideshow]]<ref name=":0">{{Cite web |title=The History of Multimedia Messaging (MMS) - MMS London |url=http://www.mmsworldlondon.com/history.htm |url-status=dead |archive-url=https://web.archive.org/web/20170504004243/http://www.mmsworldlondon.com/history.htm |archive-date=2017-05-04 |access-date=2016-12-27 |website=www.mmsworldlondon.com}}</ref> of multiple images, or audio. |
|||
{{Unreferenced|date=August 2007}} |
|||
'''Multimedia Messaging Service (MMS)''' is a standard for telephone messaging systems that allows sending messages that include multimedia objects (images, audio, video, rich text) and not just text as in [[Short message service|Short Message Service]] (SMS). It is mainly deployed in cellular networks along with other messaging systems like SMS, [[Mobile Instant Messaging]] and Mobile [[E-mail]]. Its main standardization effort is done by [[3GPP]], [[3rd Generation Partnership Project 2|3GPP2]] and [[Open Mobile Alliance]] (OMA). |
|||
Media companies have utilized MMS on a commercial basis as a method of delivering news and entertainment content, and retailers have deployed it as a tool for delivering scannable coupon codes, product images, videos, and other information. On (mainly) older devices, messages that start off with text, as SMS, are converted to and sent as an MMS when an [[emoji]] is added.<ref>{{Cite news |date=2015-02-05 |title=Emoticons in texts can rack up huge bills |url=https://www.bbc.com/news/technology-31148424 |access-date=2024-07-01 |work=BBC News |language=en-GB}}</ref><ref>{{Cite web |title=Stuff |url=https://www.stuff.co.nz/business/132980959/its-2023-so-why-does-it-cost-50c-to-send-your-mate-an-emoji |access-date=2024-07-01 |website=www.stuff.co.nz}}</ref> |
|||
== Basics == |
|||
[[Cellphones]] have popularized the services provided by SMS (Short Message Service), MMS (Multi-media Messaging Service), as well as [[WAP]] ([[Wireless Application Protocol]]). |
|||
The commercial introduction of MMS started in March 2002,<ref name=":1">{{cite book |last=Le Bodic |first=Gwenaël |title=Mobile Messaging Technologies and Services: SMS, EMS and MMS |date=2005 |publisher=[[Wiley (publisher)|John Wiley & Sons]] |isbn=0-470-01143-2 |edition=2nd |page=208}}</ref> although picture messaging had already been established in Japan.<ref>{{Cite news |last=Dodson |first=Sean |date=2003-07-03 |title=The real picture |url=https://www.theguardian.com/technology/2003/jul/03/newmedia.gadgets |access-date=2024-07-01 |work=The Guardian |language=en-GB |issn=0261-3077}}</ref> It was built using the technology of SMS<ref name=":0" /> as a captive technology which enabled service providers to "collect a fee every time anyone snaps a photo."<ref>{{cite magazine |last=Parks |first=Bob |date=October 2000 |title=Wired Magazine, The Big Picture - Philippe Kahn |url=https://www.wired.com/wired/archive/8.10/kahn.html |url-status=live |archive-url=https://web.archive.org/web/20060326205210/http://www.wired.com/wired/archive/8.10/kahn.html |archive-date=2006-03-26 |access-date=2006-04-20 |magazine=Wired}}</ref> MMS was designed to be able to work on the then-new [[GPRS]] and [[3G]] networks<ref name=":2" /> and could be implemented through either a [[Wireless Application Protocol|WAP]]-based or [[Internet Protocol|IP]]-based gateway.<ref name=":3" /> The [[3GPP]] and WAP Forum groups fostered the development of the MMS standard, which was then continued by the [[Open Mobile Alliance]] (OMA). |
|||
Text messaging (SMS,which is a text-only messaging technology for mobile networks) is mostly popular in Asia and in Europe. SMS is used by people to send short messages usually from person-to-person. |
|||
== Technical description == |
|||
Picture messaging has become more and more popular now that [[cellphone]]s have built in or attachable cameras on them enabling people to send picture messaging back and forth. Picture messaging is made possible through the MMS system which supports all kinds of photos, graphics, animation, as well as video and audio clips. MMS is the evolution of '''[[Short message service|Short Message Service]]'''. It allows the sending and receiving of multimedia messages. It has been designed to work with mobile packet data services such as [[General Packet Radio Service|GPRS]] and [[CDMA2000|1x]]/[[EVDO]]. Many people get images off of the internet and send them around to their friends and family. Mobile cards are popular. This option also allows certain phones to feature games. |
|||
MMS messages are delivered in a different way from SMS. The first step is for the sending device to encode the multimedia content in a fashion similar to sending a [[MIME]] message (MIME content formats are defined in the MMS Message Encapsulation specification). The message is then forwarded to the [[Mobile network operator|carrier's]] MMS [[store and forward]] server, known as the '''MMSC''' (Multimedia Messaging Service Centre). If the receiver is on a carrier different from the sender, then the MMSC acts as a relay, and forwards the message to the MMSC of the recipient's carrier using the Internet.<ref>[http://mbuni.org/userguide.shtml#Section_.1.1.1 "Overview of MMS"] {{Webarchive|url=https://web.archive.org/web/20090827125122/http://www.mbuni.org/userguide.shtml#Section_.1.1.1 |date=2009-08-27 }}, mbuni</ref> |
|||
Once the recipient's MMSC has received a message, it first determines whether the receiver's handset is "MMS capable" or not. If it supports the standards for receiving MMS, the content is extracted and sent to a temporary storage server with an [[HTTP]] front-end. An SMS "control message" containing the [[URL]] of the content is then sent to the recipient's handset to trigger the receiver's [[Wireless Application Protocol|WAP]] browser to open and receive the content from the embedded URL. Several other messages are exchanged to indicate the status of the delivery attempt.<ref>[http://www.nowsms.com/documentation/ProductDocumentation/mms_notifications_and_content/Sending.htm "Sending MMS Notifications and Content"] {{Webarchive|url=https://web.archive.org/web/20090925124936/http://www.nowsms.com/documentation/ProductDocumentation/mms_notifications_and_content/Sending.htm |date=2009-09-25 }}, now.sms</ref> Before delivering content, some MMSCs also include a conversion service that will attempt to modify the multimedia content into a format suitable for the receiver. This is known as "content adaptation". |
|||
The most recent addition is the mobile internet which is powered by WAP, (Wireless Application Protocol). This application allows one to access their emails, to get directions, the news and sports statistics etc... The options are endless and unpredictable. |
|||
[[File:Samsung.Front.JPG|thumb|Older mobile phones, such as this Samsung D500, usually required the manual setting up of the MMS capability]] |
|||
If the receiver's handset is not MMS capable, the message is usually delivered to a web-based service from where the content can be viewed from a normal web browser. The URL for the content is usually sent to the receiver's phone in a normal text message. This behavior is usually known as a "legacy experience" since content can still be received by the user. |
|||
The method for determining whether a handset is MMS capable is not specified by the standards. A database is usually maintained by the operator, and in it each [[MSISDN|mobile phone number]] is marked as being associated with a legacy handset or not. This method is unreliable, however, because customers can independently change their handsets, and many of these databases are not updated dynamically. |
|||
== Applications == |
|||
MMS does not utilize operator-maintained "data" plans to distribute multimedia content; they are used only if the user clicks links inside the message. |
|||
* MMS-enabled [[mobile phone]]s enable subscribers to compose and send messages with one or more [[multimedia]] parts. Multimedia parts may include text, images, audio and video. These content types should conform to the MMS Standards. For example a phone can send an MPEG-4 video in AVI format, but the other party who is receiving the MMS may not be able to interpret it. To avoid this, all mobiles should follow the standards defined by [[Open Mobile Alliance|OMA]]. [[Mobile phone]]s with built-in or attached cameras, or with built-in MP3 players are very likely to also have an MMS messaging client—a [[software]] program that interacts with the mobile subscriber to compose, address, send, receive, and view MMS messages. |
|||
[[E-mail]] and web-based gateways to the MMS system are common. On the reception side, the content servers can typically receive service requests both from WAP and normal HTTP browsers, so delivery via the web is simple. For sending from external sources to handsets, most carriers allow a [[MIME]] encoded message to be sent to the receiver's phone number using a special e-mail address combining the recipient's public phone number and a special domain name, which is typically carrier-specific. |
|||
* MMS Technology is tapped by various companies to suit different solutions. [[CNN-IBN]], India's biggest English news channel, has Mobile Citizen Journalism where citizen can MMS photos directly to the studio.{{Fact|date=June 2008}} |
|||
== Challenges == |
|||
* The [[Indian Premier League]] Club, [[Kolkata Knight Riders]] has its team owner and [[Bollywood]] Celebrity [[ShahRukh Khan]] uploading photos from the match venue to the website directly. Using a Mobile Photo Sharing Platform called Mobshare, these photos are also broadcasted to thousands of fans directly on their mobile phones. |
|||
There are some challenges with MMS that do not exist with SMS: |
|||
[[File:Useless, useless, O2 (346988504).jpg|right|300px|thumb|Handset configuration can cause problems sending and receiving MMS messages.]] |
|||
* '''[[Content adaptation]]''':<ref name=":2">{{cite journal|last=Coulombe|first=Stéphane|author2=Guido Grassel|title=Multimedia Adaptation for the Multimedia Messaging Service|journal=IEEE Communications Magazine|date=July 2004|volume=42|issue=7|pages=120–126|doi=10.1109/MCOM.2004.1316543|s2cid=4785100}}</ref> Multimedia content created by one brand of MMS phone may not be entirely compatible with the capabilities of the recipient's MMS phone. In the MMS architecture, the recipient MMSC is responsible for providing for ''content adaptation'' (e.g., image resizing, audio codec transcoding, etc.), if this feature is enabled by the mobile network operator. When content adaptation is supported by a network operator, its MMS subscribers enjoy compatibility with a larger network of MMS users than would otherwise be available. |
|||
* '''Distribution lists''': Current MMS specifications do not include distribution lists nor methods by which large numbers of recipients can be conveniently addressed, particularly by content providers, called ''[[value-added service|Value-added service providers]]'' (VASPs) in [[3GPP]]. Since most SMSC vendors have adopted [[File Transfer Protocol|FTP]] as an ad-hoc method by which large distribution lists are transferred to the SMSC prior to being used in a bulk-messaging SMS submission, it is expected{{Clarify timeframe|date=March 2023}} that MMSC vendors will also adopt FTP. |
|||
* '''[[Bulk messaging]]''': The flow of ''peer-to-peer'' MMS messaging involves several over-the-air transactions that become inefficient when MMS is used to send messages to large numbers of subscribers, as is typically the case for VASPs. For example, when one MMS message is submitted to a very large number of recipients, it is possible to receive a ''delivery report'' and ''read-reply report'' for each and every recipient. Future MMS specification work is likely to optimize and reduce the transactional overhead for the bulk-messaging case. |
|||
* '''Handset configuration''': Unlike SMS, MMS requires a number of handset parameters to be set. Poor handset configuration is often blamed as the first point of failure for many users. Service settings are sometimes preconfigured on the handset, but mobile operators are now looking at new device management technologies as a means of delivering the necessary settings for data services (MMS, WAP, etc.) via [[over-the-air programming]] (OTA). |
|||
* '''[[WAP Push]]''': Few mobile network operators offer direct connectivity to their MMSCs for content providers.{{fact|date=January 2015}} This has resulted in many content providers using WAP push as the only method available to deliver 'rich content' to mobile handsets. WAP push enables 'rich content' to be delivered to a handset by specifying the URL (via binary SMS) of a pre-compiled MMS, hosted on a content provider's web server. A consequence is that the receiver who pays WAP per kb or minute (as opposed to a flat monthly fee) pays for receiving the MMS, as opposed to only paying for sending one, and also paying a different rate. |
|||
Although the standard does not specify a maximum size for a message, 300 kB and 600 kB are the recommended sizes used by networks<ref>[https://www.gsmarena.com/glossary.php3?term=mms "MMS definition"], ''GSM Arena''</ref> for compatibility with MMS 1.2 and MMS 1.3 devices respectively. The limit for the first generation of MMS was 50 kB.<ref name=":3">{{cite web |
|||
== History == |
|||
| url = https://www.csie.ntu.edu.tw/~r91065/_log/2003-09-28/Resources/mms_composing_messages_rev_a2.pdf |
|||
| title = MMS Developer's Guide |
|||
| date = October 2001 |
|||
| publisher = [[Ericsson|Ericsson Mobility World USA]] |
|||
| access-date = May 12, 2021 |
|||
| archive-date = 2021-09-25 |
|||
| archive-url = https://web.archive.org/web/20210925144522/https://www.csie.ntu.edu.tw/~r91065/_log/2003-09-28/Resources/mms_composing_messages_rev_a2.pdf |
|||
| url-status = dead |
|||
}}</ref> |
|||
== Interfaces == |
|||
MMS was originally developed within the ''Third-Generation Partnership Program'' ([[3GPP]]), a [[Standards organizations|standards organization]] focused on standards for the [[Universal Mobile Telecommunications System|UMTS]]/[[Global System for Mobile Communications|GSM]] networks. |
|||
{{main|MMS Architecture}} |
|||
[[File:MMSCNA.png|right|thumb|330px|MMSC Reference Architecture]] |
|||
* [[MMS Architecture#MM1|MM1]]: the 3GPP interface between MMS User Agent and MMS Center (MMSC, the combination of the MMS Relay & Server) |
|||
* [[MMS Architecture#MM2|MM2]]: the 3GPP interface between MMS Relay and MMS Server |
|||
* [[MMS Architecture#MM3|MM3]]: the 3GPP interface between MMSC and external servers |
|||
* [[MMS Architecture#MM4|MM4]]: the 3GPP interface between different MMSCs |
|||
* [[MMS Architecture#MM5|MM5]]: the 3GPP interface between MMSC and [[GSM core network#Home location register (HLR)|HLR]] |
|||
* [[MMS Architecture#MM6|MM6]]: the 3GPP interface between MMSC and user databases |
|||
* [[MMS Architecture#MM7|MM7]]: the 3GPP interface between MMS VAS applications and MMSC |
|||
* [[MMS Architecture#MM8|MM8]]: the 3GPP interface between MMSC and the billing systems |
|||
* [[MMS Architecture#MM9|MM9]]: the 3GPP interface between MMSC and an [[online charging system]] |
|||
* [[MMS Architecture#MM10|MM10]]: the 3GPP interface between MMSC and a message service control function |
|||
* [[MMS Architecture#MM11|MM11]]: the 3GPP interface between MMSC and an external transcoder |
|||
== Usage, decline and discontinuation == |
|||
Since then, MMS has been deployed world-wide and across both [[Global System for Mobile Communications|GSM]]/[[General Packet Radio Service|GPRS]] and [[CDMA]] networks. |
|||
[[Verizon]] launched its MMS service in July 2003.<ref>{{Cite web |date=2003-07-08 |title=Verizon Wireless launches easy-to-use picture messaging service |url=https://www.verizon.com/about/news/vzw/2003/07/pr2003-07-03 |access-date=2024-07-04 |website=www.verizon.com |language=en}}</ref> Between 2010 and 2013, MMS traffic in the U.S. increased by 70% from 57 billion to 96 billion messages sent.<ref>{{cite web |title=CTIA's Annual Survey Says US Wireless Providers Handled 3.2 Trillion Megabytes of Data Traffic in 2013 for a 120 Percent Increase Over 2012 |url=http://www.ctia.org/resource-library/press-releases/archive/ctia-annual-survey-2013 |url-status=live |archive-url=https://web.archive.org/web/20140723023447/http://www.ctia.org/resource-library/press-releases/archive/ctia-annual-survey-2013 |archive-date=2014-07-23 |access-date=2014-07-29 |website=www.ctia.org}}</ref> This is due in part to the wide adoption of [[smartphone]]s. However take-up of MMS never matched the widespread popularity of SMS text messaging.<ref>https://www.theregister.com/2018/05/07/what_is_rich_communication_services/ {{Bare URL inline|date=August 2024}}</ref> |
|||
Due to lower cost and improved functionality provided by modern internet-based [[instant messengers]] such as [[WhatsApp]], [[Telegram (software)|Telegram]], and [[Signal (messaging app)|Signal]], MMS usage has declined,<ref>https://www.theregister.com/2016/05/20/three_uk_mms_tarriffs/ {{Bare URL inline|date=August 2024}}</ref> and it has been discontinued by several telcos since the early 2020s. Countries with [[Mobile network operator|operators]] that have discontinued MMS include: India (BSNL; from 1 November 2015),<ref>{{Cite news |title=BSNL to shutdown MMS from November 1 - Times of India |newspaper=The Times of India |date=30 October 2015 |url=https://timesofindia.indiatimes.com/bsnl-to-shutdown-mms-from-november-1/articleshow/49596485.cms}}</ref> Philippines (Sun Cellular, Smart Communications, TNT; from 28 September 2018),<ref>{{Cite web |title=Smart, Sun to discontinue MMS by September » YugaTech - Philippines Tech News & Reviews |date=23 August 2018 |url=https://www.yugatech.com/news/smart-sun-to-discontinue-mms/}}</ref> Singapore (Singtel, M1, Starhub; from 16 November 2021),<ref>{{Cite news |title=Farewell, MMS: Messaging service set to end after mid-November - The Straits Times |newspaper=The Straits Times |date=6 September 2021 |url=https://www.straitstimes.com/tech/tech-news/farewell-mms-messaging-service-set-to-end-after-mid-november}}</ref> Kazakhstan (Kcell; from 6 May 2022),<ref>{{Cite web |title=Kcell stops MMS service - Telecompaper |url=https://www.telecompaper.com/news/kcell-stops-mms-service--1423279}}</ref> Switzerland (Swisscom, Salt Mobile; from 10 January 2023),<ref>{{Cite web |title=Goodbye MMS: Swisscom to phase out MMS service ... - Swisscom Community |url=https://community.swisscom.ch/t5/Mobile/Goodbye-MMS-Swisscom-to-phase-out-MMS-service-on-10-January-2023/td-p/698303}}</ref><ref>{{Cite web |title=Salt. - MMS Discontinuation |url=https://www.salt.ch/en/help/mobile/MMS}}</ref> Germany (Vodafone; from 17 January 2023).<ref>{{Cite web |title=Vodafone switches off the MMS - January 04, 2023 - MarketScreener |date=5 January 2023 |url=https://www.marketscreener.com/quote/stock/DEUTSCHE-TELEKOM-AG-444661/news/Vodafone-switches-off-the-MMS-42661616/}}</ref> |
|||
MMS has also been standardized within the ''Third-Generation Partnership Program 2'' ([[3rd Generation Partnership Project 2|3GPP2]]), a [[Standards organizations|standards organization]] focused on specifications for [[CDMA2000]] networks. |
|||
As with most 3GPP standards, the MMS standards have three stages: |
|||
* Stage 1 - Requirements (3GPP TS 22.140) |
|||
* Stage 2 - System Functions (3GPP TS 23.140) |
|||
* Stage 3 - Technical Realizations |
|||
Both 3GPP and 3GPP2 have delegated the development of the Stage 3 Technical Realizations to the [[Open Mobile Alliance|OMA]], a [[Standards organizations|standards organization]] focused on specifications for the mobile wireless networks. |
|||
[[GSM Association]] has produced a MMS Interworking Guidelines [http://www.gsmworld.com/documents/index.shtml IR.52] document for MMS interconnection between GSM operators. |
|||
== Facts == |
|||
* Currently{{when}} 88% of the market of SMS users are under the age of 22 years old.{{Fact|date=June 2008}} |
|||
* Text message usage in 2002 was at approximately 300 million messages per month in the United States and today has risen to over 2.5 billion messages per month.{{Fact|date=June 2008}} |
|||
* [[Verizon Wireless]] and [[AT&T Mobility]], two of the largest [[cellphone]] companies, have been compatible with each other since [[March 18]], [[2005]]. On that day, Verizon's volume of text messages "tripled overnight" according to Verizon spokeswoman J. Abra Degbor.{{Fact|date=June 2008}} |
|||
* Without getting a package deal, on average Verizon and AT&T Mobility charge 25 cents per photo message. |
|||
* It is said that by 2004, SMS was the favorite method of business communication over emails, voice mail or even voice calls. |
|||
* Norwegians and Irish send or receive 2 messages a day. Malaysians send or receive 4 messages a day, Koreans get 10 messages, Singaporeans get 12 messages, and people in the Philippines get 15 messages per day.{{Fact|date=June 2008}} |
|||
== Challenges faced by MMS == |
|||
There are some interesting challenges with MMS that do not exist with SMS: |
|||
* '''Content adaptation''': Multimedia content created by one brand of MMS phone may not be entirely compatible with the capabilities of the recipients' MMS phone. In the MMS architecture, the recipient MMSC is responsible for providing for ''content adaptation'' (e.g., image resizing, audio codec transcoding, etc.), if this feature is enabled by the mobile network operator. When content adaptation is supported by a network operator, its MMS subscribers enjoy compatibility with a larger network of MMS users than would otherwise be available. |
|||
* '''Distribution lists''': Current MMS specifications do not include distribution lists nor methods by which large numbers of recipients can be conveniently addressed, particularly by content providers, called ''Value Added Service Providers'' (VASPs) in [[3GPP]]. Since most SMSC vendors have adopted [[File Transfer Protocol|FTP]] as an ad-hoc method by which large distribution lists are transferred to the SMSC prior to being used in a bulk-messaging SMS submission, it is expected that MMSC vendors will also adopt FTP. |
|||
* '''Bulk messaging''': The flow of ''peer-to-peer'' MMS messaging involves several over-the-air transactions that become inefficient when MMS is used to send messages to large numbers of subscribers, as is typically the case for VASPs. For example, when one MMS message is submitted to a very large number of recipients, it is possible to receive a ''delivery report'' and ''read-reply report'' for each and every recipient. Future MMS specification work is likely to optimize and reduce the transactional overhead for the bulk-messaging case. |
|||
* '''Handset Configuration''': Unlike SMS, MMS requires a number of handset parameters to be set. Poor handset configuration is often blamed as the first point of failure for many users. Service settings are sometimes preconfigured on the handset, but mobile operators are now looking at new device management technologies as a means of delivering the necessary settings for data services (MMS, WAP, etc.) via [[over-the-air programming]] (OTA). |
|||
* '''[[WAP Push]]''': Few mobile network operators offer direct connectivity to their MMSCs for content providers. This has resulted in many content providers using WAP push as the only method available to deliver 'rich content' to mobile handsets. [[WAP push]] enables 'rich content' to be delivered to a handset by specifying the URL (via binary SMS) of a pre-compiled MMS, hosted on a content provider's web server. A downside of WAP push is that from a billing perspective this content is typically billed at data rates rather than as an MMS. These charges can be significant and result in 'bill shock' for consumers. |
|||
Although the standard does not specify a maximum size for a message, 300 kB is the current recommended size used by networks due to some limitations on the WAP gateway side. |
|||
MMS should not be confused with [[Enhanced Messaging Service]] (EMS), which is simply |
|||
[[Short message service|Short Message Service]] (SMS) with additional payload capabilities, allowing a mobile phone to send and receive messages that have special text formatting (such as bold or color), animations, pictures, icons, sound effects, and special ring tones. |
|||
== MMSC Vendors == |
|||
* [[Acision]] |
|||
* [[Comverse]] |
|||
* [[Ericsson]] |
|||
* [[Huawei]] |
|||
* [[LG]] |
|||
* [[Motorola]] |
|||
* [[Nokia Siemens Networks]] |
|||
* [[NowSMS]] |
|||
* [http://www.oksijen.com OKSIJEN] |
|||
* [[Openwave]] |
|||
* [[Wireless Technologies Finland]] |
|||
* [[ZTE Corporation]] |
|||
== Open Source == |
|||
* [http://www.mbuni.org Mbuni Open Source MMS Gateway] |
|||
[[Rich Communication Services|RCS]] is intended to be the successor technology for MMS and SMS. |
|||
== See also == |
== See also == |
||
* [[Common Short Code]] |
|||
* [[Enhanced Messaging Service]] (EMS) |
* [[Enhanced Messaging Service]] (EMS) |
||
* [[Rich Communication Services]] (RCS) |
|||
* [[Mobile Marketing]] |
|||
* [[OTA bitmap]], a Nokia specification for picture messaging |
|||
* [[Short message service|Short Message Service]] (SMS) |
|||
* [[Mobile marketing]] |
|||
* [[Short code]] |
|||
* [[Synchronized Multimedia Integration Language]] |
|||
== |
==References== |
||
{{Reflist}} |
|||
* [[EAIF]] — Nokia's External Application Interface |
|||
* [[MM1]] — the 3GPP interface between MMS User Agent and MMS Center |
|||
* [[MM2 (MMS)|MM2]] — the 3GPP interface between MMS Relay and MMS Server |
|||
* [[MM3 (MMS)|MM3]] — the 3GPP interface between MMS Center and external servers |
|||
* [[MM4]] — the 3GPP interface between MMS Centers |
|||
* [[MM5 (MMS)|MM5]] — the 3GPP interface between MMS Center and [[GSM core network#Home Location Register .28HLR.29|HLR]] |
|||
* [[MM6]] — the 3GPP interface between MMS Center and user databases |
|||
* [[MM7]] — the 3GPP interface between MMS VAS applications and MMS Center |
|||
* [[MM8]] — the 3GPP interface between MMS Center and the billing systems |
|||
* [[MM9]] — the 3GPP interface between MMS Center and an online charging system |
|||
* [[MM10]] — the 3GPP interface between MMS Center and a message service control function |
|||
* [[MM11]] — the 3GPP interface between MMS Center and an external transcoder |
|||
== Resources == |
|||
* {{cite web|title=Text Messaging- American Dinosaur|first=Anthony|last=Wayne|url=http://www.articlesbase.com/cell-phones-articles}} |
|||
* {{cite web|title=Three Ways to Market on Mobile|first=Mike|last=Baker|url=http://www.enpocket.com/news/in-the-press}} |
|||
* {{cite web|title=Firms Make Messaging Pictures Much Easier|first=Peter J.|last=Howe|url=http://www.boston.com/buissiness/technology/articles}} |
|||
* {{cite web|title=Report Dismisses MMS hype|first=James|last=Pierce|url=http://news.zdnet.co.uk/internet}} |
|||
* {{cite web|title=Photo Messaging Services 'Baffling' to Consumers|first=Matthew|last=Broersma|url=http://news.zdnet.co.uk/communications}} |
|||
== External links == |
== External links == |
||
{{commonscat|MMS}} |
|||
* [http://www.mms-stamp.ch MMS-Stamp] - the worlds first MMS postage stamps, published by the Swiss Post after a public competition |
|||
* {{cite web|url=http://www.openmobilealliance.org/Technical/release_program/mms_v1_3.aspx|title=Multimedia Messaging Service 1.3|publisher= Open Mobile Alliance|access-date=14 Jan 2009}} |
|||
* {{cite web|url=http://www.mmaglobal.com/bestpractices.pdf|title=Consumer Best Practices Guide for Cross-Carrier Mobile Content Programs (United States)|publisher=Mobile Marketing Association|access-date=14 Jan 2009|archive-date=17 December 2011|archive-url=https://web.archive.org/web/20111217045056/http://mmaglobal.com/bestpractices.pdf|url-status=dead}} |
|||
* {{cite web|author=Eicher, Richard|title=Advances in MMS offer interactive tools to mobile marketers|publisher=Mobile Marketer|date=13 Jan 2009|url=http://www.mobilemarketer.com/cms/opinion/columns/2440.html|access-date=14 Jan 2009}} |
|||
* {{cite web|author=Morrison, Diane See|title=BMW MMS Campaign Gets 30 Percent Conversion Rate|publisher=mocoNews.net|date=17 Sep 2008|url=http://www.moconews.net/entry/419-bmw-mms-campaign-gets-30-percent-conversion-rate/|access-date=14 Jan 2009|archive-url=https://web.archive.org/web/20080921003700/http://www.moconews.net/entry/419-bmw-mms-campaign-gets-30-percent-conversion-rate/|archive-date=21 September 2008|url-status=dead}} |
|||
{{Mobile phones}} |
|||
[[Category:GSM Standard]] |
|||
{{Open Mobile Alliance standards}} |
|||
{{Telecommunications}} |
|||
[[Category:3GPP standards]] |
|||
[[ar:خدمة رسائل الوسائط المتعددة]] |
|||
[[Category:Mobile telecommunication services]] |
|||
[[cs:MMS]] |
|||
[[Category:Mobile telecommunications standards]] |
|||
[[da:MMS]] |
|||
[[Category:Open Mobile Alliance standards]] |
|||
[[de:Multimedia Messaging Service]] |
|||
[[Category:Telecommunications-related introductions in 2002]] |
|||
[[es:Multimedia Messaging System]] |
|||
[[fr:Message multimédia]] |
|||
[[ko:멀티미디어 메시지 서비스]] |
|||
[[hr:MMS]] |
|||
[[id:Multimedia Messaging Service]] |
|||
[[it:Multimedia Messaging Service]] |
|||
[[he:Multimedia Messaging Service]] |
|||
[[lb:Multimedia Messaging Service]] |
|||
[[lt:MMS]] |
|||
[[lmo:MMS]] |
|||
[[hu:MMS]] |
|||
[[nl:Multimedia Messaging Service]] |
|||
[[ja:マルチメディアメッセージングサービス]] |
|||
[[no:Multimedia Messaging System]] |
|||
[[pl:Multimedia Messaging Service]] |
|||
[[pt:Serviço de mensagens multimídia]] |
|||
[[ru:MMS]] |
|||
[[sk:Multimedia Messaging Service]] |
|||
[[sl:Multimedijski sporočilni sistem]] |
|||
[[sr:MMS]] |
|||
[[fi:Multimediaviesti]] |
|||
[[sv:Multimedia Messaging Service]] |
|||
[[vi:Dịch vụ nhắn tin đa phương tiện]] |
|||
[[tr:MMS]] |
|||
[[uk:Послуга мультимедійних повідомлень]] |
|||
[[zh:多媒體短訊]] |
Latest revision as of 01:07, 1 January 2025
Multimedia Messaging Service (MMS) is a standard way to send messages that include multimedia content to and from a mobile phone over a cellular network. Users and providers may refer to such a message as a PXT, a picture message, or a multimedia message.[1] The MMS standard extends the core SMS (Short Message Service) capability, allowing the exchange of text messages greater than 160 characters in length. Unlike text-only SMS, MMS can deliver a variety of media, including up to forty seconds of video, one image, a slideshow[2] of multiple images, or audio.
Media companies have utilized MMS on a commercial basis as a method of delivering news and entertainment content, and retailers have deployed it as a tool for delivering scannable coupon codes, product images, videos, and other information. On (mainly) older devices, messages that start off with text, as SMS, are converted to and sent as an MMS when an emoji is added.[3][4]
The commercial introduction of MMS started in March 2002,[1] although picture messaging had already been established in Japan.[5] It was built using the technology of SMS[2] as a captive technology which enabled service providers to "collect a fee every time anyone snaps a photo."[6] MMS was designed to be able to work on the then-new GPRS and 3G networks[7] and could be implemented through either a WAP-based or IP-based gateway.[8] The 3GPP and WAP Forum groups fostered the development of the MMS standard, which was then continued by the Open Mobile Alliance (OMA).
Technical description
[edit]MMS messages are delivered in a different way from SMS. The first step is for the sending device to encode the multimedia content in a fashion similar to sending a MIME message (MIME content formats are defined in the MMS Message Encapsulation specification). The message is then forwarded to the carrier's MMS store and forward server, known as the MMSC (Multimedia Messaging Service Centre). If the receiver is on a carrier different from the sender, then the MMSC acts as a relay, and forwards the message to the MMSC of the recipient's carrier using the Internet.[9]
Once the recipient's MMSC has received a message, it first determines whether the receiver's handset is "MMS capable" or not. If it supports the standards for receiving MMS, the content is extracted and sent to a temporary storage server with an HTTP front-end. An SMS "control message" containing the URL of the content is then sent to the recipient's handset to trigger the receiver's WAP browser to open and receive the content from the embedded URL. Several other messages are exchanged to indicate the status of the delivery attempt.[10] Before delivering content, some MMSCs also include a conversion service that will attempt to modify the multimedia content into a format suitable for the receiver. This is known as "content adaptation".
If the receiver's handset is not MMS capable, the message is usually delivered to a web-based service from where the content can be viewed from a normal web browser. The URL for the content is usually sent to the receiver's phone in a normal text message. This behavior is usually known as a "legacy experience" since content can still be received by the user.
The method for determining whether a handset is MMS capable is not specified by the standards. A database is usually maintained by the operator, and in it each mobile phone number is marked as being associated with a legacy handset or not. This method is unreliable, however, because customers can independently change their handsets, and many of these databases are not updated dynamically.
MMS does not utilize operator-maintained "data" plans to distribute multimedia content; they are used only if the user clicks links inside the message.
E-mail and web-based gateways to the MMS system are common. On the reception side, the content servers can typically receive service requests both from WAP and normal HTTP browsers, so delivery via the web is simple. For sending from external sources to handsets, most carriers allow a MIME encoded message to be sent to the receiver's phone number using a special e-mail address combining the recipient's public phone number and a special domain name, which is typically carrier-specific.
Challenges
[edit]There are some challenges with MMS that do not exist with SMS:
- Content adaptation:[7] Multimedia content created by one brand of MMS phone may not be entirely compatible with the capabilities of the recipient's MMS phone. In the MMS architecture, the recipient MMSC is responsible for providing for content adaptation (e.g., image resizing, audio codec transcoding, etc.), if this feature is enabled by the mobile network operator. When content adaptation is supported by a network operator, its MMS subscribers enjoy compatibility with a larger network of MMS users than would otherwise be available.
- Distribution lists: Current MMS specifications do not include distribution lists nor methods by which large numbers of recipients can be conveniently addressed, particularly by content providers, called Value-added service providers (VASPs) in 3GPP. Since most SMSC vendors have adopted FTP as an ad-hoc method by which large distribution lists are transferred to the SMSC prior to being used in a bulk-messaging SMS submission, it is expected[timeframe?] that MMSC vendors will also adopt FTP.
- Bulk messaging: The flow of peer-to-peer MMS messaging involves several over-the-air transactions that become inefficient when MMS is used to send messages to large numbers of subscribers, as is typically the case for VASPs. For example, when one MMS message is submitted to a very large number of recipients, it is possible to receive a delivery report and read-reply report for each and every recipient. Future MMS specification work is likely to optimize and reduce the transactional overhead for the bulk-messaging case.
- Handset configuration: Unlike SMS, MMS requires a number of handset parameters to be set. Poor handset configuration is often blamed as the first point of failure for many users. Service settings are sometimes preconfigured on the handset, but mobile operators are now looking at new device management technologies as a means of delivering the necessary settings for data services (MMS, WAP, etc.) via over-the-air programming (OTA).
- WAP Push: Few mobile network operators offer direct connectivity to their MMSCs for content providers.[citation needed] This has resulted in many content providers using WAP push as the only method available to deliver 'rich content' to mobile handsets. WAP push enables 'rich content' to be delivered to a handset by specifying the URL (via binary SMS) of a pre-compiled MMS, hosted on a content provider's web server. A consequence is that the receiver who pays WAP per kb or minute (as opposed to a flat monthly fee) pays for receiving the MMS, as opposed to only paying for sending one, and also paying a different rate.
Although the standard does not specify a maximum size for a message, 300 kB and 600 kB are the recommended sizes used by networks[11] for compatibility with MMS 1.2 and MMS 1.3 devices respectively. The limit for the first generation of MMS was 50 kB.[8]
Interfaces
[edit]- MM1: the 3GPP interface between MMS User Agent and MMS Center (MMSC, the combination of the MMS Relay & Server)
- MM2: the 3GPP interface between MMS Relay and MMS Server
- MM3: the 3GPP interface between MMSC and external servers
- MM4: the 3GPP interface between different MMSCs
- MM5: the 3GPP interface between MMSC and HLR
- MM6: the 3GPP interface between MMSC and user databases
- MM7: the 3GPP interface between MMS VAS applications and MMSC
- MM8: the 3GPP interface between MMSC and the billing systems
- MM9: the 3GPP interface between MMSC and an online charging system
- MM10: the 3GPP interface between MMSC and a message service control function
- MM11: the 3GPP interface between MMSC and an external transcoder
Usage, decline and discontinuation
[edit]Verizon launched its MMS service in July 2003.[12] Between 2010 and 2013, MMS traffic in the U.S. increased by 70% from 57 billion to 96 billion messages sent.[13] This is due in part to the wide adoption of smartphones. However take-up of MMS never matched the widespread popularity of SMS text messaging.[14]
Due to lower cost and improved functionality provided by modern internet-based instant messengers such as WhatsApp, Telegram, and Signal, MMS usage has declined,[15] and it has been discontinued by several telcos since the early 2020s. Countries with operators that have discontinued MMS include: India (BSNL; from 1 November 2015),[16] Philippines (Sun Cellular, Smart Communications, TNT; from 28 September 2018),[17] Singapore (Singtel, M1, Starhub; from 16 November 2021),[18] Kazakhstan (Kcell; from 6 May 2022),[19] Switzerland (Swisscom, Salt Mobile; from 10 January 2023),[20][21] Germany (Vodafone; from 17 January 2023).[22]
RCS is intended to be the successor technology for MMS and SMS.
See also
[edit]- Enhanced Messaging Service (EMS)
- Rich Communication Services (RCS)
- OTA bitmap, a Nokia specification for picture messaging
- Mobile marketing
- Short code
- Synchronized Multimedia Integration Language
References
[edit]- ^ a b Le Bodic, Gwenaël (2005). Mobile Messaging Technologies and Services: SMS, EMS and MMS (2nd ed.). John Wiley & Sons. p. 208. ISBN 0-470-01143-2.
- ^ a b "The History of Multimedia Messaging (MMS) - MMS London". www.mmsworldlondon.com. Archived from the original on 2017-05-04. Retrieved 2016-12-27.
- ^ "Emoticons in texts can rack up huge bills". BBC News. 2015-02-05. Retrieved 2024-07-01.
- ^ "Stuff". www.stuff.co.nz. Retrieved 2024-07-01.
- ^ Dodson, Sean (2003-07-03). "The real picture". The Guardian. ISSN 0261-3077. Retrieved 2024-07-01.
- ^ Parks, Bob (October 2000). "Wired Magazine, The Big Picture - Philippe Kahn". Wired. Archived from the original on 2006-03-26. Retrieved 2006-04-20.
- ^ a b Coulombe, Stéphane; Guido Grassel (July 2004). "Multimedia Adaptation for the Multimedia Messaging Service". IEEE Communications Magazine. 42 (7): 120–126. doi:10.1109/MCOM.2004.1316543. S2CID 4785100.
- ^ a b "MMS Developer's Guide" (PDF). Ericsson Mobility World USA. October 2001. Archived from the original (PDF) on 2021-09-25. Retrieved May 12, 2021.
- ^ "Overview of MMS" Archived 2009-08-27 at the Wayback Machine, mbuni
- ^ "Sending MMS Notifications and Content" Archived 2009-09-25 at the Wayback Machine, now.sms
- ^ "MMS definition", GSM Arena
- ^ "Verizon Wireless launches easy-to-use picture messaging service". www.verizon.com. 2003-07-08. Retrieved 2024-07-04.
- ^ "CTIA's Annual Survey Says US Wireless Providers Handled 3.2 Trillion Megabytes of Data Traffic in 2013 for a 120 Percent Increase Over 2012". www.ctia.org. Archived from the original on 2014-07-23. Retrieved 2014-07-29.
- ^ https://www.theregister.com/2018/05/07/what_is_rich_communication_services/ [bare URL]
- ^ https://www.theregister.com/2016/05/20/three_uk_mms_tarriffs/ [bare URL]
- ^ "BSNL to shutdown MMS from November 1 - Times of India". The Times of India. 30 October 2015.
- ^ "Smart, Sun to discontinue MMS by September » YugaTech - Philippines Tech News & Reviews". 23 August 2018.
- ^ "Farewell, MMS: Messaging service set to end after mid-November - The Straits Times". The Straits Times. 6 September 2021.
- ^ "Kcell stops MMS service - Telecompaper".
- ^ "Goodbye MMS: Swisscom to phase out MMS service ... - Swisscom Community".
- ^ "Salt. - MMS Discontinuation".
- ^ "Vodafone switches off the MMS - January 04, 2023 - MarketScreener". 5 January 2023.
External links
[edit]- "Multimedia Messaging Service 1.3". Open Mobile Alliance. Retrieved 14 Jan 2009.
- "Consumer Best Practices Guide for Cross-Carrier Mobile Content Programs (United States)" (PDF). Mobile Marketing Association. Archived from the original (PDF) on 17 December 2011. Retrieved 14 Jan 2009.
- Eicher, Richard (13 Jan 2009). "Advances in MMS offer interactive tools to mobile marketers". Mobile Marketer. Retrieved 14 Jan 2009.
- Morrison, Diane See (17 Sep 2008). "BMW MMS Campaign Gets 30 Percent Conversion Rate". mocoNews.net. Archived from the original on 21 September 2008. Retrieved 14 Jan 2009.