Table of Contents • Telematics products • Software

Bitte decken Sie die schraffierte Fläche mit einem Bild ab.Please cover the shaded area with a picture.

(24,4 x 11,0 cm)

Telematics Architecture

www.continental-corporation.com IIC19 October 2018Alexandru Lupu © Continental AG

Confidential

Table of Contents

19 October 20182Alexandru Lupu© Continental AG

• Telematics products • History, present and trends

• Software Architecture• 4+1 View applied on telematic products

Confidential

Early Telemetry in Automotive

19 October 20183Alexandru Lupu© Continental AG

Confidential

Early Telemetry in Automotive

19 October 20184Alexandru Lupu © Continental AG

Confidential

› “Tele communication Informaticsis the technology of sending, receiving and storing information via telecommunication devices in conjunction with effecting control on remote objects” (wikipedia)

› Telematics can be regarded as an evolution of telemetry (transmission of measurements from the origin to the location of computing and consumption without affecting control on the remote objects)

Definition (1)


Confidential

› In the automotive domain the term evolved to refer to automation in vehicles

› First products targeted emergency warning systems – e.g. automated crashnotification, emergency calls, roadside assistance, concierge (where is the closest gasstation?)

› Door locking/unlocking and stolen vehicle tracking were added as security-targetedfeatures (Boston bomb attack, stolen car had vehicle tracking)

› Remote diagnostics increased safety by early detection of failures

History – initial features


Confidential

› Recent introduction of 3G/4G mobile communication standards and cheap mobile data enabled permanent Internet connection

› Telematic Control Units were the first ECUs to support over-the-air software updates

› Infotainment head units benefitted as well – e.g. navigation data, internet radio streaming, web browsing, etc.

› Integrated WiFi modules allowed Internet connection sharing with passengers

History - Internet


Confidential

Telematics products – external actors


Confidential

› At a very high level telematics systems comprise:

› A processing unit connected to the local system’s control interface – serial port(s), data bus(es)

› A communication device (usually a cellular network device)

› A remote command and control center

› Telematics systems have a large domain of applicability – automotive, utility distribution (gas/electric), road safety, intelligent transportation, military, etc.

Applicability


Confidential

the telematics services can be categorized as below:

• Safety and Security

• Information and Navigation

• Entertainment

• Diagnostics

Types of telematic services


Confidential

› safety services include the automatic crash notification, emergency and medical assistance

› security services include stolen vehicle tracking, anti-theft alarm notification and remote door services

Safety and security


Automatic crash notification GPS vehicle tracking system

Confidential

using the information and navigation services the vehicle occupant can get access to location sensitive information and content

example of services in this category:

• geofencing

• point of interest download

• turn by turn navigation assistance

Information and navigation


Confidential

example of services in this category:

• on demand direct music/video downloading

• internet radio

• streaming content and synchronization with home entertainment library

Entertainment services


Confidential

the diagnostics services include

• remote diagnostics

• performance data collection

• remote DTC scanning

• the TCU can perform detailed diagnostic scans when triggered remotely or when certain key thresholds are crossed

Diagnostics


Confidential

› Emergency calls – regulated (EU eCall, ERA)

› Remote door control

› Stolen Vehicle Tracking, Theft Alarm, Vehicle Locator

› Software Update over CAN

Software OverviewBasic Product Features


Mandatory

Mandatory

Confidential

› Concierge and Roadside Assistance calls, information messages, remote diagnostics

› Geo-fencing (fleet management), navigation assistance (POIs & route download)

› Internet connectivity, WiFi hotspot

› Backend gateway

› OTA Software Updates for TCU and other ECUs

Software OverviewAdvanced Product Features


Confidential

› Core of the smart/connected car

› The TCU is the only ECU able to maintain a permanent connection with vehicle manufacturer’s backends for various scenarios

› Multiple “smart”/”connected” ECUs rather than a single one

› Non-critical ECUs will be required to implement a backend communication mechanism

› Remote software update of the entire vehicle becomes possible

› Faster vehicle data buses allow better integration with the HU

› Improved voice calls quality

