IN-VEHICLE CONNECTED

TECHNOLOGY
WHAT'S ON ?
Connectivity Systems
IVI Infotainment OS
Smartphone Solution or Gateway ?
OBD On-board Computer and diagnosis tools
OEM Value chain
Position your system/application ?
How to work with OEMs ?
HMI
Constraints
Regulations
Connected Services
Selection
IHU Specification through an example
Big Data
Value


OS HMI NAV BANDWIDTH
Android, Linux
MeeGo OS MS Auto OS
QNX
B
A
S
E

H
M
I

Automotive Propriatory
UX (high extent of adaptation)

N
A
V

Nokia/NQ
Tomtom
Google

B
D
W

M2M Operators
voda, orange, AT&T
S
E
M
I

TI
Intel
Freescale
SYSTEMS
CONNECTIVITY TYPE
CONNECTED CARS ARCHITECTURES
TCU-based
Infotainment-centric
Provides services, content for both drivers and passengers
Hotspot/LTE/wifi
Automotive and Operator driven

BYOD-based (tethered mode)
Smartphone-centric
Needs to be adapted to local needs and availability
Tethering/pairing technology dependent
Needs to be deployed by service technology companies

CAN based
Dongles
Connectivity
3 COMPUTERS BEHIND 1 WHEEL
OBD computer
Communicates with the cloud to upload information from the car

