| Clarification on TID and Msgid |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through October 29, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Murali Mohan.K |
Hi, I need clarification on these two issues... 1. I was looking at the WAP-MMS Encapsulation.pdf where there is some info which i could not understand properly. When a MMS Notification is sent to MMS client, a tid is generated by MMSC which will be used for a transaction. The spec says as follows, "The transaction identifier is created by MMS-Proxy-Relay and it is unique up to the following M-NotifyResp-ind only. If the MMS Client requests deferred delivery with M-NotifyResp-ind, the MMS Proxy MAY create new transaction identifier". So in case of a deferred delievery, how the MMS client will identify that the message it has downloaded is for a perticular notification, since the proxy might have generated a new tid??. 2. Why do we need two different identifiers in MMS messages??. one is tid and the other id msgid as specified in WAP-MMS Encap spec. The msgid is used in case of a sender requests for delivery report. why can't MMSC use the tid of the sent message as the identifier in the delivery.ind message instead of creating a new identifier?? Plz clarify me on these two doubts... Thanx in advance | |||
| Bryce Norwood - NowSMS Support (Bryce) |
1.) The TID only applies to the notification transaction itself. It is strictly for matching up a m-notifyresp-ind with the m-notification-ind. The life of that TID ends on the notifyresp. 2.) Because the TID and the message id are two different things. TIDs are transaction identifiers, and they are used to identify a particular transaction, but the message id is for identifying the message itself. (I do agree that it would be easier if the message id was used through the entire sequence of transactions.) -bn | |||
