Java ME Luminary: Asko Komsi of Nokia

Print-friendly Version

Asko Komsi is currently Nokia's Director of Industry Relations in Technology Platforms. He has worked in various expert and managerial roles for close to 20 years, in research, standardization, technology strategy boards, and ventures focusing on wireless technologies and mobile services. In his current position, Asko is responsible for next-generation mobile Java platform standardization and related industry cooperation. As part of this role, he is one of the two specification leads for the Mobile Service Architecture (MSA) initiative (JSR 248 and JSR 249) in the Java Community Process (JCP), as well as one of Nokia's representatives on JCP's executive committee for the Java Platform, Micro Edition (Java ME). Asko holds BS and MSc degrees in computer science from the University of Turku, Finland, and is currently on his way to an MBA from the Haas School of Business at the Berkeley campus of the University of California.

Asko presented Mobile Service Architecture Initiative: JSR 248 and JSR 249 at JavaOne 2005. In this interview, he explains the Mobile Service Architecture initiative, and shares with us his insights into the future of Java ME technology and more.

Qusay Mahmoud: What is your role in the MSA initiative?

Asko Komsi: I'm specification lead.

QM: What is a mobile service? What kind of services does MSA aim to support?

AK: From the consumer perspective, a mobile service is any service that will help an end user perform everyday tasks such as messaging, getting driving directions, filling in an order form, and so on, using a mobile handset. A service can be a tool to solve work-related challenges such as sales support and scheduling, an application that offers pure entertainment such as games and cartoons, or anything and everything in between. In most cases today, these end-user services are Java-based applications.

From an architecture perspective, a mobile service is a downloadable and manageable component that provides certain typically domain-specific services, sometimes called enablers, to other applications and services running in the standard MSA environment. A good example of such a service would be a shared service based on Java Messaging Service that managed and provided messaging services to a number of different applications that needed to provide instant-messaging services to their end users. Thus, enablers are designed for application programmers, to simplify development of their applications and to minimize the need for every application to include the same functionality again and again.

QM: Can you give me a couple of examples of mobile services offered by Nokia?

AK: Nokia offers a wide variety of services. First of all, as end users' mobile services, hundreds of Java-based applications are available in the Nokia Preminet catalog, starting with the hugely popular Java games and ending with an abundance of different types of mobile productivity tools. MobiTV is a great example of a consumer application, that delivers on-demand streaming mobile TV content to your handset. Other applications such as mapping and routing applications, heart-rate monitor applications connected to a heart-rate monitor product, and different versions of popular Hugo games are all good examples of consumer services and applications.

On the MSA architectural level, Nokia has long been providing a wide variety of types of enabler services, on both the handset side and the network side. Examples of such mobile services are messaging – SMS, MMS, and email – and SIP and Location services, which are currently accessible by developers through standardized Java APIs.

QM: How does MSA for CLDC differ from MSA for CDC?

AK: From Nokia's perspective, MSA for CLDC is a platform focusing on mass-market consumer mobile devices and applications, where the handsets have somewhat limited resources. Nokia sees JSR 248 as the next step beyond JTWI (Java Technology for the Wireless Industry, JSR 185), with a wider array of supported JSRs that should work on top of both CLDC and CDC.

MSA for CDC, on the other hand, is focused on higher-end extensible enterprise and consumer mobile devices and software. The basic promise for this platform is flexibility, in terms not only of supported technologies, but also business models. From Nokia's perspective, this platform should provide the foundation for the features that will become commonplace in mobile handsets.

One of the key objectives is to gradually get rid of the monolithic way of specifying mobile platforms and start to introduce technologies that provide greater flexibility for all key stakeholders in a manageable way. Nokia's view is that one of the key elements of this platform is Mobile Operational Management (JSR 232), which will provide a solid foundation for application and service management, and will create a new opportunity for companies to start introducing middleware components also in the mobile space.

QM: How does MSA relate to JTWI?

AK: The MSA initiative continues where JTWI left off a few years ago. JTWI has been very successful but technological advances and new market requirements are slowly creating demands that JTWI cannot fulfill. MSA's role is to take the next step and provide a platform that can both fulfill the current needs and provide a foundation for the future. Additionally, it is important to notice that MSA has also been designed to be an ongoing effort, providing continuity for mobile Java standardization for years to come.

