$$\rightleftharpoonup{xx}$$
$$\longleftharp{xx}$$,
$$\longrightharp{xx}$$,
Preliminaries
System model: The VANET system consists of three primary entity types: trusted authority (TA), roadside units (RSUs), and vehicles with onboard units (OBUs). The TA is central to initiating the initialization, key management, and occasional revocation. It is fully trusted and typically government- or infrastructure-controlled. Each RSU is a stationary unit deployed along the road. This provides a communication infrastructure; in this model, RSUs are assumed to be connected to the TA via a secure backbone (e.g., fiber or a secure network) so they can send or receive updates from the TA as needed. Vehicles are equipped with OBUs that enable vehicles to vehicle (V2V) and vehicles to infrastructure(V2I) communications. This study assumes that OBUs have a tamper-proof device (TPD) or secure hardware module that can store cryptographic keys and perform cryptographic operations in isolation, protecting long-term secrets from physical compromise.
Communication model: Vehicles broadcast periodic one-hop messages (such as basic safety messages) over a wireless channel (e.g., IEEE 802.11p or C-V2X PC5) that can be received by other vehicles and RSUs in range. These messages must be authenticated by the receivers to ensure their validity. RSUs also send periodic information (traffic signals and warnings) to vehicles through vehicle-to-infrastructure (V2I) communication. In this work, the primary focus is on the authentication of vehicle-to-infrastructure (V2I) messages. It means that the vehicles are authenticated by an RSU through batch authentication when they enter the RSU’s coverage region. V2V authentication can be handled similarly by having vehicles use the same signature scheme; however, batch verification is most beneficial at RSUs, which may need to verify many vehicles’ messages simultaneously.

Figure 1: Batch verification in VANET network. This figure depicts the architecture used for batch authentication, illustrating how multiple OBUs in vehicle batches (e.g., BATCH1 and BATCH2) communicate wirelessly with RSUs at intersections or traffic points, which are connected via wired links to a central TA. The protocol enables collective verification of authentication requests in high-density traffic using Chebyshev polynomials. Each vehicle computes an authentication token by evaluating Tk(x) mod P, concatenates it with its identity and timestamp, hashes the value, and transmits it to the RSU. The RSU aggregates the tokens and verifies them collectively.
Abbreviations; VANET = Vehicular Ad Hoc Network; OBU = On-board Unit; RSU = Roadside Unit; TA = Trusted Authority. Please click here to view a larger version of this figure.
Batch authentication in VANETs: In high-density traffic environments, RSUs may receive authentication requests from multiple vehicles within a very short time frame. Performing individual authentication for each request can cause significant computational delays and increase communication overhead. As illustrated in Figure 1, the proposed batch authentication mechanism leverages the mathematical properties of Chebyshev polynomials to achieve efficient multi-vehicle-verification15. Each vehicle computes an authentication token αi by evaluating a Chebyshev polynomial Tvi(Tr(x)) modulo a large prime p, where vi is the vehicle’s private key, r is the RSU’s private key, and x is a public base. The output is concatenated with the vehicle’s digital identity and timestamp, hashed, and transmitted to the RSU. The RSU aggregates all received tokens into a single value and verifies them collectively using the relation Tr.∑vi(x) modulo p. This approach significantly reduces the number of expensive verification operations, thereby improving scalability in environments such as intersections, toll gates, and traffic choke points.

