OSGi World Congress 2004

1. © copyright 2004 by OSGi Alliance All rights reserved.
Building Global Telematics System by
using OSGi

2. © copyright 2004 by OSGi Alliance. All rights reserved.
Content
• Introduction to GST
• Main results of the GST requirement
phase (WP2)
• Why does GST need OSGi?

3. © copyright 2004 by OSGi Alliance. All rights reserved.
Introduction to GST – The project
• (G)lobal (S)ystems for (T)elematics –
integrated project from the EC's 6FP (DG
INFSO)
• http://www.gstproject.org/
• Coordinated by Ertico
• GST Partners: car manufacturers, 1st tier
(terminal) suppliers, system integrators,
middleware developers network operators,
insurance companies, public authorities, etc.

4. © copyright 2004 by OSGi Alliance. All rights reserved.
Introduction to GST – Project mission
• Mission - to create an environment in which
innovative telematics services can be
developed and delivered cost effectively and
hence to increase the range of economic
telematics services available to manufacturers
and consumers.
• Philosophy - Open Systems are preferred to
proprietary ones. Specifically, telematics
platforms should conform to a set of openly
available interface specifications in order to
create a thriving market for telematics
applications.

5. © copyright 2004 by OSGi Alliance. All rights reserved.
Introduction to GST – Project vision
Service
Provider
Open
Telematics
Market
Service
Provider
Service
Provider
End
User
End
User
End
User
Ease of Market Access
Ease of Market Access
Avoid unduly high
barriers of market entry
Freedom of choice in
service consumption

6. © copyright 2004 by OSGi Alliance. All rights reserved.
verification
User requirement
definition phase
Validation requirements
and planning
Architecture and
specification phase
Systems specification
phase
Software specification
phase
Software design phase
Coding
Software integration
tests
Software verification
tests
Systems integration
tests
Architecture validation
phase
validation
validation
verification
verification
test sites
WP 2
WP 3
WP 4
WP 4
WP 5
WP 6Prototype and system
validation phase
Operational GST-
Concept Description
Introduction to GST – Project status

7. © copyright 2004 by OSGi Alliance. All rights reserved.
Introduction to GST – Project structure
• Open Systems
• Security
• S-Pay
• Certecs
• Safety channel
• Rescue
• EFCD (Electronic Floating Point Data)

8. © copyright 2004 by OSGi Alliance. All rights reserved.
Results WP2 – GST Decomposition
GST
System Realization System
Operational
System
Content
Centre Service
Centre
Control
Centre
Client
Device
Development
Centre
Certification
Centre

9. © copyright 2004 by OSGi Alliance. All rights reserved.
Operational
System
Realization
System
Service Developer
Certification Authority
Vehicle Manufacturer
Stakeholder Organisation
Test Laboratory
Existing Standards and
Specifications
Equipment Manufacturer
Communication
Infrastructure
Trust Centre/
Certificate Provider
End User
Content Centre User
Service Centre User
Control Centre User
User Credential Manager
Public Service Access Point
Vehicle
Commercial
System
The world in
which the system
Operates
The world in
which the system
is Created
The commercial
environment in
Which the system
exists
Results WP2 – GST Context

10. © copyright 2004 by OSGi Alliance. All rights reserved.
Operational System
Realization System
Entities in each system
Interact with each other
to animate it
Content Centre
Service Centre
Client System
Service Application
Telematic Control Unit
I/O Device
Vehicle Management Centre
OEM Software
Repository
Billing Centre
Service Platform
Control Centre
Payment Centre Payment Service Centre
Clearing CentreUser Credential
Store
Software Repository
Development Centre
Certification Centre
GST Standards
and specifications
Commercial
System
Results WP2 – GST System

11. © copyright 2004 by OSGi Alliance. All rights reserved.
Results WP2 – HL Architecture
id OS HL Architecture
Client System
Serv ice Centre
(SC)
Client System
(CS)
Authentication &
Authorization
(AA)
User
Subscriptions
(USubscr)
Client System
Management
(CSMgmt)
Billing Centre
(BC)
Payment Centre
(PC)
Vehicle
(Vehicle)
End-User
I/O Dev ice (IO)
Telematics
Control Unit
(TCU)
«RP»
«RP»
«RP»
«RP»
«RP»
«RP»
«RP» «RP»
«RP»
«RP»
«RP»
«RP»
«RP»
«RP»
«RP»
«RP»
«RP»
«RP»
«RP»
«RP»

12. © copyright 2004 by OSGi Alliance. All rights reserved.
WP2 Results – Use cases (examples)
• Service Deployment
• Service Fulfilment
• Check for Resources
• Service Provisioning
• Authentication
• Service Payment
• End-User Authentication
• Service Platform
Authentication
• Client System Discovery
• Service Certification
• Content Delivery
• Client System Management
• Service Development
• User Log-in
• Application Download
• Control Centre Discovery
• Authorization
• User Authorization
• Platform Authorization
• Service Authorization

13. © copyright 2004 by OSGi Alliance. All rights reserved.
WP2 Results – Requirement groups
• Service Deployment
• Client System
Management
• Service Fulfilment
• Content Delivery
• Data Handling
• Billing and Payment
• Development
• Certification
• Security
• Communications
• Off-line Operations
• Performance and
Scalability
• User Interface
• General

14. © copyright 2004 by OSGi Alliance. All rights reserved.
WP2 Results - Service deployment (Reqs.)
• The Control Centre should be able to offer
services from multiple Service Centres at the
same time
• A Service Centre should be able to deploy a
service application on any GST compliant
Control Centre
• Standard packaging format for service
deployment should be defined
• A Service must be registered in the Control
Centre, identified, and managed separately
from an application implementing it

15. © copyright 2004 by OSGi Alliance. All rights reserved.
WP2 Results - Client system management
(Reqs.)
• Any GST-compliant vehicle shall be able to
connect to any GST-compliant Control Centre and
use services from there
• Standard interface/protocol for discovery and
registration of a Client System in a Control Centre
• Diagnostics of the Client System must be
supported
• Life-cycle management of the Service
Applications must be supported
• The Client System must be remotely manageable

16. © copyright 2004 by OSGi Alliance. All rights reserved.
WP2 Results - Service fulfilment (Reqs.)
• The Service Platform must keep information about
the current version of all installed Service
Applications and System Modules
• The Service Platform must provide a way for
describing the dependencies between the Service
Applications
• Downloading services on the Client System over
various interfaces (e.g. over-the-air like WiFi,
GPRS, Bluetooth or over USB, CD, DVD etc)
• Vehicle and user profiles must be supported
• Matching the available resources of the Client
System against the application’s requirements

17. © copyright 2004 by OSGi Alliance. All rights reserved.
WP2 Results – General (Reqs.)
• The End-User shall be able to configure via
external devices service applications installed
on the Client System.
• Persistence Service for user data storage must
be available
• Transaction mechanisms for the critical
operations
• Update of the Service Platform must be
supported
• The Client System must support multiple users

18. © copyright 2004 by OSGi Alliance. All rights reserved.
GST and OSGi – the need of open
standards
• The goal of GST is to define defines an
open environment for the delivery of
telematics services
• This openness can be achieved by
specifying:
– Protocols, data structures and packaging
formats
– Abstract interfaces
– Concrete interfaces / component models

19. © copyright 2004 by OSGi Alliance. All rights reserved.
GST and OSGi – the need of specified
component model
• Simplifies the development and reduces the
costs
• Provides better compatibility of the modules
• Reduces the redundancy of the code
• Uses the resources of the client devices
efficiently
• OSGi is the most appropriate component model
available today