osgi technology in the vehicle - huihoodocs.huihoo.com/osgi/osgi-technology-in-the-vehicle.pdfosgi...

OSGi Technology in the VehicleHans-Ulrich Michel, BMW Group Research and Technology, [email protected]

Agenda

§ Starting point: Importance of Standardization§ Open Infotainment Systems§ How does BMW tackle standardization ?§ In-vehicle OSGi-integration§ BMW ConnectedDrive and Research Vehicle

§ Optimize vehicle system architecture:

- ressource sharing: shared functionality in the network

- dynamic partitioning: flexible integration of functions in ECU´s

§ Increasing Configuration Management

§ Achieve reusability of hw / sw-components in different

product lines

§ Enable “easy” maintenance of components

§ Solve lifecycle mismatch between consumer

hardware / sofware and vehicle

§ Reduction of development time,

Software-Downlaod

Some Resulting Challenges…Manage increase in system complexity, save costs –handle the variety forced by the market in the most efficient way !

Standardization- Open E/E-Architecture

- Open Infotaiment Platform

The Open System Approach at the SEI (Software Engineering Institute)

What is an Open System?

An open system is a collection of interacting software, hardware, and human components

- designed to satisfy stated needs

- with interface specifications of its components that are fully defined available to the public

- maintained according to group consensus

- in which the implementations of the components are conform to the interface specifications

Open Infotainment Platform:Part of an End-to-End System Framework

“Entities”:

§ Customer (with his personal appliances)

§ In-vehicle infotainment platform

§ “Outside” network infrastructure (GSM, GPRS, DVB-T, Bluetooth,

WLAN,..)

§ Backend Server infrastructure (Service-Provider, Content-Provider etc.)

§ “Inside” network infrastructure (CAN, MOST,..) with ECU components

„Open“ on 2 different levels: - e2e-system level

- platform level

“Open” on system and platform level

Some Characteristics of an open e2e-system:

§ Seamless availability of services on different platforms

§ Personalization of services

§ Use of heterogenous networks and backend infrastructure (seamless

roaming between service provider)

Some Characteristics of an open platform:

§ Dynamic extendable functionality on the infotainment platform

§ Reusable library of basic functionality – creation of new app´s

§ Open interface specification that enables different supplier implementations

Standardization Effort

§ Standardize the interfaces between the different,

independent entities

§ Standardize on platform level

More visual

Open Infotainment System: “Outside World”

Service Provider (Navigation)

Service Provider (Parkinfo)

Service Provider(Billing)

Server Plattform (Repository der OSGi-Objekte)

BUNDLE

Service

Device Driver

Package

Comm with external services

(billing etc.)

SERVICE PROVIDER

Customer-Admin

USER

Service Aggregator (CC)

http

(SOAP)

servicesInternetVPN/PPP

I2 I1

James

Open Infotainment System: “Internal World”Other Vehicle Bus Systems

Infotainment Bus

Infotainment Platform

Convenience / Service Framework

Operating System, HAL, Protocoll stack

Hardware Computing Platform (CPU)

Vehicle Bus net External net

JVM , JNI

14

5

AbstractionLayer AbstractionLayer (not OEM specific)(not OEM specific)

I3= I2 +...

1

2

3

4

5

Java App´s (components)

Standard API-Layer I3

Java / Native App´s

Base service Components

Framework Components

2

Phone app client comp

Virtual Most device server

comp

3

Native Code

phonelib

Acess native code

How does BMW tackle standardization ? – Examples

Information for the millions

Third Generation Telematics

Gobal Systems Telematics

OSGi Alliance

Media Oriented Systems Transport

Automotive Open System Architecture

Industry consortium

EU-Projects

Differentiation attributes Manufacturer consensus for interfaces that are not customer relevant

Look at End-2-End service chain

Marketing oriented view

OSGi-PF integration in vehicle system architecture

New application scenarious by using OSGi middleware

Focal Points for requirements and prioritization of OSGi standardization

In-vehicle OSGi integration Case 1: OSGi “Head-Unit”

Bus 1 Bus 2 Bus 4Bus 3

Roles:

-Bus Gateway, Remote Acess Gateway, Service PF with App business logic functionality,

Head Unit – Terminal with complete HMI functionality

In-vehicle OSGi integration Case 1: OSGi “Head-Unit”

Standard On-board supply system

Engine man., gearunit, windows control, anti theft system, centerlock

Vehicle App´s + Multimedia / Telematic

Audio, CD, Phone, …+ Infomanager, News,…

• Separation of stable on-board supply system

• Merging of basic vehicle-app´s with multimedia/telematic world

Advantage:

• One platform (costs)

• Possible reduction of number of ECU´s

• One HMI „for all“ is slightly easier to implement

Riscs:

• High effort in system integration

• Performance

• Startup / Shutdown behaviour

• Safety / security more difficult

In-vehicle OSGi integrationCase 2: OSGi “Advanced ECU”

Bus 1 Bus 2 Bus 4Bus 3

Roles:

Remote Acess Gateway, Service PF with App business logic functionality

In-vehicle OSGi integrationCase 2: OSGi “Advanced ECU”

Standard On-board supply system

Engine man., gearunit, windows control, anti theft system, center lock

Vehicle App´s

• Separation of stable on-board supply system

• Head unit for vehicle application world

• Seperation of multimedia and telematic world

Advantage:

• Clear seperation of stable vehicle functionality from the dynamic multimedia / telematic applications

• Security easier to achieve

Riscs:

• Cost penalty

• HMI communication

• Another ECU....

Multimedia / Telematic

Example New App-Scenario: ECU Software Download

PT-CAN

byteflight

K-CAN

TerminalTSP

Profile.xml:

SW / ECU config.

Headunit

ECU 1

