history and future of the downloadable mobile marketplace - jon bostrom, nokia

© copyright 2004 by OSGi Alliance All rights reserved.

History and Future of the Downloadable

Mobile Marketplace

History and Future of the Downloadable

Mobile Marketplace

Jon BostromCTO Nokia Java

Platform

Jon BostromCTO Nokia Java

Platform

© copyright 2004 by OSGi Alliance. All rights reserved.

The Killer Appis the one YOU NEED RIGHT NOW!


Short History of Java OTA• NTT DoCoMo Project

– Brought kvm “out of the lab”– 9 mos project in Japan– Designed API set including UI– Designed .jad concept, download architecure and the

“Java VendingMachine” download server concept• DoCoMo successfully Launched iMode Java• MIDP OTA recommended practice• General availablity of many download servers• OMA OTA• JSR 232


Download Models


Download Process


Jar

.jad

Download Transaction


Download Transaction SMS


Full Download System


• Standard makes it easier for different companies to operate in different parts of the value chain and provide different components of the technical end-to-end solution.

– Flourishing business ecosystem more likely develops around a standard solution.

– Defined by several independent companies in a collaborative process. Evolution of MIDP is not in the hands of any single company.

• MIDP standard is well established :– Several companies specialised in creating MIDP applications. Existing

skills.– Lots of MIDP content created that appeals to users.– Existing MIDP handset base guarantees that significant amounts of MIDP

content will continue to be created for several years.– Extensive tools support– Documentation and books

Why MIDP Marketplace Works


What Standards make CLDC work• Standard set of Devloper APIs (MIDP)• Application model

– Custom lifecycle for mobile devices• Packaging Model

– Custom Jar with specific manifest contents• Authority Model (who can use what APIs)

– Custom Authority model for mobile devices• Download and Installation Model

– Custom download model with content discovery• Isolation Model

– Custom isolation model 1 application per VM


Existing CLDC MID-P 2.0 Device Environment

•Management environment

•Secure sandbox

•Controlled installation

•Single app Isolation model

•API set

•Predictable but limited

•Not extensible

•No API sharingNot enough “POWER”


CDC Environment

• Classic VM• Optional J2SE Security Manager• There are several possible profiles• Personal Profile• Foundation Profile• Personal Basis Profile


Existing CDC Foundation or PBP Environment•No standardized management environment

•No coherent API model

Not enough “Control”


What standards Will make CDC work• CDC / Foundation +249 + JSR232

– Personal Profile installable on demand– Standard set of developer APIs– JSR232 = OSGi Framework + optional services + MEG services

• JSR232 (OSGi) Standardizes– Application model with lifelcyce control remote and local– Packaging model advanced component based– Authority / policy management(local and remote) (who can do

what)• Runtime and install time

– Download Installation/removal model Push and Pull for applications, services, and Class extensions

• Dependency management– Application cooperation model with Class Loader isolation model– Service registry, logging, user administration– Supports Class path extensions in a controlled way


Provides “POWER” and “CONTROL”

OSGi Managed CDC environment•STANDARDIZED

•Predictable

•Extensible

•Loadable

history and future of the downloadable mobile marketplace - jon bostrom, nokia

Technology

osgi alliance

midp standard

download system

jad download transaction

coherent api model

midp applications

evolution of midp

apis custom authority