Figure 2: Transfer authentication in VANET networks. This figure shows the proposed lightweight handover authentication protocol that allows a vehicle to move from the current RSU (Roadside unit 1) to the next RSU (Roadside unit 2) without full re-authentication, which can reduce latency. RSU1 generates an authorized card using hash-based concatenation of public keys and a random value, then applies Chebyshev polynomial operations to compute intermediate parameters (ω₁, ω₂), an initial key (IK), an encrypted session key, and a temporary key (TK). These values are sent to the vehicle and forwarded to RSU2. RSU2 verifies the data and recovers the session key using inverse Chebyshev operations, establishing a secure session key (SK) for uninterrupted communication. The protocol supports fast and secure handovers suitable for high-speed vehicular communication environments. Abbreviations; VANET = Vehicular Ad Hoc Network; RSU = Roadside Unit; IK = Initial Key; TK = Temporary Key; SK = Session Key. Please click here to view a larger version of this figure.
Transfer authentication for seamless handover: As vehicles move between RSU coverage zones, re-performing full authentication with every new RSU introduces latency and may disrupt secure sessions. The transfer authentication process, as depicted in Figure 2, enables a secure and lightweight handover. The current RSU generates an authorized card ACi by hashing the concatenation of the vehicle’s and RSU’s public keys along with a random session parameter bi. Using Chebyshev polynomial transformations TAC(x) modulo p, the RSU computes intermediate values ω1,ω2 = ω1
FPKRi, a session-specific key IKi = H(ω1
FPKvi) and an encrypted session key ω3 = (EIKi(SKi)). Finally, a temporary key TKi is derived from γ = bi.IKi-1 using another Chebyshev transformation Tγ(x). The tuple (TKi,ω2,ω3) is sent to the next RSU, which uses it to verify and resume secure communication with the vehicle without performing full re-authentication. This mechanism ensures minimal disruption and ultralow latency for vehicles moving at high speeds.
Mobility and handover: Vehicles moving from one location to another in the network may encounter multiple RSUs along their route. By combining Chebyshev polynomial-based batch authentication for initial RSU access and transfer authentication for mobility handovers, the system achieves both scalability and continuity16. Batch authentication effectively handles many simultaneous vehicle authentications, whereas transfer authentication reduces re-authentication delays during RSU transitions. Together, these mechanisms form a strong, mathematically secure, and performance-effective framework for VANET authentication.
Chebyshev polynomial preliminaries
Chebyshev polynomials (Tn(x))are the mathematical core concept of the authentication scheme. They follow a recurrence formula and have features that make them suitable for one-way cryptographic functions. The main definitions and properties are as follows.
Definition: The Chebyshev polynomial of degree n (for integer n≥ 0):
Tn(x) = cos(n arccos x),
for x
[-1,1]]. Equivalently, one can define it over the reals or modulo a prime P. The first few Chebyshev polynomials of the first kind Tn(x) up to n=4 (degree varies from 0 to 4) described in Table 2.
| S.No | Degree | Description | Result |
| 1 | T0(x) | T0(x) = cos(0.arccros x) = cos(0) = 1 | T0(x) = 1 |
| 2 | T1(x) | T1(x) = cos(1.arccros x) = cos(arcos x) = 1 | T1(x) = x |
| 3 | T2(x) | T2(x) = cos(2.arccros x) = 2cos2(arcos x)-1 = 2x2-1 (Since cos(2θ) = 2cos2θ-1) | T2(x) = 2x2-1 |
| 4 | T3(x) | T3(x) = cos(3.arccros x) = 4x3-3x
(Since cos(3θ) = 4cos3θ-3cosθ) | T3(x) = 4x3-3x |
| 5 | T4(x) | T4(x) = 8x4-8x2+1
(Since cos(4θ) = 8cos4θ-8cos2θ+1) | T4(x) = 8x4-8x2+1 |
Table 2: Evaluation of recurrence relation. This table presents the first few Chebyshev polynomials of the first kind Tn(x) (for degrees 0 to 4), computed using the recurrence relation that forms the mathematical foundation of the proposed authentication scheme. Abbreviations; Tn(x) = Chebyshev polynomial of degree n evaluated at x; n = Polynomial degree; x = Input variable.
In general, they satisfy the recurrence:
Tn+1(x) = 2xTn(x) - Tn-1(x), with T0(x) =1, T1(x) = x .
This recurrence allows efficient iterative computation of Tn(x).
Semi-group property: Similar to multiplicative exponents, Chebyshev polynomials display a composition property specifically:
Tm(Tn(x)) = Tm.n(x) ,
for any positive integers m,n. In words, if one first applies a Chebyshev polynomial of degree n to x, and then applies another Chebyshev polynomial of degree m to the result, it is equivalent to applying a Chebyshev polynomial of degree m * n directly to x. This property is central to using Chebyshev polynomials in Diffie–Hellman like key exchange and authentication protocols, because it resembles the property (ga)b = (gb)a of exponentiation in a cyclic group.
Chaotic behavior: For degrees n>1 , the map x
Tn(x) (when x is in [-1,1]) has been shown to be chaotic mapping under specific conditions. Informally, a small change in x can cause large changes in Tn(x) when n is large, and Tn(x)is distributed in [-1,1] in a way that for large n can appear random. This "pseudo-randomness" is useful in cryptography for producing non-predictable outputs.
Chebyshev polynomial discrete logarithm problem (CPDLP): This is similar to the discrete logarithm problem but uses Chebyshev polynomials. Given a prime modulus P and public values x and y = Tn(x) mod P, it’s very hard to find the integer n. In other words, if one knows x and y, figuring out n is extremely difficult when the numbers are large. This is similar to the classic discrete log problem, where finding a from ga mod P is tough.
Chebyshev polynomial Diffie–Hellman problem (CPDHP): Given x, Ta(x), and Tb(x) (for random secret integers a,b), it is hard to compute Ta.b(x) without knowing either a or b. This mirrors the Diffie–Hellman problem: give ga and gb, an adversary cannot compute gab. In the Chebyshev context, note that Tab(x) = Ta(Tb(x)) = Tb(Ta(x)) by the semi-group property; so if two parties each know one of a,b they can each compute Tab(x) easily, while an eavesdropper knowing only the individual results cannot.
The security of the scheme relies on these assumptions (CPDLP and CPDHP are intractable). For practical implementation, this study operates in a finite field (modulo a large prime P) to guarantee distinct behavior. Typically, a random number x in [2,P-2] is chosen as a system parameter (this plays a role like a generator in a multiplicative group). The TA will choose such an x and publish it as part of the public parameters. Then the Chebyshev polynomials can be computed mod P via the recurrence formula. Although x is not in [-1,1] in this case, one can use the isomorphism between Chebyshev polynomials and hyperbolic cosine for values outside [-1,1], or simply treat the recurrence algebraically mod P. The chaotic property, in a strict sense, applies to real intervals; however, for cryptographic usage, study relies on the unpredictability due to the hardness of the CPDHP in the finite field.
Attack model
In the proposed batch and transfer authentication framework for VANETs using Chebyshev polynomials, researchers consider a realistic threat landscape in which both external and internal adversaries may attempt to disrupt secure communication. External attackers are entities outside the vehicular network that aim to intercept, alter, or inject malicious messages without possessing any legitimate authentication credentials17. Internal attackers, on the other hand, are compromised or malicious vehicles or RSUs that already hold valid credentials but misuse them to impersonate others, forge data, or launch coordinated attacks.
Man-in-the-middle (MIM) attack: The adversary intercepts and relays messages between two legitimate parties while potentially altering their content. The protocol mitigates this by employing mutual authentication and session key agreement based on the hardness of the Chebyshev polynomial problem, ensuring that any intercepted data is computationally infeasible to manipulate without detection18.
Replay attack: An attacker resends previously captured valid messages to gain unauthorized access or cause network confusion. Researchers address this issue by incorporating timestamps and session identifiers into the authentication process, ensuring that messages are valid only within a short time window and cannot be reused later.
Impersonation attack: is also considered, where an attacker attempts to pose as a legitimate vehicle or RSU. By tightly binding the authentication process to unique Chebyshev polynomial keys and verifying digital signatures during batch and transfer authentication, the system ensures that only genuine participants can communicate.
Eavesdropping attacks: where adversaries passively monitor communications to extract sensitive information. The proposed scheme ensures confidentiality through secure session key generation; therefore, even if data packets are intercepted, they remain unintelligible without the secret key.
Collusion attacks: where multiple compromised entities collaborate to break the authentication protocol. The use of aggregated verification in batch authentication and independent verification in transfer authentication prevents compromised nodes from collectively forging valid credentials.
| Symbol | Description |
| Ui | i-th vehicle in the VANET |
| RSU | Roadside Unit |
| TA | Trusted Authority |
| TSi | Timestamp generated by vehicle |
| TARSU | Timestamp generated by RSU |
| TSTA | Timestamp generated by TA |
| ΔT | Maximum allowed clock difference for message validity |
| DIDUi | Pseudonym-based identity of vehicle Ui |
| DIDRSU | Pseudonym-based identity of RSU |
| Tv(x) | Chebyshev polynomial with vehicle's private key "v" |
| Tv(x) | Chebyshev polynomial with Trusted authority private key "b" |
TPKRi(x)
| Chebyshev polynomial with RSU’s public key |
| αi | Identity hash computed by vehicle Ui |
| βi | Identity hash computed by RSU for Ui |
| θi | Polynomial verification token from Ui used for aggregation |
| θ'agg | Expected aggregated polynomial (TA computed) |
| θagg | Aggregated polynomial product from all vehicles Θi |
| mi,ni | Random session key seed values from generated by TA |
| ri,ui | Secret scalar values assigned to RSU and vehicle respectively |
| PUBRSU | Public key of RSU |
| PUBui | Public key of vehicle Ui |
| E1(i),E2(i) | Masking values computed via hash for confidentiality |
| IK(i) | Components of authentication/session key exchange messages |
| SKi | Final session key established between vehicle and RSU |
| H(.) | Collision-resistant hash function |
| ESK(.)/DSK(.) | Symmetric encryption/decryption using session key |
| || | Concatenation operator |
| mod P | Modular operation over a large prime p |
Table 3: Notations. This table lists the key symbols, parameters, and cryptographic notations employed throughout the paper.
Proposed Schema:
This proposed scheme consists of two main components: (i) a batch message verification mechanism using Chebyshev polynomials and (ii) a transfer authentication protocol for vehicle handovers between RSUs. This study first provides an overview of the system setup and then describe each component in detail in the following sections along with that the terminology and the notation were illustrated in Table 3.
Vehicle registration:
Step 1: Each vehicle initiates the authentication process. Let there be n vehicles u1,u2,u3....,un attempting authentication with the same RSU at time t. Each vehicle ui computes:
αi = H(DIDui|| Tvi(Tb(x)) || TSi) (1)
Then, ui sends:
I1(i) = (αi,DIDui,TSi) (2)
to the RSU.
Step 2: RSU aggregates and prepares for batch authentication after receiving all I1(i), RSU performs:
1. Timestamp validation: |TSc - TSi| ≤ ΔT
2. Compute RSU response hash for each vehicle: βi = H(DIDRSU||Tri(Tb(x))||TSRSU)
3. Compute Chebyshev tokens: θi = Tvi(TPKRi(x)) mod P
4. Aggregate all tokens:
5. Prepare batch message:
and send to TA.
Step 3: TA verifies batch signatures
1. Verify timestamp: TSTA - TSRSU ≤ ΔT
2. Check RSU hash: βi* = H(DIDRSU || Tb(Tri(x)) || TSRSU) = βi
3. Check vehicle hash: αi* = H(DIDui|| Tb(Tvi(x)|| TSi) = αi
4. Aggregate verification: θ'agg = T∑vi(x)mod P
H(θagg) = H(θagg') If all passes, authentication is successful.
Step 4: Session key establishment (in batch) for each ui , TA performs:
1. Compute: E1(i) = H(PUBRSU||ri||TSRSU)
E2(i) = H(PUBui||vi||TSi) .
2. Generate random values mi,ni
Z*P
3. Compute session key: SKi = H(mi||ni||ri||vi)
4. Construct encrypted components:
I3(i) = H(mi)
E1(i)
I4(i) = H(ni)
E2(i)
I5(i) = SKi
H(mi)
I6(i) = SKi
H(ni)
Send bundle: {I3(i),I4(i),I5(i),I6(i),TSTA}ni=1
Step 5: RSU sends session info to each vehicle ui
1. Recover: H(mi) = I3(i)
E1(i)
SKi = I5(i)
H(mi)
2. Send to ui : {I4(i),I6(i),TSRSU+1}
Step 6: Vehicles complete session key extraction for each ui
1. Compute: H(ni) = I4(i)
E2(i)
SKi = I6(i)
H(ni)
2. Use the session key to encrypt messages:
ESKi(mi||PUBui||PUBRSU)
Step 7: Transfer authentication for seamless handover
Step 7.1: Authorized card generation by RSU will compute
ACi = H(FPKvi|| FPKRi|| bi)
ω1 = TAC(x) mod P,ω2=ω1
FPKRi
IKi = H(ω1||FPKvi)
ω3 = EIKi(SKi)
TKi = Tγ(x) mod P
γ = bi.IKi-1
Send (TKi,ω2,ω3) to the next RSU.
Step 7.2: Validation by the neighboring RSU
TAC(x) = ω2
FPKRi-1
IKi '= H(TAC(x)||FPKvi)
TTKi(IKi'(HORi))mod P = Tt(x)mod P
Step 7.3: Session key recovery (New RSU decrypts)
SKi = DIKi'(ω3)
The vehicle ui is now authenticated within the new RSU zone and can continue secure communication, with all notations used in the algorithm detailed in Table 3.
In Figure 3, researchers have explained in detail about the transfer authentication with a swim lane diagram, how the current RSU transfers the authorization to the new RSU by sending its parameters (TKi,ω2,ω3) and after receiving these parameters from the new RSU, it validates the verifies by using
TTKi(IKi'(HORi))mod P = Tt(x)mod P . From this session, the key will be recovered by the new RSU and sent to the Vehicle.

Figure 3: Transfer authentication between two RSUs. This figure illustrates the flowchart of the transfer authentication protocol in a VANET, where a vehicle facilitates secure handover between the current Roadside Unit (RSU 1) and the next Roadside Unit (RSU 2). The process begins with authenticated card generation and cryptographic computations at RSU 1, followed by transmission of parameters to the vehicle, validation, and session key recovery at RSU 2, concluding in the establishment of a secure session key. Abbreviations; VANET = Vehicular Ad Hoc Network; RSU = Roadside Unit. Please click here to view a larger version of this figure.