› Smart device-like features – navigation/traffic, complete internet access, social media

Trends


Confidential

› Initial telematics ECUs comprised a NAD (Network access device) , a VuC and a GNSS (global-navigation-satellite-system) receiver

› The NAD (Network Attached Device) connects to the cellular network for voice calls and SMS

› The VuC (Vehicle MicroController) handles calls and incoming commands while also interfacing with the vehicle bus (crash notifications, power cycles, diagnostics, software update)

› The GNSS (Global Navigation Satellite System) receiver provides location info to feature node(s)

› This design is still used for entry-level Telematics products

› Pros: easy implementation of basic functionality, low cost solution

› Cons: reduced set of features, low profitability, 2G nearing EOL

Hardware OverviewLegacy and Entry Designs


TCUTCU

VuCVuC

FeaturesFeatures

Vehicle BusVehicle Bus

NADNAD

FeaturesFeatures

BasebandBaseband

CAN, LIN, …

GNSSGNSS

2G

Confidential

TCUTCU

› Expand on the entry level design through a powerful CPU that allows implementation of complex features – Internet connectivity, Over the air software update, remote diagnostics, navigation helpers

› 3G/4G/5G/etc. modems enable faster data speeds

› Extend connectivity options to WiFi, Bluetooth (Low Energy)

› Internet connection sharing with the Head Unit and vehicle passengers

› Wireless workshop diagnostics

› BRR (BroadR-Reach) enables high-quality audio connections to the HU for non-safety critical voice calls, internet radio streaming

› High quality and improved usability, but more expensive solution

Hardware OverviewMid and High End Designs


VuCVuC

CAN, LIN, FlexRay, MOST, A2B, …

SoCSoC

APPAPP

GNSSGNSS MDMMDM

Confidential

Architecture definition

The Software Architecture is the organizational structure of the Software application describing the decomposition in its software subsystems (classes) with their connectivity and interaction mechanisms. It includes details related to principles and decisions used to build the Software.

20 / Alexandru Lupu / 06-03-2018 © Continental AG

Confidential

Why Architecture?

› Specify what needs to be created and how.

› Architecture creates a common understanding between all relevant stake holders about the final product and about the methods. ( Bedouin, Citizen, Martian).

UML (Unified Modeling Language) is a general-purpose, developmental, modeling language in the field of software engineering, that is intended to provide a standard way to visualize the design of a system.


Confidential

Architecture structure (4+1 view)


Software Architectures includes different views

1. Logical View – specify how the end-user functionality will be implemented

2. Physical View – describes what piece of software will run on which hardware.

3. Process View – concepts for performance, concurrency, scalability.

4. Development View –configuration management and deliveries

5. Scenarios – use cases of the final product

Confidential

4.1

10/19/201823

Confidential10/19/2018

24

Confidential

How to create SW Architecure

1. Get all software requirements and system architectu re.

2. Create use cases based on requirements

3. Define or reuse software components that can fulfil l those use cases

4. Describe functional use case realization in logical view

5. Think about non functional requirements and create concepts for them in process view

6. If is not defined by System Architecture define where and how your piece of software will be deployed on hardware in physical view

7. If is not defined by an external team of System integration, define how your software will be integrated and delivered in deployment view.

10/19/201825

Confidential

Requirements

› Most of the requirements are coming from Automotive Domain .

› We have to use embedded systems (they fit best into the auto vehicles)

› We have to use the buses available in auto vehicles (CAN, MOST). There are gateways from HW to SW.There are interfaces defined for each bus. Also drivers and specific binaries.

› We have to use busses available for embedded devices (USB, BlueTooth, I2C, I2S)


Confidential

Requirements - examples

10/19/201827

FMBeC - XXXX

If an automatic MB eCall is triggered, the system shall send the signal <S_SOS_LED_Status> (flashing), which activates the flashing of the LED in the SOS button.

Remark: The 1 Hz flashing frequency is generated by the SOS Button itself and is therefore no requirement for the TCU.

FMBeC - YYYY

