How to distinguish MMS notifications and SMS?

            


MMS notification is received via SMS, the SMS PDU in the package, DCS representatives SMS encoding: 7bit, 8bit, UCS2 corresponding DCS is (hex) 00,04,08 In general, received. SMS is 7bit, UCS2 encoding. MMS notification is 8bit (usually transmit data information.) However, sometimes MMS notification is sent, UCS2 coding, I do not know if the network side or unstable Stack a problem My question is:.

1. how to distinguish received a notification of SMS or MMS.

2.MMS notification is not to be encoded in 8bit.

Thank you !!!

Reply:
Bangding
Reply:
PDU which has a bit to check. You can distinguish
Reply:
Sell mobile games. QQ: 779856263
Reply:
There pdu flag flag port number, you can use this logo
Reply:
mark
Reply:
Follow

Reply:
MMS notification has its own format, check OMA (WAPFORUM) agreement related part

Said MMS notification exact are binary data.
The first few bytes of the form
"06", "05", "04", "0B", "84", "23", "F0" ...
Of course, this data will be the same with WAPPush, and many other businesses are also reuse these WDP data. And if the packet striping become 2 to 3 text messages, it will become "0B", "05", "04" .... this way.

The best you can own in accordance with the specification resolve again, part of the WSP also verify
Find such as "06", "application / vnd.wap.mms-message", "00", "AF", "84" in the field

So basically guaranteed to be a mms notification.

Reply:
Spreadtrum I do not have a decent platform software documentation buddies who have MMS Documentation on give me a thank you
zyq1206@163.com
Thanks
Reply:
efm_gy Do you have OMA (WAPFORUM) protocol information? I want to know the user receives an SMS binary encoding, such as "06", "05", "04", "0B", "84", "23", "F0" ............ Thank you friends
Reply:
efm_gy Do you have OMA (WAPFORUM) protocol information? I want to know the user receives an SMS binary encoding, such as "06", "05", "04", "0B", "84", "23", "F0" ............ Thank you friends
My mailbox 13755002297@hnmcc.com Thank you.
Reply:
mark