QM: How does the MSA initiative address security and privacy issues in Java ME applications?

AK: Since MSA for CLDC is in many ways architecturally similar to JTWI, its security and privacy architecture is based on the model JTWI uses. Thus, no significant changes are expected.

MSA for CDC, on the other hand, is the new, advanced mobile platform and, as such, will have to provide a new security framework that offers greater flexibility, yet simultaneously addresses any security or privacy concerns that its various users may have. Security and privacy issues are not taken care of simply by introducing a new JSR for them; they must be part of the design of the whole architecture. From this perspective, Nokia has been working on a total solution based on JSR 232 that provides a standards-based, dynamic environment for Java applications, services, and middleware. This architecture includes a well-defined policy-based security framework, a highly secure execution environment for multiple applications to run simultaneously, and a management framework that provides remote management and monitoring of every aspect of the platform, to ensure the highest level of security and privacy together with increased flexibility.

QM: What are the benefits of MSA to the mobile devices industry?

AK: One of the key focus areas for the MSA initiative is defragmentation.MSA will comprise new, backward-compatible specifications that not only add new functionality but also tighten up the component JSRs with additional clarifications, to help the manufacturers come up with interoperable MSA implementations. With the introduction of new functionality, Nokia hopes that we can also minimize the need for vendor- and operator-specific APIs. This development in turn will help the mobile device industry minimize the number of handset variants as well as minimize the fragmentation. The new CDC-based platform will further improve the way the handsets can answer the market demand by introducing manageable flexibility. The manufacturer will not have to try to squeeze in all possible Java APIs as part of its manufacturing process; they'll be able to introduce new APIs and features after deployment. It will be possible to customize handsets for specific purposes and businesses requirements after production.

As the platforms become more interoperable, developers will have an easier time introducing their applications for a wide array of handsets – increasing the number of applications available to consumers as well as increasing the demand for MSA-compliant handsets.

QM: How will MSA benefit mobile subscribers, developers, operators, and manufacturers?

AK: The benefits will be as follows:

• Consumers will enjoy a better user experience, and new types of applications made possible by a wide set of new technologies available to developers. So far, the focus of JTWI has been mostly on consumers. MSA will introduce a CDC-based platform that will also provide a more suitable platform for enterprise customers.
• Developers will see new functionality, wider interoperability, and greater availability of MSA-compliant handsets. These in turn will be reflected in the tools support and in the increased market and revenue opportunities. From Nokia's perspective, MSA for CDC will also introduce the concept of mobile middleware, which will provide a new opportunity and technical architecture for mobile service development.
• Operators will experience increased interoperability between MSA-compliant handsets, resulting in decreased support costs, as well as an increased number of MSA-compliant applications. These in turn will increase service usage, and consequently increase revenues. From Nokia's perspective, the new CDC-based platform will also introduce features that will provide the operators and other key stakeholders ways to introduce new post-shipment types of features in a remotely manageable way.
• Manufacturers will enjoy the benefits I detailed in my answer to your previous question; in short, reduced fragmentation and increased interoperability between platforms and devices.

QM: Who is responsible for ensuring that devices conform to JSR 248 or JSR 249?

AK: MSA uses the JCP standard technology compatibility kit (TCK) approach to compatibility testing. All MSA-compliant handsets must pass the TCKs of all component JSRs as well as the MSA TCK. Thus, any party implementing an MSA-compliant platform is responsible for TCK testing the implementation. On the application verification side, Nokia has been a founding member and active participant in the Java Verified Program, and our goal is to develop it further, to better fulfill the needs of MSA also.

QM: What's the timeline for release of the MSA specifications?

AK: The target for final specification of MSA for CLDC is December 2005. The target for final specification of MSA for CDC is the first half of 2006.

QM: When do you expect devices that support MSA to become commercially available?

AK: Nokia will naturally do its best to implement these standards as quickly as possible. At this point, however, when the standard is not ready yet, it is too early to commit to any kind of product schedule.

QM: What are your thoughts on WAP (Wireless Application Protocol) and BREW (Binary Runtime Environment for Wireless)?

