MEG & VEG Architecture Peter Kriens, CEO, aQute Contents Why a Mobile Specification?Why a Mobile...

MEG & VEG Architecture

Peter Kriens, CEO, aQutePeter Kriens, CEO, aQute

ContentsContents

• Why a Mobile Specification?Why a Mobile Specification?

• Overall ArchitectureOverall Architecture

• ProfileProfile

• DeploymentDeployment

• Device ManagementDevice Management

• Application ModelApplication Model

• Foreign ApplicationsForeign Applications

• Relation to JCPRelation to JCP

• Road AheadRoad Ahead

Why a Mobile Specification?Why a Mobile Specification?

• MIDP is very successful for mobile devicesMIDP is very successful for mobile devices– Over 200 million devices soldOver 200 million devices sold– Multi billion dollar marketMulti billion dollar market– Highly ProfitableHighly Profitable

• So who needs an So who needs an OSGiOSGi handy? handy?


• Mobile Devices are becoming very powerfulMobile Devices are becoming very powerful– 200 Mhz+ Processors200 Mhz+ Processors– Flash has become very cheapFlash has become very cheap

• End user street prices1 Gb $68, 128 Mb $13End user street prices1 Gb $68, 128 Mb $13

– Displays become bigger and more usefulDisplays become bigger and more useful– Networked Networked

• Wifi, GPRS, 3GT, UMTSWifi, GPRS, 3GT, UMTS

• Are games Are games thethe market for such powerful devices? market for such powerful devices?


• The next generation of mobile devices brings Enterprise The next generation of mobile devices brings Enterprise Applications into rangeApplications into range

– Sales Support, Expert Systems, Administrative, Data Sales Support, Expert Systems, Administrative, Data Acquisition, …Acquisition, …

• Enterprise Applications Enterprise Applications – Are exponentially more complex than gamesAre exponentially more complex than games– Require high security for all facetsRequire high security for all facets– Require collaboration between different applicationsRequire collaboration between different applications– Will connect to a myriad of devicesWill connect to a myriad of devices– Require lots of middlewareRequire lots of middleware

• Is MIDP up to this?Is MIDP up to this?


• Additionally there is a silent software crisis at Additionally there is a silent software crisis at device manufacturersdevice manufacturers

• Operators require their devices to be heavily Operators require their devices to be heavily customizedcustomized

• Managing all these configurations is a tremendous Managing all these configurations is a tremendous task that negatively influences:task that negatively influences:

– Product development costProduct development cost– Technical supportTechnical support– Developing new featuresDeveloping new features

• Is MIDP really the solution here?Is MIDP really the solution here?

Don’t think so …

Over ArchitectureOver Architecture

• What are the required features for a Mobile What are the required features for a Mobile Software Platform?Software Platform?

• Very High SecurityVery High Security– Protects against virusesProtects against viruses– Allows mixing and matching applications from different Allows mixing and matching applications from different

sourcessources

• Strong modularity support Strong modularity support – Applications from different sources can coexistApplications from different sources can coexist– Share libraries in a controlled wayShare libraries in a controlled way


• Collaboration ModelCollaboration Model– Smaller components: easier to developSmaller components: easier to develop– Mix and match: more flexible procurementMix and match: more flexible procurement– Plugin model widens the scope of devicesPlugin model widens the scope of devices

• Remote ManagementRemote Management– Maintain quality of serviceMaintain quality of service– After sales applicationsAfter sales applications– Low maintenance costLow maintenance cost

• Management by EnterprisesManagement by Enterprises– Allow Enterprise to manage part of the deviceAllow Enterprise to manage part of the device

Overall ArchitectureOverall Architecture

Operator

Enterprise

Devices

Developers

OSGi Service Platform

Mobile Architecture OverviewMobile Architecture Overview

Log

Deployment

EventAdmin

ApplContainer

DmtAdmin

ConfigAdmin

ApplicationAdmin

DownloadAgent

