The document discusses the architecture and format of Multimedia Messaging Services (MMS). It describes the MMS architecture, including the client transaction model and encapsulation protocol. It also outlines the various MMS protocol data units (PDUs) used for sending, retrieving, notifying, reporting, acknowledging, forwarding, and read reporting of MMS messages.

1. MMS Introduction Architecture & Format Monky Chen Feb xx 2005

2. Outline 1. MMS Overview 2. MMS Architecture 3. MMS Client Transaction MMS transaction model 4. MMS Encapsulation Protocol MM Message format 5. Discussion

3. 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 Architecture Client Transaction Encapsulation Protocol

4. 1.2 Comparison of MMS & SMS MMS Architecture Client Transaction Encapsulation Protocol MMS Overview

5. 2.1 MMS Architecture MMS Overview MMS Architecture Client Transaction Encapsulation Protocol

6. 2.2 MMS Overview MMS Architecture Client Transaction Encapsulation Protocol

7. 3.1 MMS Overview MMS Architecture Client Transaction Encapsulation Protocol

8. 3.2 Transaction Model MMS Overview MMS Architecture Client Transaction Encapsulation Protocol

9. 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

10. 4.2 MM Message Structure Overview MMS Overview MMS Architecture Client Transaction Encapsulation Protocol MMS Header Message Body presentation image/jpeg text/plain audio/wav Start PDU = MMS Header + Message body

11. 4.3 MMS PDUs MMS Overview MMS Architecture Client Transaction 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

12. 4.4 MMS PDUs – Send (1) MMS Overview MMS Architecture Client Transaction Encapsulation Protocol M-Send.req M-Send.conf MMS M (MM1) Origination UE MMS Proxy Relay A MIME-encoded multimedia message. M Message-Body MIME type of the message content. M Content-Type Request of read report. (“Yes”/“No”) O X-Mms-Read-Reply Request of delivery report. (“Yes”/“No”) O X-Mms-Delivery-Report Hide the sender’s address. (“Hide”/”Show”) O X-Mms-Sender-Visibility Priority of the message. O X-Mms-Priority Time of desired delivery. Validity period of the message in MMSC. Class of the message. (“Auto”/”Personal”) Subject of the message. Address of the recipient(s). Address of the recipient(s). Address of the recipient(s). Address of the sender. Arrival time of the message at MMSC. MMS version number. (now, 1.0) Unique identifier for the transaction. Specifies the PDU type: ( M-Send.req ) Field Description O O O O O (M) O (M) O (M) M O M M M Presence X-Mms-Delivery-Time X-Mms-Expiry X-Mms-Message-Class Subject Bcc Cc To From Date X-Mms-MMS-Version X-Mms-Transaction-ID X-Mms-Message-Type Field Name

13. 4.5 MMS PDUs – Send (2) MMS Overview MMS Architecture Client Transaction Encapsulation Protocol MMS M (MM1) M-Send.req M-Send.conf Originating UE MMS Proxy Relay A Unique reference for the message in MMSC. Mandatory when the message is accepted. O(M) Message-ID Text description of the response status. MMS specific status. MMS version number. Identifier in corresponding M-Send.req. Transaction type: ( M-Send.conf ) Field Description O M M M M Presence X-Mms-Response-Text X-Mms-Response-Status X-Mms-MMS-Version X-Mms-Transaction-ID X-Mms-Message-Type Field Name

14. 4.6 MMS PDUs – Notification (1) MMS Overview MMS Architecture Client Transaction Encapsulation Protocol MMS M (MM1) Receiving UE MMS Proxy Relay B M-Notification.ind M-NotifyResp.ind Location of the message. (URI) M X-Mms-Content-Location Validity period of the message in MMSC. Size of the message. (in octets) Class of the message. Subject of the message. Address of the sender. MMS version number. Unique identifier for the transaction. Transaction type: ( M-Notification.ind ) Description M M M O O M M M Presence X-Mms-Expiry X-Mms-Message-Size X-Mms-Message-Class Subject From X-Mms-MMS-Version X-Mms-Transaction-ID X-Mms-Message-Type Field Name

