CAN Database Sync Using RTR Messages for Secure ECU Communication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Vehicle CAN networks are vulnerable to hacking due to open communication channels, allowing hackers to decode and inject messages, leading to system malfunctions.

Innovation Solution

Implement a method and system that utilize a shifting CAN message reference by storing unique configurations of CAN message information in multiple databases, determining system modes based on DLC bits, and generating remote transmission requests to control CAN communication, ensuring secure and dynamic data access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a single CAN database is used for storing CAN message information, then the system complexity is low and ease of operation is maintained, but the security against hacking is insufficient

Engineering Contradiction:
ImprovesecurityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The single CAN database is segmented into multiple CAN databases (first CAN database, second CAN database, etc.), each storing different configurations of CAN message information. This segmentation allows the system to switch between different database configurations dynamically, enhancing security by preventing hackers from accessing a single static database structure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system dynamically switches between different CAN databases based on system modes of operation. The database configuration is not static but changes according to operational requirements, making it difficult for hackers to predict or access the correct database structure. This dynamic behavior is controlled through RTR messages that trigger database switching.

Inventive Principle:
Principle #15Dynamics

2Reliability

If multiple CAN databases with unique configurations are implemented, then security against decoding intercepted data is improved, but the device complexity and difficulty of operation increase

Engineering Contradiction:
ImprovesecurityVSAvoidease of operation
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The ECUs automatically switch between different CAN databases based on system modes without requiring manual intervention. The database switching is self-managed through the control system that monitors operational conditions and triggers appropriate database selections, reducing the operational burden on users while maintaining security.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system uses RTR (Remote Transmission Request) messages as a feedback mechanism to synchronize database switching across multiple ECUs. When one ECU detects a need to switch databases, it sends an RTR message to other ECUs, ensuring all components operate with the same database configuration, thereby maintaining system coherence without complex manual coordination.

Inventive Principle:
Principle #23Feedback

3Reliability

If database switching is implemented to prevent hacking, then security is improved, but the communication time and loss of time increase due to synchronization requirements

Engineering Contradiction:
ImprovesecurityVSAvoidcommunication time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Multiple CAN databases are pre-configured with different message information configurations before operation begins. This preliminary preparation allows for instantaneous switching between databases without requiring time-consuming reconfiguration or data transformation, minimizing communication delays while maintaining security through database switching.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements periodic database switching at predetermined intervals or operational milestones. This periodic approach allows ECUs to synchronize their database usage in predictable cycles, reducing the frequency of switching operations and minimizing the overall time loss associated with synchronization while still maintaining security through regular configuration changes.

Inventive Principle:
Principle #19Periodic action

4Adaptability or versatility

If RTR messages are used to control CAN communication and switch databases, then security and adaptability are improved, but the device complexity increases

Engineering Contradiction:
ImproveadaptabilityVSAvoiddevice complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The RTR message mechanism serves multiple functions: it acts as a standard CAN communication protocol element, a database switching trigger, a synchronization signal between ECUs, and a mode transition indicator. This multi-functionality reduces the need for separate dedicated components for each function, thereby limiting the increase in device complexity while achieving high adaptability and security.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS12506638B2Synching control area network (CAN) databases using remote transmission requests to control CAN communication in a vehicle
Publication Date: 2025.12.23 HYUNDAI MOTOR CO LTD
  • US12506638B2 patent drawing
  • US12506638B2 patent drawing
  • US12506638B2 patent drawing

AI summary

Systems and methods for controlling CAN communication in a vehicle are provided. The method may comprise storing CAN message information in the plurality of CAN databases such that each CAN database stores a unique configuration of the CAN message information, determining a system mode of operation comprising determining one or more LSBs of a DLC and comparing the one or more LSBs of the DLC against a database to determine the system mode of operation, generating an RTR message comprising determining one or more MSBs of the DLC and adding the one or more MSBs of the DLC to an end of an identifier, generating an RTR request value comprising the identifier and the one or more MSBs of the DLC, communicating the RTR message, to the plurality of ECUs, interpreting the RTR request value to determine the requested answer value, and communicating the requested answer value.