Wireless Messaging API 2.0

The Wireless Messaging API (WMA) 2.0 defined in JSR-205 is a set of optional APIs that provide standard access to wireless communication resources. It is based on the Generic Connection Framework, defined in the Connected Limited Device Configuration 1.1 specification.

The API is supported in Nokia Asha and Series 40 software platform devices with clarifications detailed in the Wireless Messaging API (JSR-205): Implementation Notes. The API was introduced in Series 40 3rd Edition, Feature Pack 1.

The Multimedia Messaging Service enables the exchange of messages with more content versatility than, for example, SMS or MMS messaging.

Short Message Service (SMS) is a service available on most digital mobile phones and other mobile devices that permit the sending of short messages (also known as text messages, or more colloquially SMSes, texts or even txt files) between mobile phones. Other uses of text messaging can be for ordering ringtones, wallpapers and entering competitions. There are also services available on the Internet that allow users to send text messages for free.

For examples on creating and listening to SMS messages, see the following articles in the Nokia Developer Wiki:

Multimedia Messaging Service (MMS) is a standard for a telephony messaging systems that allow sending messages that includes multimedia objects and not just text messages as in SMS. It is mainly deployed in cellular networks along with other messaging systems like SMS, Mobile Instant Messaging and Mobile E-Mail. Its main standardization effort is done by 3GPP, 3GPP2 and Open Mobile Alliance (OMA).

For an example on creating MMS messages, see section Example: Creating and sending MMS messages in this library and article Sending a multipart MMS in the Nokia Developer Wiki.

An MMS message can include one or several of the following content types:

  • Text

  • Image

  • Audio

  • Video

A multimedia message consists of the message header and the message body, which includes all the message content as separate parts. Each message part has its own header containing information about the MIME type (see MIME type) of the part, a unique Content-ID, and a Content-Location field that can be used, for example, to store the original file name of the content item.

Figure 1. MMS message format

If the content is to be presented as a preformatted slide show presentation, the message body must also include a SMIL-formatted (see SMIL) part containing the presentation information.

Last updated 11 December 2013

Back to top