Smartphone Integration tethered solution
Uses the smartphone as a modem
Replicates the phone screen onto the IVI screen (smartphone is not only a modem but
also the brain

IVI systems
Autonomous and connected
Based on embedded systems and software
A NON-OSMOTIC BARRIER
Separates the On board Computer from the Infotainment Systems (where the visible
value is)
The 2 systems are operating autonomously
Some communication is permitted via the OBD port
Mainly to read values and retrieve information
Vast sets of protocols are available to access (even write) mechatronics information
But each set is different from OEM to OEM
Access Engine Control Unit deals with
Cruise control, transmission, anti-skid, anti-theft
OEMs can provide whichever access they want across the barrier (pending regulations)
but this means long validation and development cycles not including CR management
Can only be considered at very early stage of project

















Online ServiceS
PoGo
Enhanced UI
Fleet & Diagnosis
ServiceS
WEB Access
CONNECTED IVI ARCHITECTURE - CURRENTLY DEPLOYED
Online Services
LOW-END CONNECTED IVI PLATFORM
OBD CONNECTED DONGLES - AFTERMARKET
Whats inside ?

Connected vehicle technology
Diagnostic interfaces (OBD/J1939)
Wifi, Bluetooth, cellular
Accelerometer / GPS


What is it for ?
Usage based insurance (UBI)
Driver and vehicle performance
Diagnostics
Occupant information services


A vehicles self-diagnostic and
reporting ability exposed through
a standardized connector in the
vehicle cabin
Check behind your wheel or under
the carpet !

Required in the US since 1996 for
all cars and light trucks

Defined by a collection of SAE
standards include J1962, J1850,
J1978, J1979,J2012, and J2178-x

Defines a large set of data
elements about the vehicles
engine and emissions
Only a few data elements are widely
supported
OBD II PROTOCOL
5 different physical networks are
represented on the connector
This was simplified to one protocol in 2008
Vehicles may use more than one physical network

SAE Spec J1979 defines a list of Parameter
Identification Numbers (PIDs) used to
request data from a network.

The network is a transaction based
network. Send a PID, get a result.
Other information may appear on the network but
it is for other ECUs and varies from vehicle to
vehicle
10 modes of operation
$01 used to identify what PIDs are available
$02 Freeze Frame Data (information capture
during a fault)
$03 Emissions related confirmed trouble codes
stored.
$04 Used to clear emissions related diagnostic
information.
$05 Oxygen sensor monitor and test results
$06 Request for On-Board Monitoring Test Results
$07 Emission related troubles during current or
last drive cycle
$08 Enable off-board test devices to control an
on-board system
$09 Request VIN and other vehicle information
$0A List permanent trouble codes
SMARTPHONES CONNECTIVITY
Cradle vs. handle
Distraction vs. regulation
Password, LockScreen
BT phone
Tethering vs. Contracting
It is good enough for (free) navigation
But navigation is entering the car through the IVI
Cannot access cars internals
Caveat: OBD + SP + Server
Tried by Verizon in US
Do we use or LTE phones as hotspots in the living room for smart TVs ?

MIRRORLINK SMARTPHONE CONNECTIVITY TO IVI
Consists of a VNC-type architecture whereas the phone replicates its screen onto
infotainment screen
CCC Driven (nokia initiative)
Car connectivity Consortium
Uses RTP and uPnP
Putting the "Mirror" in MirrorLink ... and then the "Link
Only approved apps can work obviously no playing your torrents on the big screen
Who approves it ? How much ?
How does your car communicate when you take your phone out?



ARCHITECTURE MIRROR-LINK
Flow and
Relationship
SW
Architecture
VNC THE SYSTEM BEHIND ML
SMARTPHONES AS A COMPANION APP
OEM specific apps to be available for driver when not driving
Use cases:
Remote access (lock/unlock)
Pre-heat and pre-con the car
Track the car PAYD information
Generic information such as fuel consumption, diagnosis status, driving behavior
Server-Meddling Architecture
car reports condition to secure cloud and smartphone accesses secure cloud
Limited direct communication except for R/C (alarm, lights, windows, lock precon)
The smartphone is a relay of information between driver and car and in-no-way a
Control Unit

COMPANION APP ARCHITECTURE
Online Services
Fleet & Diagnosis
ServiceS
WEB Access
SMARTPHONES FOR COMPANION APP
SEMCOS INITIATIVES & PLATFORMS
CARS SW ENVIRONMENT
OS & HMI
OPERATING SYSTEMS
QNX owned by RIM/Blackberry
QNX OS;
HMI framework supporting HTML5, QT, and other native UI toolsets
SDK for app environments
Support for audio and environment controls
acoustic, noise reduction
hands-free solution, voice recognition
Climate control
Vehicle Diagnosis
Car Resources access (customized only)
Project dependent CustKit
OEM proprietary: needs 3-party agreement


EMBEDDED ARCHITECTURE
The trick is to have access to APIs
Many are restricted to prevent meddling
with car systems
gps info
Environment control
Open in SDK does not mean available
in cars final SW architecture
Not just security but cost of recalls and
customer satisfaction
Tablet on wheels
When buying a car the infotainment
control and comfort count heavily in
the buying decision process

FRAGMENTED ENVIRONMENT GLUED BY APIS
HW HW HW HW HW
. . . . . . . . . . . . . .
Linux WinCE QNX Android
Infotainment Suite / Proprietary GUI
TCPIP over wifi, BT, 3G/4G, hotspot modem, BB
App
Module
App
Module
App
Module
App
Module
Driver
Assistanc
e
Navigation
Maps
. .
App
Module
CanBus / mecatronics
Mini
MM
Engine
TTS/VR
Engine
Driving
Behavi
our
Climat
e
CTRL
Diagnosis Engine
Onboard Computer
Map
dependent
Content
Layers
USE CASE: ONSTAR IN-VEHICLE APIS
I/O commands control for connected file
systems, or IHU FS
Read/Write/WriteB/getRes/deleteFile
Communication
BT profile, watchNetworkConnectivity, watchForData,
Media commands control the vehicles audio
and video playback functionality
Play/Stop/Pause/Sync
Navigation commands control the
functionality of the GPS navigation unit
Destination: Get/Set/watch/Clear
Phone command controls the infotainment
unit's built-in telephone, to make outbound
calls
Dial

System commands allow access to the
infotainment unit's system and app-
handling abilities
Speed/Focus
AppClose/Update
User Interface command allows on-
screen alerts and messages to appear.
showAlert
Utilities command allows for logging of app
exceptions and analytics information.
getLogEvent
Vehicle Info
getPosition (watch, clear)/
getvehicleData, ActiveDeviceConnected,
getVin, getRadioInfo, getvehicleData,
USE CASE: ONSTAR - REMOTE APIS
Consent methods allows for the addition and removal of
consent for select vehicles and accounts
AccountConsent/ VehicleConsent/ FleetConsent/ Revoke
Subscriber Data provides detailed information about
OnStar subscribers, accounts, and supported vehicles
SubscribersInfo, VehicleInfo, VehicleCommands, Vehicle Features
Telemetry methods allow for the use of a vehicle's
telemetry data
TelemetryEnable / TelemetryDisable / History / Callback
Batch methods allow fleet customers to handle multiple
commands with a single requestDestination:
Submit/Status/Results
Vechicle Commands provide services which
communicate with the vehicle to perform an action.
Do things like unlock the doors, start navigation, or sound the alarm all with
the call of a method
StartVehicle, CancelStart, Lock/UnlockDoor, VehicleLocation, TurnByTurn
Route,

USE CASE: OTHERS
OPENCar
Nokia, Pandora, Inrix
API library backed by documentation
App submission guidelines, dashboard and certification process to support third-party developers
Profiles supporting vehicle-specific graphics design/resolutions/capabilities, extensible vehicle telematics,
touch and voice interaction devices/models
Genevi
Pan-industry initiative
More about compliance and
standards than about platform

USE CASE: OPENCAR
The center console is both the brain and heart of the
modern driving experience. Creating a custom, branded
experience leveraging the latest software standards will
transform customer engagement.

Drivers love their smartphones and want the always-
connected, digital entertainment lifestyle that is one touch
away." But simply replicating this experience in the car is
neither safe or properly integrated with the vehicle's data
and controls..

Nokia
A CONTROLLED AND CLOSED ENVIRONMENT
OS and HMI fixes to be rolled out through dedicated bandwidth as ROM OTA
updates
Creates unavailability of the system for some time
Customer/driver expectations must be managed
Automotive in-apps store to be operated by OEMs and integrators to approve
and push new apps/services to drivers:
HMI consistency, usage learning curve
Looking for apps in menu can result in distraction and loss of control
Semi-open market such as android or apple cannot be replicated here as
systems are linked to life-critical systems
Even if controlling breaks or stirring from rogue app is highly unlikely
No-one wants to be the first one to deal with this
OEMS
SERVICES ENABLERS
IN-VEHICLE CONNECTIVITY VALUE CHAIN
HOW TO WORK WITH THE OEM VALUE CHAIN ?

1. Target a model/region the higher up you are in the value chain (internet layer) the more diversified it
is
2. Understand all their suppliers because your product will create dependencies on their systems will
inevitably create conflict with already existing offer OEMs policy is heavily multi-source biased to
allow for contingency
3. OEMS are locked in heavy complex dealer distribution flows and very few solutions (if any) can be
integrated post sales
a. Involves re-training
b. Very expensive
c. Must be bullet proof
4. OEMs are subcontracting all app-store/cloud services to large integrators or directly to Network
operator
a. They understand apps
b. They do not want to cut their margin for you
c. IT/Firewall structure & Security are unnegotiable (what if you have a licensing or distribution
server?)
OEMS ARE BECOMING SERVICE PROVIDERS
HMI INSIGHTS FOR WHEN YOU DEVELOP
AN APP
Manufacturer requirements
Window on automotive values
Needs to be tightly integrated with Look and Feel and to respect ergonomics
Must address ease-of-access requirements (cannot be smartphone-like)
Industry/Regulators regulations
Cannot distract drivers
Huge consequences risk of accidents
Risk of failing validation
Movement-locked features
Needs tight integration with solution provider
Access to HW info is critical and not always disclosed (CANBUS read-access needed)




HMI INSIGHTS FOR WHEN YOU DEVELOP
AN APP
VR/TTS
Already available
Nuance is leading the dance
Camera/sensor based
Already available for detection preventions (rear-view camera)
Brought over for driver monitoring
Gesture and eye-movements
Pupil dilatation (snoozing on the wheel)
Reading the road
Cracks in pavement, sign post recognitions


HMI AND DISTRACTION
There is a dedicated website in the US
http://www.distraction.gov/content/get-the-facts/state-laws.html
Stringency is the key word
California Court Rules Anti-Texting Laws Apply to Checking Maps While Driving Apr 2013
National Highway Traffic Safety Administration has issued its first set of voluntary
guidelines that encourage automobile manufacturers to limit the distraction risk
connected to electronic devices. feb 2013
Guidelines recommend that automakers develop infotainment system that limit the time
drivers have to take their eyes off the road to two seconds for each input (for, say, finding an
address using a navigation system) and 12 seconds to perform an overall task (such as
inputting a destination and routing to it).
NHTSA Recommends Getting Rid of Moving Navigation Maps


HMI IS NOT JUST TOUCHING IT IS ABOUT BEING
PASSIVE
VR/TTS
Already available
Nuance is leading the dance
Camera/sensor based
Already available for detection preventions (rear-view camera)
Brought over for driver monitoring
Gesture and eye-movements
Pupil dilatation (snoozing on the wheel)
Reading/Sensing the road
Cracks in pavement, sign post recognitions


SETS OF CONNECTED SERVICES
Only those requested by OEMs on specific projects
Currently chargeable and offered by OEMs as complimentary and time-limited service
Depend on 3-9s verified internet sources
tied with maps providers
Google, nokia, tomtom
Strongly subjected to marketing considerations
Fuel prices, parking prices and availability, SN buzz
Local legal regulations
Speed traps
Questionable whether connected car will leave room for new killer app types of services
straight away
This is where smartphone platform is interested
THE FIRST BATCH OF SERVICES VS. BANDWIDTH
NEEDS
Transiting through TCU
Smartphone tethering unlikely in
pre-built market due to regulations
and operator consent
After-market tethering is open but much
less lucrative
- although a very good play-ground
- needs integration with navigation apps

THE FULL SET TILL 2020
TECHNICAL CLUSTERING TO ENSURE QOS
Trend is to offer navigation, maps and services as one supplier
Technical updates and synchronization rationale
One OEM uses different suppliers for different model
automotive multi-sourcing policy
Provide many verticals transversally
Multiplication of Standards, semi-proprietary
Tpeg vs HTML
OLR, ULR, Agoras'
Tight with map formats to optimize data transfer while reducing efficiency of mixing
suppliers
Route computation, map matching done on server behind OEM/Supplier firewall
80/20 rule. Most maps updates and live information are needed in high-coverage network
areas
WHAT PEOPLE WANT IN THEIR CARS
4SQ APPLICATION FOR INFOTAINMENT
The 4SQ service shall be integrated within the navigation application
Users will be offered a 4SQ-enabled experience to enhance navigation with
Community-based features
User-generated POIs and information trail
This implementation is for connected infotainment unit and OEMs
Co-marketing: navigation to the power of community
Port smartphone-like features to car built-in environment
Implement essential features to be developed such as TTS, VR and
messaging capabilities


MAJOR COMPONENTS OF SERVICE
Explore POIs
around me
@ destination (only displayed if a route is
available)
Along route (only displayed if a route is
available)\
Ability to select a free search by selecting
top categories and specifying location in a
search box
Check-in
Simple functionality, user clicks and is
checked-in
Function is grayed if user is not logged in
Display Nearby friends
Around me
@ destination (only displayed if a route is
available)
Along route (only displayed if a route is
available)
Function is grayed if user is not logged in


Settings Control Panel
Credentials
Always Show friends Yes/No
Pre-Select categories for POIs (Use top
level categories defined in category xcel
sheets)
Show reviews and Picture Yes/No
FOURSQUARE CONTROL SCREEN
Application in IHU Screen
FOURSQUARE SETTINGS SCREEN
Shows each function defining parameters of services on 1
st
half of screen
Credentials
Set Categories of Interest CoIs
Check-in prompt function (Yes/No)
Always show friends (Yes/No)
Fetch pictures and reviews automatically
Show summary of current status
On 2
nd
half of the screen
Status for all parameters defined above



POI - EXPLORE SCREEN
Showing POIs on map around me, for all categories pre-
selected in settings
Around me
@ destination (only displayed if a route is active)
Along route (only displayed if a route is available)

Select a free search by clicking on categories and by specifying
location in a search box
Eat & Drink, Sleep, Community, Fun
Health, Wellbeing, Shop, Transports
Each top category might suggest dynamically associated
subcategories if available (TBD with 4SQ)
Friends @ location will be displayed as a specific category



IN-VEHICLE POI SEARCH SCREEN
IN-VEHICLE POI DETAILED INFORMATION
Available detailed information of POI listed on POI screen
Each entry shall be expandable to display the full details of each POI as provided
by 4SQ
pics, reviews, map snapshots
Might show reviews of friends or FoF (closer connection) first
check with 4SQ if profile affinity function is available
Add Navigate to button for each entry
Navigates to selected POI
Navigates to friend
Feedback to server when navigating to POI/Friend
Feedback to server when selecting explored POIs
IN-VEHICLE FRIENDS PLACES AROUND
This feature enables users to view friends (and FoF ) favorite places around:
reviewed
starred
created
Friends places appear in a list as for other POIs
All functions as for regular POIs are applicable (if applicable)
Info
Navigate to option




IN-VEHICLE FRIENDS PLACES AROUND
IN-VEHICLE FRIENDS ON ACTIVE MAP
When screen shows ongoing navigation, Foursquare friends shall be displayed
Configurable from settings
Pictures of friends are visible and loaded directly on the map
Need to check HMI color/screen compatibility with photos
provide a generic 4SQ people icon instead of pictures
blue for boys, pink for girls ?
When friend picture (or icon is clicked) the full details for this friend is displayed
Ability to send messages
pre-programmed messages to friend
Can navigate to friend (as waypoint or final destination)



IN-VEHICLE CHECK-IN ONCE AT
DESTINATION
Arrival at the final destination screen + check-in to the 4SQ venue
prompt
You have arrived at destination, would you like to check-in ?
Check-in button appears on the screen for user to activate
If not automated


BIG DATA
THE INTRINSIC VALUE OF CAR
CONNECTIVITY
Location
Devices know where they are and we know where they are too. Its true for the vehicle and its true for
whatever devices drivers and passengers carry around with them.
Context
We can build a picture of the situation at any given time. This may be about who is driving, and how. It
may be about how the car itself is performing. It may be about points of relevant interest along the way.
Connectivity
We can make this information work together to make good things happen for the driver; to strengthen
the bond between the driver and the automotive brand; and to generate and collect revenue for all
contributing businesses.

THE HIDDEN VALUE: TRACING & PROBING-
BIG DATA
Thats where and when the car becomes a smartphone on wheels
Driving behavior and location patterns have a considerable marketing value
Provides customer profiled information to OEMs, dealers and to a larger extent, to market analysis companies
Similar to location-based advertising on mobile phones
Real-time on devices through ads feedback
Will be hidden and asynchronous for cars
Security driven initiative
E111, e-call
Pro-diagnosis, maintain good quality of fleet (and a dealers portfolio is a virtual fleet
Car can self-book itself to garage
Dealer can order parts in advance and optimize stock
Control of metropolitan flows
Guarantees privacy
Scrambled identity for profiling
Drivers confirmation for diagnosis
WHATS NEXT FOR CONNECTED CARS
Within the next three years, every new car will, to a greater or
lesser extent, be a connected car. When most drivers already
have a smart-phone in a cradle on the dashboard, this deeper
connectivity is inevitable. The real question is not if its a
question of how far can we go?
The car is no longer a capsule - for drivers and passengers, the
vehicle must be a safely connected extension of their
environment, for automotive manufacturers and their partners,
connectivity drives a shift from product to service relationships.