Audi - TCU Project

Prof. Dr. Hans Schumacher IBM e-business Integration Services

IBM Strategy for Telematics Market

Value Chain (simplified)

Content provider

Content aggrega

-tor

Network Provider

OEM Tier-1 Supplier

Tier-2 Supplier

End-to-end Architecture & Solution Concept

IBM contributions

Supplier

Strategic Partnership between IBM and OEM

Solution Components Overview �

Audi Portal

3rd party Content Server

Vehicle

EveryPlave Wireless Gateway

LAN

GSM ISDN

Websphere Application

Server

Internet

WAP GW

MOST Head Unit

TCU

CAN Gateway

Wireless Network

VPN

Technical Project Targets • Development of an end-to-end telematic

prototype: •  Browse external WML/HTML content from Head Unit •  Browse car-internal content from Head Unit and external browser •  Download Java applications into vehicle •  Start and stop Java applications in the vehicle •  Send and receive voice calls

• IBM provided: •  Architecture development •  End-to-end security •  Overall system integration and project management •  Pervasive Computing (PvC) Client Components •  Embedded Java •  Integration of WebSphere Everyplace Server Components •  Telematics Control Unit (TCU) hardware development

The IBM Offering vs. Project Deliverables

Business Consulting Architecture Design System Integration Application Development

Proof of Concept Implementation Application Hosting Outsourcing

Customized e-business Products

The Services

The Building Blocks

Hardware, Middleware, Partners

Application Framework for e-business

Portal Offerings: HW, SW, Services

The Back-End Architecture

Product / Pre-product level Demo level component

Open Communication Standards

IP

WML Browser (UP)

IP UDP/TCP

IP

HTTP Server (Servlets)

Proxy/Firewall (SOCKS - Server)

SecureWay Wireless Client

IP

W@P Gateway

TCP IP

HTTP Server: WML- HTML Content

MOST GSM (CSD) (V110) ISDN LAN, Internet

UDP UDP TCP

HTML Content

UDP WAP Stack

TCP

NetServices NetServices

SOCKS Client

WLP WLP

HTTP HTTP

MOST Phone Control Application

MOST Phone Function Block

Service Management Framework (SMF/OSGI)

TCP

HTML Browser

SOCKS Client

SecureWay Gateway

HTML Browser

Head Unit

Telematics Control Unit

Device Driver Device Driver Device Driver Device

Driver

Gateway Server

Why OSGI for a telematics platform?

Download capability changes the market due to new applications: •  Remote diagnostics •  SW Updates

•  Software problem fixing

•  Hardware problem circumvention

•  Software sales

•  Personalized telematics services

Meets challenges in the automotive industry: •  Majority of innovations involve software •  Product cycles for telematics components are much shorter than the for the vehicle itself •  A flexible software framework yields

  asset protection by shielding the applications from platform changes   ease of migration to newest technology/hardware

IBM EveryPlace Wireless •  Open Communication Standard: TCP/IP •  Optimized Point-to-Point Protocol; Data/Header Compression; Retry suppression •  Data Security (AES, 56bit DES, Triple DES, RC-5) •  Bi-directional (2-Way) Authentication (Two Party Key Distribution Protocol; 2PKDP) •  Dynamic Disconnect-Reconnect (Cellular Networks) •  Supports 10’s of thousands of con-current user’s •  Supports large multitude of wireless networks (dial-in, packet, digital, analog) •  Wireless Gateway High Availability ready

Security in the IBM SecureWay Wireless Familiy

Why was the IBM architecture chosen?

Leadership by Technology: •  Seamless integration of the vehicle into the Internet

•  Highest security where needed (end-to-end encryption, dial-in

protection)

•  Flexibility via modular structure to meet overall requirements •  Scalable from integrated Head Unit to multiple networked Head

Units •  Multiple wireless network support

•  Connectivity to multiple in-vehicle wired or wireless networks •  Remote software management, including operating system updates

•  Remote control of in-car application programs •  Access to car device parameters (on-line, logged, pre-processed)

Why was the IBM architecture chosen?

Leadership by Technology:

•  IBM provides critical components for an actual implementation of this architecture within the constraints of the vehicle environment

•  Key components are implemented in Java

•  IBM offers the back-end architecture and infrastructure to provide the full set of services exploiting the functional base implemented in the vehicle

•  The architecture follows open standards

Project Organization

Contract

Technical Cooperation

Motorola QSSL Subcontractor 3SOFT Becker

Why do an A-sample with IBM?

Seeing is believing… •  Demonstrate the functionality in real hardware and software •  Prove the robustness of critical components like the Java VM, … •  Determine resource consumption (RAM, Flash, Processor, Power, Space,..) •  Analyze performance behavior and critical paths •  Run use cases end-to-end •  Solve open implementation issues •  Build components and building blocks for reuse in the actual product

Work with a reliable partner and an industry leader •  IBM can build on experience with telematics engagements in Korea, Japan, USA, and Europe •  Telematics components are continuously enhanced •  Use IBM as a technology enabler •  Use IBM project management •  Engage a team that stays with the product from initial design through mass deployment

Summary

The Audi telematics A-sample project has provided a platform securely integrating OSGI based components with wireless telephony and and service portal / Internet access and built the base for a worldwide leadership position.

IBM has made essential contributions to this platform in -  the overall architecture -  critical components in the telematics control unit -  project management and integration up to A-sample level -  architecture and components for the Audi Portal