## 3 Methodology  
This research presents an enhanced lightweight authentication protocol for vehicles utilizing a third-party certification authority (CA) in vehicular AdHoc networks (VANETs). The CA assumes the responsibility of monitoring traffic within the network. The study introduces separate protocols for registration, authentication, V2V, and V2X communication while addressing resource allocation and sharing in vehicular communication. The research proposes greedy resource allocation and graph-based baseline resource allocation algorithms, which have been implemented in MATLAB. REST APIs using PHP 8 and MySQL have been developed to establish the V2V and V2I communication channels, with performance analysis conducted using the collaborative API development tool, Postman.  
We need both approaches, greedy resource allocation and graph-based baseline resource allocation algorithms, because they serve different purposes and are suited for different resource allocation problems. Greedy algorithms offer simplicity and efficiency, making them useful for quick and straightforward allocation tasks where immediate gains are prioritized. On the other hand, graph-based baseline algorithms provide a more comprehensive and optimized solution by considering dependencies, constraints, and the overall system state. They are suitable for complex resource allocation problems requiring a global perspective and the ability to handle intricate resource relationships. By having both approaches, we can apply the most appropriate algorithm based on the specific requirements and constraints of the resource allocation problem.  
The results demonstrate the exceptional performance of the protocols in V2V and V2X communication, particularly in terms of average End-to-End (E2E) delay, link failure, and secure communication. The protocols yield notable benefits, including enhanced throughput, maximized Packet Delivery Ratio (PDR), and reduced TCP connection timeouts. The notions and assumptions are presented in Table 4.  
\begin{table}
\begin{tabular}{c c} \hline
**Notation** & **Description** \\ \hline \(V_{i}\) & A Vehicle \\ \(S\) & Certification Authority Server \\ \(ID_{i}\) & Vehicle ID \\ \(RN_{i}\) & Vehicle Registration Number \\ \(filter_{par}()\) & Extract Numeric Values from a String \\ \(NC_{i}\) & Vehicle Numeric Code extracted from the Registration Number \\ \(E_{i}\) & Vehicle e-mail \\ \(PW_{i}\) & Vehicle Password \\ \(||\) & Concatenation \\ \(h(.)\) & One-Way Hash Function \\ \(t_{i}\) & Vehicle Timestamp \\ \(t_{s}\) & Server-Side Timestamp \\ \(r_{i}\) & LCG-Based Random Numbers \\ \(VC_{s}\) & Vehicle Code generated by the server \\ \(SVC_{s}\) & Shuffled Vehicle Code using the FYS algorithm \\ \(RES_{s}\) & The Result computed on the Server-Side \\ \(SPW_{i}\) & Secured Password for Vehicle \\ \(UC_{i}\) & Updated Vehicle Code \\ \(UC_{s}\) & Updated Vehicle Code generated by the server \\ \(REF_{i}\) & Vehicle Reference \\ \(SUCV_{s}\) & Shuffling of Updated Vehicle Code generated by the server \\ \(VCA_{s}\) & Vehicle Code for Authentication generated by the server \\ \(SELECT\_{RANDOM_{s}}\) & OTP-Like Vehicle Code generated by the server \\ \(SK_{s}\) & Vehicle Session Key generated by the server \\ \(AT_{i}\) & Vehicle Authentication Method \\ \(AS_{i}\) & Vehicle Authentication Status \\ \(Message\) & Server Response Against HTTP Request \\ \(<>\) & Not Equal Operator \\ \(lat\) & Latitude \\ \(long\) & Longitude \\ \(CL_{i}\) & Current location of the vehicle moving on the road \\ \(LIII_{i}\) & Vehicle Threshold Location Interval \\ \(IT_{s}\) & Server Interval Table \\ \(LT_{s}\) & Server Log Table \\ \hline \end{tabular}
\end{table}
Table 4: Notation Guide.