This entry is part 15 of 17 in the series Sending out an SMS

I have added a page with references to the official 3GPP, Open Mobile Alliance (formerly WAP Forum) and other specifications that are relevant for the topics in this blog so far.

See here.

I’ll keep that page up-to-date.

EMS and WAP Push support

This entry is part 9 of 17 in the series Sending out an SMS

As I have been writing about EMS and WAP Push, I am sure your ask yourself: “Does my phone support this?”. Again we dig into the WURFL database and we see that WAP Push is widely supported, but EMS a little less so.

This is understandable, because WAP Push is a protocol used in MMS (or picture messaging). Since most phones nowadays are camera phones and support picture messaging, they’re very likely to support WAP Push.

Here is a list of devices that support EMS and/or WAP Push, according to WURFL:

Read More…

Collected UAProf URLs

If you’re interested in the capabilities of a particular device, I have assembled a list of all the UAProf URLs from the WURFL database:

Read More…

An example UAProf file

To give you a feel of the kind of information you’ll find in a UAProf file I include an example. It is fascinating how much information is available.

Here is the UAProf file for a T-Mobile Dash:

Read More…

UAProf device profiles

When you’re sending plain text SMS messages to a mobile device you don’t have to worry too much about whether the device can display it correctly. Plain text SMS messages are the lowest common denominator of mobile messaging.

When you want to send more complicated messages, like:

  • EMS messages
  • Pictures messages (or MMS messages)
  • Ringtones
  • Wallpapers

You’ll need to know more about the device you’re sending to. There are many possible formats and even when you know which format to use you’ll need to worry about sizes, capacity, supported characters sets and more.

This problem can be addressed in different ways. Read More…