Content for TS 23.140 Word version: 6.16.0
1 Scope p. 10
The present document defines the stage 2 and stage 3 description of the non-realtime Multimedia Messaging Service, MMS. Stage 2 identifies the functional capabilities and information flows needed to support the service described in stage 1.
The present document includes information applicable to network operators, service providers and terminal, switch and database manufacturers.
The present document contains the core functions for a non realtime Multimedia Messaging Service, MMS, which are sufficient to provide a basic service.
MMS uses a number of technologies to realise the requirements of the stage 1 description (3G TS 22.140). The present document describes how the service requirements are realised with the selected technologies. As far as possible existing protocols (e.g. WAP, SMTP, ESMTP as transfer protocols; lower layers to provide push, pull, notification) and existing message formats (e.g. SMIL, MIME) shall be used for the realisation of the Multimedia Messaging Service.
The present document serves as a foundation for the development of MMS. It describes a new service which has no direct equivalent in the previous ETSI/GSM world or in the fixed network world. In consequence readers may find that certain aspects are not clearly defined or open to misinterpretation. Where any such case is encountered it is essential that the issue is brought to the 3GPP TSG T2 standards body (see page 2 for contact information) for discussion and resolution in order to provide interoperable implementations.
2 References p. 10
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TS 22.140: "Multimedia Messaging Service; Stage 1".
[2]
TR 21.905: "Vocabulary for 3GPP Specifications".
[3] void
[4] void
[5]
IETF; STD 0011 (RFC 2822): "Internet Message Format", URL: http://www.ietf.org/rfc/rfc2822.txt.
[6]
RFC 2046: "Multipurpose Internet Mail extension (MIME) Part Two: Media Types", URL: http://www.ietf.org/rfc/rfc2046.txt.
[7] void.
[8] void
[9] void
[10] void
[11]
TS 24.011: "Point to Point (PP) Short Message Service (SMS) support on mobile radio interface".
[12] void
[13] void
[14] void
[15] void
[16] void
[17] void
[18] void
[19] void
[20] void
[21] void
[22]
RFC 2821: STD 0010 "Simple Mail Transfer Protocol", URL: http://www.ietf.org/rfc/rfc2821.txt.
[23]
WAP Forum (November 1999): "WAP Wireless Session Protocol", WAP-WSP-19991105- , URL: http://www.wapforum.org/.
[24] void
[25] void
[26] void
[27] void
[28] void
[29] void
[30] void
[31]
ITU-T Recommendation T.37 (06/98): "Procedures for the transfer of facsimile data via store and forward on the Internet".
[32]
ITU-T Recommendation T.30 (1996): "Procedures for document facsimile transmission in the general switched telephone network".
[33]
RFC 2421 (Sept. 1998): "Voice Profile for Internet Mail - version 2, VPIM" , URL: http://www.ietf.org/rfc/rfc2421.txt.
[34]
IETF; STD 0053 (RFC 1939): "POP 3, Post Office Protocol - Version 3" , URL: http://www.ietf.org/rfc/rfc1939.txt.
[35]
RFC 1730 (December 1994): "IMAP4, Internet Message Access Protocol - Version 4" , URL: http://www.ietf.org/rfc/rfc1730.txt..
[36]
Adobe Systems: "Tag Image File Format (TIFF), Version 6", URL:, http://www.adobe.com.
[37]
TR 23.039: "Interface protocols for the connection of Short Message Service Centres (SMSCs) to Short Message Entities (SMEs)".
[38] void
[39] void
[40]
TS 26.233: "End-to-end transparent streaming Service (PSS); General Description".
[41]
TS 26.234: "End-to-end transparent streaming Service (PSS); Protocols and Codecs".
[42] void
[43] void
[44]
RFC 2045: "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", URL: http://www.ietf.org/rfc/rfc2045.txt
[45] void
[46] void
[47] void
[48]
RFC 2616: "Hypertext Transfer Protocol, HTTP/1.1", URL: http://www.ietf.org/rfc/rfc2616.txt.
[49] void
[50] void
[51] void
[52] void
[53]
RFC 1327: "Mapping between X.400(1988)/ISO 10021 and RFC 822", URL: http://www.ietf.org/rfc/rfc1327.txt.
[54]
TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting Packet Based Services and Packet Data Networks (PDN)"
[55]
Open Mobile Alliance; OMA-TS-WAP-ProvCont-v1_1: Provisioning Content Version 1.1, URL: http://www.openmobilealliance.org/
[56]
Open Mobile Alliance; OMA-MMS-ENC-v1_2: Multimedia Messaging Service, Encapsulation Protocol, Version 1.2, URL: http://www.openmobilealliance.org
[57]
RFC 1870: "SMTP Service Extension for Message Size Declaration", URL: http://www.ietf.org/rfc/rfc1870.txt
[58]
RFC 1652: "SMTP Service Extension for 8bit-MIME transport", URL: http://www.ietf.org/rfc/rfc1652.txt
[59] void
[60]
RFC 3403: "Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database", URL: http://www.ietf.org/rfc/rfc3403.txt
[61]
RFC 3761, "The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)", URL: http://www.ietf.org/rfc/rfc3761.txt
[62]
TS 29.002: "Mobile Application Part (MAP) specification".
[63]
TS 22.066: "Support of Mobile Number Portability (MNP); Service description. Stage 1".
[64]
TS 23.066: "Support of Mobile Number Portability (MNP); Technical realization. Stage 2".
[65]
RFC 2617 "Access Authentication", URL:http://www.ietf.org/rfc/rfc2617.txt
[66]
RFC 2246 "TLS protocol, version 1.0" , URL:http://www.ietf.org/rfc/rfc2246.txt
[67]
TS 31.102: "Characteristics of the USIM Application".
[68]
W3C Note 08 May 2000: "Simple Object Access Protocol (SOAP) 1.1", URL: http://www.w3.org/TR/SOAP
[69]
W3C Note 11 December 2000: "SOAP Messages with Attachments", URL: http://www.w3.org/TR/SOAP-attachments
[70]
RFC 2376: "XML Media Type", URL: http://www.ietf.org/rfc/rfc2376.txt.
[71]
RFC 2387: "The MIME Multipart/Related Content Type", URL: http://www.ietf.org/rfc/rfc2387.txt.
[72]
RFC 2111: "Content-ID and Message-ID Uniform Resource Locators", URL: http://www.ietf.org/rfc/rfc2111.txt.
[73] void
[74]
TS 26.140: "Multimedia Messaging Service; Media formats and codecs".
[75]
TS 51.011: (Rel-4): "Specification of the Subscriber Identity Module - Mobile Equipment (SIM-ME) interface".
[76]
"Digital Rights Management": Open Mobile AllianceTM, OMA-Download-DRM-v1_0, http://www.openmobilealliance.org/
[77]
"DRM Rights Expression Language": Open Mobile AllianceTM, OMA-Download-DRMREL-v1_0, http://www.openmobilealliance.org/
[78]
"DRM Content Format": Open Mobile AllianceTM, OMA-Download-DRMCF-v1_0, http://www.openmobilealliance.org/
[79]
ITU-T Recommendation E.212: "The international identification plan for mobile terminals and mobile users".
[80]
TS 32.240: "Charging Management; Charging Architecture and Principles ".
[81]
TS 32.270: "Charging Management; Multimedia Messaging Service (MMS) charging".
[82]
Open Mobile Alliance; OMA-ERELD-MMS-v1_2-20030923-C: Enabler Release Definition for MMS Version 1.2, URL: http://www.openmobilealliance.org/
[83]
TS 23.078: "Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4 - Stage 2"
[84]
RFC 3588 "Diameter Base Protocol", URL: http://www.ietf.org/rfc/rfc3588.txt.
[85]
Open Mobile Alliance; OMA-MMS-CONF-v1_2-20040219-C: MMS Conformance Document 1.2, URL: http://www.openmobilealliance.org/
[86]
TS 29.140: "MM10 interface based on Diameter protocol (Stage 3)".
[87]
TS 31.111: "USIM Application Toolkit (USAT) ".
[88]
Open Mobile Alliance; OMA-TS-STI-V1_0-20050704-C: Standard Transcoding Interface Specification, URL: http://www.openmobilealliance.org/.
[89]
RFC 4355: "IANA Registration for ENUMservices email, fax, mms, ems and sms", URL: http://www.ietf.org/rfc/rfc4355.txt
[90]
Open Mobile Alliance; OMA MMS Management Object: URL: http://www.openmobilealliance.org/
[91]
Open Mobile Alliance; OMA Device Management Protocol: Version 1.2. OMA-TS-DM_Protocol-V1_2. URL: http://www.openmobilealliance.org
3 Definitions and Abbreviations p. 14
3.1 Definitions p. 14
For the purposes of the present document, the terms and definitions defined in TR 21.905 and TS 22.140 and the following apply:
Abstract message:
information which is transferred between two MMS entities used to convey an MM and/or associated control information between these two entities
Application Data:
Information / data specific to an application other than the MMS User Agent / VASP which is intended to be transported without alteration by using MMS. Application Data may be of any content type and format.
Delivery Report:
feedback information provided to an originator of MM (MMS User Agent or VASP) by an MMS Relay/Server about the status of the delivery of an MM
External Server:
network entity/application of an external system such as Internet email, unified messaging system or facsimile to which MMs may be sent to and/or from which MMs may be received by an MMS User Agent via an MMS service provider
Forwarding MMS User Agent:
MMS User Agent that is the intended recipient of an MM, that requests forwarding of the MM for delivery to other recipient(s) without having to first download the MM
Forwarded MM:
MM originally sent from a sender to an intended recipient which is then forwarded to other recipient(s) and to which a delivery report and/or read-reply report may refer and which may be subject to further forwarding
Message ID:
a unique identifier for an MM
Message Reference:
a unique identifier for an MM indicating the location of the MM
MMBox:
network storage associated with a user into which MMs, along with MM State and MM Flags, may be stored, retrieved, and deleted
Messaging Service Control Function:
an external entity used for number translation purposes
MM State:
the state of an MM within the MMBox, as one of several, mutually-exclusive enumerated values
MM Flags:
a list of zero, one, or more keyword flags, defined by the MMS User Agent, associated with the MM
MM Cancellation:
act of the originating MMS VAS Application to cancel an already submitted MM on the originator MMS Relay/Server
MM Delivery:
act of a recipient MMS Relay/Server delivering an MM to a recipient MMS User Agent
MM Submission:
act of an originator MMS User Agent / VAS Application submitting an MM to the originator MMS Relay/Server
MM Notification:
a notification to the MMS User Agent with specific, Message related information;
MM Replacement:
Act of the originating VAS Application to replace an already submitted MM on the originator MMS Relay/Server
MMSNA:
Multimedia Messaging Service Network Architecture encompasses all the various elements that provide a complete MMS to a user
MMSE:
collection of MMS-specific network elements under the control of a single administration
MMS Relay/Server:
MMS-specific network entity/application that is under the control of an MMS service provider
MMS Retrieval Mode:
the mode in which the Multimedia Message is retrieved from the Network
MMS User Agent:
application residing on a UE, an MS or an external device that performs MMS-specific operations on a user's behalf and/or on another application's behalf.
MMS VAS Applications:
Applications providing Value Added Services (e.g. news service or weather forecasts) to MMS users.
Original MM:
(initial) MM sent from a sender to a recipient and to which a delivery report and/or a read-reply report and/or a reply-MM may refer and/or which may be subject to being forwarded
Originator MMSE:
MMSE associated with the sender of an MM
Originator MMS Relay/Server:
MMS Relay/Server associated with the sender of an MM
Originator MMS User Agent:
MMS User Agent associated with the sender of an MM
Originator VASP:
VASP which is sending an MM
Read-Reply Report:
feedback information to an originator MMS User Agent by a recipient MMS User Agent about the status of handling/rendering of an original MM in a recipient MMS User Agent
Recipient MMSE:
MMSE associated with the recipient of an MM
Recipient MMS Relay/Server:
MMS Relay/Server associated with the recipient of an MM
Recipient MMS User Agent:
MMS User Agent associated with the recipient of an MM
Recipient VASP:
VASP which is receiving an MM
Reply-MM:
the first reply accepted by the recipient MMS Relay/Server (after checking the reply charging limitations, such as the latest time of submission) in case of reply-charging
Service provider identification:
an identification for a service provider, e.g. a domain name, MCC+MNC, or a subset of the IMSI identifying the service provider. It is possible for the MMS Relay/Server to host several service providers. Mechanisms for this are implementation- and operator-specific.
Short code:
Service provider specific address which is a string of alphanumeric characters
SOAP Attachment:
Multimedia content, e.g. audio, image, text, presentation or a combination of different media types and/or formats, transferred from an MMS VASP to an MMS Relay/Server or vice versa.
Time stamp:
The date, time and the additional information, e.g. UTC, GMT or time zone, which allows the unambiguous identification of time.
Transaction:
message pair sent between an MMS User Agent and MMS Relay/Server, or between MMS Relay/Servers
3.2 Abbreviations p. 15
For the purposes of the present document, the abbreviations defined in [1] and [2] and the following apply:
CDR
Charging Data Record
DCF
DRM Content Format
DNS
Domain Name System
DRM
Digital Rights Management
EMA
Electronic Message Association
E-Mail
Electronic Mail
ENUM
Electronic Numbering
FQDN
Fully Qualified Domain Name
GW
Gateway
HTTP
Hypertext Transfer Protocol
IANA
Internet Assigned Numbering Authority
IETF
Internet Engineering Task Force
IMAP4
Internet Message Access Protocol
MIME
Multipurpose Internet Mail Extensions
MM
Multimedia Message
MMS
Multimedia Messaging Service
MMSE
Multimedia Messaging Service Environment
MMSNA
Multimedia Messaging Service Network Architecture
MSCF
Messaging Service Control Function
MTA
Mail Transfer Agent
PDU
Protocol Data Unit
POP3
Post Office Protocol Version 3
RADIUS
Remote Authentication Dial In User Service
RFC
Request for Comments
RTSP
Real Time Streaming Protocol
SDP
Session Description Protocol
SMIL
Synchronised Multimedia Integration Language
SMTP
Simple Mail Transfer Protocol
SOAP
Simple Object Access Protocol
SPI
Service Provider Identification
TLD
Top Level Domain
UA
User Agent
URI
Uniform Resource Identifiers
VAS
Value Added Service
VASP
Value Added Service Provider
VPIM
Voice Profile for Internet Mail
W3C
WWW Consortium
WAP
Wireless Application Protocol
WSP
WAP Session Protocol
XML
Extensible Markup Language
