MMS
http://www.openmobilealliance.org/ OMA-MMS-ENC-v1_1-20021030-C.
The WAP Multimedia Messaging Service (MMS) uses WAP WSP/HTTP as underlying protocols to transfer MMS PDUs between the MMS Client, which resides on the terminal (MS) and the MMS Proxy -Relay.
This structure is based on the well-known message structure of Internet email binary encoding of MMS PDUs. Because of the limited bandwidth of the air interface of mobile networks MMS PDUs are transferred between an MMS Client and an MMS Proxy -Relay in binary encoded message format. This process is called encapsulation. WSP PDUs or HTTP messages, which contain MMS PDUs as their body, are used for this transport.
MMS PDUs, which are described in this specification, are included in WSP PDUs/HTTP messages of different types. The entire MMS information is contained in MMS PDUs, which are encapsulated in WSP PDUs/HTTP messages.
The content type of WSP PDUs/HTTP messages containing MMS PDUs is "application/vnd.wap.mms - message."
MMS has no header structure as it consists of messages.
Field | Reference Number: |
0x81 | Bcc |
0x82 | Cc |
0x83 | X-Mms-Content-Location |
0x84 | Content-Type |
0x85 | Date |
0x86 | X-Mms-Delivery-Report |
0x87 | X-Mms-Delivery-Time |
0x88 | X-Mms-Expiry |
0x89 | From |
0x8A | X-mms-Message-Class |
0x8B | Message-ID |
0x8C | X-Mms-Message-Type |
0x8D | X-Mms-MMS-Version |
0x8E | X-Mms-Message-Size |
0x8F | X-Mms-Priority |
0x90 | X-Mms-Read-Report |
0x91 | X-Mms-Report-Allowed |
0x92 | X-Mms-Response-Status |
0x93 | X-Mms-Response-Text |
0x94 | X-Mms-Sender-Visibility |
0x95 | X-Mms-Status |
0x96 | Subject |
0x97 | To |
0x98 | X-Mms-Transaction-Id |
0x99 | X-Mms-Retrieve-Status |
0x9A | X-Mms-Retrieve-Text |
0x9B | X-Mms-Read-Status |
0x9C | X-Mms-Reply-Charging |
0x9D | X-Mms-Reply-Charging-Deadline |
0x9E | X-Mms-Reply-Charging-ID |
0x9F | X-Mms-Reply-Charging-Size |
0xA0 | X-Mms-Previously-Sent-By |
0xA1 | X-Mms-Previously-Sent-Date |
Read more about this topic: Cellular Data Communication Protocol