Developer

System overview

Request Access
Version: 0.5.0

Introduction

This document provides a system overview of the Automotive Navigation Application (ANA), its main components, dependencies, and how it fits into an automaker’s system. It is intended to help put other parts of this documentation into perspective.

High-level overview

The diagram below provides a high-level overview of ANA and the context in which it operates.

System overview

System at a glance

Automotive Navigation Application is built on TomTom Orbis Map and Navigation SDK.

Several key aspects are outlined below:

  • In-vehicle infotainment system. Automotive Navigation Application operates within an Android Automotive OS-based infotainment, which integrates seamlessly into vehicles. Such a system typically supports multiple displays (such as a Center Display and an Instrument Cluster) and provides access to various vehicle data, such as battery state of charge and vehicle location. Additionally, the application utilizes Android Automotive APIs and Storage, for example, caches and persists user preferences.
  • Cellular data usage. Automotive Navigation Application prioritizes the usage of TomTom Online Services when an internet connection is available. If the connection is lost, it reverts to cached data.
  • Vehicle Integration Library (VIL). The VIL is a client library designed to facilitate the provisioning of necessary Vehicle Data and Configurations to ANA. Automakers must integrate VIL into one or more Navigation Integration Client services, which are responsible for propagating essential vehicle data and configurations from the platform to ANA.
  • Online services and access management. TomTom Online Services are hosted in a TomTom-managed cloud environment. Access from ANA to these APIs is controlled by an Access Management Service, which requires integration with the automaker’s Identity Access Management (IAM) system for identity management, authentication, and authorization. Access tokens, issued by an automaker’s IAM system, should be provided to the Vehicle Integration Library.

Reference

For more information, refer to: