WAP Gateway support required for MMS support

WAP Gateway support required for MMS support SearchSearch

SMS & MMS Technical Forum » NowSMS Support - MMS & Advanced Issues (Product Support Only) » Archive through July 14, 2004 » WAP Gateway support required for MMS support « Previous || Next »
Author Message
warren faleiro
Unregistered guest
Posted on Friday, March 05, 2004 - 10:45 pm:   

I am a little confused about WAP and MMS dependencies.
1) What version of WAP is a WAP Gateway required to support to transport WAP encoded MM1 PDU's orginating from the handsets?
2) What version of WAP is a WAP Gateway required to support in order to be able to act as a PPG for delivery of MM1 notifications (MMSC sends PAP to PPG)?
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2030
Registered: 10-2002
Posted on Tuesday, March 09, 2004 - 07:05 pm:   


quote:

1) What version of WAP is a WAP Gateway required to support to transport WAP encoded MM1 PDU's orginating from the handsets?




The WAP gateway needs to support SAR (segmentation and re-assembly). This is not a WAP version dependency issue. SAR was defined beginning with WAP v1.1. However, SAR continues to be defined as "optional" in the WAP WTP specification.

In practice, if you're talking about interoperating with various MMS clients, SAR is required ... despite what the specifications may say.


quote:

2) What version of WAP is a WAP Gateway required to support in order to be able to act as a PPG for delivery of MM1 notifications (MMSC sends PAP to PPG)?




This is also not a version issue.

An MMSC does not need to interface with a separate PPG. For example, the MMSC that is built into the NowSMS gateway performs WAP push operations directly in a GSM/GPRS SMS environment.

However, the NowSMS MMSC does also have an option to connect to a separate WAP Push Proxy Gateway (http://www.nowsms.com/support/bulletins/tb-nowsms-007.htm).

Push primitives were defined as part of the WAP 1.1 specifications, I believe. However, the higher level push operations were defined beginning with WAP 1.2.

However, none of this is really a version issue. Push Proxies are often completely separate from the WAP gateway that is being used. There is no requirement that a push message must be sent through the same gateway that a handset is configured for regular WAP access.

Does that help answer your questions? Feel free to reply for more clarification ...
warren faleiro
Unregistered guest
Posted on Monday, March 15, 2004 - 01:30 am:   

Yes - this is useful. I was under the impression that WAP 1.2.1 support was required for MMS transport as that is something I read in a Nokia WAP gateway document. I am using the NowSMS to send out m-notification-ind messages from our MMSC in a test setting (using a GSM phone and SIM).

I setting up access to our MMSC via a network operator WAP gateway. Do the following GPRS connection settings have any impact on submitting MMS messages from the handset :
1) connection type - temporary vs permanent
2) Authentication type -secure vs non-secure
3) Login type -
I think that these only affect the connection from the handset to the WAP gateway and not the session to the MMSC that is carried on top. Is that correct?
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2110
Registered: 10-2002
Posted on Monday, March 15, 2004 - 07:39 pm:   

Hi Warren,

Nokia WAP gateway documents are often written from a perspective of their product implementation. So I would suspect that their WAP gateway version that added support for WAP 1.2.1 was their first version that implemented SAR as a standard feature.

To answer your questions:


quote:

Do the following GPRS connection settings have any impact on submitting MMS messages from the handset :
1) connection type - temporary vs permanent
2) Authentication type -secure vs non-secure
3) Login type -
I think that these only affect the connection from the handset to the WAP gateway and not the session to the MMSC that is carried on top. Is that correct?




These settings do only affect the connection from the handset to the WAP gateway. HOWEVER, they can have an impact on whether or not the connection can be routed from handset->WAP GW->MMSC.

Connection type should ALWAYS be set to permanent.

This permanent vs. temporary terminlogy is Nokia specific. Temporary means that the WAP connection-less protocol is used, and this protocol does not support SAR. Nokia handsets generally get confused if an MMS profile is configured for this "temporary" setting.

On other handsets, this setting will be shown as "Connection oriented" vs. "connection-less". Again, always configure for "connection-oriented".

And on yet some other handsets, they prompt for a port number. Use 9201, which is the standard "connection-oriented" port.

"Authentication type" and "Login type" settings are for specifying how the device logs on when connecting to the GPRS APN (if required). If those settings are incorrect, you generally will not get a GPRS connection.

-bn

Login Login / Register Logout Logout Search Last 30 Days Topics Topics