This is a presentation I prepared for a lecture on mobile messaging. It covers MMS (Multimedia Messaging Service) - Architecture and Transactions.

1. MMS Architecture and Transaction Flows Mobile Messaging G. Le Bodic PART 5

2. Course Contents Part 8 Instant Messaging and IMS Messaging Part 7 Mobile Email Day 2 Day 1 Part 6 MMS: Design of multimedia content and application development Part 5 MMS: Architecture and Transaction Flows Part 4 Short Message Service Part 3 Messaging Services in Europe and elsewhere Part 2 Standardization Part 1 Introduction to mobile communications networks

4. MMS architecture

13. WAP 1.x realisation of MMS

14. Content adaptation

17. Content adaptation: UAProf (2/3)

18. Content adaptation: UAProf (3/3) http://www.sonyericsson.com/UAProf/T610R301.xml

19. Streaming

28. MM1: protocol data units MMbox message deletion confirmation M-Mbox-Delete.conf 1.2 MMbox message deletion request M-Mbox-Delete.req Message deletion from MMbox MMbox message upload confirmation M-Mbox-Upload.conf 1.2 MMbox message upload request M-Mbox-Upload.req Message upload to MMbox MMbox contents view confirmation M-Mbox-View.conf 1.2 MMbox contents view request M-Mbox-View.req View contents of MMbox MMbox message store/update confirmation M-Mbox-Store.conf 1.2 MMbox message store/update request M-Mbox-Store.req Message store or update into MMbox Message forward confirmation M-forward.conf 1.1 Message forward request M-forward.req Message forward Read report indication (originator MMSE) M-read-orig.ind 1.1 Read report indication (recipient MMSE) M-read-rec.ind Read report 1.0 Delivery report indication M-delivery.ind Delivery report 1.0 Message retrieval acknowledgement indication M-acknowledge.ind Message retrieval confirmation M-retrieve.conf 1.0 Message retrieval request WSP/HTTP GET.req Message retrieval Message notification response indication M-notifyresp.ind 1.0 Message notification indication M-notification.ind Notification Message submission confirmation M-send.conf 1.0 Message submission request M-send.req Message submission From OMA Description PDU name Transaction

30. MM1: submission request (1/2) O 1.0 Request for a delivery report. This parameter indicates whether or not delivery report(s) are to be generated for the submitted message. Two values can be assigned to this parameter: 'yes' (delivery report is to be generated) or 'no' (no delivery report requested). If the message class is 'auto', then this parameter is present in the submission PDU and is set to 'no'. X-Mms-Delivery-Report O 1.0 Visibility of the sender address. This parameter is either set to 'show' (default) for showing the sender address to recipient(s) or 'hide' for hiding the sender address to recipient(s). From MMS 1.2, 'show' is not anymore the default value for this parameter. If this parameter is not present in an MMS 1.2 PDU, then network preferences for the sender anonymity feature are used. X-Mms-Sender-Visibility O 1.0 Priority such as 'low', 'normal' (default) or 'high'. X-Mms-Priority O 1.0 Earliest delivery time. Default value for this parameter is 'immediate delivery'. X-Mms-Delivery-Time O 1.0 Expiry date. Default value for this parameter is 'maximum'. X-Mms-Expiry O 1.0 Message class such as 'auto' (automatically generated by the MMS client), 'personal' (default), 'advertisement' and 'informational'. Other classes can also be defined in the form of text strings. X-Mms-Message-Class O 1.0 A short textual description for the message. Subject O 1.0 One or multiple addresses (phone number or email address) for message recipient(s). Secondary recipients / blind copy. Bcc O 1.0 One or multiple addresses (phone number or email address) for message recipient(s). Secondary recipients. Cc O 1.0 One or multiple addresses (phone number or email address) for message recipient(s). Primary recipients. To  1.0 Address of the originator MMS client (phone number or email address) or 'insert token' if the originator address is to be provided by the MMSC. From O 1.0 Date and time of message submission. Date  1.0 MMS protocol version such as 1.0, 1.1 or 1.2. X-Mms-MMS-Version  1.0 Unique identifier for the submission transaction. X-Mms-Transaction-ID  1.0 MMS protocol data unit type. Value: M-send-req X-Mms-Message-Type St. From OMA Description Parameter name

