architecture of telematics systems course 3

Architecture of Telematics Systems

Course 3

https://www.continental.com/en

Andreea Grădinaru

Infotainment and Connectivity

Human Machine Interface

https://www.continental.com/en

Internal

Space for Sender Information

1. Introduction

• Telematics Systems

• Continental products

2. Architecture

• Hardware view

• Architecture role

• Best practices

3. Case Study

Agenda

29 September 2019

2Andreea Gradinaru, © Continental Automotive GmbH

Internal


1. Introduction



2. Architecture

• Hardware view


• Best practices

3. Case Study

Agenda

29 September 2019


Internal


What is a Telematics System?

29 September 2019


Internal


• Telecommunication Informatics

• “Telematics is an interdisciplinary field that encompasses telecommunications, vehiculartechnologies, for instance, road transportation, road safety, electrical engineering (sensors,instrumentation, wireless communications, etc.), and computer science (multimedia,internet, etc).” (https://en.wikipedia.org/wiki/Telematics)

• “Vehicle Telemetry – Tapping remotely into a car’s data systems provides lots of usefulservices” (www.economist.com)

Telematics

29 September 2019


• Can be regarded as an evolution of

telemetry (transmit measurements from

the origin to the location of computing

and consumption without affecting

control on the remote objects).

Alexandru Lupu, © Continental Automotive GmbH, 2018

https://en.wikipedia.org/wiki/Telematics

Internal


• Security;

• Safety;

• Navigation;

• Entertainment;

• Diagnosis;

Features

29 September 2019


Internal


• Examples:

✓ Stolen vehicle tracking;

✓ Anti-theft alarm notification;

✓ Remote door (un)lock;

✓ Software updates Over-the-Air;

✓ Secure connection with OEM Backend;

Security

29 September 2019


Figure 1: Automatic crash notification

Internal


• Examples:

✓Automatic crash notification;

✓ Emergency assistance;

✓Vehicular communication system (V2V)

✓ Emergency Electronic Brake Lights;

✓ Cooperative Passing Assist;

✓ Forward Collision Warning;

✓ See-Through Sensor Sharing;

Safety

29 September 2019


Figure 2: GPS vehicle tracking system

Internal


• Examples:

✓ Traffic information – eg: traffic congestion, weather forecast;

✓Geofencing;

✓Point of interest download;

✓Turn by Turn Navigation Assistant;

Navigation

29 September 2019


Figure 3: Representation of Geofence

Internal


• Examples:

✓Music / video downloading;

✓ Internet radio;

✓ Streaming content;

✓ Synchronization with home entertainment library;

✓ Establish high bandwidth connection → share with Head Unit and vehicle passengers;

✓ Video Conferencing;

Entertainment

29 September 2019


Internal


• Examples:

✓ Detailed diagnosis scan – trigger: remote / exceed certain thresholds;

✓ Performance data collection;

✓ Scan Diagnosis Trouble Codes;

Diagnostics

29 September 2019


Internal


https://www.continental-automotive.com/en-gl/Passenger-Cars/Interior/Connectivity-Telematics/Telematics

Telematics System - @ Continental

29 September 2019


https://www.continental-automotive.com/en-gl/Passenger-Cars/Interior/Connectivity-Telematics/Telematics

Internal


1. Introduction



2. Architecture

• Hardware view


• Best practices

3. Case Study

Agenda

29 September 2019


Internal


• Components

• NAD (Network Access Device) → connection to cellular network (voice calls, SMS)

• VuC (Vehicle MicroController) → interface with vehicle bus, process point for

commands and calls;

• GNSS (Global Navigation Satellite System) → provider for location information;

• Advantages: easy implementation of basic functionality, low cost solution;

• Disadvantages: reduced set of features, low profitability, 2G nearing EOL;

Hardware → Legacy & Entry Designs

29 September 2019


TCU

VuC

Features

Vehicle Bus

NAD

Features

Baseband

CAN, LIN, …

GNSS

2G

Figure 4: (Simplified) Representation of

Legacy & Entry Design

Internal


• SoC → 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)

• Advantages: high quality, features;

• Disadvantages: expensive;

Hardware → Mid & High End Designs

29 September 2019


TCU

VuC

CAN, LIN, FlexRay,

MOST, A2B, …SoC

APP

GNSS MDM

Figure 5: (Simplified) Representation of

Mid & High End Design

Internal


Architecture - #1

29 September 2019


Figure 6: Semantic areas of UML 2.5.1

© https://www.omg.org/spec/UML/2.5.1

https://www.omg.org/spec/UML/2.5.1

Internal


Architecture - #2

29 September 2019


Figure 7: Responsibilities of the Software Architecture Role

Internal


1. Use a predefined template for Documentation of Architecture.

• For

• Overall

• Black Box

• White Box

• Interfaces

• Advantages:

• Uniformity (standardized structure);

• Readability (across different teams / projects);

• Disadvantage:

• Customization needed to the specifics of the project (addition / deletion);

• Example: https://arc42.org/download

Best practices - #1

29 September 2019


https://arc42.org/download

Internal


2. Loose coupling between building blocks

• Example:

• Inheritance;

• Resource sharing;

• Temporal;

• Control;

• Reduce coupling – Eg: dependency inversion through interfaces, factories,

dependency injection;

• Advantages: Reusability, portability;

3. Strong cohesion

• Separation of concerns – Eg: MVC (core vs. visualization & persistence;

Best practices - #2

29 September 2019


Internal


4. Keep It Stupid Simple (as brief as possible while as detailed as necessary) while it still is

• Appropriate (understandable) to the target group;

• Maintainable.

5. Respect Single Responsibility principle.

• Eg: Open-Closed principle, encapsulation, abstraction (interfaces, layers, patterns,

models & views);

• Advantages: robustness against change, extensibility, separation, avoid implicit

assumptions regarding implementation;

Best practices - #3

29 September 2019


Internal


6. Use an iterative approach for decomposition.

Best practices - #4

29 September 2019


Use Case

Decomposition

into components

Responsibilities

& Interdependencies

Dynamic

Behaviour

Interfaces

Black Box

View

White Box

View

Requirements

Figure 8: (Simplified) Representation of an iterative approach for Decomposition

Internal


7. Use architectural patterns.

• Examples:

✓ Layers

✓ Microkernel

✓ Pipes & Filters

✓ Client – Server

✓ Master – Slave

✓ Event - bus

Best practices - #5

29 September 2019


Internal


8. Use the 4+1 architectural view.

Best practices - #6

29 September 2019


Figure 9: 4+1 architectural view

Internal


1. Introduction



2. Architecture

• Hardware view

• Recap

• Best practices

3. Case Study

Agenda

29 September 2019


Internal


Q & A

29 September 2019


Internal


End of theory.

Start of practice.

Thank you.

29 September 2019


architecture of telematics systems course 3

Documents