The system shall provide the ability to end an automatic eCall by a single press on the MFL end button after the timer <V_KEYLOCK_TIMER_AUTOMATIC_ECALL> has expired.

Confidential

Architecture in Rhapsody - Scenarios


• Scenarios can be created only based on requirements and are depicted in Use case diagrams.

• A use case defines an interactions between a role ("actor") and a system, to achieve a goal. The actor can be a human, an external system.

Confidential

Logical View – Requirements allocation / traceabilit y

› Allocate requirements to Subsystems is done using Object model diagrams.

› Requirements shall be:

- satisfied by subsystems or classes

- traced by use cases


Confidential

Remote door lock/unlock

10/19/201830

Remote UnlockUserUser

Locked CarKeys InCar

Confidential

Logical View – Sequence diagram

› Is the most commonly used diagram to show how objects (may be actors, components , classes, etc. ) interact with each other to satisfy desired behavior

Confidential19 October 2018

32Alexandru Lupu © Continental AG

Remote Door lock

Confidential

Logical view –class diagram in Rhapsody.


bdd [Package] ArchitecturalElements [decomp_TCAM]

ME_TCAM

«Block,ME»

EE_TCAM

«Block,EE»

SW_VUC

«Block,SW»

SW_OTP

«Block,SW»

SW_App

«Block,SW»

SW_BLE

«Block,SW»

SYA_TCAM_VGM::SYA_PhysArch_TCAM_VGM::ArchitecturalElements::TCAM

«Block,SY»

TCAM

«Block,SY»

«derive»

1 1 1 1 1 1

Confidential

Logical View - Activity Diagram

Activity diagram is basically a flow chart to represent the flow from one activity to another activity . The activity can be described as an operation of the system. So the control flow is drawn from one operation to another.

Confidential

Logical View – State chart Diagram

› Depicts a class functionality as a state machine.

› A class may have only one associated state or activity diagram

.

stm [Use Case] providePowerManagement [Power_States_BLE]

Standby

The exact description for the standby is to be checked with the BLE colleagues. This is to prevent potential missunderstandings.

In this context, the standby has the followig feature:- BLE is interruptable via SPI interface- BLE has no bluetooth activity, e.g. advertisement, etc. - BLE consumes as low power as possible

Active

Start_BLE_Activity_Command_Over_SPI

ERA_CallBack_Transition_CMD_Over_SPI

PowerUp_and_Init

PowerDownKL_30_or_BuB_Connection

Confidential

Development View – Model object diagram

› Mapping of SW Blocks to actual files and folders


DAB_ApplicationAdapter1 «SW block»

«ref ine»

DAB Application Adaption

«ref ine»

DAB Core

DAB HMI Access Library

«ref ine»

dabHMIAccessLibrary1 «SW block»

«ref ine»

«ref ine»

DABCore1 «SW block»

«ref ine»

Confidential

Physical View - Deployment diagram

Confidential

Process View – Security (in Diagnostics connection)


Confidential

Questions


Confidential

Backup – System Architecture of telematic products


Confidential

the main components of a telematics system are as follows:

› • telematics control unit

› • telematics network operations system

› • wireless communications infrastructure

› • service provider call center

› • service/content provider

System Architecure


Confidential

Context diagram


bdd [Package] Context [context_physical_TCAM]

itsCarKey:CarKey1

itsCarBattery:CarBattery1

itsSensorBLE:SensorBLE1

itsSmartDeviceBTLE:SmartDeviceBLE1

itsVolvoBackend:VolvoBackend1

itsCallPartner:VoiceCallPartner1

itsWiFiHotspot:WiFiHotspot1

itsWiFiClient:WiFiClient1

itsTPMS_Sensor:TPMS_Sensor1

itsAppleDevice:AppleDevice1

itsSDARS_satellite:SDARS_satellite1itsCEM:CEM1

itsECU_Airbag:ECU_Airbag1

itsEnvironmentalTemperature:EnvironmentalTemperature1

itsOHC:OHC1

itsBackupSpeaker:BackupSpeaker1

itsGNSS_satellite:GNSS_satellite1

Backup battery for TCAM is considered as part of TCAM

