Wap push VS MMS

Wap push VS MMS SearchSearch
Author Message
medium kuriboh
New member
Username: Mediumkuriboh

Post Number: 9
Registered: 04-2008
Posted on Sunday, January 25, 2009 - 04:20 am:   

I am newbie, i wish to know what is the difference between the 2, if they are related...

Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 389
Registered: 08-2008
Posted on Monday, January 26, 2009 - 09:31 pm:   


Well, it depends on how much you want to know (and how much you need to know).

WAP Push is a protocol for pushing content to mobile devices.

From an end-user perspective, when you talk about WAP Push, you are mostly talking about "service indication" alerts, which are the most common type of WAP push. These "service indication" alerts can only contain some text and a URL link.

The WAP Push protocol can support other types of content and alerts. The two other most commonly implemented content types are configuration settings (also known as "OTA" or "Over The Air" settings, and also known as OMA Provisioning Content) and MMS.

For more information on how MMS works, see http://www.nowsms.com/howmmsworks.htm.

Note ... however, that that link talks more about the actual over the air implementation of MMS.

I see in another posting that you are asking about making an MM7 connection to your mobile operator. MM7 hides all of that actual over the air implmentation of MMS from you ... and learning more about how MMS actually works might not get you any closer to actually doing what you want to do.

NowSMS Support
New member
Username: Xucaixing

Post Number: 1
Registered: 07-2009
Posted on Saturday, July 04, 2009 - 03:17 pm:   

hi, Des
I want to make a mini project to send a MM from PC to the destinate Mobile. Is that means my opinion is impossible as you above mention?
thank you!
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 993
Registered: 08-2008
Posted on Sunday, July 05, 2009 - 07:27 pm:   


If you want to send MMS from a PC to a mobile then you need to have a GSM modem (GPRS, EDGE, 3G, etc.) connected to the PC.

I copied the following text from one of our manuals which provides some information about what a GSM modem is:


A GSM modem is a specialized type of modem which accepts a SIM card, and operates over a subscription to a mobile operator, just like a mobile phone. From the mobile operator perspective, a GSM modem looks just like a mobile phone.

For the purpose of this document, the term GSM modem is used as a generic term to refer to any modem that supports one or more of the protocols in the GSM evolutionary family, including the 2.5G technologies GPRS and EDGE, as well as the 3G technologies WCDMA, UMTS, HSDPA and HSUPA.

A GSM modem exposes an interface that allows applications such as NowSMS to send and receive messages over the modem interface. The mobile operator charges for this message sending and receiving as if it was performed directly on a mobile phone. To perform these tasks, a GSM modem must support an “extended AT command set” for sending/receiving SMS messages, as defined in the ETSI GSM 07.05 and and 3GPP TS 27.005 specifications.

GSM modems can be a quick and efficient way to get started with SMS, because a special subscription to an SMS service provider is not required. In most parts of the world, GSM modems are a cost effective solution for receiving SMS messages, because the sender is paying for the message delivery.

A GSM modem can be a dedicated modem device with a serial, USB or Bluetooth connection, such as the Falcom Samba 75 used in this document. (Other manufacturers of dedicated GSM modem devices include Wavecom, Multitech and iTegno.) To begin, insert a GSM SIM card into the modem and connect it to an available USB port on your computer.

A GSM modem could also be a standard GSM mobile phone with the appropriate cable and software driver to connect to a serial port or USB port on your computer. Any phone that supports the “extended AT command set” for sending/receiving SMS messages, as defined in ETSI GSM 07.05 and/or 3GPP TS 27.005, can be supported by the Now SMS/MMS Gateway. Note that not all mobile phones support this modem interface.

Due to some compatibility issues that can exist with mobile phones, using a dedicated GSM modem is usually preferable to a GSM mobile phone. This is more of an issue with MMS messaging, where if you wish to be able to receive inbound MMS messages with the gateway, the modem interface on most GSM phones will only allow you to send MMS messages. This is because the mobile phone automatically processes received MMS message notifications without forwarding them via the modem interface.

It should also be noted that not all phones support the modem interface for sending and receiving SMS messages. In particular, most smart phones, including Blackberries, iPhone, and Windows Mobile devices, do not support this GSM modem interface for sending and receiving SMS messages at all at all. Additionally, Nokia phones that use the S60 (Series 60) interface, which is Symbian based, only support sending SMS and MMS messages via the modem interface, and do not support receiving SMS or MMS via the modem interface. Nokia phones based upon Series 40 3rd Edition or later have similar restrictions to the Series 60 devices, while older Series 40 1st and 2nd Edition phones do not have this restriction.

When you install your GSM modem, or connect your GSM mobile phone to the computer, be sure to install the appropriate Windows modem driver from the device manufacturer. To simplify configuration, the Now SMS/MMS Gateway will communicate with the device via this driver. If a Windows driver is not available for your modem, you can use either the "Standard" or "Generic" 33600 bps modem driver that is built into windows. A benefit of utilizing a Windows modem driver is that you can use Windows diagnostics to ensure that the modem is communicating properly with the computer.

NowSMS Support

Add Your Message Here, or click here to start a new topic.
Bold text Italics Underline Create a hyperlink Insert a clipart image
Options: Automatically activate URLs in message