Introduction

DIAS (DIagnostic Anti-tampering Systems)

Modern vehicles with internal combustion engines are equipped with exhaust aftertreatment systems that drastically reduce the emission of harmful exhaust gases. However, there are companies that offer facilities and services to disable these exhaust aftertreatment systems. In a joint European research and development project, DIAS, we will help prevent or uncover these manipulations.

Eclipse KUKSA

../_images/appstacle-kuksa.PNG
  • KUKSA is a code-based result of the internationally funded project, APPSTACLE (2017 - 2019).
../_images/kuksa_ecosystem.png
  • An open-source eco-system for the connected vehicle domain.
  • It is introduced to establish a standard for car-to-cloud scenarios.
  • It improves comprehensive domain-related development activities.
  • It opens the market to external applications and service provider.
  • It facilitates the use of open-source software wherever possible without compromising security.
  • The initial release (0.1.0): 30.09.2019 / The second release (0.2.0): 01.2020
  • Implementing the DIAS use-case with KUKSA benefits both parties by enabling the solution to be compliant with any vehicles regardless of OEM-specific standards.

DIAS-KUKSA

One objective of DIAS is to create a cloud-based diagnostic system. To manage a large scale of vehicles, sufficient computing power and resource are required. A cloud-based system would not only provide these but also make the entire system easy to scale according to the number of target vehicles by utilizing cloud service providers such as Azure, AWS and Bosch IoT Hub. For the system to be powered by service providers like these, it is essential to establish connectivity between the vehicle-server-based applications and the external-server-based applications. The KUKSA infrastructure offers the means for instituting such connectivity.

The goal of this documentation is to make clear how to set up each infrastructure component according to the case of DIAS in a sequential manner so that readers can have a thorough understanding of how to apply their own implementation on the established connectivity with KUKSA.

DIAS-KUKSA Overall Schema

../_images/overall_schema.png

The figure illustrates the entire connectivity cycle from the vehicle to the end-consumer. In the following chapters, how to establish such connectivity is described in detail.