AK: WAP was the first step in the effort to come up with standard technologies to access various mobile Internet-related services. As everybody can see, WAP has evolved a lot during the last years, and WAP technologies with a wide set of new technologies are now being standardized in OMA (Open Mobile Alliance). Hundreds of millions of handsets now support OMA standards, and JCP has several JSRs that focus on creating Java APIs to OMA standards. Thus, from my perspective, WAP and OMA have been very successful in their efforts to standardize mobile platform technologies and in creation of highly successful mobile-services markets.

The Binary Runtime Environment for Wireless (BREW) is Qualcomm's proprietary downloadable applications platform for mobile handsets and a hosted end-to-end business system for wireless carriers. Java ME, on the other hand, is the preferred application development environment for mobile devices endorsed by Nokia. The openness of Java enables developers to create versatile applications with multiple distribution and business opportunities.

QM: JSR 249 targets the CDC platform and the Foundation Profile. Is Nokia using CDC?

AK: Nokia has used the CDC platform for quite some time already. It was first introduced as part of our Communicator devices, several years ago. Today, it's being used on our Series 80 handsets and we are moving the CDC platform also into the more mainstream Series 60 devices.

QM: Where do you see Java ME technologies and mobile data services going in the next three years?

AK: Java ME is the leading mobile end-to-end application technology. In support of that, Nokia is committed to the continued use and evolution of the Java platform in the mobile space. We have launched more than a hundred Java-enabled mobile device models, and are investing in extensive Java developer community support by providing tools, guidelines, and a hosted, end-to-end content provisioning system, Preminet Solution. We have created developer platforms that span multiple devices, enabling developers to take advantage of large economies of scale when creating mobile applications. As you know, Nokia is actively involved in the specification and development work that is carried out by the open industry organization called the Java Community Process. Nokia is a member of the executive committee of JCP and we are the specification lead for many essential JSRs and initiatives.

One of these is the Mobile Service Architecture. Nokia and Vodafone have established the MSA initiative within the JCP to improve application compatibility across multi-vendor mobile devices through structured Java ME API standardization. The initiative will define a common, open, standards-based, next-generation mobile Java development and deployment platform for consumer and enterprise applications and services.

Thus, we are in this for the long haul and we are deeply committed to the continued use and evolution of the Java platform in the mobile space.

If you look at what the MSA expert group is planning on doing during the next 3 years, the first step is to introduce the JSR 248 platform and provide the developers with a wider variety of new technologies so that they can benefit from the features that are becoming commonplace in our handsets today. After that, I see that we have to move from the JSR 248 type of monolithic architecture to a more dynamic architecture that provides the mobile industry a better way of managing different handset configurations, business models, and so on. I think that the current "one size fits all" approach will not be usable in the future and we need a new way to manage the Java platform itself as well as applications, services, and middleware.

QM: Do you have any advice for wireless Java application developers?

AK: The first thing is to study the early draft specification of JSR 248 to familiarize yourself with all the new features that are coming to market next year. This specification will provide a huge improvement over JTWI and will create a number of new opportunities for new, compelling consumer and enterprise applications.

I also urge developers to start thinking in terms of what the MSA for CDC platform could bring to them. It is the next-generation Java platform and our goal is to make it as future-proof as possible. We think that flexibility and manageability are the key concepts that need to be introduced to the mobile space to provide the widest possible opportunity for new mobile applications, services, and middleware to flourish.

In general, I think that the statistics show that the mobile applications business is working and there are lots of opportunities there for successful business. MSA will significantly improve the platform offering and will provide benefits for all key stakeholders in the mobile application value chain. Consequently, the opportunities are improving and the market is growing so this is the time, if any, to enter the market and take the service market away from the "old fashioned" personal computers. MSA and mobile services are here to stay!

QM: Any last words?

AK: Nokia has been an active member of JCP for years now as can be seen, for example, from the high number of JSRs our specification leads have introduced and successfully finished. From our perspective, MSA is the next substantial effort on Nokia's part to create the next-generation mobile Java platform in order to further enlarge and improve the mobile service market. Connecting people can be done in a multitude of ways and Java ME is one of the key tools in Nokia's efforts to implement its vision.

Qusay H. Mahmoud provides Java-related consulting and training services. He has published dozens of articles on Java technology, and is the author of Distributed Programming with Java (Manning Publications, 1999) and Learning Wireless Java (O'Reilly, 2002).