MonitorAdmin

Servicesmanagementserver

Cond. PermAdmin

Services ForeignApplications

Start Level PackageAdmin

What Was Missing In OSGi R3What Was Missing In OSGi R3

• End-to-end DeploymentEnd-to-end Deployment

• Device ManagementDevice Management

• Device MonitoringDevice Monitoring

• Application ModelApplication Model

• Foreign Application supportForeign Application support

• Security Policy Model based on mobile conditionsSecurity Policy Model based on mobile conditions– Subscriber (IMSI)Subscriber (IMSI)– Device Type (IMEI)Device Type (IMEI)

SecuritySecurity

Java 2 PermissionsJava 2 PermissionsPer Bundle PermissionsPer Bundle Permissions

Each Bundle carries its own permissionsEach Bundle carries its own permissions This set of permissions can never be exceededThis set of permissions can never be exceeded

Bundle Signing is completely specifiedBundle Signing is completely specified Authentication of bundlesAuthentication of bundles

Permission Management via:Permission Management via: SignersSigners Location of originLocation of origin Custom conditionCustom condition

R4 Core Security is equipped to handle MEG R4 Core Security is equipped to handle MEG RequirementsRequirements

SecuritySecurity

• Provide a flexible policy Provide a flexible policy management for a delegated management for a delegated management modelmanagement model

• An Operator must be able to An Operator must be able to sell a device to an Enterprise sell a device to an Enterprise and be assured the enterprise and be assured the enterprise can not do anything the can not do anything the Operator does not wantOperator does not want

• The Enterprise administrator The Enterprise administrator must be able to give the device must be able to give the device to a person and restrict the to a person and restrict the possibilities furtherpossibilities further

• Bundles must be restricted to Bundles must be restricted to only the permissions they needonly the permissions they need

Operator

Enterprise

Sales

Management domain

Bundle

Security LayerSecurity Layer

• Signing based on Public Key Signing based on Public Key CryptographyCryptography– Operator signs signing certificate Operator signs signing certificate

of Deployerof Deployer• Developer adds a local permissions Developer adds a local permissions

file to the bundlefile to the bundle– Easy to readEasy to read

• The local permissions are audited by The local permissions are audited by the Deployerthe Deployer

• Deployer signs the bundleDeployer signs the bundle• The bundle gets deployed on a The bundle gets deployed on a

Service PlatformService Platform• The permissions of the bundle are The permissions of the bundle are

the intersection of:the intersection of:– Local permissionsLocal permissions– System permissions for that System permissions for that

signersigner• Operator remains in full control at all Operator remains in full control at all

timestimes

BundleA

controls

localpermissions

signature


systempermissions

S

Enterprise

Developer

Operator


• Permissions can be assigned based Permissions can be assigned based on:on:– SignerSigner– Location (Channel)Location (Channel)– Custom ConditionCustom Condition

• Multiple signers are possibleMultiple signers are possible– Bundle gets union of signer Bundle gets union of signer

permissionspermissions• No partial signing, all signers must No partial signing, all signers must

sign all contentsign all content• Flexible management API for Flexible management API for

permissionspermissions• DynamicDynamic

– changes take effect immediatelychanges take effect immediately• Compatible with standard Java 2 Compatible with standard Java 2

VMsVMs– Take advantage of optimizationsTake advantage of optimizations


systempermissions

&localpermissions

BundleA

Location, signer, custom


• Signer requires coarse grained to be Signer requires coarse grained to be feasiblefeasible

• Bundle can use very fine grainedBundle can use very fine grained• Standard PermissionsStandard Permissions

– FilePermissionFilePermission– RuntimePermissionRuntimePermission– SocketPermissionSocketPermission– ……

• Framework permissionsFramework permissions– AdminPermissionAdminPermission– ServicePermissionServicePermission– PackagePermissionPackagePermission– BundlePermissionBundlePermission

