C03 Architecture of TelematicsSystems

Architecture of Telematics Systems
Course 3
Andreea Grădinaru
https://www.continental.com/en Infotainment and Connectivity
Human Machine Interface
Agenda
1. Introduction
• Telematics Systems
• Continental products
2. Architecture
• Hardware view
• Architecture role
• Best practices
3. Case Study
Space for Sender Information 29 September 2019

Internal Andreea Gradinaru, © Continental Automotive GmbH 2
Agenda
1. Introduction
2. Architecture
• Hardware view
• Best practices
3. Case Study

What is a Telematics System?

Telematics
• Telecommunication Informatics
• “Telematics is an interdisciplinary field that encompasses telecommunications, vehicular
technologies, 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 useful
services” (www.economist.com)
• 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

Features
• Security;
• Safety;
• Navigation;
• Entertainment;
• Diagnosis;

Security
• Examples:
✓ Stolen vehicle tracking;
✓ Anti-theft alarm notification;
✓ Remote door (un)lock;
✓ Software updates Over-the-Air;
✓ Secure connection with OEM Backend;
Figure 1: Automatic crash notification

Safety
• Examples:
✓Automatic crash notification;
✓ Emergency assistance;
✓Vehicular communication system (V2V)
✓ Emergency Electronic Brake Lights;
✓ Cooperative Passing Assist;
✓ Forward Collision Warning;
✓ See-Through Sensor Sharing;
Figure 2: GPS vehicle tracking system

Navigation
• Examples:
✓ Traffic information – eg: traffic congestion, weather forecast;
✓Geofencing;
✓Point of interest download;
✓Turn by Turn Navigation Assistant;
Figure 3: Representation of Geofence

Entertainment
• 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;

Diagnostics
• Examples:
✓ Detailed diagnosis scan – trigger: remote / exceed certain thresholds;
✓ Performance data collection;
✓ Scan Diagnosis Trouble Codes;

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

Agenda
1. Introduction
2. Architecture
• Hardware view
• Best practices
3. Case Study

Hardware → Legacy & Entry Designs
• 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;
TCU
CAN, LIN, …
VuC NAD 2G
Vehicle Bus Baseband
Features
Features
GNSS
Figure 4: (Simplified) Representation of
Legacy & Entry Design

Hardware → Mid & High End Designs
• 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;
TCU
CAN, LIN, FlexRay, SoC
MOST, A2B, …
GNSS MDM
VuC
APP
Figure 5: (Simplified) Representation of

Mid & High End Design

Architecture - #1
Figure 6: Semantic areas of UML 2.5.1

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

Architecture - #2
Figure 7: Responsibilities of the Software Architecture Role

Best practices - #1
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 - #2
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 - #3
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 - #4
6. Use an iterative approach for decomposition.
Requirements Decomposition
into components
Use Case
Responsibilities Dynamic
Black Box & Interdependencies Behaviour
View
White Box Interfaces

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

Best practices - #5
7. Use architectural patterns.

• Examples:
✓ Layers
✓ Microkernel
✓ Pipes & Filters
✓ Client – Server
✓ Master – Slave
✓ Event - bus

Best practices - #6
8. Use the 4+1 architectural view.
Figure 9: 4+1 architectural view

Agenda
1. Introduction
2. Architecture
• Hardware view
• Recap
• Best practices
3. Case Study

Q&A

End of theory.
Start of practice.
Thank you.


C03 Architecture of TelematicsSystems

Uploaded by

Copyright:

Available Formats

C03 Architecture of TelematicsSystems

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

C03 Architecture of TelematicsSystems

Uploaded by

Copyright:

Available Formats

Architecture of Telematics Systems

Space for Sender Information 29 September 2019

Space for Sender Information 29 September 2019

Space for Sender Information 29 September 2019

• Can be regarded as an evolution of

Alexandru Lupu, © Continental Automotive GmbH, 2018

Space for Sender Information 29 September 2019

Space for Sender Information 29 September 2019

Figure 1: Automatic crash notification

Space for Sender Information 29 September 2019

Figure 2: GPS vehicle tracking system

Space for Sender Information 29 September 2019

Figure 3: Representation of Geofence

Space for Sender Information 29 September 2019

Space for Sender Information 29 September 2019

Space for Sender Information 29 September 2019

Space for Sender Information 29 September 2019

Space for Sender Information 29 September 2019

Vehicle Bus Baseband

Space for Sender Information 29 September 2019

Figure 5: (Simplified) Representation of

Space for Sender Information 29 September 2019

Figure 6: Semantic areas of UML 2.5.1

Space for Sender Information 29 September 2019

Figure 7: Responsibilities of the Software Architecture Role

Space for Sender Information 29 September 2019

Space for Sender Information 29 September 2019

2. Loose coupling between building blocks

Space for Sender Information 29 September 2019

5. Respect Single Responsibility principle.

Space for Sender Information 29 September 2019

6. Use an iterative approach for decomposition.

White Box Interfaces

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

Space for Sender Information 29 September 2019

7. Use architectural patterns.

Space for Sender Information 29 September 2019

8. Use the 4+1 architectural view.

Figure 9: 4+1 architectural view

Space for Sender Information 29 September 2019

Space for Sender Information 29 September 2019

Space for Sender Information 29 September 2019

Space for Sender Information 29 September 2019

You might also like