OSGi World Congress 2004

1. Standards Ecosystem for
End-to-End Management of
Mobile Handsets
Sanjay Gupta
Motorola

2. Mobile Management Needs of the Industry
• Remote software mass
deployment, updating,
and repair
• Over-the-air and local
configuration of devices,
services, and applications
• Device monitoring and
diagnosis
Customer Service
Representative Admin Console
Provisioning,
Configuration,
and Download
Servers

3. Role of the OSGi Mobile Expert Group
• A management framework that will allow
shareable components to be installed, updated,
and removed dynamically
• A predictable software lifecycle model
• An ability to configure and to manage mobile
devices remotely
• A security model to ensure a safe environment
The OSGi MEG is addressing these needs by defining:

4. What Technology is Required?
• A means of representing device and software
configuration parameters on the device
• A protocol for querying and setting parameters
remotely
• A protocol for downloading software
components and content
Can these capabilities be leveraged from
existing mobile standards?

5. Mobile Standards Ecosystem
GSMA
Mobile
Requirements &
Market Forums
W3C
ApplicationTransport
3GPP2
IETF
3GPP
Wireline
Domain 3G Cellular Standards
CDG
Others
OMA
Others
Platform
OMTP
OSGi
CE Linux
BREW
Symbian
.NET
JCP

6. Open Mobile Alliance
• Formed in June 2002 by the mobile industry through joining of Open
Mobile Architecture initiative and the WAP Forum
• Integrated other mobile organizations
– SyncML Initiative
– Location Interoperability Forum (LIF)
– Multimedia Messaging Interoperability Process (MMS-IOP)
– Wireless Village
– Mobile Gaming Interoperability Forum (MGIF)
– Mobile Wireless Internet Forum (MWIF)
• Represented globally by over 360 member companies
– Mobile Operators
– Wireless Vendors
– IT Companies
– Content Providers & Others

7. Goals of the Open Mobile Alliance
• Define global standards for mobile services and
applications
• Deliver open technical specifications based upon market
requirements
• Ensure interoperability across devices, geographies,
service providers, operators, and networks
• Drive consolidation of standards activity within the
mobile data service industry
• Represented globally by over 360 member companies
– Mobile Operators
– Wireless Vendors
– IT Companies
– Content Providers & Others

8. OMA Workgroups
Board of Directors
Technical
Plenary
Operations and
Process
Committee
Release
Planning and
Management
Committee
Interoperability
Device
Management
Location
Browser and
Content
Interoperability
Data
Synchronization
Messaging
Requirements
Developers
Interest Group
Mobile Web
Services
Presence and
Availability
Security
Game Services
Mobile
Commerce and
Charging
Push to Talk
Over Cellular

9. OMA Device Management
• Remote Configuration Maintenance/Management
– SyncML DM Parameter Management
– Software Inventory (What is installed? Operational? Configured?)
– Configuration Synchronization between Multiple Devices
• Remote Customer Care
– Event Reporting, Performance, QoS
• Provisioning
– OTA and Smart Card
• Backup and Restore
– Restoration after device change or hardware failure
– Backup of User Preferences
• Firmware OTA Update
– Updating of radio characteristics and software
Device Management is one of OMA’s most
important work areas, covering:

10. OMA DM Standards Timeline and Roadmap
OMA DM Spec 1.2 or separate enablers
Generic Provisioning
•Standardized Objects
•Remote Customer Care
•Various Standardized Objects – Web Srvs, etc.
•Work with other standards groups, 3GPP
•Remote File Management
•Backup & Restore (Joint with SyncML DS)
•Firmware OTA Updates
OMA
•Syncml.org
merges into
the OMA
•WAP merges
into the OMA
Q4 04 Q1 05 Q2 05 Q3 05Q2 04Q4 03 Q3 04Q1 04 Q4 05
•Existing SyncML DM Standard (1.1.1)
•Device Management Protocol
•Representation Protocol, Device Management Usage
•Device Management Standardised Objects
•Device Management Tree and Description
•Notification Initiated Session
•Device Management Bootstrap
•Device Management Security
•Device Management Conformance Requirements
Completed
In Progress
OMA DM Spec v1.1.2
•Spec v1.1.1 in OMA
template approved
•Standards Legend
•OMA – Open Mobile Alliance
•3GPP – 3rd Generation Partnership Project
•DS – Data Synchronization
Ongoing OMA DM Req
Work
•List of DM updated use
cases
OMA / OSGi
• Motorola submits request to
DM WG for liaison with OSGi
• DM WG approves; request
sent to OMA Board
Future OMA DM release
•Radio Software Download –
Parameters, RF Conf, Terminal
Apps
SyncML DM Spec
v1.1.1 (see above)
•Existing OMA Client Provisioning Standard (1.1)
•Provisioning Architecture Overview 1.1 [PROVARCH]
•Provisioning Bootstrap 1.1 [PROVBOOT]
•Provisioning Content 1.1 [PROVCONT]
•Provisioning User Agent Behaviour 1.1 [PROVUAB]
•Smart Card Provisioning 1.1 [PROVSC]
OMA Client Provisioning 1.1
(see below)
OSGi
• Submits request to OMA
for liaison relationship

11. OSGi MEG and OMA
• Enable the remote and local management of OSGi
services-oriented framework
– OTA updating of device parameters
– Tree representation of parameters
– Device monitoring
– Device management security
• Increase interoperability across platforms, both MEG and
non-MEG based.
• Leverage expertise not existing within the OSGi
The OSGi Mobile Expert Group can use OMA technology to:

12. OSGi MEG and OMA
• Defines how OMA DM can be implemented
– Provides a CDC-based API for DM functions
• Influences a CLDC-based DM API in JSR 246
– Standardizes tree structure for storing of device
parameters
• Extends OMA DM in necessary areas
– Adds additional data types to DM tree node support
(Arrays and Vectors)
– Expanded security model for DM tree node access
The MEG also offers the following in return:

13. A Mobile Platform Architecture
Device Hardware
Operating System
JVM (CDC+FP)
OSGi Framework
Deployment
Device
Management
App Manager
Policy
Download
Agent
Others
DM Tree
Download
Server
Device
Management
Server
OMA Download Protocol
OMA DM Protocol
MEG
Services
OSGi
OMA

14. Motorola’s Involvement
Motorola is leading efforts in both groups to
ensure their success:
• President of the OSGi Alliance
• Co-chair of the OSGi MEG
• MEG DM Workgroup Lead
• MEG Deployment Workgroup
Lead
• MEG Application Model
Workgroup Lead
• Member Board of Directors
• Vice-chair of DM Workgroup

15. Relationship Between OMA and OSGi
• Currently, an informal relationship exists
between groups
– Several members participate in both OMA DM and
OSGi MEG DM workgroups.
• But a formal liaison is in progress
– Jan 2004: OSGi invites OMA for a liaison relationship
– May 2004: Motorola request for a liaison request is
approved by OMA DM workgroup and OMA Technical
Plenary
– Ongoing: Request under review by OMA Board

16. Summary
Together, OMA DM and the OSGi
MEG define an interoperable
mobile operationally managed
platform you can deploy!

17. THANK YOU