RESEARCH ARTICLE
Decoding Vehicle Motion Data on the Internal Network
Maen Qaseem Ghadi1, *
Article Information
Identifiers and Pagination:
Year: 2023Volume: 17
E-location ID: e187444782301030
Publisher ID: e187444782301030
DOI: 10.2174/18744478-v17-e230111-2022-37
Article History:
Received Date: 28/8/2022Revision Received Date: 4/12/2022
Acceptance Date: 7/12/2022
Electronic publication date: 01/02/2023
Collection year: 2023
open-access license: This is an open access article distributed under the terms of the Creative Commons Attribution 4.0 International Public License (CC-BY 4.0), a copy of which is available at: https://creativecommons.org/licenses/by/4.0/legalcode. This license permits unrestricted use, distribution, and reproduction in any medium, provided the original author and source are credited.
Abstract
Background:
Encrypting functions of vehicle internal networks makes the lives of third parties more difficult since, in most cases, the meaning of messages carried by the CAN bus is not disclosed
Objectives:
This paper proposes a reverse engineering method to discover, to a large extent, the semantics of CAN messages in a vehicle internal network.
Methods:
A filtering mechanism has been applied that includes several statistical processes to interpret the codes of CAN messages. The speed change function of a vehicle has been chosen as an example to be followed in the development steps of this approach to predict the motion mechanism of the vehicle. The selected codes were verified by developing a multilevel model that relates the hierarchical relationship between the bytes and IDs and their impact on the speed factor.
Results:
The most influential IDs and bytes on vehicle speed functions were: ID 512, ID 520, ID 664, B2, B4, and B6, respectively.
Conclusion:
The selected codes used to model the observed speed do not mean they all share the speed function, but there is a good possibility that at least some fulfill this function. However, with some optimization, the same methodology can be applied to detect other semantic messages in the CAN network based on the expected data type.
