OSGi Technology in the Vehicle. Hans-Ulrich Michel, BMW Group Research and Technology,

Transcription

1 OSGi Technology in the Vehicle Hans-Ulrich Michel, BMW Group Research and Technology,

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

3 Some Resulting Challenges Manage increase in system complexity, save costs handle the variety forced by the market in the most efficient way! 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 Standardization - Open E/E-Architecture - Open Infotaiment Platform

4 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

5 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

6 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

7 Standardization Effort Standardize the interfaces between the different, independent entities Standardize on platform level More visual

8 Open Infotainment System: Outside World I2 I1 Service Aggregator (CC) Customer- Admin Comm with external services (billing etc.) Service Provider (Parkinfo) USER SERVICE PROVIDER James Internet VPN/PPP services Server Plattform (Repository der OSGi-Objekte) BUNDLE Service Device Driver Package http (SOAP) Service Provider (Navigation) Service Provider (Billing)

9 Open Infotainment System: Internal World Other Vehicle Bus Systems Infotainment Bus Infotainment Platform Native Code phonelib 3 Acess native code 1 Convenience / Service Framework Operating System, HAL, Protocoll stack Hardware Computing Platform (CPU) Vehicle Bus net Phone app client comp JVM, JNI Virtual Most device server comp 4 External net 2 5 I3= I AbstractionLayer (not OEM specific) Java App s (components) Standard API-Layer I3 Java / Native App s Base service Components Framework Components

10 How does BMW tackle standardization? Examples Industry consortium OSGi Alliance Information for the millions Media Oriented Systems Transport Third Generation Telematics Automotive Open System Architecture Gobal Systems Telematics EU-Projects

11 Focal Points for requirements and prioritization of OSGi standardization Marketing oriented view OSGi-PF integration in vehicle system architecture Look at End-2-End service chain New application scenarious by using OSGi middleware Differentiation attributes Manufacturer consensus for interfaces that are not customer relevant

12 In-vehicle OSGi integration Case 1: OSGi Head-Unit Bus 1 Bus 2 Bus 3 Bus 4 Roles: -Bus Gateway, Remote Acess Gateway, Service PF with App business logic functionality, Head Unit Terminal with complete HMI functionality

13 In-vehicle OSGi integration Case 1: OSGi Head-Unit Standard On-board supply system Engine man., gearunit, windows control, anti theft system, center lock 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

14 In-vehicle OSGi integration Case 2: OSGi Advanced ECU Bus 1 Bus 2 Bus 3 Bus 4 Roles: Remote Acess Gateway, Service PF with App business logic functionality

15 In-vehicle OSGi integration Case 2: OSGi Advanced ECU Standard On-board supply system Engine man., gearunit, windows control, anti theft system, center lock Vehicle App s Multimedia / Telematic 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...

16 Example New App-Scenario: ECU Software Download Terminal TSP Profile.xml: SW / ECU config. ECU 1 K-CAN Headunit TCAP sync Headunit ECU 2 ECU 3 PT-CAN byteflight ECU loader Terminal Agent Liste Tapp s Control Center Sync Delta TSP Flashcard Profile.xml: Key/Value Softwarepacket configdata,state data,.. Terminal service management Terminal capabilities synchroniztion ECU 1 Profile.xml ECU 2 Profile.xml -TSP von Server / Flashcard auf Terminal -- Server hat Masterkopie von TSP -- SW wird immer von Server zum Fahrzeug abgeglichen (Server entscheidet)

17 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

18 BMW Research Vehicle The Future

19 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)

20 BMW Research Vehicle - Architecture DECT Phone CD Player IR-Camera GPRS CSD Module GPRS WLAN Module WLAN Bluetooth Access Point BT AP Parkticket Display :30 Hanauerstr. ctr VGA Display idrive Controller MOST Ring CAN Optolyzer (MOST) I/O Unit (Router) Ethernet Head Unit (Terminal) Navigation Audio System Power Management Unit

21 BMW Research Vehicle The Future

