Tachograph Security Controller Program Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Tachographs face challenges in ensuring high security against manipulation and maintaining reliability, as existing systems lack robust mechanisms for verifying and updating executable programs securely.

Innovation Solution

A method involving an application controller and a security controller, where the security controller decrypts and verifies an encrypted program code using signatures, ensuring only authentic and intact code is executed, and allows for secure updating by replacing the program code packet-by-packet, while preventing unauthorized access and maintaining functionality even if verification fails.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the tachograph uses a separate security controller with encryption and signature verification for program code, then security against manipulation is improved, but device complexity increases

Engineering Contradiction:
Improvesecurity against manipulationVSAvoiddevice complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The tachograph system is divided into two separate controllers: an application controller for executing program code and a security controller for managing security functions. This segmentation allows security-critical operations (encryption, decryption, signature verification) to be isolated from application logic, enhancing security while maintaining manageable complexity through clear functional separation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The security controller acts as an intermediary between external sources and the application controller. It verifies the authenticity and integrity of program code through decryption and signature verification before allowing execution, thereby protecting the system without requiring the application controller to handle complex security operations directly.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If the tachograph allows program updates through secure decryption and verification, then adaptability is improved, but reliability risks increase during the update process

Engineering Contradiction:
Improveprogram update capabilityVSAvoidoperational reliability during update
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The security controller performs preliminary verification of the program code's authenticity and integrity through signature verification and decryption before the code is executed. This preliminary action ensures that only verified code replaces existing programs, preventing corrupted or malicious code from compromising system reliability during updates.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements a feedback mechanism where the security controller continuously verifies program code integrity and provides status information to the application controller. This feedback loop ensures that updates are properly validated and that the system can detect and respond to verification failures, maintaining reliability throughout the update process.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8931091B2Method for operating a tachograph and tachograph
Publication Date: 2015.01.06 CONTINENTAL AUTOMOTIVE TECHNOLOGIES GMBH
  • US8931091B2 patent drawing
  • US8931091B2 patent drawing
  • US8931091B2 patent drawing

AI summary

A method for operating a tachograph having an application controller and a safety controller. A memory is associated with the application controller and a further memory is associated with the safety controller. An encrypted program code having at least one associated signature is made available to the safety controller. The encrypted program code is decrypted by means of the security controller and verified by the at least one signature. It is detected whether the decrypted program code (EPC) is intended for the application controller and/or for the security controller. Depending on what is detected, the program in the memory and/or the further program in the further memory is at least partially replaced by the decrypted program code and, depending on a result of the verification, the at least partially replaced program and/or the at least partially replaced further program is released for executing.