• Service PermissionsService Permissions– ConfigurationPermissionConfigurationPermission– EventPermissionEventPermission– ApplicationPermissionApplicationPermission

Fine grained local permissions

Coarse grained system permissions

Deployment AdminDeployment Admin

• Deployment Admin Deployment Admin – Adds new deployment artifact: Deployment Package (DP)Adds new deployment artifact: Deployment Package (DP)– Groups bundles, resources and other artifacts Flexible Groups bundles, resources and other artifacts Flexible

Deployment format for Deployment format for – BundlesBundles– MegletsMeglets– Configuration dataConfiguration data– Custom types with Custom types with Resource ProcessorsResource Processors

• SignedSigned– Tamper proofTamper proof– SecuritySecurity

Deployment AdminDeployment Admin

• Run custom code at installation, updated, and Run custom code at installation, updated, and uninstallationuninstallation– Database conversionDatabase conversion– Installation scriptsInstallation scripts

• Fix Packs, a delta formatFix Packs, a delta format– Reduce download timeReduce download time

• Deployment Packages are first class citizensDeployment Packages are first class citizens

• Extensive information is available to troubleshoot Extensive information is available to troubleshoot

Deployment Admin ServiceDeployment Admin Service

• Deployment Admin provides the Deployment Admin provides the possibility to install and update possibility to install and update Deployment PackagesDeployment Packages

• Deployment Packages areDeployment Packages are– A set of bundles with associated A set of bundles with associated

Resource ProcessorResource Processor– TransactionalTransactional– No sharing with other Deployment No sharing with other Deployment

PackagesPackages• Resource Processors provide the Resource Processors provide the

semantics for the semantics for the bitsbitsof the resources of the resources in the JAR filein the JAR file– Process (install)Process (install)– Drop (uninstall)Drop (uninstall)

• Security based on the permissions Security based on the permissions associated with the signer of the associated with the signer of the Deployment PackageDeployment Package

Depl.Admin

ResourceProcessor

DeploymentAdmin

Rrsrc.Proc.

DmtDataPlugin

EventAdmin

Autoconf


• Deployment PackageDeployment Package– Based on JAR FormatBased on JAR Format

• Manifest describes the Manifest describes the resources and associates resources and associates them with a Resource them with a Resource ProcessorProcessor

• Fix PackagesFix Packages– Provide only updated Provide only updated

contentscontents

manifest.mf

signer.sf

signer.rsa

bundle-A.jar

bundle-B.jar

autoconf.xml

certificates.cer

Global section

Name: bundle-A.jarSHA1-Digest: RTasy&yasi987iasj=Bundle-SymbolicName: com.acme.aBundle-Version: 2.1

Name: certificates.crSHA1-Digest: lkMjUasm87asj&jasloeDP-ResourceProcessor: com.acme.c509

CertificateProcessor

ResourceProcessor


• CustomizersCustomizers• A Deployment Package can A Deployment Package can

contain its own Resource contain its own Resource Processor bundleProcessor bundle

• This customizer is installed and This customizer is installed and started before other bundles in started before other bundles in the Deployment Packagethe Deployment Package

• It registers a Resource It registers a Resource Processor serviceProcessor service

• The Deployment Admin will The Deployment Admin will only allow contents from the only allow contents from the correct DP to be processed by correct DP to be processed by the customizerthe customizer

• The customizer gets access to The customizer gets access to the private data area of its the private data area of its related bundlesrelated bundles

DP

Customizer

Depl.Admin

bundleA

Device ManagementDevice Management

• The basic OSGi architecture is management The basic OSGi architecture is management protocol agnosticprotocol agnostic

– Provides a model where many parties can participateProvides a model where many parties can participate

• What is missing is an abstraction to manage a What is missing is an abstraction to manage a device in detaildevice in detail

• The OMA DM protocol is dominant in the mobile The OMA DM protocol is dominant in the mobile device marketdevice market

– Will be supported by a wide range of devicesWill be supported by a wide range of devices