31. MM1: submission request (2/2)  1.0 Content type of the multimedia message. (e.g. application/vnd.wap.multipart.related ). Content-Type  1.2 MMBox message flag – This parameter indicates the list of flags associated to a message stored in the MMBox (considered only if X-Mms-Store is set to 'yes'). X-Mms-MM-Flags  1.2 MMBox message state – When X-Mms-Store is set to 'yes', this parameter indicates the message state in the originator's MMBox (e.g. sent, draft, etc.). If X-Mms-Store is set to 'yes' and if this parameter is not present then the message default state is 'sent'. X-Mms-MM-State  1.2 MMBox storage request - This parameter indicates whether the originator MMS client requests to save the message in the originator's MMBox in addition from sending it. X-Mms-Store  1.1 Reply charging – identification. This parameter is inserted in a reply message only and refers to the original message identifier ( Message-ID parameter). X-Mms-Reply-Charging-ID  1.1 Reply charging – maximum message size. This parameter specifies the maximum size for message replies. This parameter is only present in the PDU if reply charging is requested. X-Mms-Reply-Charging-Size  1.1 Reply charging – deadline. This parameter specifies the latest time for the recipient(s) to submit a message reply. This parameter is only present in the PDU if reply charging is requested. X-Mms-Reply-Charging-Deadline  1.1 Request for reply charging. The presence of this parameter indicates that reply charging is requested by the message originator. Two values can be assigned to this parameter: 'requested' when the originator is willing to pay for the message reply(s) or 'requested text only' when the originator is willing to pay for message reply(s) containing text only. In any case, two parameters (reply message size and reply deadline) specify conditions for the message reply to be paid for by the originator. X-Mms-Reply-Charging  1.0 Request for a read report. This parameter indicates whether or not read reports are to be generated for the message. Two values can be assigned to this parameter: 'yes' (read report is to be generated) or 'no' (no read report requested). If the message class is auto, then this parameter is present in the submission PDU and is set to 'no'. X-Mms-Read-Report

32. MM1: submission response  1.2 MMBox message textual status - Textual description qualifying the value assigned to the X-Mms-Store-Status parameter. X-Mms-Store-Status-Text  1.2 MMBox message status - This parameter is present only if the two following conditions are fulfilled: - the originator MMSC supports the MMBox feature - the X-Mms-Store parameter was present in the corresponding submission request When available, this parameter indicates whether or not the submitted message has been successfully stored in the MMBox. See status codes in Appendix D. X-Mms-Store-Status  1.2 Reference to the message stored in the MMBox - This parameter is present only if the three following conditions are fulfilled: - the originator MMSC supports the MMBox feature - the X-Mms-Store parameter was present in the corresponding submission request - the X-Mms-Store-Status indicates 'success' When available, this parameter provides a reference to the message stored in the MMBox (reference used later for message retrieval or view request). X-Mms-Content-Location  1.0 Message unique identifier. This identifier is always provided by the MMSC if the submission request is accepted. Message-ID  1.0 Human readable description of the transaction status. X-Mms-Response-Text  1.0 Status code for the submission transaction. The submission request can be accepted or rejected (permanent or transient errors). See status codes in Appendix B. X-Mms-Response-Status  1.0 MMS protocol version such as 1.0, 1.1 or 1.2. X-Mms-MMS-Version  1.0 Unique identifier for the submission transaction. The same as the one for the corresponding submission request. X-Mms-Transaction-ID  1.0 MMS protocol data unit type. Value: M-send-conf X-Mms-Message-Type St. From OMA Description Parameter name

52. MM4: example

58. MM7: Introduction to SOAP

59. MM7: graphical convention

60. MM7: submission Transaction flow Response Request

61. MM7: submission, example Request

62. MM7: submission, example Response

63. MM7: delivery Transaction flow Response Request

64. MM7: cancel Transaction flow Response Request

65. MM7: replace Transaction flow Response Request

66. MM7: delivery report Transaction flow Response Request

67. MM7: read report Transaction flow Response Request

68. MM7: generic error handling Transaction flows Response