Tc us and connectivity for automotive telematics
-
date post
13-Sep-2014 -
Category
Automotive
-
view
1.452 -
download
1
description
Transcript of Tc us and connectivity for automotive telematics
Stephen LongdenSpecialist ~ ITS & Telematics, SBD20 September 2010
TCUs and Connectivity for automotive telematics
Telematics@China Tour Guangzhou
Bridging the gap between the
automotive industry
and the real world
Telematics & ITS
Security
Low Speed Impact
Improving society
Reducing the cost of ownership
Technical research
End customer surveys & analysis
Program management and product development
Market intelligence
Strategic business planning
Independent testing &
benchmarking
Some of our customers
Overview
How will vehicle manufacturers
enable connectivity?
What are the barriers to
implementation?Conclusions
Overview
How will vehicle manufacturers
enable connectivity?
What are the barriers to
implementation?Conclusions
Connectivity Barriers
Designing the TCU
Communications approach and data transfer method are key
Connectivity Barriers
Brought-in or built-in connectivity?
?
Connectivity Barriers
Connectivity options in detail...
OEM pays the ongoing costs
User pays the ongoing costs
SIM brought-in, modem built-in
SIM slot
Bluetooth SAP to user’s phone
SIM and modem brought-in
Plug-in modem
User’s phone
Wireless link to user’s phone
Wired link to user’s phone
Bluetooth HFP (data over
voice)
Bluetooth DUN/PAN (tethering)
Bluetooth SPP(side-loading)
Bluetooth MAP(SMS transfer)
Brought-in
SIM and modem built-in
Built-in
Connectivity Barriers
Built-in connectivity provides a robust solution
Connectivity Barriers
Brought-in connectivity is low-cost and the call costs are transferred to the user
Connectivity Barriers
Who is doing what? – embedded modem and SIM
Connectivity Barriers
Who is doing what? – external SIM and modem: Bluetooth DUN/PAN link to phone
Brought-in solution - Bluetooth HFP (data over voice)
Embedded (built-in) solutionCustomer pays for call costs
Connectivity Barriers
There is no single perfect connectivity solution
e.g. 1 e.g. 2
Low cost; user pays ongoing costs
Widely compatible solution
Low data rates are acceptable
Easy for customer to operate
Best communications performance
Robust (safety & security services)
Volume OEM Premium OEM
Connectivity Barriers
Communications speed – faster is not necessarily better
SMS (text)
CSD / CDMA one
(2G)
UMTS / EV-DO /
HSPA / etc(3G)
LTE etc(4G)
FastestSlowest
Overview
How will vehicle manufacturers enable
connectivity?
What are the barriers to implementation? Conclusions
Connectivity Barriers
Connectivity via a brought-in device has potential
compatibility concerns
Bluetooth DUN/PANWired link to phone
Bluetooth MAPBluetooth SAPBluetooth SPPBluetooth HFP
Plug-in modemSIM slot
Embedded (built-in)
Lowest usability rating
Highest usability rating
Phone bill
Connectivity Barriers
2G cut-off?
Long vehicle life meansembedded solutions risk becoming obsolete
Typical lifetime
Typical lifetime
Overview
How will vehicle manufacturers enable
connectivity?
What are the barriers to implementation? Conclusions
Conclusions
• Vehicle manufacturers need to make decisions on communications approach and data transfer method before finalising their TCU design.
• Built-in/embedded or brought-in connectivity is key decision.
• Embedded is secure and reliable, but expensive. Brought-in is low cost but less reliable. Each solution has benefits and risks.
• Vehicle manufacturers are taking both strategies.
• There will be no single solution. It will be a mix according to the services, VM and model.
www.sbd.co.uk
Know what tomorrow brings…