MM4 interface

MM4 interface SearchSearch
Author Message
somya
Posted on Thursday, September 25, 2003 - 10:44 am:   

hi
why the information regarding reply charging is not forwarded in MM4_forward.REQ message in case of interworking?
This type of information should be known to the receiver MMSE.
somya
Posted on Thursday, September 25, 2003 - 10:56 am:   

why the X-mms is being added to the information element of MM4messages.Whats the life of these header and how these are being used?
Bryce Norwood - NowSMS Support
Posted on Saturday, October 11, 2003 - 09:47 pm:   


quote:

why the information regarding reply charging is not forwarded in MM4_forward.REQ message in case of interworking?
This type of information should be known to the receiver MMSE.




Good question. I wonder if this is an oversight. Perhaps additional MM4 headers will be defined in future verisons of the 3GPP MMS specifications.

I suspect that the reason why this is not defined is because of the complex billing requirements that would be involved. As I think about the potential scenarios that could occur here, I think I understand why these headers were not included in the MM4 definitions.


quote:

why the X-mms is being added to the information element of MM4messages.Whats the life of these header and how these are being used?




MM4 is used to interconnect MMSCs. These headers are used to encapsulate MMS related information as it is routed over the SMTP protocol between MMSCs.

The MMSC receiving the MM4 request would convert the message out of MM4 format in order to deliver the message.

Maybe you can clarify your question?
somya
Posted on Monday, October 13, 2003 - 09:05 am:   

Hi !
thanks for ur prvious Answers.
Regarding the X-mms header, i m not clear that why this type of conversion is done for elemnts of MM4 messages.Why dont we send all elemnets of MM4 messages as it is in DATA command of SMTP?
Bryce Norwood - NowSMS Support
Posted on Monday, October 13, 2003 - 06:37 pm:   

Because the MM4 message might need to be relayed through existing SMTP servers.

Therefore it needs to conform to the message formats of SMTP.

It would have been possible to define a new MIME content type (or use a generic XML type with its own schema like MM7), where the first part of the multipart SMTP message content would contain the MMS headers. But the team that defined the MM4 standard apparently wanted to keep the message format simple and opted to map MMS headers into the SMTP message header instead.

I suspect that they made this decision so that the MM4 interface would be interoperable with more external SMTP servers.