|Definition of SMS Push||Search|
|SMS & MMS Technical Forum » MMS & SMS Technical Discussions (unsupported) » Archive through February 03, 2005 » Definition of SMS Push||« Previous || Next »|
|Lindo C. Estrera
Post Number: 1
Can anybody help me to define in non-technical terms what is an SMS Push? I am very glad if you can help me.
A SMS Push is a message to tell the terminal to initiate the session. This happens because you can't initiate an IP session simply because you don't know the IP Adress of the mobile terminal...
|Lindo C. Estrera
Post Number: 2
Thanks a lot. Now I have a better understanding what is SMS Push.
SMS Push is simply the process of sending an SMS message to a device. By the very nature of SMS, if you send an SMS message to a device, this is an SMS Push.
I suspect you are looking to use SMS Push as a trigger to wake up an application on the mobile device or to cause an application on the device to do some type of processing or alert.
In this case, you are looking to use either WAP Push (sent over SMS) or port addressed SMS.
The simplest types of WAP Push is "Service Indication" and "Service Load".
A Service Indication (SI) WAP Push is what most of us think of as WAP Push. WAP Push is more than this, but we've seen these types of messages, so they are our reference point. When a user receives one of these SI WAP Push messages, the mobile phone displays alert text that was contained in the push message and gives the user the option of connecting directly to the URL specified in the alert.
This is usually more "friendly" than sending an SMS text message that contains a URL because the mobile phone displays only the text of the SI WAP Push, but not the URL.
A Service Load (SL) WAP Push is more simplistic. It cannot contain any alert text, only a URL. When the mobile phone receives the SL message, it automatically loads the URL. At least that was the original intent ... there are, of course, security concerns with such a message, so most phones will not automatically launch the URL, and will instead display the URL and prompt the user as to whether or not to load it. (Or some phones, simply ignore SL WAP Push messages.)
WAP Push is more complex than either of these push types. SI and SL are both content types that are defined by the WAP Forum / Open Mobile Alliance (http://www.openmobilealliance.org).
Theoretically, any type of content could be sent as the payload to a WAP Push message. But realistically, if the push is being sent over SMS, the actual content that is sent in the push should be kept small.
For example, MMS is actually implemented over WAP Push. When an MMS message is to be sent to a device, a WAP Push is sent to the device, where the content type of the WAP Push is what is known as an "MMS Notification". The MMS Notification contains header information about the MMS message, and a URL that the MMS client can access to download the content of the MMS message. (See http://www.nowsms.com/how-mms-works)
So, when a WAP Push message is received on a mobile device, essentially the device has a WAP Push receiver that looks at the content-type of the WAP Push message to determine how to handle it. It might route it to a built-in application that processes SI and SL messages, or to an MMS client. There is also a content type called "OMA Provisioning Content" which contains device configuration information. (See http://www.nowsms.com/doc/web-menu-interface/send-oma-ota-settings)
(Note: WAP Push also has a concept of "Application-ID:" names/numbers that are to be used for routing WAP Push content to an application. Techically, this should take precedence over content type.)
While WAP Push was designed to be extensible and facilitate various content types, unfortunately, the popular mobile phone application environments didn't do a good job of providing a standard way for applications running on a phone to register their push content type. The Windows Mobile push router provides this type of facility, however in most other mobile phone application environments, there are not clear APIs for registering to receive a particular WAP Push content type.
As an alternative to WAP Push, what has caught on is port directed SMS, which is widely implemented in J2ME MIDP on mobile devices.
The concept is basically that when you send an SMS message to a device, you can also specify a port number on that device. An application on the device can register to receive all SMS messages sent to a particular port number. So when a message is received on a port that the application is listening on, the message gets routed to that application instead of to the message inbox. There is some more information about this concept at the following link: http://www.nowsms.com/sms-port-number
I suspect that when you are asking about SMS Push, you are actually asking about this idea of sending an SMS message to a port number registered with a mobile application.
a simple example using Application Port Addressing of SMS:
This allows short messages to be routed to one of multiple applications, using a method similar to TCP/UDP ports in a TCP/IP network.
Ports example: (Allocated by IANA)
2948/tcp WAP PUSH
2948/udp WAP PUSH
2949/tcp WAP PUSH SECURE
2949/udp WAP PUSH SECURE
9200/tcp WAP connectionless session service
9200/udp WAP connectionless session service
|Lindo C. Estrera
Post Number: 3
Thanks a lot. Now I am startuing to develop the SMS Push support for a new product.
Can somenone tell me what exactly do I need to use SMS to deploy software ..???
I have some SMS services in one server, but I cannot realized if I can use this server to perform deployment.
Many, many, many thanks.
can anyone tell me what is "sms push to WAP & MMS"? Thanks a lot!