22 Head Head Unit Unit 3GT 3GT Framework Framework... Parkinfo Parkinfo Application Application HMI HMI Framework Framework Navigation Navigation Application Application Remote Remote Management Management Agent Agent... Personal Personal Info Info Manager Manager... SyncML SyncML User Application Layer Terminal Application & Managed Service Layer Initial Provisioning Layer, I2 3GT 3GT Terminal Terminal Remote Remote Management Management Transport Transport Provisioning Provisioning Distributed Distributed Registry Registry Authentication Authentication... Authorization Authorization Accounting Accounting Preinstalled (Unmanaged) Bundles OSGi: OSGi: ProSyst ProSyst mbserver mbserver Java: Java: JDK JDK OS: OS: Windows Windows or or Linux Linux Hardware: Hardware: P P III III MHz, MHz, MB, MB, GB GB Bluetooth Bluetooth USB USB

23 Head Head Unit Unit 3GT 3GT Framework Framework... Parkinfo Parkinfo Navigation Navigation Personal Personal Info Info Application Application Application Application Manager Manager... HMI HMI Navigation Navigation SyncML SyncML Framewor Framewor Base Base k Remote k Remote Management Management Agent Agent User Application Layer Terminal Application & Managed Service Layer Initial IO IO Unit Provisioning Unit Layer, I2 3GT 3GT Terminal Terminal Remote Remote Management Management Transport Transport Provisioning Provisioning OSGi: OSGi: ProSyst ProSyst mbserver mbserver Java: Java: JDK JDK OS: OS: Windows Windows or or Linux Linux Distributed Distributed Registry Registry Hardware: Hardware: P P III III MHz, MHz, MB, MB, GB GB Bluetooth Bluetooth USB USB Authentication Authentication... Authorization Authorization Accounting Accounting Ad Ad Hoc Hoc Communication Communication Ad Hoc Message Repeater Preinstalled (Unmanaged) Bundles OSGi: OSGi: ProSyst ProSyst mbserver mbserver Java: Java: JDK JDK Ad Hoc Message Repeater Navigation Navigation Connector Connector OS: OS: Windows Windows 2000, 2000, IP IP routing routing configuration configuration Hardware: Hardware: P P III III MHz, MHz, MB, MB, GB GB Bluetooth Bluetooth USB USB Map Map Server Server

24 BMW Research Vehicle Applications Infomanager Adresses, calender, , tasks,..

25 BMW Research Vehicle Applications Seamless Navigation Backend user account stored travel data Internet Internet Bluetooth PC Vehicle 1. Plan a travel at Home 2. Travel by car Download travel data / route Onboard-route guidance PDA 3. Walking to destination Use PDA with map / walking route to go from parking lot destination

26 BMW Research Vehicle Applications Seamless Navigation

27 BMW Research Vehicle Applications Seamless Navigation

28 BMW Research vehicle Applications Car-2-Car Communication

29 BMW Research vehicle Applications Car-2-Car Communication

30 Thank you for paying attention

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

32 Questions?

33 Backup

34 AUTOSAR Architecture get_v() v_warn()... function n-1 function n function 1 function 2... function n-1 function n AUTOSAR-RTE AUTOSAR-RTE Basic system functions core functions, drivers HAL Basic system functions core functions, drivers HAL OS Hardware OS Hardware

35 OSGi Integration Platform and Autosar - What is possible MHP Xlet Xlet Xlet Xlet WAP Jini UPnP Communication Autosar Osalet Osalet Osalet Osalet Osalet OSGi Framework

36 Main Goals Functional Domains Automotive Open System Architecture (AUTOSAR) Specification of interfaces Standardized, openly disclosed interfaces Vehicle centric Engine HW-independent SW-layer Transferability of functions Redundancy activation AUTOSAR RTE: by specifying interfaces and their communiation mechanisms, the application are decoupled from the underlaying hardware and basic software, enabling the realization of standard library functions Chassis Multimedia/ Telematics Functional Domains Body/ Comfort Safety (active/ passive) Man Machine Interface Passenger centric