• The MEG therefore supports the OMA DM The MEG therefore supports the OMA DM management model with the Dmt Admin Servicemanagement model with the Dmt Admin Service

Dmt AdminDmt Admin

• Generic API to manipulate Generic API to manipulate the the Device Management Device Management TreeTree– Single consistent API for Single consistent API for

applications to interact with applications to interact with the configuration of the the configuration of the devicedevice

• Seamless interaction with Seamless interaction with the management of the the management of the native devicenative device– Tree can be partly Tree can be partly

implemented in the native implemented in the native device, partly in Javadevice, partly in Java

.

Device

Battery

Level

OSGi

log

query1

query2

cfg

LogConfigAdmin

Nativecode

Dmt AdminDmt Admin

• Implementation of the tree nodes can be provided Implementation of the tree nodes can be provided by downloadable servicesby downloadable services– Useful for extensions, accessories, optionsUseful for extensions, accessories, options

• Extensive Meta model Extensive Meta model – Provide rich GUIs with very little effortProvide rich GUIs with very little effort– Validation and this reliabilityValidation and this reliability

• TransactionalTransactional– ReliabilityReliability– Partly implementation specificPartly implementation specific

• API based on OMA DMAPI based on OMA DM– Supports other protocolsSupports other protocols

MonitoringMonitoring

• Light weight solution for Light weight solution for bundles to provide status bundles to provide status variables to the management variables to the management systemsystem– Free space, thread usage, Free space, thread usage,

database usagedatabase usage

• Status Variables are mapped Status Variables are mapped to the DMTto the DMT– Provides unified access by the Provides unified access by the

management systemmanagement system

• A schedule can be created to A schedule can be created to query the variables at a regular query the variables at a regular intervalinterval– DebuggingDebugging– Performance tuningPerformance tuning– OptimizingOptimizing

Monitorable

MonitorAdmin

MonitorAdmin

Data Plugin

Any Bundle …

Generic Application ModelGeneric Application Model

• A generic model that is A generic model that is intended to abstract different intended to abstract different application models so they can application models so they can be treated as onebe treated as one– Provides for third party screen Provides for third party screen

managersmanagers• Provides for rich GUIsProvides for rich GUIs

– Icons, help, etc.Icons, help, etc.– Can monitor the state of Can monitor the state of

running instancesrunning instances• Applications can be scheduled Applications can be scheduled

for execution when a specific for execution when a specific event arrivesevent arrives– Calendar notificationCalendar notification

• Interacts with JSR 211 Content Interacts with JSR 211 Content HandlersHandlers

ApplicationModel

Symbian

ScreenManager

MIDP 1.0 MIDP 2.0

Foreign ApplicationsForeign Applications

• MIDP, BREW, Symbian, DOJO, MIDP, BREW, Symbian, DOJO, XLet, Applet, …XLet, Applet, …

• An OSGi Mobile Device is An OSGi Mobile Device is required to provide application required to provide application containers for different containers for different application models.application models.

• The Application Model The Application Model manages these applications manages these applications

• Some models use JavaSome models use Java– Why not provide access to Why not provide access to

OSGi functionalityOSGi functionality• The Foreign Application Model The Foreign Application Model

defines how non-OSGi defines how non-OSGi Applications can access and Applications can access and provide servicesprovide services

– Header usageHeader usage– Access to Framework classAccess to Framework class

MIDP 2.0

org.osgi.applicationorg.osgi.applicationFrameworkFramework

MIDP 1.0 XLet

OSGi Vehicle ArchitectureOSGi Vehicle Architecture

• The OSGi Vehicle Profile shares its architecture The OSGi Vehicle Profile shares its architecture with the Mobile Profilewith the Mobile Profile

• The Vehicle Profile provides specific vehicle The Vehicle Profile provides specific vehicle oriented servicesoriented services

• The Vehicle Profile uses many more of the Core The Vehicle Profile uses many more of the Core Compendium Services because it is more matureCompendium Services because it is more mature

