This document discusses the history and future of downloadable mobile marketplaces. It provides a short history of Java over-the-air (OTA) technology and download models used in mobile devices. It describes the components of a full download system including .jad files, jar files, and download transactions using SMS. The document argues that standards help make download systems work by creating an ecosystem for developers and ensuring technical solutions are interoperable between companies. It also discusses how OSGi frameworks can provide control and capabilities to classic CDC/Java environments on mobile devices.

1. © 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 Bostrom
CTO Nokia Java
Platform
Jon Bostrom
CTO Nokia Java
Platform

2. © copyright 2004 by OSGi Alliance. All rights reserved.
The Killer App
is the one YOU NEED RIGHT NOW!

3. © copyright 2004 by OSGi Alliance. All rights reserved.
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

4. © copyright 2004 by OSGi Alliance. All rights reserved.
Download Models

5. © copyright 2004 by OSGi Alliance. All rights reserved.
Download Models

6. © copyright 2004 by OSGi Alliance. All rights reserved.
Download Models

7. © copyright 2004 by OSGi Alliance. All rights reserved.
Download Process

8. © copyright 2004 by OSGi Alliance. All rights reserved.
Jar
.jad
Download Transaction

9. © copyright 2004 by OSGi Alliance. All rights reserved.
Download Transaction SMS

10. © copyright 2004 by OSGi Alliance. All rights reserved.
Full Download System

11. © copyright 2004 by OSGi Alliance. All rights reserved.
• 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

12. © copyright 2004 by OSGi Alliance. All rights reserved.
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

13. © copyright 2004 by OSGi Alliance. All rights reserved.
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 sharing
Not enough “POWER”

14. © copyright 2004 by OSGi Alliance. All rights reserved.
CDC Environment
• Classic VM
• Optional J2SE Security Manager
• There are several possible profiles
• Personal Profile
• Foundation Profile
• Personal Basis Profile

15. © copyright 2004 by OSGi Alliance. All rights reserved.
Existing CDC Foundation or PBP Environment
•No standardized management environment
•No coherent API model
Not enough “Control”

16. © copyright 2004 by OSGi Alliance. All rights reserved.
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

17. © copyright 2004 by OSGi Alliance. All rights reserved.
Provides “POWER” and “CONTROL”
OSGi Managed CDC environment
•STANDARDIZED
•Predictable
•Extensible
•Loadable