End of this blog

Posted August 20, 2008 by Olle
Categories: Uncategorized

I am leaving Ericsson Mobility World Developer Program tomorrow (August 21) and will no longer post on this blog.

To keep up to date with what is happening with the developer program, visit the website.

New articles at the developer program website

Posted August 20, 2008 by Olle
Categories: Uncategorized

Two articles I have written that touch on Java and mobility have recently been published on the Ericsson Mobility World Developer Program website.

Final article from JavaOne 2008 published

Posted May 29, 2008 by Olle
Categories: JavaOne sessions

This got a bit delayed, but anyway, the following article has been published on the JavaOne wrap-up page on the Ericsson Mobility World Developer Program website:

Mobile service creation demos – a success

New Mobile Service Architecture will include IMS Service API

Posted May 9, 2008 by Olle
Categories: Uncategorized

(This article has now been published on the Ericsson Mobility World Developer Program website.)

The Mobile Service Architecture (MSA) specifies a standardized set of APIs that allows developers to access various capabilities – from sending SMS messages to accessing the address book information – on mobile phones. Ericsson is a member of the expert group that is drafting the upcoming second version of MSA, which will include an IMS (IP Multimedia Subsystem) API.

Java Micro Edition (ME) developers were treated with an overview of the current and forthcoming versions of MSA on May 8, in technical session held by Kay Glahn, consultant at Vodaphone, and Erkki Rysä, technical manager at Nokia.

Glahn said that improving and extending the current MSA will make more advanced smartphone features available to Java ME developers, as well as reduce ambiguity and fragmentation in the current MSA.

According to Glahn, the interoperability that MSA creates in the Java-enabled phone market, will allow developers write applications for a bigger market and thereby make more profit. MSA makes it easier to both develop applications and deploy them on different types of handsets. Manufacturers and operators, meanwhile, will benefit from a larger developer community that turns out more applications, since this means both increased demand for MSA-compatible devices and telecom service usage. Finally, Glahn argued, end users will get a benefit from the wider choice of available applications.

”There will be benefits for the whole industry, for all players in the ecosystem, which is something that is very good for the developer community,” Glahn said.

Unlike the first version of MSA (specified in JSR-248), MSA 2 does not only cover Java feature phones (CLDC phones), but also more advanced phones (CDC phones). MSA 2 will specify three different sets of API – a limited, a core, and a full set – for different types of phones, from low-end phones to advanced smartphones.

The final draft of a new version of MSA (MSA 2) is being drawn up in Java Specification Request (JSR) 249 and is being expected to be published in the fourth quarter of 2008.

Since MSA 2 will be fully backwards compatible with the already existing MSA 1, Rysä’s message was clear:
”There is no reason not to start developing devices now because there are already MSA-compliant devices out there.”

Magnus Olsson, responsible for Java ME standards at Ericsson, and member of the JCP executive committee

(EC) for Java ME says that MSA 2 will be much better adapted to market needs than MSA 1.

“The MSA initiative learned from past experience that rather than creating a large set of APIs, one-size-fits-all instead adapt to the available set of compelling device features while adding the benefits of reachability into new market segments,” Olsson says.

“A layered set of APIs will enable deployment on a significant increased market segment with mobile devices previously too limited for MSA. Feature phones and advanced smartphones will benefit from a consistent set of core APIs that can be extended with additional APIs for specific device features adding capabilities such as location, enhanced multimedia and advanced communication services based on IMS.”

Included in MSA, is JSR-281 IMS Services API, with Ericsson as the specification lead. The API will allow developers to create applications that integrate with IMS networks, which is telecom industry’s preferred standard for delivering converged multimedia services. The JSR work have now been delivered to the JCP (Java Community Process) organization and is to be presented to the JCP executive committe for the final approval ballot.

“JSR-281 has been received with great appreciation by the industry, with operators already starting to show an interest how the new IMS API allow developers to benefit from using IMS, so there is a demand for compelling IMS applications that developers now can meet,” Olsson says. “The IMS API provides access to a core set of IMS features that will allow developers to create converged multimedia applications such as presence, push-to-talk, and video conferencing without having to deal with the more complex groundwork and underlying details of the IMS technology.”

By Olle Blomberg

Article about the Mobile Service Architecture (first version):

JCP page about JSR-249:

JCP page about JSR-248:

JCP page about JSR-281:

Yet another two articles…

Posted May 8, 2008 by Olle
Categories: Uncategorized


Posted May 7, 2008 by Olle
Categories: Uncategorized

Articles about SailFin and Neil Young

Posted May 7, 2008 by Olle
Categories: Uncategorized

Tags: ,

Two more articles published today, one about project SailFin, based on an interview with Sreeram Duvur at Sun, and one about Rich Green’s general session.


Get every new post delivered to your Inbox.