|
3G/UMTS |
||
|
MMS
MMS is a method of communication by which you can exchange the non-text / multi-media contents. MMS can be implemented in various access technologies as follows.
But core protocol sequence is basically same as shown in the examples in this page.
Case 1 : MT MMS - No Delivery Report, No Read Report
: This example is the case where MT MMS is performed with a UE Test Equipment (Anritsu MD8475 + NowSMS) 01) < In Idle Mode or In Connected Mode > 02) < Send a MMS (from Network) to Test UE > 03) < Various Protocol Sequence depending on Situation > 04) UE <- NW : downlinkDirectTransfer + SMS : CP-DATA 05) UE -> NW : uplinkDirectTransfer + SMS : CP-ACK 06) UE -> NW : uplinkDirectTransfer + SMS : CP-DATA 07) UE <- NW : downlinkDirectTransfer + SMS : CP-ACK 08) < You will see SMS(MMS Delivery Notification) on UE display > 09) < Open the SMS and Retrieve MMS Contents > 10) < Various Protocol Sequence to establish the connected that is required to download the contents >
Note : In this example, it is assumed that MMS Notification is done in single SMS. However, there are cases that the notification message is conveyed in multiple SMS (Concatenated SMS)
< 04) UE <- NW : downlinkDirectTransfer + SMS : CP-DATA >
downlinkDirectTransfer: r3 (0) r3 downlinkDirectTransfer-r3 rrc-TransactionIdentifier: 0 cn-DomainIdentity: cs-domain (0) nas-Message: 0901a601000481999999009d440a81214365870900f54150... GSM A-I/F DTAP - CP-DATA Protocol Discriminator: SMS messages .... 1001 = Protocol discriminator: SMS messages (0x09) 0... .... = TI flag: allocated by sender .000 .... = TIO: 0 DTAP Short Message Service Message Type: CP-DATA (0x01) CP-User Data Length: 166 RPDU (not displayed) GSM A-I/F RP - RP-DATA (Network to MS) Message Type RP-DATA (Network to MS) RP-Message Reference RP-Message Reference: 0x00 (0) RP-Originator Address - (999999) Length: 4 1... .... = Extension: No Extension .000 .... = Type of number: unknown (0x00) .... 0001 = Numbering plan identification: ISDN/Telephony Numbering (ITU-T Rec. E.164 / ITU-T Rec. E.163) (0x01) BCD Digits: 999999 RP-Destination Address Length: 0 RP-User Data Length: 157 TPDU (not displayed) GSM SMS TPDU (GSM 03.40) SMS-DELIVER 0... .... = TP-RP: TP Reply Path parameter is not set in this SMS SUBMIT/DELIVER .1.. .... = TP-UDHI: The beginning of the TP UD field contains a Header in addition to the short message ..0. .... = TP-SRI: A status report shall not be returned to the SME .... .1.. = TP-MMS: No more messages are waiting for the MS in this SC .... ..00 = TP-MTI: SMS-DELIVER (0) TP-Originating-Address - (1234567890) Length: 10 address digits 1... .... : No extension .000 .... : Type of number: (0) Unknown .... 0001 : Numbering plan: (1) ISDN/telephone (E.164/E.163) TP-OA Digits: 1234567890 TP-PID: 0 00.. .... : defines formatting for subsequent bits ..0. .... : no telematic interworking, but SME-to-SME protocol ...0 0000 : the SM-AL protocol being used between the SME and the MS (0) TP-DCS: 245 1111 .... = Coding Group Bits: Data coding/message class (15) 1111 .... : Data coding/message class .... 0... : Reserved .... .1.. : Message coding: 8 bit data .... ..01 : Message Class: Class 1 Default meaning: ME-specific TP-Service-Centre-Time-Stamp Year 14, Month 05, Day 28 Hour 23, Minutes 23, Seconds 39 Timezone: GMT + 5 hours 0 minutes TP-User-Data-Length: (139) depends on Data-Coding-Scheme TP-User-Data User-Data Header User Data Header Length (6) IE: Application port addressing scheme, 16 bit address (SMS Control) Information Element Identifier: 0x05 Length: 4 Destination port: 2948, As allocated by IANA (http://www.IANA.com/) Originator port: 9200, As allocated by IANA (http://www.IANA.com/) Wireless Session Protocol, Method: Push (0x06), Content-Type: application/vnd.wap.mms-message Transaction ID: 0xcd PDU Type: Push (0x06) Headers Length: 34 Content-Type: application/vnd.wap.mms-message Headers X-Wap-Application-Id: x-wap-application:mms.ua MMS Message Encapsulation, Type: m-notification-ind X-Mms-Message-Type: m-notification-ind (0x82) X-Mms-Transaction-ID: 5386A6D4 X-Mms-MMS-Version: 1.0 From: 2580 Subject: MT MMS X-Mms-Message-Class: Personal (0x80) X-Mms-Message-Size: 780946 X-Mms-Expiry: 604800.000000000 seconds X-Mms-Content-Location: http://192.168.1.2:7082/20140528/23/5386A6D3a.MMS
DL-DCCH (Hex) : 8D 6E 3C 4B 81 40 15 01 20 34 C0 20 00 90 33 33 33 20 13 A8 81 50 24 28 6C B0 E1 20 1E A8 2A 10 46 46 52 60 51 60 C0 A0 81 70 84 7E 19 A0 C4 4C 2E 0E 0D 8D 2C 6C 2E 8D 2D ED C5 EE CD CC 85 CE EC 2E 05 CD AD AE 65 AD AC AE 6E 6C 2C EC A0 15 F0 91 90 53 06 A6 67 06 C8 26 C8 86 80 11 B2 11 20 D0 06 46 A7 06 00 12 C9 AA 84 09 A9 AA 60 11 50 11 C0 61 7D 52 51 00B0 20 61 27 50 10 6D 0E 8E 8E 07 45 E5 E6 27 26 45 C6 26 C7 05 C6 25 C6 47 46 E6 07 06 45 E6 46 06 26 86 06 A6 47 05 E6 46 65 E6 A6 67 06 C8 26 C8 86 6C 25 C9 A9 AA 60 00
< 05) UE -> NW : uplinkDirectTransfer + SMS : CP-ACK >
uplinkDirectTransfer cn-DomainIdentity: cs-domain (0) nas-Message: 8904 GSM A-I/F DTAP - CP-ACK Protocol Discriminator: SMS messages .... 1001 = Protocol discriminator: SMS messages (0x09) 1... .... = TI flag: allocated by receiver .000 .... = TIO: 0 DTAP Short Message Service Message Type: CP-ACK (0x04) UL-DCCH : E6 B5 20 99 8E C0 00 C4 82 00
< 06) UE -> NW : uplinkDirectTransfer + SMS : CP-DATA >
uplinkDirectTransfer cn-DomainIdentity: cs-domain (0) nas-Message: 8901020200 GSM A-I/F DTAP - CP-DATA Protocol Discriminator: SMS messages .... 1001 = Protocol discriminator: SMS messages (0x09) 1... .... = TI flag: allocated by receiver .000 .... = TIO: 0 DTAP Short Message Service Message Type: CP-DATA (0x01) CP-User Data Length: 2 RPDU (not displayed) GSM A-I/F RP - RP-ACK (MS to Network) Message Type RP-ACK (MS to Network) RP-Message Reference RP-Message Reference: 0x00 (0) UL-DCCH : BE B2 EA 4F 96 C0 02 44 80 81 01 00 00
< 07) UE <- NW : downlinkDirectTransfer + SMS : CP-ACK >
downlinkDirectTransfer: r3 (0) r3 downlinkDirectTransfer-r3 rrc-TransactionIdentifier: 0 cn-DomainIdentity: cs-domain (0) nas-Message: 0904 GSM A-I/F DTAP - CP-ACK Protocol Discriminator: SMS messages .... 1001 = Protocol discriminator: SMS messages (0x09) 0... .... = TI flag: allocated by sender .000 .... = TIO: 0 DTAP Short Message Service Message Type: CP-ACK (0x04) DL-DCCH :BA 21 1E 44 89 40 00 21 20 80
< 08) < You will see SMS(MMS Delivery Notification) on UE display > >
Following is the SMS (MMS Delivery Message) shown on SamSung Galaxy 4 as an example.
< 09) < Open the SMS and Retrieve MMS Contents > > < 10) < Various Protocol Sequence to establish the connected that is required to download the contents > > < 11) < Downloading Contents > >
TCP : From UE to MMS Center GET /20140528/23/5386A6D3a.MMS HTTP/1.1??Accept: */*, application/vnd.wap.mms-message, application/vnd.wap.sic??x-wap-profile: http://wap.samsungmobile.com/uaprof/SHV-E330S.xml??Accept-Language: ko-KR, en-US??Host: 192.168.1.2:7082??Connection: Keep-Alive??User-Agent: Android-Mms/2.0????
TCP : From UE to MMS Center HTTP/1.0 200 OK??Content-Length: 780946??Content-Type: application/vnd.wap.mms-message??Connection: close ??????????S??{?MT MMS????2580???????????? ???"<5386A6D2.txt>??5386A6D2.txt?MT MMS Testing??????"<Koala.jpg>
TCP : From MMS Center to UE A lot of Binary Data of the MMS Contents Following is the SMS (MMS Delivery Message) shown on SamSung Galaxy 4 as an example to show MMS Contents downloading process.
Case 2 : MO MMS - No Delivery Report, No Read Report
: This example is the case where MO MMS is performed with a UE Test Equipment (Anritsu MD8475 + NowSMS) 01) < In Idle Mode or In Connected Mode > 02) < Send a MMS (from UE) to Test Equipment > 03) < UE send MMS message through IP data > // Therefore you would not see any Radio Signaling Message here
|
||
