Vehicle Network Message Sequence Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current vehicle network communication systems are vulnerable to unauthorized access, as they cannot distinguish between abnormal and normal messages when an unauthorized message is replicated or when an abnormal message is misjudged as normal, leading to potential safety risks.
Innovation Solution
A data communication method and apparatus for a vehicle network that checks the message sequence and the number of normally received messages, performing error verification to identify and block unauthorized abnormal messages by processing messages as normal or abnormal based on sequence and error verification results.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional checksum or CRC verification is used to protect application data, then data transmission reliability is improved, but the system remains vulnerable to unauthorized access and message sequence manipulation
Solution Approach 1:
The verification mechanism is segmented into multiple independent checks: sequence counter verification, message ID verification, and checksum/CRC verification. Each layer independently validates different aspects of message integrity, creating a multi-layered security approach that addresses both reliability and unauthorized access prevention
Solution Approach 2:
The sequence counter and message ID are verified before performing checksum or CRC verification. This preliminary validation ensures that only messages with correct sequence and identity proceed to error checking, preventing unauthorized messages from being processed even if they have valid checksums
2Measurement precision
If sequence counter and transmission time information are used to detect false or omitted data, then message loss detection is improved, but the system cannot distinguish between delayed normal messages and unauthorized abnormal messages
Solution Approach 1:
The receiving ECU provides feedback by verifying the message ID against the expected sequence and comparing it with previously received message IDs. This feedback mechanism allows the system to distinguish between legitimate sequence variations and unauthorized message injection by checking whether the message ID follows the expected sequential pattern
Solution Approach 2:
The verification process dynamically adjusts based on the message sequence state. The system maintains a rolling window of expected message IDs and adapts its verification criteria based on the current sequence position, allowing it to differentiate between temporary delays and unauthorized access attempts
3Object-affected harmful factors
If comprehensive error verification is performed on all received messages, then security against unauthorized access is improved, but processing time and system complexity increase
Solution Approach 1:
The system performs partial verification by first checking sequence counters and message IDs, and only performing full checksum/CRC verification on messages that pass the initial sequence validation. This selective approach provides comprehensive security for legitimate messages while reducing unnecessary processing of obviously unauthorized messages
Solution Approach 2:
The message ID field serves multiple functions: it acts as a sequence identifier for ordering messages, a uniqueness identifier for detecting duplicates, and a reference for checksum verification. This multi-functionality reduces the need for separate verification fields, simplifying the overall system while maintaining comprehensive security
Data Source
AI summary
A data communication method of a vehicle network may include: receiving, by a reception controller, a message from a transmission controller; determining, by the reception controller, whether a message sequence normally increases; determining, by the reception controller, the number of normally received messages in the message sequence, when it is determined that the message sequence normally increases; performing, by the reception controller, error verification on the received message, when it is determined that the number of normally received messages is equal to or more than a preset number; and processing, by the reception controller, the received message as a normal message when the error verification result for the received message indicates that no error is present in the received message.