# Toward Generative AI-Based Intrusion Detection Systems for the Internet of Vehicles (IoV)
## 2 Background
### IoV Communication Architecture  
There is still no agreement among academics about the structure of the Internet of Vehicles architecture. In Ref. [5], [PERSON] mentioned that the IoV architecture closely resembles that of the IoT and defined a three-layer architecture named the \"Client-Connection-Cloud\" system. The first layer (sensing layer) includes sensors inside the vehicle that collect environmental data and monitor the vehicle's conditions. The network layer is the second layer, which supports different V2X communication modes to ensure seamless connectivity between vehicles, infrastructure, and other devices. The third layer (application layer) integrates statistical tools, data storage, and processing capabilities to enable efficient big data analysis and decision-making, supporting IoV intelligence. Over the years, several researchers have proposed different IoV architecture designs. Table 2 provides a summary of the existing IoV architectures. Considering the evolving security and privacy challenges in IoV systems, the seven-layer IoV architecture proposed by [PERSON] et al. in Ref. [7] stands out as the most suitable IoV architecture for addressing these concerns. Unlike previous designs that lacked integrated security mechanisms, this architecture incorporates a dedicated security layer functioning transversally across all layers to manage authentication, authorization, and transaction accounting, ensuring consistent and system-wide protection. It also features a data filtering and preprocessing layer that ensures only relevant, useful, and non-sensitive data is transmitted, reducing network traffic and minimizing the risk of privacy breaches. Additionally, the model offers an intelligent communication interface that optimizes network selection based on various factors such as network quality, communication requirements, and transaction costs, further enhancing the secure and efficient handling of data. According to the seven-layer architecture proposed by [PERSON] et al. [7], the IoV system is structured into distinct yet interconnected layers, each playing a specific role in ensuring the system's effectiveness and security. As illustrated in Figure 3, the User Vehicle Interface Layer facilitates communication between the driver and the vehicle, managing alerts and notifications through visual, auditory, or haptic feedback, depending on the context. The Data Acquisition Layer is responsible for gathering data from both internal vehicle sensors and external sources such as other vehicles, traffic infrastructure, and environmental sensors. The Data Filtering and Preprocessing Layer reduces network congestion and data overload by filtering out irrelevant information and prioritizing data based on the vehicle's subscribed services. The Communication Layer selects the most suitable network for data transmission by evaluating parameters such as quality of service, \begin{table}
\begin{tabular}{c c c} \hline \hline
**Existing Architectures** & **Layers** & **Layers Name** \\ \hline
2011—[PERSON] [5] & Three & 1—Client, 2—Connection, 3—Cloud \\ \hline
2016—[PERSON] et al. [6] & Five & 1—Perception, 2—Coordination, 3—Artificial intelligence, 4—Application, 5—Business \\ \hline
2017—[PERSON] et al. [7] & Seven & 1—User interaction layer, 2—Data acquisition layer, 3—Data filtering and preprocessing layer, 4—Communication layer, 5—Control and management layer, 6—Business layer, 7—Security layer \\ \hline
2019—[PERSON] et al. [8] & Four & 1—Cloud computing, 2—SDN control, 3—Fog computing, 4—Infrastructure \\ \hline
2020—[PERSON] et al. [9] & Four & 1—Cloud platform, 2—Edge, 3—Data acquisition, 4—Security authentication \\ \hline
2022—[PERSON] et al. [10] & Three & 1—Clients, 2—Endorsement and commitment peers, 3—Ordering services \\ \hline
2023—[PERSON] et al. [11] & Four & 1—Terminal, 2—Network, 3—Platform, 4—Service \\ \hline \hline \end{tabular}
\end{table} 
Table 2: Summary of the existing IoV architectures. congestion, security, and cost.