Enhancing Autonomous Vehicle Safety with Blockchain Technology: Securing Vehicle Communication and AI Systems
<p>Fog computing architecture with three layers: cloud layer (<b>top</b>) for centralized storage and large-scale processing; fog layer (<b>center</b>) for decentralized computation closer to data sources; and edge layer (<b>bottom</b>) for end devices like vehicles generating and collecting data.</p> "> Figure 2
<p>Types of denial-of-service (DoS) attacks in vehicular communication systems: (a) packet flooding, (b) V2V radio jamming, and (c) V2I radio jamming.</p> "> Figure 3
<p>Illustration of a Sybil attack in a vehicular network. A malicious vehicle (red car) creates multiple fake identities to inject false information into the network, misleading nearby vehicles and disrupting communication. Examples include spoofed hazard warnings, false location data, and network congestion, which compromise the safety and trustworthiness of vehicle-to-vehicle (V2V) communication.</p> ">
Abstract
:1. Introduction
- A complete blockchain-based architecture proposal for autonomous vehicle communication, along with an extensible and reusable prototype.
- The integration of smart contracts for cross-layer communication in the authentication of participants, data storage and processing, and management of deployed AI models across AVs.
- A comprehensive study and comparison of the current state of the art in terms of the interaction between IoT devices and blockchain algorithms. This study is supported through implemented experiments.
2. Background
2.1. Vehicular Ad Hoc Networks (VANETs)
2.2. IoT Devices
2.2.1. Roadside Units (RSUs)
2.2.2. Smart Traffic Lights
2.3. Blockchain
2.3.1. Ledger
2.3.2. Smart Contracts
2.3.3. Byzantine Fault Tolerance Protocol
2.3.4. Fog Computing
- Cloud layer-handles centralized storage and large-scale data processing tasks, such as managing extensive databases or running computationally intensive applications.
- Fog layer-acts as an intermediary between the cloud and edge devices, consisting of local servers, routers, and firewalls. This layer processes data closer to its source, reducing latency and ensuring that time-sensitive applications (e.g., vehicular networks) perform efficiently.
- Edge layer-comprises end devices like vehicles, sensors, and other IoT systems that generate and collect data. These devices communicate directly with the fog layer or through roadside units (RSUs), enabling real-time interactions and local processing.
2.4. Attacks in V2X Scenarios
2.4.1. Denial of Service (DoS) Attack
- Packet flooding-the attacker floods the network with a large number of unnecessary or malicious packets, overloading communication channels and preventing legitimate vehicles from sending or receiving critical data, such as collision warnings or traffic updates.
- Radio jamming in V2V communication-the attacker disrupts direct communication between vehicles by emitting high-power signals that jam the radio frequencies used for vehicle-to-vehicle interactions. This prevents vehicles from exchanging safety-critical information, potentially leading to accidents or traffic congestion.
- Radio jamming in V2I communication-the attacker targets the communication between vehicles and infrastructure, such as roadside units (RSUs), by jamming the radio frequencies used for vehicle-to-infrastructure interactions. This disruption can prevent vehicles from receiving vital data, such as traffic light signals, road conditions, or navigation assistance, affecting both safety and traffic flow.
2.4.2. Sybil Attack
3. Related Work
4. Proposed Architecture and Implementation
4.1. System Architecture Overview
- Vehicles layer: vehicles equipped with IoT devices and sensors on board generate real-time data.
- Edge/fog layer: roadside units (RSUs) serve as edge nodes to facilitate local processing and reduce latency.
- Blockchain layer: a decentralized ledger where all transactions (vehicle interactions and data exchanges) are securely recorded.
- Cloud layer: for high-level processing and analysis, data that do not occur in real time can be outsourced to the cloud.
- Smart contracts: to automate the enforcement of policies for secure communication, authentication, and data exchange.
4.2. Technical Implementation of the System
- Initialization and node configuration. Each vehicle and RSU acts as a blockchain node and is equipped with the following:
- –
- Public–private key pairs-each vehicle and RSU is assigned a unique identity represented by a public–private key pair using elliptic curve cryptography (ECC). The public key acts as an identifier, while the private key is used to sign transactions securely.
- –
- Blockchain client-vehicles and RSUs are equipped with lightweight blockchain clients to minimize resource usage while ensuring compatibility with the decentralized network.
- –
- IoT sensors-vehicles are equipped with various sensors (e.g., GPS, LIDAR, and cameras) to collect data for secure communication and decision making. These sensor data are signed and securely transmitted to RSUs and other vehicles for validation.
- Secure data generation and signing. When a vehicle generates data (e.g., location, speed, and hazard warnings), the system ensures data integrity through cryptographic signing:
- –
- The vehicle’s on-board unit (OBU) signs the data using its private key.
- –
- The signed data are packaged into a blockchain transaction and propagated across the network to nearby RSUs and vehicles.
- Data validation via the blockchain.
- –
- Transaction propagation-the transaction (signed data) is propagated through the network and received via nearby RSUs (edge nodes) and vehicles.
- –
- Consensus mechanism-RSUs use the Practical Byzantine Fault Tolerance (PBFT) protocol to validate transactions:
- *
- Verify the signature using the sender’s public key.
- *
- Ensure the data’s integrity and authenticity.
- –
- Transaction recording-once the transaction is validated, it is bundled into a block. Each RSU maintains a local blockchain ledger, and validated blocks are propagated to other RSUs in the network to ensure consistency.
- Smart contract deployment. Smart contracts play a critical role in automating network operations:
- –
- Authentication-when a vehicle or RSU joins the network, the smart contract verifies its identity using its public–private key pair.
- –
- Role-based access control-smart contracts enforce access restrictions to sensitive data. For example, hazard alerts are broadcast to all nearby vehicles, but personal vehicle information remains encrypted and accessible only to authorized nodes.
- Tools and platforms.
- –
- Hyperledger fabric-used as the blockchain platform due to its support for permissioned networks and modular architecture.
- –
- Python-utilized for simulations and integration with Hyperledger Fabric.
- –
- Key libraries-cryptography is used for ECC key generation and signature verification, while SimPy is employed for network latency and mobility modeling.
4.3. Communication Proof of Concept
- Secure vehicle-to-vehicle communication (V2V)
- –
- Data broadcast-vehicles broadcast signed messages, such as emergency braking or hazard warnings, to nearby vehicles and RSUs.
- –
- Message verification (Algorithm 1)-the receiving vehicles verify the authenticity of the message by checking the sender’s public key and the blockchain entries. This ensures that the message does not originate from a malicious actor (protection against Sybil attacks).
Algorithm 1 Message verification algorithm - 1:
- Input: Message m, Sender’s Public Key
- 2:
- Output: Validation Status (True/False)
- 3:
- Step 1: Extract the digital signature from m
- 4:
- Step 2: Verify the signature using
- 5:
- Step 3: Check the blockchain ledger for the sender’s identity
- 6:
- if signature and sender identity are valid then
- 7:
- return True
- 8:
- else
- 9:
- return False
- 10:
- end if
- –
- Data sharing-after validation, the data are used to support the receiving vehicle’s decision making (e.g., adjusting speed to avoid a collision).
- Secure vehicle-to-infrastructure communication (V2I)
- –
- Data aggregation with RSUs-RSUs collect and process data from nearby vehicles. They can take over local traffic management, store road condition data, or interact with traffic lights to optimize traffic flow.
- –
- Blockchain recording-important V2I interactions (such as toll payments or the prioritization of emergency vehicles) are recorded in the blockchain for transparency and verification. The message does not originate from a malicious actor (protection against Sybil attacks).
- –
- Fog computing-part of the data processing takes place at the edge (RSUs) so that decisions can be made in real time without having to send all data to the cloud, reducing latency.
Algorithm 2 Algorithm to determine RSUs in range |
|
4.4. Blockchain Components
- Blockchain platform-our implementation is based on Hyperledger Fabric [24], a permissioned blockchain platform that ensures that only authorized vehicles and RSUs participate in the network.
- Consensus algorithm-the system uses a Byzantine Fault Tolerant (BFT) [25] consensus mechanism, in this case Practical Byzantine Fault Tolerance (PBFT) (Algorithm 3) [26], which is suitable for environments with a relatively small number of participants (RSUs and vehicles) and requires fast consensus.
- Cryptographic techniques-the developed system relies on elliptic curve cryptography (ECC) [27] for secure key generation, as it provides strong security with relatively small key sizes, which is ideal for resource-constrained in-vehicle IoT devices.
Algorithm 3 Practical Byzantine Fault Tolerance (PBFT) |
|
4.5. Security and Privacy Measures Implemented
- End-to-end encryption-we implemented end-to-end encryption to ensure that all communication between vehicles (V2V) and vehicles and infrastructure (V2I) is encrypted. Public–private key pairs were used, with each vehicle and RSU having their own cryptographic keys.
- When data (e.g., vehicle location, speed, and hazard warnings) are transmitted, they are first encrypted with the sender’s private key to ensure that the data cannot be read by unauthorized parties. Only the recipient who has the corresponding public key can decrypt the message. This guarantees that the data remain confidential and tamper-proof throughout the entire communication.
- We used elliptic curve cryptography (ECC) for public–private key pair generation, as it offers strong security properties and efficient key generation, which are crucial for resource-constrained environments such as vehicular networks.
- Tamper-proof ledger-the blockchain acts as a tamper-proof ledger that records all vehicle interactions and data exchanges. Each transaction between vehicles and RSUs is validated via a consensus mechanism and stored in blocks that are cryptographically linked to previous blocks.
- Once data have been written to the blockchain, they are immutable. This means that no vehicle, RSU, or external company can change or delete previous data entries, ensuring an accurate and transparent record of all events.
- We configured the blockchain to be permissioned so that authorized nodes (such as vehicles and RSUs) can access the ledger while maintaining transparency across the network. This ensures accountability, as all interactions are logged, and the integrity of the data can be verified by all participants.
- Decentralization-to ensure decentralization, we established an approved blockchain with multiple participating nodes. Vehicles, RSUs, and infrastructure nodes (e.g., cloud servers) each act as decentralized nodes in the network. No single node controls the entire system, making the network resilient to attacks.
- We used the Practical Byzantine Fault Tolerance (PBFT) consensus algorithm to reach an agreement across the network, even in the presence of faulty or malicious nodes. This protocol ensures that the network can still reach consensus and validate transactions as long as fewer than 1/3 of the nodes are compromised.
- Decentralization makes the system resistant to denial of service (DoS) and Sybil attacks. For example, in a Sybil attack, where an attacker creates multiple fake identities to manipulate the network, the blockchain’s consensus protocol ensures that only authenticated nodes can participate in the decision-making process. In addition, the distributed nature of the system means that there is no single point of failure, which minimizes the likelihood of successful DoS attacks.
4.6. Considerations for Optimizing Performance
- Edge processing-to minimize the communication load on the blockchain, we deployed RSUs (roadside units) as edge computing nodes [28,29]. RSUs are strategically placed at the roadside and are responsible for local data processing tasks such as traffic monitoring, hazard detection, and vehicle coordination. By processing data locally, RSUs significantly reduce the need for constant interaction with the cloud or blockchain network.
- RSUs are able to make real-time decisions at the border. For example, if a hazard is detected, the RSU analyzes the data locally and transmits the warning directly to nearby vehicles. Only important data, such as final decisions or important transaction details, are sent to the blockchain for logging, reducing the overall communication load of the system.
- This implementation reduces latency by keeping processing close to the data source and minimizing the need to forward non-critical information to the cloud or blockchain. It also conserves bandwidth and improves the overall responsiveness of the system to real-time traffic conditions.
- Scalability-to ensure that the system can handle a large number of vehicles, we designed the blockchain with a hierarchical architecture. The system includes lightweight nodes (vehicles) and more powerful nodes (RSUs) that manage the ledger and perform more resource-intensive tasks.
- Lightweight nodes (vehicles): Vehicles act as lightweight nodes in the network. They primarily generate and verify smaller transactions (e.g., position updates or hazard warnings) and rely on the RSUs for more complex blockchain interactions.
- Powerful nodes (RSUs): RSUs serve as more robust nodes capable of managing parts of the blockchain ledger and participating in the consensus mechanism. By distributing the more computationally intensive tasks to the RSUs, the system remains scalable even if the number of vehicles increases.
5. Evaluation
5.1. Safety Simulations and Feedback
- Sybil attack scenario-The first scenario in our evaluation involved the simulation of a Sybil attack where a malicious node attempted to create 50 false identities to disrupt the network. The attacker’s goal was to inject false data into the vehicle-to-vehicle (V2V) communication to manipulate and disrupt the coordination between the vehicles. By injecting these fake identities, the attacker attempted to confuse the network by generating false information about vehicle locations, traffic conditions or hazards, potentially leading to false actions by other vehicles. This type of attack can lead to significant safety risks, including traffic jams or collisions, as vehicles are misled about the actual state of the environment.Our system’s blockchain-based consensus mechanism was able to successfully detect and block all 50 fake identities, preventing any manipulation of V2V communication. This result demonstrates the robustness of the system’s authentication process, which relies on cryptographic identities validated via the blockchain to ensure that only legitimate vehicles can participate in the network. The system’s ability to mitigate this attack with a 100% success rate while minimally impacting latency underscores its effectiveness in securing vehicle communications against Sybil attacks.
- Denial of service attack scenario-in the second scenario, we simulated a denial of service (DoS) attack in which a malicious node flooded the network with 1000 fake transaction requests per second and targeted the communication between vehicles and RSUs (vehicle-to-infrastructure, or V2I) to overload the blockchain nodes. The goal of the attack was to disrupt the network by overloading the roadside units (RSUs) and preventing legitimate transactions from being processed.The system’s consensus mechanism, combined with rate-limiting measures, successfully mitigated the attack by discarding 95% of malicious requests at the network level before they could reach the blockchain. The remaining 5% of requests were validated by the RSUs, identified as fake transactions, and discarded without being included in a block, ensuring that the malicious activity did not compromise the integrity of the blockchain ledger.
- Mitigation rate-the system was able to neutralize 95% of attacks at the network layer, while the blockchain layer rejected 100% of forged transactions, maintaining data accuracy and security.
- Impact on throughput-during the peak of the attack, the throughput of the system was reduced by 20% as resources were temporarily allocated to process and forged requests were rejected. However, no legitimate transaction was delayed by more than 50 ms, allowing communication between vehicles and RSUs to continue despite the attack.
- The generation and validation of vehicle identities (to mitigate Sybil attacks);
- The processing of large volumes of transaction requests during DoS attack simulation;
- And the implementation of the Practical Byzantine Fault Tolerance (PBFT) algorithm for consensus.
5.2. Consensus Mechanism Evaluation (PBFT)
- Faulty node-tolerance scenario-in a simulated scenario, faulty or malicious nodes were introduced into the network, with the number of faulty nodes gradually increasing from 0 to 5 out of a total of 10 nodes to simulate Byzantine failures.As a result, the system successfully reached a consensus with up to three faulty nodes (in accordance with the PBFT tolerance of up to f = 1/3 Byzantine nodes). When the number of faulty nodes increased to four or more, consensus could not be reached, and the network could not reach an agreement concerning transaction validation.
- –
- Fault tolerance-the system was able to tolerate up to 3 faulty nodes in a 10-node network while maintaining consensus and data integrity.
- –
- Impact on latency-With one to two faulty nodes, the consensus time increased by 10%. With three faulty nodes, the consensus time increased by 25%. When the number of faulty nodes reached four, the system could no longer agree on the validity of the transaction.
The PBFT consensus algorithm worked as expected and successfully maintained a consensus with up to f = 1/3 faulty nodes. Beyond this limit, the network became unstable, as predicted through PBFT theory. - Malicious node injection scenario-malicious nodes attempted to participate in the consensus process by sending corrupted or false blocks to disrupt the network.PBFT successfully identified and excluded the malicious nodes during the preparation and handover phase. The corrupted blocks were discarded, and the network reached a consensus with valid blocks from honest nodes.
- –
- Mitigation rate-100% of malicious nodes were detected and excluded from the consensus process.
- –
- Impact on latency-the presence of malicious nodes increased the consensus time by 15%, but the system remained functional and stable.
The PBFT consensus mechanism proved to be effective in identifying and excluding malicious nodes, ensuring network operability without interruption, results that we summarized in Table 2.
5.3. Simulated Network Dynamics
- Impact of vehicle mobility on communication latency-in real-world vehicular networks, the continuous movement of vehicles leads to dynamic changes in topology, which can introduce latency variations. Simulations were designed to account for the following:
- –
- Vehicles entering and exiting the communication range of roadside units (RSUs).
- –
- Changing distances between vehicles and RSUs, affecting the signal strength and communication delay.
Observations:- –
- As vehicles moved, latency increased slightly when transitioning between RSUs, averaging a 15% rise in the communication delay compared to static conditions.
- –
- The algorithm for selecting the nearest RSU (Algorithm 1 in the paper) effectively minimized disruptions, with vehicles reconnecting to optimal RSUs within 2–3 ms.
- –
- The dynamic handoff process demonstrated that the framework could maintain a consistent data exchange without losing critical information, even during high-mobility scenarios.
- Effects of jitter and latency variability on performance-jitter refers to the variability in packet transmission times, which is common in mobile vehicular networks due to fluctuating signal strength and environmental interference. To simulate this, random delays ranging from 5 to 50 ms were introduced into the communication paths between vehicles, RSUs, and blockchain nodes.Observations:
- –
- For low to moderate jitter (up to 10 ms), the framework’s performance remained stable, with Sybil attack detection rates exceeding 97%. The system handled the variability without noticeable degradation in its mitigation capabilities.
- –
- When jitter increased to 20 ms or more, there were slight delays in the consensus process, which affected transaction throughput. During peak jitter conditions, the throughput decreased by approximately 5%, although no malicious transactions were validated.
- –
- Severe jitter (above 40 ms) occasionally caused temporary delays in the system’s attack detection capabilities, but blockchain consistency was preserved as malicious nodes were eventually identified and excluded during subsequent consensus rounds.
6. Discussion
6.1. Effectiveness of Safety Mechanisms
6.2. Weighing Up Latency vs. Security
6.3. Scalability and Network Dynamics
6.4. Real-World Feasibility and Deployment
6.5. Consequences Under Data Protection Law
6.6. Novelty and Differentiation
- Enhanced security with smart contracts and PBFT consensus-unlike prior works that rely on centralized or static mechanisms for data validation and node authentication, our framework employs smart contracts and the Practical Byzantine Fault Tolerance (PBFT) consensus algorithm to ensure secure and decentralized operations.
- Modularity and interoperability with existing V2X standards-a unique aspect of the proposed framework is its modular design, which supports interoperability with widely adopted V2X standards, such as ITS-G5 and Cellular-V2X (C-V2X).
- Differentiation from existing RSU-based approaches-while existing works propose RSU-based architectures for forwarding data, they primarily focus on centralized data management or anomaly detection. In contrast, our framework achieves the following:
- –
- Distributes computation and decision-making across a decentralized blockchain network, eliminating single points of failure.
- –
- Utilizes RSUs not only as data aggregation points but also as lightweight blockchain clients. RSUs participate in the consensus process, validate transactions locally, and reduce latency in real-time data exchanges.
- –
- Integrates smart contract-based authentication directly at the RSU level, ensuring that only verified nodes can contribute to the network.
- Real-world considerations-existing studies often evaluate their frameworks under idealized or static conditions, limiting their applicability in real-world scenarios. The current research achieves the following:
- –
- Includes simulations with dynamic vehicular mobility, network jitter, and latency variability, highlighting the framework’s robustness under real-world constraints.
- –
- Demonstrates how the modular design and decentralized consensus can adapt to diverse conditions, such as varying traffic densities and communication delays.
7. Future Work
- Real-world testing: While our current simulations provided valuable insights into system behavior in attack scenarios, future efforts will focus on transitioning from simulations to real-world testing. Deploying the system in real vehicle environments will allow us to validate its performance and robustness under dynamic conditions, taking into account real-time factors such as network variability, physical obstacles, and hardware limitations.
- Optimization for large-scale networks: As the number of connected vehicles and RSUs grows in future smart cities, scalability remains a critical challenge. In the future, we plan to explore more advanced optimization techniques, such as dynamic node allocation or sharding, to efficiently handle larger networks without overwhelming the capacity of the blockchain.
- Energy efficiency improvements: Blockchain operations, especially in resource-constrained environments such as vehicles, can consume significant amounts of energy. We aim to investigate energy-efficient consensus algorithms or adaptive energy saving strategies, such as the integration of localized fog or edge computing solutions, to reduce the overall energy demand of the system.
- Improved data protection measures: While we have implemented encryption and data anonymization techniques, in the future, we will explore even more advanced privacy-preserving methods, such as homomorphic encryption or secure multi-party computation [32]. These methods could further protect sensitive information without compromising the security or functionality of the system.
- Advanced security mechanisms: We intend to enhance the security architecture by integrating machine learning-based intrusion detection systems (IDSs). These systems could dynamically detect and prevent novel or evolving attacks that could bypass traditional security mechanisms.
- Evaluation of hybrid consensus models: PBFT performed well in our simulations, but exploring hybrid consensus models that combine PBFT with proof-of-stake (PoS) or other consensus algorithms could provide even better scalability and fault-tolerance, especially in environments with rapidly changing network topologies such as vehicular networks.
8. Conclusions
Author Contributions
Funding
Data Availability Statement
Conflicts of Interest
References
- Paduraru, C.; Jianu, A.; Stefanescu, A. Blockchain for Artificial Intelligence: An Industry and Literature Survey. In Proceedings of the 18th International Conference on Software Technologies (ICSOFT), Rome, Italy, 10–12 July 2023; pp. 135–150. [Google Scholar]
- Chen, L.; Zhao, Y.; Wang, M. A Secure and Efficient Blockchain-Based System for Vehicle-to-Everything (V2X) Communication. IEEE Trans. Intell. Transp. Syst. 2022, 23, 1–14. [Google Scholar]
- Rashid, M.; Alam, S.; Khan, M. Enhancing Security in VANETs with Blockchain and PBFT Consensus Mechanism. Comput. Netw. 2021, 184, 107644. [Google Scholar]
- Huang, J.; Wu, F.; Zhang, H. Blockchain-Based Decentralized Data Integrity Protocol for Autonomous Vehicles. IEEE Access 2023, 11, 7509–7522. [Google Scholar]
- Zhu, H.; Huang, X.; Zhang, W. Integration of Blockchain and AI in Autonomous Vehicle Safety. Int. J. Distrib. Sens. Netw. 2023, 19, 2023. [Google Scholar]
- Smith, A.; Jones, K.; Lee, D. Blockchain and Smart Contract Applications in Transportation Systems. Transp. Sci. 2023, 54, 130–144. [Google Scholar]
- Ramasamy, K.; Subramanian, D. Blockchain-Based Privacy Solutions in Vehicular Ad-Hoc Networks (VANETs). Comput. Secur. J. 2022, 108, 102456. [Google Scholar]
- Patel, S.; Kumar, A.; Verma, P. Implementation of Smart Contracts in AV Communication for Authentication and Privacy. J. Automot. Secur. 2023, 48, 102–118. [Google Scholar]
- Park, D.; Shin, J.; Lee, Y. Mitigating Sybil Attacks in AV Communication Networks via Blockchain. IEEE Veh. Technol. J. 2023, 13, 51–63. [Google Scholar]
- Chao, Y.; Lin, Z.; Wu, L. Smart Contracts for Autonomous Vehicle Interactions: A Case Study on Data Privacy. Int. J. Blockchain Res. 2023, 7, 289–304. [Google Scholar]
- Jeon, H.; Kim, Y.; Choi, M.; Park, D.; Son, S.; Lee, J.; Choi, G.; Lim, Y. CARLA Simulator-Based Evaluation Framework Development of Lane Detection Accuracy Performance Under Sensor Blockage Caused by Heavy Rain for Autonomous Vehicle. IEEE Robot. Autom. Lett. 2022, 7, 9977–9984. [Google Scholar] [CrossRef]
- Mohammed, R.; El-Sayed, A.; Lin, M. Performance Evaluation of PBFT and Hybrid Consensus in IoT Networks. IEEE Trans. Internet Things 2023, 7, 3023–3035. [Google Scholar]
- Rao, P.; Patel, S.; Gupta, M. Securing V2X Communication with Blockchain-Based Consensus Algorithms. J. Emerg. Transp. Technol. 2024, 19, 68–79. [Google Scholar]
- Kumar, A.; Sharma, P.; Gupta, R.; Singh, M. Enhancing Autonomous Vehicle Network Security Using Byzantine Fault Tolerance and Blockchain. Int. J. Intell. Syst. 2024, 9979371. [Google Scholar] [CrossRef]
- Wang, Y.; Zhao, L.; Chen, Z. Fog Computing in Autonomous Vehicles: Blockchain-Enabled Resource Management. Veh. Netw. J. 2022, 12, 200–215. [Google Scholar]
- Lee, J.; Park, S. Privacy Management in Vehicular Networks: A Smart Contract Approach. IEEE Veh. Commun. 2023, 17, 98–109. [Google Scholar]
- Tan, Y.; Li, J. Blockchain-Driven Solutions for Privacy and Security in Vehicular Networks. J. Comput. Telecommun. 2024, 60, 120–134. [Google Scholar]
- Liu, Z.; Zhao, M.; Xu, F. Leveraging Elliptic Curve Cryptography in AV Blockchain Systems for Efficient Authentication. Cybersecur. J. 2022, 13, 115–129. [Google Scholar]
- Davies, T.; Brown, R.; White, S. Energy-Efficient Consensus Mechanisms for Blockchain in Resource-Constrained Environments. Blockchain Sustain. Dev. 2023, 6, 54–72. [Google Scholar]
- Gao, Y.; Liu, Q.; Zhang, S. Scalability and Optimization in Blockchain for Autonomous Vehicular Networks. Smart Cities J. 2023, 5, 241–257. [Google Scholar]
- Zhao, Y.; Yu, H.; Liang, Y. Privacy-Preserving Distributed Collaboration Scheme for Autonomous Vehicles. IEEE Trans. Intell. Transp. Syst. 2024, 29, 201–214. [Google Scholar]
- Zhang, T.; Wang, J.; Han, L. Decentralized Authentication and Security Protocols for Autonomous Vehicle Networks. J. Netw. Secur. 2022, 12, 45–56. [Google Scholar]
- Van Brummelen, G. Heavenly Mathematics: The Forgotten Art of Spherical Trigonometry; Princeton University Press: Princeton, NJ, USA, 2013; ISBN 9780691148922. [Google Scholar]
- Wickremasinghe, G.; Frost, S.; Rafferty, K.; Sharma, V. Demonstrating a Hyperledger Fabric-based Blockchain with Knowledge Graphs for a Supply Chain Ecosystem. In Proceedings of the IEEE International Conference on Blockchain and Cryptocurrency (ICBC), Dublin, Ireland, 27–31 May 2024. [Google Scholar]
- Qi, X.; Chen, Z.; Zhang, Z.; Jin, C.; Zhou, A.; Zhuo, H.; Xu, Q. A Byzantine Fault Tolerant Storage for Permissioned Blockchain. In Proceedings of the ACM SIGMOD Conference, Xi’an, China, 20–25 June 2021; pp. 2770–2774. [Google Scholar]
- Wang, Z.-F.; Liu, S.-Q.; Wang, P.; Zhang, L.-Y. BW-PBFT: Practical byzantine fault tolerance consensus algorithm based on credit bidirectionally waning. Peer-to-Peer Netw. Appl. 2023, 16, 2915–2928. [Google Scholar] [CrossRef]
- Hankerson, D.; Vanstone, S.; Alfred Menezes, A. Elliptic Curve Cryptography Chapter in Encyclopedia of Cryptography, Security and Privacy; Springer: Berlin/Heidelberg, Germany, 2021; Available online: https://link.springer.com/referenceworkentry/10.1007/978-3-642-27739-9_245-2 (accessed on 28 October 2024).
- Liu, K.; Ma, R.; Yang, F. Edge Computing for Autonomous Vehicles: Enhancing Security and Reducing Latency. Int. J. Veh. Netw. Data Anal. 2023, 5, 95–109. [Google Scholar]
- Song, Q.; Wang, R.; Chen, L. Edge and Fog Computing in Autonomous Vehicles: Security and Privacy Aspects. J. Appl. Comput. 2023, 14, 102–118. [Google Scholar]
- Chang, Y.; Lee, C.; Yang, J. Optimizing Blockchain for Autonomous Vehicles Using Sharding Techniques. J. Distrib. Comput. 2024, 35, 445–462. [Google Scholar]
- Wong, P.; Li, X.; Huang, J. Enhancing Data Privacy in Autonomous Vehicle Networks through Zero-Knowledge Proofs. IEEE J. Priv. Data Secur. 2024, 16, 87–102. [Google Scholar]
- Kang, H.; Kim, S.; Woo, M. Secure Multi-Party Computation for Privacy in Vehicular Blockchain Networks. Int. J. Priv. Secur. 2023, 11, 78–91. [Google Scholar]
Scenario | Description | Result |
---|---|---|
Sybil attack | A malicious node created 50 fake identities to manipulate vehicle-to-vehicle (V2V) communication | 100% success rate in detecting and blocking Sybil attacks, with a minimal impact on latency |
DoS attack | A malicious node flooded the network with 1000 fake transaction requests per second to overload the RSUs and blockchain nodes in vehicle-to-infrastructure (V2I) communication | 95% of malicious traffic was blocked, 100% of spoofed transactions were rejected, and throughput was reduced by 20% during the peak of the attack, with no legitimate transaction delayed by more than 50 ms |
Scenario | Description | Result |
---|---|---|
Faulty node tolerance. | Faulty or malicious nodes were introduced into the network, increasing the number from 0 to 5 out of 10 nodes in order to simulate Byzantine failures. | The system successfully achieved consensus with up to three faulty nodes (in accordance with the PBFT tolerance of up to Byzantine nodes). With four or more faulty nodes, consensus could not be achieved, and the network could not validate transactions. |
Fault tolerance. | The system was able to tolerate up to 3 faulty nodes in a 10-node network while maintaining consensus and data integrity. | With one to two faulty nodes, the consensus time increased by 10%, and with three faulty nodes by 25%. With four faulty nodes, consensus was no longer possible. |
Malicious node injection. | Malicious nodes attempted to participate in consensus by sending corrupted or false blocks to disrupt the network. | PBFT successfully identified and excluded 100% of the malicious nodes during the preparation and handover phase. The corrupted blocks were discarded, and the network reached a consensus with valid blocks. |
Impact on latency. | The presence of malicious nodes increased the consensus time. | The Consensus time increased by 15% due to the presence of malicious nodes, but the system remained stable and functional. |
Metric | Idealized Conditions | Dynamic Conditions (Mobility & Jitter) |
---|---|---|
Sybil attack detection rate | 100% | 97% |
DoS attack mitigation rate | 95% | 90% |
Consensus latency | 100 ms | 120 ms (average), peaks of 150 ms |
Throughput reduction (DoS) | 20% | 25% |
Disclaimer/Publisher’s Note: The statements, opinions and data contained in all publications are solely those of the individual author(s) and contributor(s) and not of MDPI and/or the editor(s). MDPI and/or the editor(s) disclaim responsibility for any injury to people or property resulting from any ideas, methods, instructions or products referred to in the content. |
© 2024 by the authors. Licensee MDPI, Basel, Switzerland. This article is an open access article distributed under the terms and conditions of the Creative Commons Attribution (CC BY) license (https://creativecommons.org/licenses/by/4.0/).
Share and Cite
Iordache, S.; Patilea, C.C.; Paduraru, C. Enhancing Autonomous Vehicle Safety with Blockchain Technology: Securing Vehicle Communication and AI Systems. Future Internet 2024, 16, 471. https://doi.org/10.3390/fi16120471
Iordache S, Patilea CC, Paduraru C. Enhancing Autonomous Vehicle Safety with Blockchain Technology: Securing Vehicle Communication and AI Systems. Future Internet. 2024; 16(12):471. https://doi.org/10.3390/fi16120471
Chicago/Turabian StyleIordache, Stefan, Catalina Camelia Patilea, and Ciprian Paduraru. 2024. "Enhancing Autonomous Vehicle Safety with Blockchain Technology: Securing Vehicle Communication and AI Systems" Future Internet 16, no. 12: 471. https://doi.org/10.3390/fi16120471
APA StyleIordache, S., Patilea, C. C., & Paduraru, C. (2024). Enhancing Autonomous Vehicle Safety with Blockchain Technology: Securing Vehicle Communication and AI Systems. Future Internet, 16(12), 471. https://doi.org/10.3390/fi16120471