TCAM

«Block,SY»

powerOHC

«flow»

ButtonWakeUp:GPIO«flow»

BTLowEnergy:RF_Signal

«flow»

«flow»

WiFi:RF_Signal

«flow»

«flow»

«flow»

GSM:RF_Signal

«flow»

«flow»

OHC:A2B

«flow»

GNSS:RF_Signal«flow»

Speaker:Analog

«flow»

RKE:RF_Signal

«flow»«flow»

SDARSConnector:CoaxSDARS:RF_Signal«flow»

Airbag:GPIO

«flow»

DebugUSB:USB

«flow»

DebugSerial:Serial

«flow»

DebugJTAG:JTAG

«flow»

EnvTemp:Temperature

«flow»

CEM:K_line

«flow»

Infotainment:CAN

VGM:BroadRR

vehicle:Ubatt

«flow»

«flow»

«flow»

itsIHU:IHU1

«flow»

US variant only

Confidential

Internal


ibd [Package] Context

[context_internal_TC AM ]

TCAM

«Block,SY»

itsSW_App_1:SW_App1

AudioManager:tpAC

HAL:tpHAL

OS:osAPI

NADIF:tpNADIF

itsSW_OTP_1:SW_OTP1

VehicleCommService:tpVCS

WiFiAntennaSwitch:GPIO

HAL:tpHAL

AudioController:tpAC

WiFiExternal:Antenna

VoCBaseFrame:VOC_UART

BackupMic:I2S

Reset:GPIO

OS:osAPI

eSIM:SIM

DebugSerial:Serial

NADIF:tpNADIF

Speaker:DAC

VGM:BroadRR

WiFiInternal:Antenna

GNSS:UART

Phone2:Antenna

Phone1:Antenna

ECallInternal:Antenna

DebugUSB:USB

VuC_IPC:INC

itsSW_VUC_1:SW_VUC1

AUDIO_MUTE:GPIO

VoCBaseFrame:VOC_UART

eCallAntennaDiag:ADC

Reset:GPIO

BLE_RTCwakeup:GPIO

eCallAntSwitch:GPIO

Phone1AntennaDiag:ADC

controlPSU:GPIO

OHC:I2C

SoC_IPC:INC

BLE:BLE_VUC_SPI

EnvTemp:ADC

ButtonWakeUp:GPIO

Infotainment:CAN

Airbag:GPIO

RKE:SPI

CEM:Serial

Vbatt:ADC

itsEE_TCAM_1:EE_TCAM1

BuBvariant:GPIO

BuBtemp:Temperature

BuB:Ubatt

ECallInternal:Antenna

Phone1:Antenna

PhoneWiFi:Antenna

WiFiInternal:Antenna

GNSS:Antenna

BTLowEnergy:Antenna

RKE:Antenna

outputSoC:StubInterfaceBlock

outputBLE:StubInterfaceBlock

outputVuC:StubInterfaceBlock

Inputs:StubInterfaceBlock

SDARSamplified:RF_Signal

SDARS:Antenna

itsME_TCAM_1:ME_TCAM1

autoEth:RosenbergerConnector

data:DataConnector20PIN

Outputs:StubInterfaceBlock

power:PowerConnector4PIN

SDARSoutput:RF_Signal

SDARSConnector:Coax

itsSW_BLE_1:SW_BLE1

BLE_RTCwakeup:GPIO

VuC:BLE_VUC_SPI


powerOHC

ButtonWakeUp:GPIO


WiFi:RF_Signal

GSM:RF_Signal

OHC:A2B

GNSS:RF_Signal

Speaker:Analog

RKE:RF_Signal

SDARSConnector:Coax SDARS:RF_Signal

Airbag:GPIO

DebugUSB:USB

DebugSerial:Serial

DebugJTAG:JTAG

EnvTemp:Temperature

CEM:K_line

Infotainment:CAN

VGM:BroadRR

vehicle:Ubatt

Refer to HW/SW Interface Description

BLE Chip

VuC

SoC

US variant

Documents

Table of Contents • Telematics products • Software