Ericsson: Enablers - The link between Terminals, Networks and Applications

Now the thought of having the same basic set of applications across different networks is indeed appealing, but how should developers approach this new opportunity? Imagine starting a software project where you do not know what the target platform is! The handset manufacturers are careful about disclosing plans of future handsets because of the tough competition, but still depend on good applications for the success. Here I will show a method to understand what the applications of the future will be, by looking at what ties terminals, networks and applications together - Enablers.

For each and every mobile Internet device, there is a set of Enablers that decide what you can do with it. The basic GSM/GPRS handset only supports voice, SMS and WAP and then that is exactly the kind of applications you can get. As handsets get more and more advanced we see more and more Enablers added into the devices and networks. One example of such an enabler is positioning support. If your terminal supports that, the handset will be able to report what the position is. This opens up for a new range of applications that leverage this feature, where you might for example have a taxi ordering application that knows in what city you are. Positioning as an Enabler also requires support in the network, but we'll get back to that in a while.

Other examples of Enabler support in terminals are Multimedia Messaging Service (MMS), video playback and Bluetooth. All of those enablers open up for a new set of applications for the user. Just as the networks themselves are migrated into the future by adding first GPRS and then 3G, these Enablers add more and more applications capabilities step-by-step. In 2001 we started with WAP and SMS and then Enhanced Message Service (EMS) and SyncML. Going into 2002 we add positioning support, Java and MMS and later video playback. From the application's point of view this is what decides what the GPRS and 3G applications will be, not primarily the networks themselves. This means that you can actually know what categories of applications there will be in 3G networks by knowing what Enablers the 3G terminals will support.

You can view an enabler as a catalyst that, when available, opens up for a new bouquet of applications. For example, the positioning Enabler removes the need for the user to type in his current address and makes a new range of position-aware applications possible, like 'The Weather Near me', 'Buddy-locator'. Although some of these applications will be completely new, the bulk is instead previously known applications that now work a lot better. This is a key success factor for the introduction of new technology - migrate step-by-step into more advanced features without the quantum leaps. It has been shown many times that the most difficult part is not to migrate the technology but to migrate the minds of the users - it is hard to change habits!

Enabler	Handset/Network Support needed	Main added capability	Example applications
WAP 1.1/2.0	Handset & Network	Transactions and viewing information via a browser	Buing movie tickets, checking sport results
MMS	Handset & Network	Sending and receiving messages of text, sound, pictures and (later) video	Take a picture with a (sometimes built-in) camera and send it to a friend. Get the daily Garfield cartoon.
Positioning	Network mainly (GPS in hadsets for added accuracy)	Uses network to fetch user position when he/she allows it (used together with other enabler like WAP)	Find the closest gas station, What will the weather be where you are right now?
Java (primarily J2ME: Java 2 Micro Edition)	Terminal primarily (Network for provisioning & charging)	Standardized execution environment that allows programs to be downloaded to the handset	Games with moving objects, stock trading where tickers are updated in real-time

Table above shows four sample Enablers and what they add to the picture

Here we can also see an interesting detail, that some Enablers primarily need support in the terminal while others require some kind of server in the network (WAP, MMS etc). Generally, an Enabler is a client component plus a server component that adds a certain feature to the network. As an example, a weather application might use WAP to present the content efficiently on the screen. Then an operator might introduce positioning support in the network and now the applications developer can present the weather report differently depending on were the user is currently located.

MMS is one of the key enablers, which we see spreading around the world right now. The first networks were launched during spring 2002 and now more and more handsets are appearing on the market. Some react when I call MMS an Enabler as it has often been regarded as a great application in itself. The point I want to make is that it is very dangerous to view MMS as an application that will drive itself without need for support. After all, what is it that we are going to send to each other using MMS? Who is going to create the MMS slide shows and clips? Some of the content will be downloaded via WAP or created on the handset. With a camera built into the phone or attached to it, the user can more easily create appealing content on top of MMS.

We need to view MMS as an Enabler in order to create focus on the content that is so dearly needed to help it succeed. Then there will be sites that not only host ring tones and logos showing Britney Spears but also advanced MMS shows with animations, pictures and sound clips that create early multimedia experiences on the nice color screen handsets. When we view MMS as an Enabler we also make sure there are communities where content and applications developers can get help, support and exchange experiences as well as download content creation tools. Ericsson Mobility World is an excellent example of such a community that drives the development of applications and supports the applications developers in their efforts to make MMS a success.

Christoffer Andersson of Stockholm, Sweden, is Director of Business Development, Market Area EMEA (Europe Middle East and Africa), for Ericsson. In this role he and the Mobile Internet Drive Team drives the sales and adoption of new services, like Multimedia Messaging, in the region and removes the barriers for market launch. He is a frequent speaker at industry events, like 3GSM World Congress and CeBIT, and a regular writer for the Ericsson Mobility World website.

Christoffer is also author of the Amazon.com best-selling book 'GPRS and 3G Wireless Applications - The Professional Developer's Guide', published by John Wiley & Sons.