## 8 Simulation and Results  
### Simulation Setup  
Considering various vehicular applications and scenarios, the proposed microservice-based framework was evaluated over NS-3 environments. The mobility of considered vehicles was achieved using the simulation of urban mobility (SUMO) platform. We used the ms-van3t platform available at [42]. We modified our previously proposed system model introduced in [43] and considered it for the proposed VANET. The vehicles' mobility was simulated to match highway conditions. Utilizing OpenFlow version 1.3, all essential SDN modules for the SDN controller and OpenFlow switches were integrated. The simulation topology was developed in accordance with the specifications outlined in Table 3. The simulation consisted of a five-kilometer-long, bidirectional, two-lane road with an RN87-like curvature. The traffic density (TD) parameters summarized in Table 3 were used to distribute vehicles along this road. Table 3 identifies the specifications of the used MEC servers and RSUs. It also displays the attributes of the fog nodes and the SDN network employed in the simulation. The road considered was covered by five RSUs, with a circular coverage of 0.5 km radius for each RSU. The system deployed five MEC units connected to RSUs, with the specifications introduced in Table 3. Each RUS coverage was served by five fog nodes distributed over the coverage area. Communication was carried out over the NR C-V2X using the platform introduced in [42]. Heterogeneous computing tasks of different applications were considered during the simulation. These tasks were of different applications, including sensor data, image processing, V2V communications, video processing, and traffic management. The data were extracted from the datasets introduced in [44; 45; 46; 47; 48]. Various datasets were considered to cover a variety of computing tasks ranging from simple to complex tasks. The tasks were categorized into four main categories in terms of computing complexity as follows: \begin{table}
\begin{tabular}{c c} \hline \hline
**Parameter** & **Value** \\ \hline \multirow{4}{*}{Road} & Length = 5 Km \\  & Direction: Bi-directional \\  & Lane: Two \\  & Curvature: RN87-like \\ \hline \multirow{4}{*}{RSU} & Number = 5 \\  & Interface = NR C-V2X \\  & Radio transmission range = 500 m \\  & Max. transmission level = 20 dBm \\  & Packet transmission frequency = 10 Hz \\ \hline \multirow{4}{*}{Vehicles} & Number (N) = \(N\)\(\epsilon\) [200, 400, 600, 800] \\  & TD = TDv1 \(\epsilon\) [0.1, 0.2, 0.3] vh/m \\  & Mobility (\(\
u\)) = \(\
u\) i [30, 40, 50, 60, 70] \\ \multirow{4}{*}{Number\({}_{\text{area}}\)} & \multirow{4}{*}{\(\epsilon\) = NR C-V2X} \\  & & \\ \hline \multirow{4}{*}{SDN} & Service \(\text{rate}_{\text{Controller}}\) = 30,000 req/sec \\  & OpenFlow version = 1.3 \\ \cline{1-1}  & Average request \(\text{rate}_{\text{switch}}\) = \(\epsilon\) [1500, 3000] \\ \cline{1-1}  & Processing delay\({}_{\text{Controller}}\) = 0.5 us \\ \cline{1-1}  & & \\ \hline \multirow{4}{*}{MEC} & Number = 5 \\  & Placement = equidistant \\ \cline{1-1}  & MEC & Processing \(\in\) [0.7, 2.5] GHz \\ \cline{1-1}  & Max. workload = 10 Mbps \\ \cline{1-1}  & Storage (RAM, HDD) = (4 \(\times\) 2048 Mb, 256 Gb) \\ \hline \multirow{4}{*}{Fog} & Number = 5 per RSU \\  & Processing \(\in\) [0.7, 1.4] GHz \\ \cline{1-1}  & Storage (RAM, HDD) = (2048 Mb, 10 Gb) \\ \hline \multirow{4}{*}{Tasks} & Streaming bandwidth \(\epsilon\) [10, 2048] (Kb/S) \\ \cline{1-1}  & App Category: I, II, III, IV \\ \hline \hline \end{tabular}
\end{table} 
Table 3: Parameters used during simulation. - Category (I): Very simple tasks, including sensor data;  
- Category (II): Simple tasks, including workloads equivalent to processing simple images and websites;  
- Category (III): Medium-complexity tasks, including 3D images and simple videos;  
- Category (IV): High-complex tasks, including high-quality and 3D videos. Tasks were randomly allocated to the considered vehicles, and the next task was assigned once the task was completed.