Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

2005 OSGi Alliance Status - John Barr, Ph.D., Past President, OSGi Alliance; Director, Standards Realization, Motorola


Published on

OSGi World Congress 2005

Published in: Technology
  • Be the first to comment

  • Be the first to like this

2005 OSGi Alliance Status - John Barr, Ph.D., Past President, OSGi Alliance; Director, Standards Realization, Motorola

  1. 1. 2005 OSGi Alliance Status John R. Barr, Ph.D. Past President, OSGi Alliance Chair OSGi World Congress
  2. 2. OSGi AllianceOSGi Alliance •• The OSGi Alliance is an open organizationThe OSGi Alliance is an open organization –– Established in 1999, currently 44+ membersEstablished in 1999, currently 44+ members –– Membership spans many industriesMembership spans many industries –– Voting members treated equallyVoting members treated equally –– Membership information available atMembership information available at OSGi Alliance IT Providers ISV Device Manufacturers Service Providers Developers Auto Makers Solution Providers Others
  3. 3. History of OSGi AllianceHistory of OSGi Alliance •• Companies start work on Java Embedded Server in 1998Companies start work on Java Embedded Server in 1998 •• Open Services Gateway Initiative launched in March 1999Open Services Gateway Initiative launched in March 1999 •• First Member Meeting: LondonFirst Member Meeting: London –– May 1999May 1999 •• Specification Releases:Specification Releases: –– R1R1 –– May 2000 (JES Framework)May 2000 (JES Framework) –– R2R2 –– October 2001 (Gateway Management)October 2001 (Gateway Management) –– R3R3 –– March 2003 (Automotive)March 2003 (Automotive) –– R4R4 -- October 2005 (Core + Mobile + Vehicle)October 2005 (Core + Mobile + Vehicle) •• OSGi World Congress:OSGi World Congress: –– StockholmStockholm –– 2424--27 September 200227 September 2002 –– DDüüsseldorfsseldorf –– 2121--24 October 200324 October 2003 –– BarcelonaBarcelona –– 1111--15 October 200415 October 2004 –– ParisParis -- 1111--14 October 200514 October 2005
  4. 4. Market VisionMarket Vision •• More devices are intelligent and adaptableMore devices are intelligent and adaptable –– Automotive electronics /Automotive electronics / telematicstelematics –– SmartphonesSmartphones –– Even highEven high--end home theater remote controlsend home theater remote controls •• Data networks have become ubiquitousData networks have become ubiquitous •• All of these components need increasingly complexAll of these components need increasingly complex softwaresoftware
  5. 5. Market OpportunityMarket Opportunity •• OSGi technology:OSGi technology: –– Makes software components easier to manageMakes software components easier to manage –– Enables portability of valueEnables portability of value--added services acrossadded services across markets and devicesmarkets and devices –– Enables desired business modelEnables desired business model Multi-Vendor, Open Walled Garden
  6. 6. OSGi Technology In A NutshellOSGi Technology In A Nutshell What is OSGi technology?What is OSGi technology? An enterpriseAn enterprise--class execution environment for dynamicallyclass execution environment for dynamically deploying and managing software components that deliverdeploying and managing software components that deliver services and applications to networked devicesservices and applications to networked devices
  7. 7. OSGi Service Platform RoadmapOSGi Service Platform Roadmap 2000 2001 2003 2005 Home&IndustrialAutomation Vehicle Mobile • Framework • HTTP • Log • Device Access R1 • Package Admin • Configuration Admin • Permission Admin • User Admin • Preferences • Meta Type • Service Tracker R2 • UPnP • Initial Provisioning • Name Space • Start Level • IO Connector • Wire Admin • XML Parser • Measurement and State • Position • Execution Environment R3 • Application Tracker • Signed Bundles • Declarative Services • Power Management • Device Management • Security Policies • UPnP Exporter • Diagnostic/Monitoring • Framework Layering R4
  8. 8. Why Standards & Not Proprietary?Why Standards & Not Proprietary? •• Reduce riskReduce risk –– Avoid single vendor dependenceAvoid single vendor dependence –– Increases interoperabilityIncreases interoperability •• FlexibilityFlexibility –– Multiple sources / suppliersMultiple sources / suppliers –– Switching costs reducedSwitching costs reduced •• Durability of solutionDurability of solution –– Multiple industry stakeholders foster long term investmentMultiple industry stakeholders foster long term investment –– Single vendor approaches often abandoned more quicklySingle vendor approaches often abandoned more quickly •• QualityQuality –– Industry collaboration increases quality of the standardIndustry collaboration increases quality of the standard –– Competition between sources / suppliers increases quality of proCompetition between sources / suppliers increases quality of products andducts and servicesservices
  9. 9. WhatWhat’’s In It For You?s In It For You? HOMEAUTO OFFICE MOBILE Service Providers Content & Media Providers Application Developers Manufacturers IT Providers Cost Savings Increased Speed to Market Strategic Market Differentiation Increased Revenue Consolidated Support OSGi Alliance INPUT AND ACCESS ACROSS THE ENTIRE VALUE CHAIN
  10. 10. Key Technical BenefitsKey Technical Benefits •• Full local and remote application lifecycleFull local and remote application lifecycle management (manage heaps of code)management (manage heaps of code) •• Standardized serviceStandardized service--oriented componentoriented component architecturearchitecture •• Deliver lowest cost Bill Of Materials for an open,Deliver lowest cost Bill Of Materials for an open, portable Serviceportable Service--Oriented ArchitectureOriented Architecture •• Dynamic discovery and binding of softwareDynamic discovery and binding of software components during runtimecomponents during runtime •• Enterprise class runtime for embedded devicesEnterprise class runtime for embedded devices •• Accommodates desired policy and security modelAccommodates desired policy and security model
  11. 11. Position In The EcosystemPosition In The Ecosystem Semiconductor & OS Providers Platform & System Integrators Device Manufacturers Enterprises Solution Integrators, ISVs “In-to” - Pre-Design / Embedded “On-to” - Aftermarket / Download Post install Platform, Apps & Data Pre-enable new devices Service Providers Solution Integrators, ISVs “On-to” - Aftermarket / Download Post install Apps & Data Solutions Solutions Enablement Composition Client Platform (into) Client Platform (onto) Applications & Services Applications & Services OSGi Service Platform OSGi Service Platform
  12. 12. OSGi AdoptionOSGi Adoption •• OSGiOSGi member company applicationsmember company applications –– Connected HomeConnected Home –– Automotive Infotainment/TelematicsAutomotive Infotainment/Telematics –– Mobile/ServiceMobile/Service ProvisioningProvisioning •• EUEU--projectsprojects –– TEAHATEAHA –– CENELECCENELEC SmartHouseSmartHouse Code ofCode of PracticePractice –– ERTICO 3GT and GSTERTICO 3GT and GST •• OSGi UsersOSGi Users‘‘ Forum/GroupsForum/Groups –– Japan, France, Korea (...)Japan, France, Korea (...) •• LiaisonsLiaisons with other organizationswith other organizations –– JCP (JavaJCP (Java Community ProcessCommunity Process)) –– HGI (HGI (Home GatewayHome Gateway Initiative)Initiative) –– ERTICO GST (Automotive/Telematics)ERTICO GST (Automotive/Telematics) –– OMA (Open MobileOMA (Open Mobile AllianceAlliance)) Deployment Fact SheetDeployment Fact Sheet onon wwwwww..osgiosgi..orgorg
  13. 13. R4 ReleaseR4 Release •• Tuesday, the OSGi Alliance announced the officialTuesday, the OSGi Alliance announced the official release of OSGi Service Platform R4release of OSGi Service Platform R4 –– R4 Core Specification (R4 Core Specification (pdfpdf)) –– R4 Core Companion Code (jar)R4 Core Companion Code (jar) –– R4 Service Compendium Specification (R4 Service Compendium Specification (pdfpdf)) –– R4 Service Compendium Companion Code (jar)R4 Service Compendium Companion Code (jar) –– R4 Minimum Execution Environment (jar)R4 Minimum Execution Environment (jar) –– R4 Foundation Execution Environment (jar)R4 Foundation Execution Environment (jar) •• Available atAvailable at
  14. 14. Soon to be released for R4Soon to be released for R4 •• OSGi Service Platform, Mobile SpecificationOSGi Service Platform, Mobile Specification –– Submitted to JCP for adoption as JSRSubmitted to JCP for adoption as JSR--232232 ““Mobile OperationalMobile Operational ManagementManagement”” •• Jon Bostrom, Nokia, andJon Bostrom, Nokia, and VenkatVenkat AmirisettyAmirisetty, Motorola, are co, Motorola, are co--specificationspecification leads for JSRleads for JSR--232.232. •• Early Draft Review started 7 October 2005Early Draft Review started 7 October 2005 –– Target Release Date: 1Q2006Target Release Date: 1Q2006 •• OSGi Service Platform, Vehicle SpecificationOSGi Service Platform, Vehicle Specification –– HansHans--Ulrich Michel, BMW, and OlivierUlrich Michel, BMW, and Olivier PavPavéé, Siemens AG, are, Siemens AG, are coco--chairs of the Vehicle Expert Groupchairs of the Vehicle Expert Group –– Liaison with ERTICO Global System Telematics (GST) ProjectLiaison with ERTICO Global System Telematics (GST) Project –– Target Release Date: 2Q2006Target Release Date: 2Q2006
  15. 15. IBM Keynote SpeakerIBM Keynote Speaker •• CraigCraig HaymanHayman, Vice President, Development &, Vice President, Development & Technical Support, Workplace, Portal &Technical Support, Workplace, Portal & Collaboration Software Division, IBMCollaboration Software Division, IBM –– Responsible for delivery of:Responsible for delivery of: •• IBMIBM’’s Client Technologys Client Technology •• VoiceVoice •• RFIDRFID •• Industry SolutionsIndustry Solutions –– XML standard for objects in transactional systemsXML standard for objects in transactional systems –– WebSphereWebSphere Studio line of productsStudio line of products