| MMS Notification PDU as SMS |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through October 29, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Murali Mohan.K |
Hi, I would like to know how a MMS Notification PDU arrives to the phone over SMS. I have the following assumptions abt the MMS over WAP environment. Let me know if I am right. MMS Notification arrives as a WAP-Push msg over SMS bearer. Which means the phone will have to identify a WAP-Push msg and redirect the msg to the MMS Client running on the phone (instead of displaying the SMS content on the UI). If the MMS notification is longer than 160 chars (octets), it will be segmented into 2 SMSs while sending and the receiving SMS application will have to concatenate these SMSs and pass the resultant byte stream to the application. If the above argument is right and there is a WAP Browser running on the phone along with an MMS Client, I wonder to which application the notifcation is passed by the SMS Application, since both can accept a WAP-Push message. Can anyone plz let me know how things work in the above scenario?? Thanx in advance... Awaiting ur response.. | |||
| Bryce Norwood - NowSMS Support (Bryce) |
Hi, Your assumptions are basically correct. How the message gets routed on the phone is an implementation decision for the developer of the client software on the phone. Some might take shortcuts, but how it should work is that there is a WAP push receiver on the phone. This WAP push receiver decides how to handle the message based on the content-type of the push message and/or the "X-Wap-Application-Id:" header of the message. Most WAP push messages are of the "application/vnd.wap.sic" format, which is for service indications. There is another format, "application/vnd.wap.slc", or service load, which is also defined for WAP (theoretically this type of push invokes the browser directly without prompting the user, but needless to say this capability makes operators nervous). The content type for an MMS notification message is "application/vnd.wap.mms-message". So a WAP push receiver would evaluate the content type of the push, and would know to pass the "application/vnd.wap.mms-message" type to the MMS client. Technically, the "X-Wap-Application-Id:" header is what should be used in the push to specify which application should receive the push, but I've noticed quite a few MMS phones that don't need this header and route to the MMS client based upon the content type of the push. "x-wap-application:mms.ua" is the "X-Wap-Application-Id:" value for the MMS client. -bn | |||
| muralimohank |
hi, | |||
| Murali Mohan.K |
Hi Bryce, Thanx for the response. I got a notification message from Nokia forum and I have attached it below. I am able to identify notification pdu in that, but where can I find the info for the upper part of the PDU. PDU received as SMS is like this... 06 05 04 0B 84 23 F0 00 06 22 61 70 70 6C 69 63 61 74 69 6F 6E 2F 76 6E 64 2E 77 61 70 2E 6D 6D 73 2D 6D 65 73 73 61 67 65 00 AF 84 8C 82 98 61 00 8D 90 96 53 65 71 75 65 6C 20 53 6F 6C 75 74 69 6F 6E 73 00 8A 80 8E 01 1E 88 06 81 04 3D D9 D6 F3 83 68 74 74 70 3A 2F 2F 32 30 32 2E 31 37 35 2E 32 34 30 2E 31 32 32 2F 6D 6D 73 63 2F 67 77 73 3F 6D 65 73 73 61 67 65 69 64 3D 38 5F 38 00 I have segregated the above PDU as below.. Unknown headers =============== 06 05 04 0B 84 23 F0 00 06 22 61 70 70 6C 69 63 61 74 69 6F 6E 2F 76 6E 64 2E 77 61 70 2E 6D 6D 73 2D 6D 65 73 73 61 67 65 00 AF 84 Actual MMS notification message starts ====================================== 8C 82 98 61 00 8D 90 96 53 65 71 75 65 6C 20 53 6F 6C 75 74 69 6F 6E 73 00 8A 80 8E 01 1E 88 06 81 04 3D D9 D6 F3 83 68 74 74 70 3A 2F 2F 32 30 32 2E 31 37 35 2E 32 34 30 2E 31 32 32 2F 6D 6D 73 63 2F 67 77 73 3F 6D 65 73 73 61 67 65 69 64 3D 38 5F 38 00 If I write an SMS application which redirects the notification to my MMS client, I need to parse the "unknown headers" which I think is not defined in any WAP specs. Can youi just let me know where can I get the info for this. It would be great if you can point me to the right link. I think it should be some SMS spec which defines those "unknown headers", but I don't know which document. Expecting your response ASAP.. Murali | |||
| Bryce Norwood - NowSMS Support (Bryce) |
Murali, You need to look at the WAP WDP and WSP specifications. An MMS Notification is encapsulated inside of a WAP push message. The WAP WDP specification talks about how the WAP protocol is implemented on top of different protocols, such as SMS. You're going to need to understand how User Data Headers (UDH) are used in SMS for WAP (similar to how they have been used for years with Nokia Smart Messaging). Then you'll need to refer to the WAP WSP specification which covers connection-less push, and you'd need to decode the WSP header before you move to the MMS Encapsulation data. Have fun! -bn | |||
| Anonymous |
06 05 04 0B 84 23 F0 this is user data header(udh) of binary sms 0B 84 : originating port 23 F0 : destination port(9200) 00 06 ... version info 22 61 70 70 6C 69 63 61 74 69 6F 6E 2F 76 6E 64 2E 77 61 70 2E 6D 6D 73 2D 6D 65 73 73 61 67 65 encoded mime type application/vnd.wap.mms-message 00 AF 84 : ??? also i do not know this. if anybody has solved all parts, i would appreciate any infos. email: amarjiran@yahoo.com thanks amar | |||
| ql |
AF 84 : X-Wap-Application-ID: 4 | |||
| Anonymous |
who will plain on Actual MMS notification message starts what does 8C 82 98 means | |||
| Anonymous |
8c82: X-MMS-Message-Type:m-notification-ind 98:X-MMS-Transaction-Id 83:X-MMS-Content-Location thanks, changejoy | |||
| Anonymous |
that's good | |||
| John |
Hi,bryce, I don't understand the following sentence, What's WAP push receiver ? how does it work? I must develop a program for it? thanks a lot. How the message gets routed on the phone is an implementation decision for the developer of the client software on the phone. | |||
| Anonymous |
it seems as a black box | |||
