MMS Introduction Architecture & Format Monky Chen Feb xx 2005
Dec 17, 2014
MMS Introduction Architecture & Format
Monky Chen
Feb xx 2005
Outline
1. MMS Overview
2. MMS Architecture
3. MMS Client Transaction– MMS transaction model
4. MMS Encapsulation Protocol– MM Message format
5. Discussion
1.1 Introduction
• MMS = Multimedia Messaging Services
• To provide a rich set of content (Image/ Text/ Audio) to subscribers in a message context.
• Example:
MMS Overview
MMS Overview MMS Architecture Client Transaction Encapsulation
Protocol
1.2 Comparison of MMS & SMS
MMS Overview
MMS Overview MMS Architecture Client Transaction Encapsulation
Protocol
2.1 MMS Architecture
MMS Overview
MMS ArchitectureMMS ArchitectureClient Transaction Encapsulation
Protocol
2.2
MMS Overview
MMS ArchitectureMMS ArchitectureClient Transaction Encapsulation
Protocol
3.1
MMS Overview
MMS Architecture
Client TransactionClient TransactionEncapsulation
Protocol
3.2 Transaction Model
MMS Overview
MMS Architecture
Client TransactionClient TransactionEncapsulation
Protocol
4.1 Why Encapsulation?
• Limited bandwidth of the air interface between an MMS Client and an MMS Proxy-Relay, PDUs are encoded in binary encoding format.
MMS Overview
MMS Architecture Client Transaction
Encapsulation Protocol
Encapsulation Protocol
4.2 MM Message Structure Overview
MMS Overview
MMS Architecture Client Transaction
Encapsulation Protocol
Encapsulation Protocol
MMS Header
Message Body
presentation
image/jpeg
text/plain
audio/wav
Start
PDU = MMS Header + Message body
4.3 MMS PDUs
MMS Overview
MMS Architecture Client Transaction
Encapsulation Protocol
Encapsulation Protocol
• 12 types of PDUs in MMS level• Send: M-Send.req, M-Send.conf• Retrieve: WSP/HTTP GET.req, M-Retrieve.conf• Notification: M-Notification.ind, M-NotifyResp.ind• Reporting: M-Delivery.ind• Acknowledgement: M-Acknowledge.ind• Read Report: M-Read-Rec.ind, M-Read-Orig.ind• Forward transaction: M-Forward.req, M-Forward.conf
4.4 MMS PDUs – Send (1)
MMS Overview
MMS Architecture Client Transaction
Encapsulation Protocol
Encapsulation Protocol
Field Name Presence Field Description
X-Mms-Message-Type M Specifies the PDU type: (M-Send.req)
X-Mms-Transaction-ID M Unique identifier for the transaction.
X-Mms-MMS-Version M MMS version number. (now, 1.0)
Date O Arrival time of the message at MMSC.
From M Address of the sender.
To O (M) Address of the recipient(s).
Cc O (M) Address of the recipient(s).
Bcc O (M) Address of the recipient(s).
Subject O Subject of the message.
X-Mms-Message-Class O Class of the message. (“Auto”/”Personal”)
X-Mms-Expiry O Validity period of the message in MMSC.
X-Mms-Delivery-Time O Time of desired delivery.
X-Mms-Priority O Priority of the message.
X-Mms-Sender-Visibility O Hide the sender’s address. (“Hide”/”Show”)
X-Mms-Delivery-Report O Request of delivery report. (“Yes”/“No”)
X-Mms-Read-Reply O Request of read report. (“Yes”/“No”)
Content-Type M MIME type of the message content.
Message-Body M MIME-encoded multimedia message.
M-Send.req
M-Send.conf
MMSM(MM1)
Origination UE
MMS Proxy Relay A
4.5 MMS PDUs – Send (2)
MMS Overview
MMS Architecture Client Transaction
Encapsulation Protocol
Encapsulation Protocol
MMSM(MM1)
M-Send.req
M-Send.conf
Field Name Presence Field Description
X-Mms-Message-Type M Transaction type: (M-Send.conf)
X-Mms-Transaction-ID M Identifier in corresponding M-Send.req.
X-Mms-MMS-Version M MMS version number.
X-Mms-Response-Status M MMS specific status.
X-Mms-Response-Text O Text description of the response status.
Message-ID O(M) Unique reference for the message in MMSC.
Mandatory when the message is accepted.
Originating UE
MMS Proxy Relay A
4.6 MMS PDUs – Notification (1)
MMS Overview
MMS Architecture Client Transaction
Encapsulation Protocol
Encapsulation Protocol
MMSM(MM1)
Receiving UE
MMS Proxy Relay B
M-Notification.ind
M-NotifyResp.ind
Field Name Presence Description
X-Mms-Message-Type M Transaction type: (M-Notification.ind)
X-Mms-Transaction-ID M Unique identifier for the transaction.
X-Mms-MMS-Version M MMS version number.
From O Address of the sender.
Subject O Subject of the message.
X-Mms-Message-Class M Class of the message.
X-Mms-Message-Size M Size of the message. (in octets)
X-Mms-Expiry M Validity period of the message in MMSC.
X-Mms-Content-Location M Location of the message. (URI)
4.7 MMS PDUs –Notification (2)
MMS Overview
MMS Architecture Client Transaction
Encapsulation Protocol
Encapsulation Protocol
MMSM(MM1)
Receiving UE
MMS Proxy Relay B
M-Notification.ind
M-NotifyResp.ind
Name M/O Comments
X-Mms-Message-Type M Transaction type: (M-NotifyResp.ind)
X-Mms-Transaction-ID M Unique identifier for the transaction.
X-Mms-MMS-Version M MMS version number.
X-Mms-Status M Message status.
X-Mms-Report-Allowed O Sending of delivery report allowed or not.
4.8 MMS PDUs –Retrieve (1)
MMS Overview
MMS Architecture Client Transaction
Encapsulation Protocol
Encapsulation Protocol
MMSM(MM1)
Receiving UE
MMS Proxy Relay B
M-Retrieve.conf
M-Acknowledge.ind
WSP/HTTP GET.req
Name Comments
TID Transaction Id
Type PDU type = “Get” (WAP-WSP 8.2.3.1)
URILen Length of URI
URI Location of the message.
Headers Headers related with the GET request
4.9 MMS PDUs –Retrieve (2)
MMS Overview
MMS Architecture Client Transaction
Encapsulation Protocol
Encapsulation Protocol
MMSM(MM1)
Receiving UE
MMS Proxy Relay B
M-Retrieve.conf
M-Acknowledge.ind
WSP/HTTP GET.reqName M/O Comments
X-Mms-Message-Type M Transaction type: (M-Retrieve.conf)
X-Mms-Transaction-ID M(O) Mandatory when immediate retrieval.
X-Mms-MMS-Version M MMS version number. (now, 1.0)
Message-ID O Unique reference of the message.
Date M Sending date and time.
From O Address of the sender.
To O Address of the recipient.
Cc O Address of the recipient.
Subject O Message subject.
X-Mms-Message-Class O Message class.
X-Mms-Priority O Priority of the message.
X-Mms-Delivery-Report O Delivery report is requested or not.
X-Mms-Read-Reply O Read report is requested or not.
Content-Type M MIME type of the message content.
Message-Body M MIME-encoded multimedia message.
4.10 MMS PDUs – Acknowledgement
MMS Overview
MMS Architecture Client Transaction
Encapsulation Protocol
Encapsulation Protocol
MMSM(MM1)
Receiving UE
MMS Proxy Relay B
M-Retrieve.conf
M-Acknowledge.ind
WSP/HTTP GET.req
Name M/O Comments
X-Mms-Message-Type M Transaction type: (M-Acknowledge.ind)
X-Mms-Transaction-ID M Unique identifier for the transaction.
X-Mms-MMS-Version M MMS version number. (now, 1.0)
X-Mms-Report-Allowed O Sending of delivery report allowed or not.
4.11 MMS PDUs – Delivery Reporting
MMS Overview
MMS Architecture Client Transaction
Encapsulation Protocol
Encapsulation Protocol
MMSM(MM1)
M-Delivery.ind
Field Name Presence Field Description
X-Mms-Message-Type M Transaction type: (M-Send.conf)
X-Mms-Transaction-ID M Identifier in corresponding M-Send.req.
X-Mms-MMS-Version M MMS version number.
X-Mms-Response-Status M MMS specific status.
X-Mms-Response-Text O Text description of the response status.
Message-ID O(M) Unique reference for the message in MMSC.
Mandatory when the message is accepted.
Originating UE
MMS Proxy Relay A
4.12 MMS PDUs – Forwarding
MMS Overview
MMS Architecture Client Transaction
Encapsulation Protocol
Encapsulation Protocol
MMSM(MM1)
M-Delivery.ind
Originating UE
MMS Proxy Relay A
4.13 MMS PDUs – Read Report
MMS Overview
MMS Architecture Client Transaction
Encapsulation Protocol
Encapsulation Protocol
MMSM(MM1)
M-Delivery.ind
Originating UE
MMS Proxy Relay A