15. 4.7 MMS PDUs –Notification (2) MMS Overview MMS Architecture Client Transaction Encapsulation Protocol MMS M (MM1) Receiving UE MMS Proxy Relay B M-Notification.ind M-NotifyResp.ind Sending of delivery report allowed or not. Message status. MMS version number. Unique identifier for the transaction. Transaction type: ( M-NotifyResp.ind ) Comments O M M M M M/O X-Mms-Report-Allowed X-Mms-Status X-Mms-MMS-Version X-Mms-Transaction-ID X-Mms-Message-Type Name

16. 4.8 MMS PDUs –Retrieve (1) MMS Overview MMS Architecture Client Transaction Encapsulation Protocol MMS M (MM1) Receiving UE MMS Proxy Relay B M-Retrieve.conf M-Acknowledge.ind WSP/HTTP GET.req Headers related with the GET request Location of the message. Length of URI PDU type = “ Get ” (WAP-WSP 8.2.3.1) Transaction Id Comments Headers URI URILen Type TID Name

17. 4.9 MMS PDUs –Retrieve (2) MMS Overview MMS Architecture Client Transaction Encapsulation Protocol MMS M (MM1) Receiving UE MMS Proxy Relay B M-Retrieve.conf M-Acknowledge.ind WSP/HTTP GET.req Sending date and time. M Date Message class. O X-Mms-Message-Class MIME-encoded multimedia message. M Message-Body MIME type of the message content. M Content-Type Read report is requested or not. O X-Mms-Read-Reply Delivery report is requested or not. O X-Mms-Delivery-Report Priority of the message. O X-Mms-Priority Message subject. Address of the recipient. Address of the recipient. Address of the sender. Unique reference of the message. MMS version number. (now, 1.0) Mandatory when immediate retrieval. Transaction type: ( M-Retrieve.conf ) Comments O O O O O M M(O) M M/O Subject Cc To From Message-ID X-Mms-MMS-Version X-Mms-Transaction-ID X-Mms-Message-Type Name

18. 4.10 MMS PDUs – Acknowledgement MMS Overview MMS Architecture Client Transaction Encapsulation Protocol MMS M (MM1) Receiving UE MMS Proxy Relay B M-Retrieve.conf M-Acknowledge.ind WSP/HTTP GET.req Sending of delivery report allowed or not. MMS version number. (now, 1.0) Unique identifier for the transaction. Transaction type: ( M-Acknowledge.ind ) Comments O M M M M/O X-Mms-Report-Allowed X-Mms-MMS-Version X-Mms-Transaction-ID X-Mms-Message-Type Name

19. 4.11 MMS PDUs – Delivery Reporting MMS Overview MMS Architecture Client Transaction Encapsulation Protocol MMS M (MM1) M-Delivery.ind Originating UE MMS Proxy Relay A Unique reference for the message in MMSC. Mandatory when the message is accepted. O(M) Message-ID Text description of the response status. MMS specific status. MMS version number. Identifier in corresponding M-Send.req. Transaction type: ( M-Send.conf ) Field Description O M M M M Presence X-Mms-Response-Text X-Mms-Response-Status X-Mms-MMS-Version X-Mms-Transaction-ID X-Mms-Message-Type Field Name

20. 4.12 MMS PDUs – Forwarding MMS Overview MMS Architecture Client Transaction Encapsulation Protocol MMS M (MM1) M-Delivery.ind Originating UE MMS Proxy Relay A

21. 4.13 MMS PDUs – Read Report MMS Overview MMS Architecture Client Transaction Encapsulation Protocol MMS M (MM1) M-Delivery.ind Originating UE MMS Proxy Relay A