• It is likely the vertical profiles will come closer in the It is likely the vertical profiles will come closer in the futurefuture

Vehicle ProfileVehicle Profile

• Start Level ServiceStart Level Service• URL HandlersURL Handlers• Package Admin ServicePackage Admin Service• Permission Admin ServicePermission Admin Service• Log ServiceLog Service• Http ServiceHttp Service• Device AccessDevice Access• Configuration Admin ServiceConfiguration Admin Service• Metatype(2) ServiceMetatype(2) Service• Preference ServicePreference Service• User Admin ServiceUser Admin Service• Wire Admin ServiceWire Admin Service• IO Connector ServiceIO Connector Service• Declarative ServicesDeclarative Services• Event Admin ServiceEvent Admin Service• Power Management ServicePower Management Service• Diagnostic ServiceDiagnostic Service• Service Tracker UtilityService Tracker Utility• XML Parser UtilityXML Parser Utility• Position UtilityPosition Utility• Measurement and State UtilityMeasurement and State Utility

Power ManagementPower Management

• The power management service The power management service makes power management pluggablemakes power management pluggable

• The system power state can be set The system power state can be set externallyexternally

– Full PowerFull Power– PM ActivePM Active– SuspendSuspend– SleepSleep– Power offPower off

• is mapped to different device power is mapped to different device power statestate

– D0-D3 power statesD0-D3 power states• Power manager can take device Power manager can take device

specific capabilities in considerationspecific capabilities in consideration• An observer bundle can follow the An observer bundle can follow the

transitions in the system and device transitions in the system and device power statepower state

Device Power State

PowerManager

System Power StateListener

Observer

Device PowerImpl

SystemPower

System Power

Device PowerState Listener

• And now for something completely different …And now for something completely different …

Relation to JCPRelation to JCP

• The relation to the JCP is The relation to the JCP is troublesometroublesome

• Several JSRs overlap with JSR Several JSRs overlap with JSR 232232

• JSR 277 ModularizationJSR 277 Modularization– However, long way off from However, long way off from

J2MEJ2ME• JSR 271 MIDP 3.0JSR 271 MIDP 3.0

– Is addressing some of the Is addressing some of the solutions that MEG providessolutions that MEG provides

• JSR 246 OMA DM AccessJSR 246 OMA DM Access– Based on JSR 232 Dmt Admin, Based on JSR 232 Dmt Admin,

but slightly differentbut slightly different– Needs to be mergedNeeds to be merged

• JSR 249/248 MSA CDC/CLDCJSR 249/248 MSA CDC/CLDC– Must select JSR 232 to make Must select JSR 232 to make

MEG viableMEG viable

JSR 232OSGi MEG

JSR 277Modules

JSR 246OMA DM

JSR 271MIDP 3.0

JSR 248/249 MSA

CDC/CLDC

ConclusionConclusion

• The Mobile and Vehicle Profiles are taking advantage of The Mobile and Vehicle Profiles are taking advantage of the powerful OSGi R4 Service Platformthe powerful OSGi R4 Service Platform

• The Mobile Platform focuses on deployment and device The Mobile Platform focuses on deployment and device managementmanagement

– Applications will be foreign applicationsApplications will be foreign applications– Mobile APIs will be derived from JCP JSRsMobile APIs will be derived from JCP JSRs

• The Vehicle Platform provides a more extensive The Vehicle Platform provides a more extensive application environmentapplication environment

• Both platforms provide share more than they differBoth platforms provide share more than they differ• The OSGi Service Platform provides therefore many The OSGi Service Platform provides therefore many

opportunities for applications that can live in both markets.opportunities for applications that can live in both markets.

MEG & VEG Architecture Peter Kriens, CEO, aQute Contents Why a Mobile Specification?Why a Mobile...

Documents

Transcript of MEG & VEG Architecture Peter Kriens, CEO, aQute Contents Why a Mobile Specification?Why a Mobile...