ECU 2

ECU 3

Headunit

Profile.xml:

Key/Value

Softwarepacket configdata,state

data ,..

Profile.xml

ECU 1Profile.xml

ECU 2

-TSP von Server / Flashcard auf Terminal

-- Server hat Masterkopie von TSP

-- SW wird immer von Server zum Fahrzeug abgeglichen (Server entscheidet)

ECU loader

Terminal Agent

Terminal service management

Terminal capabilities synchroniztion

Control Center

TCAP sync

Liste Tapp´s

Sync Delta TSP

Flashcard

BMW ConnectedDrive: Networks Driver, Vehicle and Environment

An Innovative concept which interconnects information, communication and assistance systems inside and outside the vehicle, location based and destination oriented.

- BMW Assist

- BMW Online

- Driver Assistance

BMW Research Vehicle – The Future

Main Goals

• Use OSGi-Platform and implement End-2-End service chain with a software management architecture that enables software download (3GT-based)

• Show different car networking situation:- car to backend server - car to personal appliances, (PDA,mobile) - car to car (Ad-Hoc networking)

BMW Research Vehicle - Architecture

Navigation

iDriveController

Optolyzer(MOST)

IR-Camera

Ethernet

VGA DisplayParkticket Display

BT AP

BluetoothAccess

Point

GPRS

GPRSCSD

Module

DECTPhone

Power Management Unit

14.10.2003 14:30Hanauerstr.ctr. 23618

14.10.2003 14:30Hanauerstr.ctr. 23618

MOSTRing

WLAN

WLANModule

CDPlayer

I/O Unit

(Router)

Head Unit

(Terminal)

AudioSystem

CAN

BMW Research Vehicle – The Future

Head UnitHead Unit

Hardware: P III 700 MHz, 256 MB, 30 GBBluetooth USB


OS: Windows 2000 or Linux


3GT Framework3GT Framework

Java:≥ JDK 1.3.1

Java:≥ JDK 1.3.1

OSGi:ProSyst mBServer 5.1


3GT Terminal3GT Terminal

Remote Management Transport Provisioning


DistributedRegistry

DistributedRegistry

HMI Framework

HMI Framework

SyncMLSyncML

AuthenticationAuthorizationAccounting

AuthenticationAuthorizationAccounting ... ...

Personal Info Manager


Navigation Application


Parkinfo Application

Parkinfo Application ... ...

... ... Remote Management AgentRemote Management Agent

User Application Layer

Terminal Application & Managed Service Layer

Preinstalled (Unmanaged) Bundles

Initial Provisioning Layer, I2

Head UnitHead Unit





3GT Framework3GT Framework

Java:≥ JDK 1.3.1

Java:≥ JDK 1.3.1



3GT Terminal3GT Terminal



DistributedRegistry

DistributedRegistry

HMI Framework

HMI Framework

Navigation Base

Navigation Base

SyncMLSyncML

AuthenticationAuthorizationAccounting

AuthenticationAuthorizationAccounting ... ...





Parkinfo Application

Parkinfo Application ... ...

... ... Remote Management AgentRemote Management Agent

User Application Layer

Terminal Application & Managed Service Layer

Preinstalled (Unmanaged) Bundles

Initial Provisioning Layer, I2IO UnitIO Unit



OS: Windows 2000, IP routing configuration

OS: Windows 2000, IP routing configuration

Java:≥ JDK 1.3.1

Java:≥ JDK 1.3.1



Ad

Hoc

C

omm

unic

atio

n

Ad

Hoc

C

omm

unic

atio

n

Ad

Hoc

Mes

sage

R

epea

ter

Ad

Hoc

Mes

sage

R

epea

ter

Map ServerMap Server

Nav

igat

ion

Con

nect

or

Nav

igat

ion

Con

nect

or

BMW Research Vehicle – ApplicationsInfomanager

Adresses, calender, email, tasks,..

Backend• user account• stored travel data

PC PDAVehicle

Bluetooth

Inte

rnet

Inte

rnet

1. Plan a travel at Home 2. Travel by car• Download travel data / route• Onboard-route guidance

3. Walking to destination• Use PDA with map / walking route

to go from parking lot destination

BMW Research Vehicle – ApplicationsSeamless Navigation

BMW Research Vehicle – ApplicationsSeamless Navigation

BMW Research vehicle – ApplicationsCar-2-Car Communication

Thank you for paying attention

We are open for discussions for open communication platforms and open standards.

Questions?

Backup

OS

AUTOSAR-RTE

function n-1 function n

Basic system functionscore functions, drivers

Hardware

HAL

get_v() v_warn() ...

OS

AUTOSAR-RTE

function n-1 function n

Basic system functionscore functions, drivers

Hardware

HAL

function 1 function 2 ...

AUTOSAR Architecture

OSGi Integration Platform and Autosar -What is possible…

OSGi Framework

MH

P

XletXletXletXlet

WA

P

Jini

UP

nP

Com

mun

icat

ion

Au

tosa

r

Osalet

Osalet

Osalet

Osalet

Osalet

Main Goals Functional Domains

Engine

ChassisSafety(active/passive)

Functional Domains

Multi-media/

Telematics

Man MachineInterface

Body/Comfort

Vehicle´centric‘

Passenger´centric‘

Automotive Open System Architecture (AUTOSAR)Ø Specification of interfacesØ Standardized, openly disclosed interfacesØ HW-independent SW-layerØ Transferability of functionsØ Redundancy activation

AUTOSAR RTE: by specifying interfaces and their communiationmechanisms, the application are decoupled from the underlaying hardware and basic software, enabling the realization of standard library functions

osgi technology in the vehicle - huihoodocs.huihoo.com/osgi/osgi-technology-in-the-vehicle.pdfosgi...

Documents