# PBF: A New Privacy-Aware Billing Framework for Online Electric Vehicles with Bidirectional Auditability

Authors: Rasheed Hussain; Junggab Son; Donghyun Kim; Michele Nogueira; Heekuck Oh; Alade O. Tokuta; Jungtaek Seo
Journal: Wireless Communications and Mobile Computing
 (2017)

---

## Abstract

Recently an online electric vehicle (OLEV) concept has been introduced, where vehicles are propelled by the wirelessly transmitted electrical power from the infrastructure installed under the road while moving. The absence of secure-and-fair billing is one of the main hurdles to widely adopt this promising technology. This paper introduces a new secure and privacy-aware fair billing framework for OLEV on the move through the charging plates installed under the road. We first propose two extreme lightweight mutual authentication mechanisms, a direct authentication and a hash chain-based authentication between vehicles and the charging plates that can be used for different vehicular speeds on the road. Second, we propose a secure and privacy-aware wireless power transfer on move for the vehicles with bidirectional auditability guarantee by leveraging game theoretic approach. Each charging plate transfers a fixed amount of energy to the vehicle and bills the vehicle in a privacy-aware way accordingly. Our protocol guarantees secure, privacy-aware, and fair billing mechanism for the OLEVs while receiving electric power from the infrastructure installed under the road. Moreover, our proposed framework can play a vital role in eliminating the security and privacy challenges in the deployment of power transfer technology to the OLEVs.


---

## Body

## 1. Introduction

As the fuel price is going up, alternative fuel vehicles, in particular, electric vehicles, are getting more attention. Previously, electric vehicles were suffering from various issues such as low reliability, high consumer satisfaction, and low return on investment [1]. However, thanks to the recent advancements in automotive, electronics, and communication technologies, electric vehicles have overcome the issues and have become pervasive on the present highways. Still, there are a number of challenges to address in order to make electric vehicles more practical. One of the most crucial problems is that the capacity of the state-of-the-art battery for electric vehicles is not sufficient to drive the cars over a long distance without recharging. It is well known that the battery technology has been slowly improved [2], and thus we can hardly expect to have a much higher capacity battery for electric vehicles in the near future. Meanwhile, as of today, there is a relatively small number of places to recharge the battery of an electric vehicle along a highway [3]. Most of all, compared to the time to refuel a traditional vehicle with a combustion engine, it takes significantly longer to charge the battery through plug-in technology in a charging station [4] or by staying on a wireless charging plate (CP) [5].Recently, the concept of online electric vehicle (http://olev.kaist.ac.kr/en/index.php) is introduced to alleviate the aforementioned issues of electric vehicles. Electric vehicles with a special onboard unit can obtain the electricity on the move in a wireless manner while passing over a road surface under which power line is installed. It is envisioned that this new technology will make a significant contribution to expanding the adoption of electric vehicles. Despite the apparent benefits, there are still a number of issues that need to be resolved to aid the wide deployment of online electric vehicles. In particular, consider the problem of designing a proper billing mechanism for this wireless-charging-on-the-move strategy. One straightforward solution would be taking a picture of every vehicle that is entering a road designed for online electric vehicles and sending the flat amount of bill to each one of them. This strategy works well for many vehicles with combustion engine on modern toll plaza at highways where they pay their toll tax in a wireless and efficient manner. However, it is clearly not fair for online electric vehicles with almost fully charged battery to pay the same amount of money paid by those vehicles with the almost empty battery since the driver of a vehicle with the fully charged battery may not want to use online power service to save the cost. In addition, collecting pictures of the vehicles entering every part of the road is almost not possible and also can cause a privacy abuse. Therefore, it is not desirable even though this strategy is widely used for toll tax collection at a toll plaza on the highways. Moreover, recently radio frequency identification (RFID) gained a lot of attention from the service providers and has been widely deployed due to its simple operation and low cost [6–9]. However, our case is completely different from RFID scenario because in our case the requirements for traceability and deniability are critical when compared to RFID authentication and billing. Hence the comparison between RFID-based solutions and our scenario would not be fair.Motivated by our observations, in this paper, we propose a new secure-and-fair billing framework for online electric vehicles. In detail, we propose to adopt a road which consists of a series of short-and-equal-sized electricity supply segments, each of which serves as a unit for billing. Before an online electric vehicle enters a new segment, it can decide to use the electricity, while moving over the segment, or deny it depending on its current battery level. Once the vehicle decided to use the electricity, it needs to authenticate itself to the segment and obtain a secret to consuming it (see Figure1). To improve the degree of fairness and service granularity, that is, to be billed for actual use only, it is important to make the segment short. At the same time, to improve the efficiency of the segment, which is the actual rate of the segment used for charging against the portion of the segment used for other use such as authentication, it is crucial to design the authentication protocol to be as lightweight as possible. To guarantee the privacy of each driver and reduce the operation cost, it is highly desirable not to use a camera for billing. Rather than using the camera to take the picture of each vehicle to enter every segment, we propose a wireless communication based conditional privacy mechanism so that the real identity of the driver can be exposed by the revocation authority only if there is a legal need such as refusing to pay after actual electricity consumption. Finally and most importantly, we provide a mutual audit mechanism through which a driver cannot deny the usage of legitimate electricity, as well as the electricity service provider cannot overcharge.Figure 1
Online electric vehicle can charge its battery while moving after the authentication with the highway segment.Summary of Contributions. This paper is the extension of our previous work [10]. The preliminary version of this work contains basic mutual authentication mechanism between CP and OBU whereas in the current extended version we address the issues of conditional privacy preservation, two mutual authentication mechanisms, bidirectional auditability, and billing mechanism in the charging-on-the-move environment. Moreover, the extended version also includes a game theoretic approach to guarantee bidirectional auditability in the charging process. To this end, in this paper, we propose a security framework for electric vehicles which supports the following relevant features, and thus the contributions of this paper are as follows.(a) Bidirectional Audit. We design a mechanism that guarantees privacy-aware bidirectional auditability for both electric power providing authority and the vehicles. To deal with the billing and auditing, we propose a semisimultaneous billing where each vehicle, when it charges its battery, is billed on plate-by-plate basis where each plate delivers a constant amount of energy. In other words, the vehicles are billed with a fixed amount.(b) Conditional Privacy. We use multiple pseudonymous mechanism to preserve the conditional privacy of the vehicles at every stage of the protocol.(c) Mutual Authentication. We devise a fast and lightweight authentication mechanism for vehicles and the charging plates keeping in mind the portion of the charging plate designated for authentication.(d) Game Theoretic Approach. We employ a game theoretic approach to model the proposed bidirectional auditability mechanism in order to establish Nash Equilibrium between the charging plate and the vehicle.This paper proceeds as follows. Section2 outlines the literature review regarding wireless power transfer followed by the system model and problem definition in Section 3. In Section 4, we outline our proposed scheme and quantitatively analyze our system in Section 5. In Section 6, we give our concluding remarks.


## 2. Literature Review

Today, some of world most renowned automobile companies are producing battery propelled vehicles and it is envisioned that soon electric vehicles will outclass the conventional automobiles due to economic and environmental reasons. The technological breakthrough in both electrification technology and the energy storage technology has made it possible for the automobile companies to achieve this milestone. From the studies conducted so far, it can be inferred that, in the near future, most of the fossil fuel propelled vehicles will possibly be replaced by the electric vehicles (see [11]). In [11], Weissinger et al. outlined the speed range, storage range, and the battery types of vehicles till the year 2008. To date, many efficient charging schemes have been proposed in the literature to save the commute time for the drivers [12]. However, the frequency of recharging is still a problem that needs to be addressed.To motivate the use of electric vehicles, a new concept of wireless power transfer (WPT) was introduced [5]. In [5], authors carried out a detailed survey regarding wireless power transfer and covered many dimensions such as the distance between the transmitting and receiving entity, and cost of the technology. The concept of green car was introduced in 2009 by KAIST, South Korea, by the name of online electric vehicle (OLEV) [13]. The motivation for OLEV was the weight and the cost of the battery in electric vehicles, low frequency of charging, fast installation, low maintenance cost, and so forth. To date, remarkable results have been achieved by this project and currently they operate and run prototype buses in the KAIST campus, South Korea [14, 15]. Nonetheless, such online vehicle would require massive power line infrastructure installed under the road. Moreover coverage would be another issue due to the cost factor. For secure WPT, vehicles need to preform mutual authentication with the CPs before the power transfer begins. However, the interconnection time between the CP and OBU is very short. Therefore, it is essential to devise an extreme lightweight and yet efficient authentication mechanism for this purpose. It is to be noted that although there exist sophisticated and efficient authentication mechanisms in VANET [16], these schemes cannot be directly used in our scenario due to the unique features, characteristics, and challenges of the charging on the move.From mutual authentication standpoint, Chuang and Lee [17] proposed a hash-based authentication mechanism called trust-extended authentication mechanism (TEAM). TEAM adopts the concept of transitive trust relationships where a normal vehicle becomes the trusted entity after successful authentication and can delegate the authentication process in the absence of the authorities. Moreover TEAM does not protect the privacy since original ID is shared during authentication. On the other hand, even if a normal vehicle successfully authenticates itself, it does not guarantee that the vehicle will not be malicious while delegating authentication function. Therefore, we believe that the transitive trust may lead to even worst situation from security standpoint in VANET.Billing is an important requirement in commercial networks and it can be abstractly divided into two classes, time-based billing and content-based billing. In the former, nodes (subscribers or consumers) pay the service fee based on time, for instance, the Internet access charges, and in the latter case, nodes pay based on the content they receive where the specific content costs a constant amount of money, for example, downloading a song from iTunes and so forth [18]. A number of billing mechanisms have been proposed for wireless mesh networks [19, 20] and commercial VANET applications [18, 21]. In [18], the authors propose a portable authentication/authorization/accounting (AAA) framework for purchasing services from the RSUs. They use signature-based and key policy attribute-based encryption (KP-ABE) in their billing mechanism to attain localized fine-grained access control and also employ E-coin. In another work, Yeh and Lin [21] proposed a local and proxy-based authentication and billing scheme to lessen the long-distance communication overhead. They also proposed an incentive-aware multihop forwarding for vehicles in the VANET. They use batch verification mechanism in their scheme to fulfill the security requirements and signature-based communications. However, our service scenario is different because we deal with the charging plates installed underneath the road and such sophisticated cryptographic primitives will cause enormous delay. Therefore, aforementioned schemes are not directly applicable in our scenario.Recently, some considerable results were appeared for the OLEVs. Zhao et al. proposed a new billing scheme which could detect free-riders, who charge their vehicle without payment, by checking their battery level before and after a charging plate [22]. The free-riders could charge by getting closer to authenticated and billed vehicles. However, this is an unrealistic solution as vehicles should not be on the same charging segment, which is 50 m long or longer than one mile according to their description, to avoid to be treated as a free-rider. All vehicles in traffic jam must pay for charging even if they do not want to charge. Saxena and Choi proposed a bilinear pairing based authentication scheme for flexible charging in vehicle-to-grid networks [23]. However, their proposed scheme is not compatible with our environment as they considered a wired charging which vehicles need to be connected to for a relatively longer time period. Li et al. proposed a fast authentication scheme with segmented charging plates for wireless charging [24]. Their simulation results show that the proposed scheme is highly efficient as it takes only 0.11 ms to verify vehicles. However, their system model needs to have a gap between charging pads to prevent the free-riders. The two neighboring charging pads should be separated by 0.8 m while the length of charging pads is 0.4 m, and thus this setting makes the system have low utilization of charging. Heavy vehicles, which need more energy to move, would be discharged slowly on the road.In this paper, we, to the best of our knowledge, for the first time propose a secure and privacy-aware mechanism to transfer the electric power to propel the vehicles moving on the road where the power transfer technology is installed underneath the road in the form of charging plates. Moreover our proposed scheme also guarantees bidirectional audit. First we propose two lightweight and fast privacy-aware mutual authentication mechanisms between the vehicles and the charging plates installed under the road. The two authentication mechanisms can be adapted with different vehicular speeds and the length of the charging plates. Then we propose a secure charging mechanism for vehicles with bidirectional auditability guarantee where vehicle is billed in a semisimultaneous manner on the per-plate basis. We also employ a game theoretic approach for modeling and guaranteeing auditability by establishing Nash Equilibrium between the charging plates and the vehicles.


## 3. System Model and Problem Statement

### 3.1. System Participants and Network Model

Our proposed system model consists of electric vehicles and an electric power delivery infrastructure. Electric power delivery service is exercised by the charging service providing authority (CSPA) that is responsible for providing the vehicles with the electric charge through charging plates and billing them accordingly. The charging infrastructure is installed under the surface of the road and each road segment of a certain length is covered by the charging plates. The charging plates also have hardware for communication and computation purpose and these plates are responsible for authentication prior to battery charging, billing, and logging the audit information. These charging plates communicate with both vehicles and CSPA back and forth during the charging and the billing process. We also introduce some components from vehicular ad hoc network (VANET) that are frequently assumed in VANET. These components are used by electric vehicles (throughout the paper, the terms “vehicle,” “vehicular node,” and “OBU” are used interchangeably and we mean electric vehicle collectively by these terms) for initialization and registration. These components include vehicle management, registration, and revocation authorities. The department of motor vehicles (DMV) is at the top of the hierarchy where every vehicle should be registered beforehand. Revocation authorities are leveraged to revoke the identity of the vehicle when needed with the consent from law enforcement authorities (police or judiciary) in the form of a warrant. There may be heterogeneous types of vehicles on the road, but for ease of understanding, we focus only on the electric vehicles in this paper. Therefore, our proposed scheme can be easily implemented in the VANET framework, which is one of the most popular and promising future vehicular infrastructures.The taxonomy of the system participants is shown in Figure2 and the network model is shown in Figure 3. We consider a fleet of electric vehicles on the road where these vehicles receive electric power from the power line installed beneath the road, depending upon the usage of the vehicle. It can be seen in Figure 1 that road segment consists of the power line distribution technology installed beneath the road in the form of charging plates. A portion of the charging plate is leveraged for authentication purpose and the rest of the charging plate is used for transferring the electrical energy to the vehicle (see Figure 1). Vehicles mutually authenticate with the charging plates before receiving electric power from the plates. After successful authentication, the fixed designated amount of electrical energy is transferred to the battery and the vehicle is billed accordingly. The communication channel between vehicles, registration, and revocation authorities, and the charging plates is based on Dedicated Short Range Communication (DSRC) (https://www.fcc.gov/wireless/bureau-divisions/mobility-division/dedicated-short-range-communications-dsrc-service) standard whereas charging plates are connected to the charging service providers through high-speed wired links.Figure 2
Taxonomy of system participants.Figure 3
The network model.In our network model, bidirectional auditability is of paramount importance because the vehicle wants to get the energy if it has paid for it and similarly the service provider must receive the amount of due amount if the electrical charge is transferred to the vehicle. Therefore, in the next subsection, we outline the bidirectional auditability problem by leveraging game theoretic approach.


### 3.2. Problem Definition

Based on the aforementioned system and network model, we outline our problem statement. The problem statement is multidimensional and covers a number of aspects for the unique environment of wireless charging. The wireless-charging-on-the-move phenomenon has a unique set of requirements and thus introduces new problems. Firstly, due to the billing and audit, both charging plates and vehicles must mutually authenticate each other. However, due to the high speed of vehicles and the small size of the charging plate, the authentication mechanism should be extremely lightweight and fast. Secondly, in order to make the wireless charging service on the move, user satisfaction is going to be a major challenge from the privacy standpoint. In other words, the users will prefer to make the charging and billing mechanism anonymous. Therefore, a conditional privacy-aware and yet secure mechanism should be in place to cover the whole charging and billing process. Thirdly, the vehicles and the service providers should be able to carry out bidirectional auditability where both parties should be able to verify the amount of charge and the respective bill.In order to argue on the bidirectional auditability, we employ a game between the user and CP as an instance of the Guest-Host problem (GHP). In the GHP, guest and host at a hotel make sure that both of them are audited in a fair way. In game theoretic approach, an important stage called Nash Equilibrium (NE) is achieved where each player is assumed to be aware of the equilibrium strategies of the opponent(s). In NE, no player can gain anything by changing only his/her own strategy. In other words, during the game, a stage is reached where no player can benefit from changing its strategy while other players keep their existing strategy. Therefore, the current set of strategies and their payoff collectively constitute NE. In our proposed scheme, an uncooperative game theoretic approach will be explained in the later section.


### 3.3. Assumptions

Our proposed scheme is based on the following assumptions.(a)
Electric vehicles are equipped with onboard unit (OBU) and Tamper-Resistant Module (TRM) to carry out the secure computation. It is to be noted that messages are constructed inside TRM and the security parameters (keys) are saved into TRM. TRM takes care of the message construction according to its configuration. The modules that give the data as input to the TRM can still provide TRM with wrong information.(b)
DMV is a trustworthy entity and only DMV is authorized to initialize the TRM and store necessary security parameters and keys in it, whereas CSPA, charging plates, and OBUs are not trustworthy.(c)
For a single charging plate, a fixed amount of charge is transferred to vehicles and a fixed amount of bill is charged to the customer, and thus this constitutes a semistatic and fixed billing system. This can be extended to detect the exact amount of energy transferred to vehicles.(d)
We use the energy encryption scheme [25] to prevent free-riders who charge their vehicles without payment by being located on the same charging plates with a legal paid vehicle.


### 3.4. Threat Model

In our threat model, we consider that both participating parties (charging plates and vehicles) may be malicious. Their behavior can be malicious in terms of either bypassing the billing process or overcharging the energy receiving entity. Besides, the CSPA can also abuse the privacy of the electric power consumer vehicle by either exposing their location information or selling out their location-based profile to other third parties such as ads agencies. Moreover, both passive and active adversaries are considered who can sniff the communication between charging plate and OBU, modify it, or forge it. We argue that the adversaries will have more resources than the participating entities. However, the timeliness of possible attack is a challenging front for the adversaries where the possible attacks must be performed within the stipulated time that is equal to the duration of the charging and billing.


### 3.5. System Requirements and Security Models

Based on the system and threat models, we argue that the proposed scheme is secure if it satisfies the following security models.(S-1)
Mutual authentication: whenever a vehicle is moving on the authentication section and the vehicle needs to charge battery, both the vehicle and the charging plate can authenticate each other to prevent illegal charging and illegal payment. Also, an illegal vehicle and an illegal charging plate cannot pass the authentication protocol.(S-2)
Bidirectional auditability: while transferring electric power to the vehicle, bidirectional auditability must be guaranteed. In other words, a billing and provided electric power message can be verified by both a vehicle and a CSPA. Also, the billing procedure must be verifiable by all the entities, that is, OBU, CSPA, and DMV to prevent the vehicle overbilled and the CSPA underpaid.(S-3)
Conditional privacy: the conditional privacy of the vehicle’s location and the user must be preserved. The identity of a vehicle owner should be revoked to the power supplier only if it is legally necessary, for example, in case the user refuses to pay. Therefore, with this requirement fulfilled, attackers cannot obtain the user identity.Additionally, the proposed authentication and billing framework must fulfill the following requirements.(R-1)
Due to the resource constraints of the charging plate and the speed of the vehicle, the communication between charging plate and OBU and between charging plate and CSPA must be sufficiently efficient. Moreover, the authentication mechanism must be very fast and lightweight.(R-2)
At the time of charging, both the players should be in the Nash Equilibrium state.


## 3.1. System Participants and Network Model

Our proposed system model consists of electric vehicles and an electric power delivery infrastructure. Electric power delivery service is exercised by the charging service providing authority (CSPA) that is responsible for providing the vehicles with the electric charge through charging plates and billing them accordingly. The charging infrastructure is installed under the surface of the road and each road segment of a certain length is covered by the charging plates. The charging plates also have hardware for communication and computation purpose and these plates are responsible for authentication prior to battery charging, billing, and logging the audit information. These charging plates communicate with both vehicles and CSPA back and forth during the charging and the billing process. We also introduce some components from vehicular ad hoc network (VANET) that are frequently assumed in VANET. These components are used by electric vehicles (throughout the paper, the terms “vehicle,” “vehicular node,” and “OBU” are used interchangeably and we mean electric vehicle collectively by these terms) for initialization and registration. These components include vehicle management, registration, and revocation authorities. The department of motor vehicles (DMV) is at the top of the hierarchy where every vehicle should be registered beforehand. Revocation authorities are leveraged to revoke the identity of the vehicle when needed with the consent from law enforcement authorities (police or judiciary) in the form of a warrant. There may be heterogeneous types of vehicles on the road, but for ease of understanding, we focus only on the electric vehicles in this paper. Therefore, our proposed scheme can be easily implemented in the VANET framework, which is one of the most popular and promising future vehicular infrastructures.The taxonomy of the system participants is shown in Figure2 and the network model is shown in Figure 3. We consider a fleet of electric vehicles on the road where these vehicles receive electric power from the power line installed beneath the road, depending upon the usage of the vehicle. It can be seen in Figure 1 that road segment consists of the power line distribution technology installed beneath the road in the form of charging plates. A portion of the charging plate is leveraged for authentication purpose and the rest of the charging plate is used for transferring the electrical energy to the vehicle (see Figure 1). Vehicles mutually authenticate with the charging plates before receiving electric power from the plates. After successful authentication, the fixed designated amount of electrical energy is transferred to the battery and the vehicle is billed accordingly. The communication channel between vehicles, registration, and revocation authorities, and the charging plates is based on Dedicated Short Range Communication (DSRC) (https://www.fcc.gov/wireless/bureau-divisions/mobility-division/dedicated-short-range-communications-dsrc-service) standard whereas charging plates are connected to the charging service providers through high-speed wired links.Figure 2
Taxonomy of system participants.Figure 3
The network model.In our network model, bidirectional auditability is of paramount importance because the vehicle wants to get the energy if it has paid for it and similarly the service provider must receive the amount of due amount if the electrical charge is transferred to the vehicle. Therefore, in the next subsection, we outline the bidirectional auditability problem by leveraging game theoretic approach.


## 3.2. Problem Definition

Based on the aforementioned system and network model, we outline our problem statement. The problem statement is multidimensional and covers a number of aspects for the unique environment of wireless charging. The wireless-charging-on-the-move phenomenon has a unique set of requirements and thus introduces new problems. Firstly, due to the billing and audit, both charging plates and vehicles must mutually authenticate each other. However, due to the high speed of vehicles and the small size of the charging plate, the authentication mechanism should be extremely lightweight and fast. Secondly, in order to make the wireless charging service on the move, user satisfaction is going to be a major challenge from the privacy standpoint. In other words, the users will prefer to make the charging and billing mechanism anonymous. Therefore, a conditional privacy-aware and yet secure mechanism should be in place to cover the whole charging and billing process. Thirdly, the vehicles and the service providers should be able to carry out bidirectional auditability where both parties should be able to verify the amount of charge and the respective bill.In order to argue on the bidirectional auditability, we employ a game between the user and CP as an instance of the Guest-Host problem (GHP). In the GHP, guest and host at a hotel make sure that both of them are audited in a fair way. In game theoretic approach, an important stage called Nash Equilibrium (NE) is achieved where each player is assumed to be aware of the equilibrium strategies of the opponent(s). In NE, no player can gain anything by changing only his/her own strategy. In other words, during the game, a stage is reached where no player can benefit from changing its strategy while other players keep their existing strategy. Therefore, the current set of strategies and their payoff collectively constitute NE. In our proposed scheme, an uncooperative game theoretic approach will be explained in the later section.


## 3.3. Assumptions

Our proposed scheme is based on the following assumptions.(a)
Electric vehicles are equipped with onboard unit (OBU) and Tamper-Resistant Module (TRM) to carry out the secure computation. It is to be noted that messages are constructed inside TRM and the security parameters (keys) are saved into TRM. TRM takes care of the message construction according to its configuration. The modules that give the data as input to the TRM can still provide TRM with wrong information.(b)
DMV is a trustworthy entity and only DMV is authorized to initialize the TRM and store necessary security parameters and keys in it, whereas CSPA, charging plates, and OBUs are not trustworthy.(c)
For a single charging plate, a fixed amount of charge is transferred to vehicles and a fixed amount of bill is charged to the customer, and thus this constitutes a semistatic and fixed billing system. This can be extended to detect the exact amount of energy transferred to vehicles.(d)
We use the energy encryption scheme [25] to prevent free-riders who charge their vehicles without payment by being located on the same charging plates with a legal paid vehicle.


## 3.4. Threat Model

In our threat model, we consider that both participating parties (charging plates and vehicles) may be malicious. Their behavior can be malicious in terms of either bypassing the billing process or overcharging the energy receiving entity. Besides, the CSPA can also abuse the privacy of the electric power consumer vehicle by either exposing their location information or selling out their location-based profile to other third parties such as ads agencies. Moreover, both passive and active adversaries are considered who can sniff the communication between charging plate and OBU, modify it, or forge it. We argue that the adversaries will have more resources than the participating entities. However, the timeliness of possible attack is a challenging front for the adversaries where the possible attacks must be performed within the stipulated time that is equal to the duration of the charging and billing.


## 3.5. System Requirements and Security Models

Based on the system and threat models, we argue that the proposed scheme is secure if it satisfies the following security models.(S-1)
Mutual authentication: whenever a vehicle is moving on the authentication section and the vehicle needs to charge battery, both the vehicle and the charging plate can authenticate each other to prevent illegal charging and illegal payment. Also, an illegal vehicle and an illegal charging plate cannot pass the authentication protocol.(S-2)
Bidirectional auditability: while transferring electric power to the vehicle, bidirectional auditability must be guaranteed. In other words, a billing and provided electric power message can be verified by both a vehicle and a CSPA. Also, the billing procedure must be verifiable by all the entities, that is, OBU, CSPA, and DMV to prevent the vehicle overbilled and the CSPA underpaid.(S-3)
Conditional privacy: the conditional privacy of the vehicle’s location and the user must be preserved. The identity of a vehicle owner should be revoked to the power supplier only if it is legally necessary, for example, in case the user refuses to pay. Therefore, with this requirement fulfilled, attackers cannot obtain the user identity.Additionally, the proposed authentication and billing framework must fulfill the following requirements.(R-1)
Due to the resource constraints of the charging plate and the speed of the vehicle, the communication between charging plate and OBU and between charging plate and CSPA must be sufficiently efficient. Moreover, the authentication mechanism must be very fast and lightweight.(R-2)
At the time of charging, both the players should be in the Nash Equilibrium state.


## 4. Proposed Bidirectional Auditability in Online Electric Vehicle

In this section, we outline the proposed power transfer and billing mechanism and the bidirectional audit between the charging plate and the OBU by a game theoretic approach.


### 4.1. Baseline

Before using the wireless electric energy transfer service on the move, vehicles must have registered with the DMV to initialize their TRM and to store the security parameters and pseudonyms in it. Additionally, the vehicles must also register with the CSPA to get the necessary security parameters, required to the charging plates at authentication stage. Charging plates are installed under the designated road segments by CSPA and are equipped with hardware that is capable of carrying out secure computation and communication operations for authentication and billing purpose. Whenever a vehicle (the term“vehicle” throughout the rest of the paper should be read as electric vehicle; for the sake of simplicity, we use the term vehicle instead of charging vehicles) enters the road section with power line underneath it, it opts for either obtaining the electric power or not. If the vehicle selects the power reception, then it has to mutually authenticate with the charging plate. We propose two very fast and lightweight mutual authentication mechanisms; one is based on only hash and XOR functions and inspired by the Chuang and Lee’s scheme [17], while the second one is based on the hash chain. The former is a direct authentication between charging plate and OBU whereas the latter is authentication through CSPA. In the former scheme, charging plate incurs minimum communication delay, whereas, in the latter, charging plate incurs minimum computation delay. Both of the proposed schemes are suited for specific purposes that are explained later in the paper. After successful authentication, the power transfer process starts and charging plate sends the billing information to both OBU and CSPA. The billing is fixed on per charging plate basis. To preserve users’ privacy, we use pseudonymous approach and vehicles change their pseudonyms at every charging plate at the time of charging. We also model the billing and audit as a game between OBU and charging plate where both of them must achieve the Nash Equilibrium state.


### 4.2. Preliminaries and Initializations

#### 4.2.1. System Initialization

Notations in the Notations section are employed throughout the paper. We achieve user privacy through pseudonymous. In addition, in order to store the individual secret keys of the vehicles, that is,Ksym and KV in the database of revocation authorities (RAs), we use ElGamal encryption algorithm over elliptic curve cryptography (ECC) due to its proven security. Let G be a cyclic group of prime order q, where G is generated by a generator P. First of all, DMV chooses a random number x∈Z∗ as its private key and computes PK+=xP as its public key. DMV then uses threshold based secret share scheme [26] and divides x into j parts, where j is the number of revocation authorities, each RAi holds a share xi, and xi∈(x1,x2,x3,…,xj). In order to construct x from individual xi, RAs must elect one of them to be group leader and construct x from combination of xi. For the selection of group leader, any available efficient group leader election mechanism in the networks can be used.


#### 4.2.2. TRM Installation

Only DMV is authorized to install the TRM in the vehicle for the first time after purchase or repurchase. The owner of the vehicle has to personally visit the DMV for the installation and/or initialization of the TRM. After confirming the credentials of the vehicle and its owner, DMV initializes TRM and saves the system parameters in the TRM including(G,q,P,PK+,cV,incV). Additionally DMV also preloads TRM with vehicle’s individual secret key KV and pseudonym generation key Ksym.


#### 4.2.3. Pseudonyms Assignment

DMV generatesn number of pseudonyms for each vehicle by taking vehicle’s secret counter cV and increments it by vehicle V’s incrementing factor incV. The pseudonym is a complex value that also contains trapdoor for revocation. The format of generic pseudonym is given by PSOBUi=(α)Ksym∥α⊕IDKV∥niKDMV-, where α=cV+ni·incV, ni is the current count of generated pseudonym (note that it may not be linear), and ID is the vehicle’s identity. Then DMV stores these pseudonyms in its database and indexes it with the value of n. After all pseudonyms are generated for the vehicles, DMV saves these pseudonyms in vehicle’s TRM along with another value XOBU=h(PSOBU1∥PSOBU2∥⋯∥PSOBUn) and sends the anonymous pseudonyms to RAs as well. In order to help in revocation, TRM also encrypts both Ksym and KV and sends it to RAs which serve as a trapdoor in revocation. The aforementioned keys are encrypted with public master key using ElGamal encryption as follows: (1)δ1=rP,δ2=Ksym∥KV⊕HrPK+.r is a random nonce selected by the TRM for this encryption, then it sends δ1,δ2 to RAs. However, RAs can only decrypt the keys Ksym and KV when they have a warrant to do so after colluding to construct x from individual xi. The reason for saving encrypted keys in RAs database is twofold: RAs use these keys to revoke a vehicle in case of any dispute and for privacy reasons; we do not want RAs to link pseudonyms and/or extract cV and incV from the beacons until necessary, otherwise.It is also to be noted that when a vehicle consumes all the pseudonyms it has in the pseudonym pool, it needs to obtain a batch of fresh pseudonyms from the DMV. The vehicle does not need to be physically present at DMV, rather it can obtain the pseudonyms from DVM by connecting through Internet. We assume that the existing pseudonym refilling strategies can be used [27–30]. Now we outline the two mechanisms for mutual authentication and billing.


### 4.3. Direct Mutual Authentication (DMA)

In the direct approach, OBU and CP mutually authenticate each other without the intervention of CSPA. First of all, CSPA createsl number of master secret keys MSK based on hash chain by selecting a secret s, where MSKi=hi(s) and sends the key to DMV as follows: (2)CSPA⟶DMV:MSKii=1,2,3,…,l.MSKi is a hash chain-based master secret key which is based on a secret s and MSKl=hl(s). In other words, each MSKi is used for a designated amount of time, and CSPA updates MSKi after regular intervals. Since MSKi is distributed by CSPA, it can be updated in timely manner by CSPA and vehicles will receive the updated MSKi in their next registration phase with CSPA. After that, DMV also sends XOBU of the registered vehicles to CSPA for records(3)DMV⟶CSPA:XOBU.Each vehicle has a pool of legitimate traceable pseudonyms from DMV and at the time of authentication, any pseudonym from the pool can be used to start charging. The vehicle will be billed based on the used pseudonym.


#### 4.3.1. Vehicle Registration with CSPA

The vehicle, most precisely its OBU, must register with CSPA before charging. We assume a secure channel between CSPA and the vehicle. The registration of the vehicle proceeds as follows. The vehicle starts with the already shared password and upon successful access, the CSPA calculates some security parameters for the vehicle and sends it back to the OBU. The different steps and their descriptions are given below:(a)
OBU→CSPA:PWDOBU,XOBU. OBU sends these values to CSPA on a secure channel. If PWDOBU is valid, then the protocol will proceed.(b)
CSPA calculates the following 3 values, that is,H1,H2, and H3. H1 is used as a secure parameter kept by CSPA. H2 and H3 are the authentication parameters that are sent back to the OBU(4)H1=hs∥XOBU,H2=h2s∥XOBU,H3=MSKi⊕H1.(c)
CSPA registers the OBU by sending the hash functionh(), H2, and H3 to the OBU and recording these parameters by storing them in its database against the value of XOBU.CSPA→OBU:XOBU,h(),H2,H3.


#### 4.3.2. Authentication between OBU and CP

After completing the registration phase with CSPA, when the vehicle passes through the section of the power line-enabled road, it starts authentication process with the charging plate. The vehicle starts the authentication process by selecting a pseudonym from its pool of pseudonyms. Then it starts the power receiving process with the selected pseudonym in an anonymous way. The partial per charging bill is prepared based on the presented pseudonym in the authentication/charging process. It is to be noted that a fixed amount of electric power is delivered to the vehicle’s power reception module and it costs the user a fixed amount. The comprehensive mutual authentication steps are given below:(a)
OBU selects a pseudonymPSOBUi,i=1,2,3,…,n, from its pool and calculates the following parameters:(5)c1=hH2⊕PSOBUi,c2=hPSOBUi⊕XOBU,c3=hhPSOBUi∥c2∥H3δ4=rOBU⊕PSOBUi.(b)
Then OBU sends CP, the values calculated in previous step along withH3(6)OBU⟶CP:c1,c2,c3,H3,δ4.(c)
CP executes the following steps:
(i)
Start withH3 and extract the secret H1 as MSKi⊕H1⊕MSKi.(ii)
It calculatesH2 from H1 and extracts PSOBUi from c1.(iii)
CP also extractsrOBU from δ4 which is used in the construction of session key.(iv)
Then it checks for the valuec2 if it is equal to hPSOBUi⊕XOBU.(v)
And it checks ifc3 is equal to the retrieved values h(h(PSOBUi)∥c2∥H3), then the OBU is authenticated; otherwise the authentication fails. It is to be noted that there will be a fixed number of tries, of which failing will halt the authentication process.After successful authentication, OBU and CP initiate the protocol to construct a session keySKOBU-CP which is used for the later communication and billing parameters. The initialization of session key from CP serves as an acknowledgment to authentication as well. The OBU would not have been authenticated, otherwise. At this point CP already extracted XOBU, PSOBUi, and rOBU from c2, c1, and δ4, respectively. Now CP selects a nonce as rcp and calculates session key as SKOBU-CP=h(PSOBUi∥rOBU∥rcp). CP also calculates the following parameters:(7)IDJ=hrOBU∥IDcp,c4=IDJ⊕rcp,c5=rcp⊕hhPSOBUi,c6=hrcp∥c4∥c5,c7=H1⊕h2PSOBUi.I
D
c
p is the ID of the charging plate. After calculating the above values, CP constructs an authentication reply message and sends it back to OBU. This authentication reply means that OBU has been authenticated and other parameters will be sent for the session key calculation. The following authentication reply message is sent to OBU:(8)CP⟶OBU:c4,c5,c6,c7.From the above reply message, OBU extractsrcp from c4 and IDJ and checks if c6 is equal to h(rcp∥c4∥c5). If the information is correct, then the OBU authenticates CP as well and computes the session key SKOBU-CP=h(PSOBUi∥rOBU∥rcp), extracts H1 from c7, and stores it as a security parameter.At this point in time, the mutual authentication is completed and the electric power reception process will start based on the established session keySKOBU-CP.When these two entities (OBU and CP) authenticate each other, then the vehicle will receive the designated amount of power from the road (CP). At the end of each phase of the charging plate atCPi, a unit cost Ci will be accumulated to the account of the OBU against its presented PSOBUi. At the end of the whole power transfer from a number of charging plates, both OBU and CSPA will have the log of the amount of transferred power and the OBU will be billed accordingly which will be verifiable by both CSPA and the OBU. The whole authentication process in case of DMA is shown in Figure 4.Figure 4
Authentication process in DMA scenario.


### 4.4. Pure Hash Chain-Based Authentication (PHA)

For a fast moving vehicle, the DMA approach can be applied where computation is done locally by the charging plate; however, DMA may incur reasonable computation delay. Therefore, we propose another indirect authentication mechanism based on hash chain carried out by CSPA where computation delay is minimum whereas a small communication delay is introduced. Moreover this mechanism is most favorable for low speed vehicles. DMV provides the OBU withn pseudonyms PSOBUi,i=1,2,3,…,n, and hash chain corresponding to each pseudonym h(PSOBUi),h2(PSOBUi),…,hn(PSOBUi). We assume that, for the sake of charging its battery, the vehicle registers with the CSPA based on some designated policy. In other words, the car uses a new hash chain based on the designated interval in the policy. Authentication process takes place as follows:(a)
The vehicle registers with CSPA and sends one of the hash chain headshn(PSOBUi) to CSPA(9)OBU⟶CSPA:hnPSOBUi,XOBU,CertOBU.(b)
At the time of authentication and request for charging, the vehicle must provide CP with a member hash from the registered hash chainhn-1(PSOBUi)(10)OBU⟶CP:hn-1PSOBUi,XOBU.(c)
CP forwards this value to the CSPA(11)CP⟶CSPA:timestamp,hn-1PSOBUi,XOBU.(d)
CSPA validates the hash, checks ifh(hn-1(PSOBUi))=hn(PSOBUi), and replies accordingly. CSPA also replaces hn(PSOBUi) with h(hn-1(PSOBUi)). In addition to authentication, CSPA also provides the CP with a session key SKOBU-CP and saves it in its database with time and the XOBU. It is to be noted that CSPA issues a single session key for all the plates for a particular vehicle and a particular hash chain(12)CSPA⟶CP:Auth.Status,SKOBU-CP,SKOBU-CPKOBU+,CP⟶OBU:SKOBU-CPKOBU+.(e)
If the authentication is successful, then charging plate will transfer the electric power to the vehicle; otherwise the process halts. It is to be noted that one hash chain is long enough to use it for the whole day. For the next day, the vehicles can register another hash chain. This process will still preserve the conditional privacy of the OBU.The protocol for pure hash chain-based authentication mechanism is given in Figure5.Figure 5
Authentication process in PHA scenario.


### 4.5. Power Transfer, Billing, and Auditability

Once the mutual authentication is completed between the charging plate and OBU, the vehicle starts to receive the power from the road (CP) semisimultaneously with billing. More precisely, the vehicle is billed at the charging plate level. At the end of the charging process, the total bill is accumulated both at OBU and the CSPA. The process is explained in case of both direct and indirect authentication as shown in Figures6 and 7, respectively.Figure 6
Power transfer and billing process in DMA scenario.Figure 7
Power transfer and billing process in PHA scenario.


#### 4.5.1. Online Electric Power Transfer and Billing in DMA

In case of DMA, CSPA has access to the pseudonym used in the authentication process through CP. Therefore, after a successful authentication and establishment of a session key, vehicle requests for the electric power and presents the charging plate and CSPA with the pseudonym and other parameters for the billing purpose. The series of steps are given below:(13)OBU⟶CP:timestamp∥ChargingReq.∥PSOBUi∥hKVαSKOBU-CP,α=timestamp∥ChargingReq.∥PSOBUi,CP⟶OBU:Ack,timestamp∥PSOBUi∥hKVα.At this point, CP starts billing and sends the bill log to OBU and to CSPA. The bill is logged against two values, XOBU and the consumed pseudonym PSOBUi,(14)CP⟶CSPA:timestamp∥PSOBUi∥XOBU∥CostCPi,CSPA:CostXOBU=∑i=1nCostCPi.In case of DMA, the CSPA accumulates all partial billing information from individual CPs and bill the OBU accordingly. It is worth noting that we use a constant cost per charging plate. For our current proposed scheme, we consider fixed energy transfer and fixed price per certain amount of transferred energy. These parameters can be set by the service provider(s). On part of service provider(s), fixed amount of energy transfer and thus fixed price would be easy to implement and faster, whereas, for customers, dynamic billing makes more sense. However, some tradeoff solution will suffice. In the current setup, if the price is fixed per unit, and the value/volume of unit is kept small, then we can compare this scheme with the dynamic billing. For instance, depending on the demand of the customers, x units of charge could be transferred to the customer and the customer will be billed accordingly. It is also worth noting that fixed billing mechanism will alleviate the problem of free-riders that would otherwise be possible in dynamic environment if the security keys are compromised.


#### 4.5.2. Online Electric Power Transfer and Billing in PHA

In case of PHA, the CSPA does not have access to individual pseudonyms; rather it maintains the billing information based on theXOBU value. After successful authentication, OBU requests for online power transfer and the power transfer begins. Meanwhile, CSPA bills the cost for the current CP and accumulates it to the account against XOBU with timestamp information. The series of steps are given below: (15)OBU⟶CP:timestamp∥ChargingReq.∥XOBU∥hKVβSKOBU-CP,β=timestamp∥ChargingReq.∥XOBU.The CP forwards the request to CSPA where CSPA constructs a reply message for the OBU. Meanwhile when CP receives the reply message from CSPA, the vehicle will start receiving power and CSPA will record the cost for the current charging plate(16)CSPA⟶CP:timestamp∥XOBU∥hKVβ.CP forwards the message to OBU accordingly whereas CSPA calculates the bill for current CP and accumulates with the partial bills from previous CPs(17)CSPA:CostXOBU=∑i=1n-1CostCPi-1+CostCPi.This way, CSPA calculates the bill partially simultaneously with charging process which is the motive of our GHP game. We will discuss our OBU-CP game in the next subsection.


### 4.6. Revocation

In this subsection, we outline our efficient revocation mechanism.The proposed protocol preserves the users’ privacy; however in case of any misbehavior and/or bypassing the protocol, the users are subject to revocation. We incorporate an efficient revocation mechanism through which RAs can efficiently revoke the identity of the participating node. As we know the revocation functionality is distributed among a number of RAs rather than a single RA. These RAs share a part of the secret part of the share. When there is a need for revocation, the RAs collude, get a judicial warrant, and construct the secret from the shares. It is to be noted that RAs may select a session leader among them to carry out the decryption process. The encrypted keysKsym and KV are stored in RAs. When RAs obtain the secret x, they decrypt the aforementioned keys from ciphertext (δ1,δ2). In order to decrypt the encrypted keys, RA proceeds with the following steps.Take the secret valuex and calculate the following value: (18)decδ1,δ2,x=δ2⊕Hxδ1.By replacing δ2 and δ1 with the original values, we get(19)decδ1,δ2,x=Ksym∥KV⊕HrPK+⊕Hxδ1,decδ1,δ2,x=Ksym∥KV⊕HrxP⊕Hxδ1,decδ1,δ2,x=Ksym∥KV⊕HrxP⊕HrxP,decδ1,δ2,x=Ksym∥KV.After decrypting the keys, RA takes the pseudonym in question and extract the trapdoor in it in order to revoke the node. As aforementioned, every pseudonym has the trapdoor value. RA decrypts (α)Ksym and then decrypts α⊕IDKV. Then RA extracts the ID from the value α⊕ID that corresponds to the pseudonym in question. This way the pseudonym in question and hence the node are revoked by the RAs.


## 4.1. Baseline

Before using the wireless electric energy transfer service on the move, vehicles must have registered with the DMV to initialize their TRM and to store the security parameters and pseudonyms in it. Additionally, the vehicles must also register with the CSPA to get the necessary security parameters, required to the charging plates at authentication stage. Charging plates are installed under the designated road segments by CSPA and are equipped with hardware that is capable of carrying out secure computation and communication operations for authentication and billing purpose. Whenever a vehicle (the term“vehicle” throughout the rest of the paper should be read as electric vehicle; for the sake of simplicity, we use the term vehicle instead of charging vehicles) enters the road section with power line underneath it, it opts for either obtaining the electric power or not. If the vehicle selects the power reception, then it has to mutually authenticate with the charging plate. We propose two very fast and lightweight mutual authentication mechanisms; one is based on only hash and XOR functions and inspired by the Chuang and Lee’s scheme [17], while the second one is based on the hash chain. The former is a direct authentication between charging plate and OBU whereas the latter is authentication through CSPA. In the former scheme, charging plate incurs minimum communication delay, whereas, in the latter, charging plate incurs minimum computation delay. Both of the proposed schemes are suited for specific purposes that are explained later in the paper. After successful authentication, the power transfer process starts and charging plate sends the billing information to both OBU and CSPA. The billing is fixed on per charging plate basis. To preserve users’ privacy, we use pseudonymous approach and vehicles change their pseudonyms at every charging plate at the time of charging. We also model the billing and audit as a game between OBU and charging plate where both of them must achieve the Nash Equilibrium state.


## 4.2. Preliminaries and Initializations

### 4.2.1. System Initialization

Notations in the Notations section are employed throughout the paper. We achieve user privacy through pseudonymous. In addition, in order to store the individual secret keys of the vehicles, that is,Ksym and KV in the database of revocation authorities (RAs), we use ElGamal encryption algorithm over elliptic curve cryptography (ECC) due to its proven security. Let G be a cyclic group of prime order q, where G is generated by a generator P. First of all, DMV chooses a random number x∈Z∗ as its private key and computes PK+=xP as its public key. DMV then uses threshold based secret share scheme [26] and divides x into j parts, where j is the number of revocation authorities, each RAi holds a share xi, and xi∈(x1,x2,x3,…,xj). In order to construct x from individual xi, RAs must elect one of them to be group leader and construct x from combination of xi. For the selection of group leader, any available efficient group leader election mechanism in the networks can be used.


### 4.2.2. TRM Installation

Only DMV is authorized to install the TRM in the vehicle for the first time after purchase or repurchase. The owner of the vehicle has to personally visit the DMV for the installation and/or initialization of the TRM. After confirming the credentials of the vehicle and its owner, DMV initializes TRM and saves the system parameters in the TRM including(G,q,P,PK+,cV,incV). Additionally DMV also preloads TRM with vehicle’s individual secret key KV and pseudonym generation key Ksym.


### 4.2.3. Pseudonyms Assignment

DMV generatesn number of pseudonyms for each vehicle by taking vehicle’s secret counter cV and increments it by vehicle V’s incrementing factor incV. The pseudonym is a complex value that also contains trapdoor for revocation. The format of generic pseudonym is given by PSOBUi=(α)Ksym∥α⊕IDKV∥niKDMV-, where α=cV+ni·incV, ni is the current count of generated pseudonym (note that it may not be linear), and ID is the vehicle’s identity. Then DMV stores these pseudonyms in its database and indexes it with the value of n. After all pseudonyms are generated for the vehicles, DMV saves these pseudonyms in vehicle’s TRM along with another value XOBU=h(PSOBU1∥PSOBU2∥⋯∥PSOBUn) and sends the anonymous pseudonyms to RAs as well. In order to help in revocation, TRM also encrypts both Ksym and KV and sends it to RAs which serve as a trapdoor in revocation. The aforementioned keys are encrypted with public master key using ElGamal encryption as follows: (1)δ1=rP,δ2=Ksym∥KV⊕HrPK+.r is a random nonce selected by the TRM for this encryption, then it sends δ1,δ2 to RAs. However, RAs can only decrypt the keys Ksym and KV when they have a warrant to do so after colluding to construct x from individual xi. The reason for saving encrypted keys in RAs database is twofold: RAs use these keys to revoke a vehicle in case of any dispute and for privacy reasons; we do not want RAs to link pseudonyms and/or extract cV and incV from the beacons until necessary, otherwise.It is also to be noted that when a vehicle consumes all the pseudonyms it has in the pseudonym pool, it needs to obtain a batch of fresh pseudonyms from the DMV. The vehicle does not need to be physically present at DMV, rather it can obtain the pseudonyms from DVM by connecting through Internet. We assume that the existing pseudonym refilling strategies can be used [27–30]. Now we outline the two mechanisms for mutual authentication and billing.


## 4.2.1. System Initialization

Notations in the Notations section are employed throughout the paper. We achieve user privacy through pseudonymous. In addition, in order to store the individual secret keys of the vehicles, that is,Ksym and KV in the database of revocation authorities (RAs), we use ElGamal encryption algorithm over elliptic curve cryptography (ECC) due to its proven security. Let G be a cyclic group of prime order q, where G is generated by a generator P. First of all, DMV chooses a random number x∈Z∗ as its private key and computes PK+=xP as its public key. DMV then uses threshold based secret share scheme [26] and divides x into j parts, where j is the number of revocation authorities, each RAi holds a share xi, and xi∈(x1,x2,x3,…,xj). In order to construct x from individual xi, RAs must elect one of them to be group leader and construct x from combination of xi. For the selection of group leader, any available efficient group leader election mechanism in the networks can be used.


## 4.2.2. TRM Installation

Only DMV is authorized to install the TRM in the vehicle for the first time after purchase or repurchase. The owner of the vehicle has to personally visit the DMV for the installation and/or initialization of the TRM. After confirming the credentials of the vehicle and its owner, DMV initializes TRM and saves the system parameters in the TRM including(G,q,P,PK+,cV,incV). Additionally DMV also preloads TRM with vehicle’s individual secret key KV and pseudonym generation key Ksym.


## 4.2.3. Pseudonyms Assignment

DMV generatesn number of pseudonyms for each vehicle by taking vehicle’s secret counter cV and increments it by vehicle V’s incrementing factor incV. The pseudonym is a complex value that also contains trapdoor for revocation. The format of generic pseudonym is given by PSOBUi=(α)Ksym∥α⊕IDKV∥niKDMV-, where α=cV+ni·incV, ni is the current count of generated pseudonym (note that it may not be linear), and ID is the vehicle’s identity. Then DMV stores these pseudonyms in its database and indexes it with the value of n. After all pseudonyms are generated for the vehicles, DMV saves these pseudonyms in vehicle’s TRM along with another value XOBU=h(PSOBU1∥PSOBU2∥⋯∥PSOBUn) and sends the anonymous pseudonyms to RAs as well. In order to help in revocation, TRM also encrypts both Ksym and KV and sends it to RAs which serve as a trapdoor in revocation. The aforementioned keys are encrypted with public master key using ElGamal encryption as follows: (1)δ1=rP,δ2=Ksym∥KV⊕HrPK+.r is a random nonce selected by the TRM for this encryption, then it sends δ1,δ2 to RAs. However, RAs can only decrypt the keys Ksym and KV when they have a warrant to do so after colluding to construct x from individual xi. The reason for saving encrypted keys in RAs database is twofold: RAs use these keys to revoke a vehicle in case of any dispute and for privacy reasons; we do not want RAs to link pseudonyms and/or extract cV and incV from the beacons until necessary, otherwise.It is also to be noted that when a vehicle consumes all the pseudonyms it has in the pseudonym pool, it needs to obtain a batch of fresh pseudonyms from the DMV. The vehicle does not need to be physically present at DMV, rather it can obtain the pseudonyms from DVM by connecting through Internet. We assume that the existing pseudonym refilling strategies can be used [27–30]. Now we outline the two mechanisms for mutual authentication and billing.


## 4.3. Direct Mutual Authentication (DMA)

In the direct approach, OBU and CP mutually authenticate each other without the intervention of CSPA. First of all, CSPA createsl number of master secret keys MSK based on hash chain by selecting a secret s, where MSKi=hi(s) and sends the key to DMV as follows: (2)CSPA⟶DMV:MSKii=1,2,3,…,l.MSKi is a hash chain-based master secret key which is based on a secret s and MSKl=hl(s). In other words, each MSKi is used for a designated amount of time, and CSPA updates MSKi after regular intervals. Since MSKi is distributed by CSPA, it can be updated in timely manner by CSPA and vehicles will receive the updated MSKi in their next registration phase with CSPA. After that, DMV also sends XOBU of the registered vehicles to CSPA for records(3)DMV⟶CSPA:XOBU.Each vehicle has a pool of legitimate traceable pseudonyms from DMV and at the time of authentication, any pseudonym from the pool can be used to start charging. The vehicle will be billed based on the used pseudonym.


### 4.3.1. Vehicle Registration with CSPA

The vehicle, most precisely its OBU, must register with CSPA before charging. We assume a secure channel between CSPA and the vehicle. The registration of the vehicle proceeds as follows. The vehicle starts with the already shared password and upon successful access, the CSPA calculates some security parameters for the vehicle and sends it back to the OBU. The different steps and their descriptions are given below:(a)
OBU→CSPA:PWDOBU,XOBU. OBU sends these values to CSPA on a secure channel. If PWDOBU is valid, then the protocol will proceed.(b)
CSPA calculates the following 3 values, that is,H1,H2, and H3. H1 is used as a secure parameter kept by CSPA. H2 and H3 are the authentication parameters that are sent back to the OBU(4)H1=hs∥XOBU,H2=h2s∥XOBU,H3=MSKi⊕H1.(c)
CSPA registers the OBU by sending the hash functionh(), H2, and H3 to the OBU and recording these parameters by storing them in its database against the value of XOBU.CSPA→OBU:XOBU,h(),H2,H3.


### 4.3.2. Authentication between OBU and CP

After completing the registration phase with CSPA, when the vehicle passes through the section of the power line-enabled road, it starts authentication process with the charging plate. The vehicle starts the authentication process by selecting a pseudonym from its pool of pseudonyms. Then it starts the power receiving process with the selected pseudonym in an anonymous way. The partial per charging bill is prepared based on the presented pseudonym in the authentication/charging process. It is to be noted that a fixed amount of electric power is delivered to the vehicle’s power reception module and it costs the user a fixed amount. The comprehensive mutual authentication steps are given below:(a)
OBU selects a pseudonymPSOBUi,i=1,2,3,…,n, from its pool and calculates the following parameters:(5)c1=hH2⊕PSOBUi,c2=hPSOBUi⊕XOBU,c3=hhPSOBUi∥c2∥H3δ4=rOBU⊕PSOBUi.(b)
Then OBU sends CP, the values calculated in previous step along withH3(6)OBU⟶CP:c1,c2,c3,H3,δ4.(c)
CP executes the following steps:
(i)
Start withH3 and extract the secret H1 as MSKi⊕H1⊕MSKi.(ii)
It calculatesH2 from H1 and extracts PSOBUi from c1.(iii)
CP also extractsrOBU from δ4 which is used in the construction of session key.(iv)
Then it checks for the valuec2 if it is equal to hPSOBUi⊕XOBU.(v)
And it checks ifc3 is equal to the retrieved values h(h(PSOBUi)∥c2∥H3), then the OBU is authenticated; otherwise the authentication fails. It is to be noted that there will be a fixed number of tries, of which failing will halt the authentication process.After successful authentication, OBU and CP initiate the protocol to construct a session keySKOBU-CP which is used for the later communication and billing parameters. The initialization of session key from CP serves as an acknowledgment to authentication as well. The OBU would not have been authenticated, otherwise. At this point CP already extracted XOBU, PSOBUi, and rOBU from c2, c1, and δ4, respectively. Now CP selects a nonce as rcp and calculates session key as SKOBU-CP=h(PSOBUi∥rOBU∥rcp). CP also calculates the following parameters:(7)IDJ=hrOBU∥IDcp,c4=IDJ⊕rcp,c5=rcp⊕hhPSOBUi,c6=hrcp∥c4∥c5,c7=H1⊕h2PSOBUi.I
D
c
p is the ID of the charging plate. After calculating the above values, CP constructs an authentication reply message and sends it back to OBU. This authentication reply means that OBU has been authenticated and other parameters will be sent for the session key calculation. The following authentication reply message is sent to OBU:(8)CP⟶OBU:c4,c5,c6,c7.From the above reply message, OBU extractsrcp from c4 and IDJ and checks if c6 is equal to h(rcp∥c4∥c5). If the information is correct, then the OBU authenticates CP as well and computes the session key SKOBU-CP=h(PSOBUi∥rOBU∥rcp), extracts H1 from c7, and stores it as a security parameter.At this point in time, the mutual authentication is completed and the electric power reception process will start based on the established session keySKOBU-CP.When these two entities (OBU and CP) authenticate each other, then the vehicle will receive the designated amount of power from the road (CP). At the end of each phase of the charging plate atCPi, a unit cost Ci will be accumulated to the account of the OBU against its presented PSOBUi. At the end of the whole power transfer from a number of charging plates, both OBU and CSPA will have the log of the amount of transferred power and the OBU will be billed accordingly which will be verifiable by both CSPA and the OBU. The whole authentication process in case of DMA is shown in Figure 4.Figure 4
Authentication process in DMA scenario.


## 4.3.1. Vehicle Registration with CSPA

The vehicle, most precisely its OBU, must register with CSPA before charging. We assume a secure channel between CSPA and the vehicle. The registration of the vehicle proceeds as follows. The vehicle starts with the already shared password and upon successful access, the CSPA calculates some security parameters for the vehicle and sends it back to the OBU. The different steps and their descriptions are given below:(a)
OBU→CSPA:PWDOBU,XOBU. OBU sends these values to CSPA on a secure channel. If PWDOBU is valid, then the protocol will proceed.(b)
CSPA calculates the following 3 values, that is,H1,H2, and H3. H1 is used as a secure parameter kept by CSPA. H2 and H3 are the authentication parameters that are sent back to the OBU(4)H1=hs∥XOBU,H2=h2s∥XOBU,H3=MSKi⊕H1.(c)
CSPA registers the OBU by sending the hash functionh(), H2, and H3 to the OBU and recording these parameters by storing them in its database against the value of XOBU.CSPA→OBU:XOBU,h(),H2,H3.


## 4.3.2. Authentication between OBU and CP

After completing the registration phase with CSPA, when the vehicle passes through the section of the power line-enabled road, it starts authentication process with the charging plate. The vehicle starts the authentication process by selecting a pseudonym from its pool of pseudonyms. Then it starts the power receiving process with the selected pseudonym in an anonymous way. The partial per charging bill is prepared based on the presented pseudonym in the authentication/charging process. It is to be noted that a fixed amount of electric power is delivered to the vehicle’s power reception module and it costs the user a fixed amount. The comprehensive mutual authentication steps are given below:(a)
OBU selects a pseudonymPSOBUi,i=1,2,3,…,n, from its pool and calculates the following parameters:(5)c1=hH2⊕PSOBUi,c2=hPSOBUi⊕XOBU,c3=hhPSOBUi∥c2∥H3δ4=rOBU⊕PSOBUi.(b)
Then OBU sends CP, the values calculated in previous step along withH3(6)OBU⟶CP:c1,c2,c3,H3,δ4.(c)
CP executes the following steps:
(i)
Start withH3 and extract the secret H1 as MSKi⊕H1⊕MSKi.(ii)
It calculatesH2 from H1 and extracts PSOBUi from c1.(iii)
CP also extractsrOBU from δ4 which is used in the construction of session key.(iv)
Then it checks for the valuec2 if it is equal to hPSOBUi⊕XOBU.(v)
And it checks ifc3 is equal to the retrieved values h(h(PSOBUi)∥c2∥H3), then the OBU is authenticated; otherwise the authentication fails. It is to be noted that there will be a fixed number of tries, of which failing will halt the authentication process.After successful authentication, OBU and CP initiate the protocol to construct a session keySKOBU-CP which is used for the later communication and billing parameters. The initialization of session key from CP serves as an acknowledgment to authentication as well. The OBU would not have been authenticated, otherwise. At this point CP already extracted XOBU, PSOBUi, and rOBU from c2, c1, and δ4, respectively. Now CP selects a nonce as rcp and calculates session key as SKOBU-CP=h(PSOBUi∥rOBU∥rcp). CP also calculates the following parameters:(7)IDJ=hrOBU∥IDcp,c4=IDJ⊕rcp,c5=rcp⊕hhPSOBUi,c6=hrcp∥c4∥c5,c7=H1⊕h2PSOBUi.I
D
c
p is the ID of the charging plate. After calculating the above values, CP constructs an authentication reply message and sends it back to OBU. This authentication reply means that OBU has been authenticated and other parameters will be sent for the session key calculation. The following authentication reply message is sent to OBU:(8)CP⟶OBU:c4,c5,c6,c7.From the above reply message, OBU extractsrcp from c4 and IDJ and checks if c6 is equal to h(rcp∥c4∥c5). If the information is correct, then the OBU authenticates CP as well and computes the session key SKOBU-CP=h(PSOBUi∥rOBU∥rcp), extracts H1 from c7, and stores it as a security parameter.At this point in time, the mutual authentication is completed and the electric power reception process will start based on the established session keySKOBU-CP.When these two entities (OBU and CP) authenticate each other, then the vehicle will receive the designated amount of power from the road (CP). At the end of each phase of the charging plate atCPi, a unit cost Ci will be accumulated to the account of the OBU against its presented PSOBUi. At the end of the whole power transfer from a number of charging plates, both OBU and CSPA will have the log of the amount of transferred power and the OBU will be billed accordingly which will be verifiable by both CSPA and the OBU. The whole authentication process in case of DMA is shown in Figure 4.Figure 4
Authentication process in DMA scenario.


## 4.4. Pure Hash Chain-Based Authentication (PHA)

For a fast moving vehicle, the DMA approach can be applied where computation is done locally by the charging plate; however, DMA may incur reasonable computation delay. Therefore, we propose another indirect authentication mechanism based on hash chain carried out by CSPA where computation delay is minimum whereas a small communication delay is introduced. Moreover this mechanism is most favorable for low speed vehicles. DMV provides the OBU withn pseudonyms PSOBUi,i=1,2,3,…,n, and hash chain corresponding to each pseudonym h(PSOBUi),h2(PSOBUi),…,hn(PSOBUi). We assume that, for the sake of charging its battery, the vehicle registers with the CSPA based on some designated policy. In other words, the car uses a new hash chain based on the designated interval in the policy. Authentication process takes place as follows:(a)
The vehicle registers with CSPA and sends one of the hash chain headshn(PSOBUi) to CSPA(9)OBU⟶CSPA:hnPSOBUi,XOBU,CertOBU.(b)
At the time of authentication and request for charging, the vehicle must provide CP with a member hash from the registered hash chainhn-1(PSOBUi)(10)OBU⟶CP:hn-1PSOBUi,XOBU.(c)
CP forwards this value to the CSPA(11)CP⟶CSPA:timestamp,hn-1PSOBUi,XOBU.(d)
CSPA validates the hash, checks ifh(hn-1(PSOBUi))=hn(PSOBUi), and replies accordingly. CSPA also replaces hn(PSOBUi) with h(hn-1(PSOBUi)). In addition to authentication, CSPA also provides the CP with a session key SKOBU-CP and saves it in its database with time and the XOBU. It is to be noted that CSPA issues a single session key for all the plates for a particular vehicle and a particular hash chain(12)CSPA⟶CP:Auth.Status,SKOBU-CP,SKOBU-CPKOBU+,CP⟶OBU:SKOBU-CPKOBU+.(e)
If the authentication is successful, then charging plate will transfer the electric power to the vehicle; otherwise the process halts. It is to be noted that one hash chain is long enough to use it for the whole day. For the next day, the vehicles can register another hash chain. This process will still preserve the conditional privacy of the OBU.The protocol for pure hash chain-based authentication mechanism is given in Figure5.Figure 5
Authentication process in PHA scenario.


## 4.5. Power Transfer, Billing, and Auditability

Once the mutual authentication is completed between the charging plate and OBU, the vehicle starts to receive the power from the road (CP) semisimultaneously with billing. More precisely, the vehicle is billed at the charging plate level. At the end of the charging process, the total bill is accumulated both at OBU and the CSPA. The process is explained in case of both direct and indirect authentication as shown in Figures6 and 7, respectively.Figure 6
Power transfer and billing process in DMA scenario.Figure 7
Power transfer and billing process in PHA scenario.


### 4.5.1. Online Electric Power Transfer and Billing in DMA

In case of DMA, CSPA has access to the pseudonym used in the authentication process through CP. Therefore, after a successful authentication and establishment of a session key, vehicle requests for the electric power and presents the charging plate and CSPA with the pseudonym and other parameters for the billing purpose. The series of steps are given below:(13)OBU⟶CP:timestamp∥ChargingReq.∥PSOBUi∥hKVαSKOBU-CP,α=timestamp∥ChargingReq.∥PSOBUi,CP⟶OBU:Ack,timestamp∥PSOBUi∥hKVα.At this point, CP starts billing and sends the bill log to OBU and to CSPA. The bill is logged against two values, XOBU and the consumed pseudonym PSOBUi,(14)CP⟶CSPA:timestamp∥PSOBUi∥XOBU∥CostCPi,CSPA:CostXOBU=∑i=1nCostCPi.In case of DMA, the CSPA accumulates all partial billing information from individual CPs and bill the OBU accordingly. It is worth noting that we use a constant cost per charging plate. For our current proposed scheme, we consider fixed energy transfer and fixed price per certain amount of transferred energy. These parameters can be set by the service provider(s). On part of service provider(s), fixed amount of energy transfer and thus fixed price would be easy to implement and faster, whereas, for customers, dynamic billing makes more sense. However, some tradeoff solution will suffice. In the current setup, if the price is fixed per unit, and the value/volume of unit is kept small, then we can compare this scheme with the dynamic billing. For instance, depending on the demand of the customers, x units of charge could be transferred to the customer and the customer will be billed accordingly. It is also worth noting that fixed billing mechanism will alleviate the problem of free-riders that would otherwise be possible in dynamic environment if the security keys are compromised.


### 4.5.2. Online Electric Power Transfer and Billing in PHA

In case of PHA, the CSPA does not have access to individual pseudonyms; rather it maintains the billing information based on theXOBU value. After successful authentication, OBU requests for online power transfer and the power transfer begins. Meanwhile, CSPA bills the cost for the current CP and accumulates it to the account against XOBU with timestamp information. The series of steps are given below: (15)OBU⟶CP:timestamp∥ChargingReq.∥XOBU∥hKVβSKOBU-CP,β=timestamp∥ChargingReq.∥XOBU.The CP forwards the request to CSPA where CSPA constructs a reply message for the OBU. Meanwhile when CP receives the reply message from CSPA, the vehicle will start receiving power and CSPA will record the cost for the current charging plate(16)CSPA⟶CP:timestamp∥XOBU∥hKVβ.CP forwards the message to OBU accordingly whereas CSPA calculates the bill for current CP and accumulates with the partial bills from previous CPs(17)CSPA:CostXOBU=∑i=1n-1CostCPi-1+CostCPi.This way, CSPA calculates the bill partially simultaneously with charging process which is the motive of our GHP game. We will discuss our OBU-CP game in the next subsection.


## 4.5.1. Online Electric Power Transfer and Billing in DMA

In case of DMA, CSPA has access to the pseudonym used in the authentication process through CP. Therefore, after a successful authentication and establishment of a session key, vehicle requests for the electric power and presents the charging plate and CSPA with the pseudonym and other parameters for the billing purpose. The series of steps are given below:(13)OBU⟶CP:timestamp∥ChargingReq.∥PSOBUi∥hKVαSKOBU-CP,α=timestamp∥ChargingReq.∥PSOBUi,CP⟶OBU:Ack,timestamp∥PSOBUi∥hKVα.At this point, CP starts billing and sends the bill log to OBU and to CSPA. The bill is logged against two values, XOBU and the consumed pseudonym PSOBUi,(14)CP⟶CSPA:timestamp∥PSOBUi∥XOBU∥CostCPi,CSPA:CostXOBU=∑i=1nCostCPi.In case of DMA, the CSPA accumulates all partial billing information from individual CPs and bill the OBU accordingly. It is worth noting that we use a constant cost per charging plate. For our current proposed scheme, we consider fixed energy transfer and fixed price per certain amount of transferred energy. These parameters can be set by the service provider(s). On part of service provider(s), fixed amount of energy transfer and thus fixed price would be easy to implement and faster, whereas, for customers, dynamic billing makes more sense. However, some tradeoff solution will suffice. In the current setup, if the price is fixed per unit, and the value/volume of unit is kept small, then we can compare this scheme with the dynamic billing. For instance, depending on the demand of the customers, x units of charge could be transferred to the customer and the customer will be billed accordingly. It is also worth noting that fixed billing mechanism will alleviate the problem of free-riders that would otherwise be possible in dynamic environment if the security keys are compromised.


## 4.5.2. Online Electric Power Transfer and Billing in PHA

In case of PHA, the CSPA does not have access to individual pseudonyms; rather it maintains the billing information based on theXOBU value. After successful authentication, OBU requests for online power transfer and the power transfer begins. Meanwhile, CSPA bills the cost for the current CP and accumulates it to the account against XOBU with timestamp information. The series of steps are given below: (15)OBU⟶CP:timestamp∥ChargingReq.∥XOBU∥hKVβSKOBU-CP,β=timestamp∥ChargingReq.∥XOBU.The CP forwards the request to CSPA where CSPA constructs a reply message for the OBU. Meanwhile when CP receives the reply message from CSPA, the vehicle will start receiving power and CSPA will record the cost for the current charging plate(16)CSPA⟶CP:timestamp∥XOBU∥hKVβ.CP forwards the message to OBU accordingly whereas CSPA calculates the bill for current CP and accumulates with the partial bills from previous CPs(17)CSPA:CostXOBU=∑i=1n-1CostCPi-1+CostCPi.This way, CSPA calculates the bill partially simultaneously with charging process which is the motive of our GHP game. We will discuss our OBU-CP game in the next subsection.


## 4.6. Revocation

In this subsection, we outline our efficient revocation mechanism.The proposed protocol preserves the users’ privacy; however in case of any misbehavior and/or bypassing the protocol, the users are subject to revocation. We incorporate an efficient revocation mechanism through which RAs can efficiently revoke the identity of the participating node. As we know the revocation functionality is distributed among a number of RAs rather than a single RA. These RAs share a part of the secret part of the share. When there is a need for revocation, the RAs collude, get a judicial warrant, and construct the secret from the shares. It is to be noted that RAs may select a session leader among them to carry out the decryption process. The encrypted keysKsym and KV are stored in RAs. When RAs obtain the secret x, they decrypt the aforementioned keys from ciphertext (δ1,δ2). In order to decrypt the encrypted keys, RA proceeds with the following steps.Take the secret valuex and calculate the following value: (18)decδ1,δ2,x=δ2⊕Hxδ1.By replacing δ2 and δ1 with the original values, we get(19)decδ1,δ2,x=Ksym∥KV⊕HrPK+⊕Hxδ1,decδ1,δ2,x=Ksym∥KV⊕HrxP⊕Hxδ1,decδ1,δ2,x=Ksym∥KV⊕HrxP⊕HrxP,decδ1,δ2,x=Ksym∥KV.After decrypting the keys, RA takes the pseudonym in question and extract the trapdoor in it in order to revoke the node. As aforementioned, every pseudonym has the trapdoor value. RA decrypts (α)Ksym and then decrypts α⊕IDKV. Then RA extracts the ID from the value α⊕ID that corresponds to the pseudonym in question. This way the pseudonym in question and hence the node are revoked by the RAs.


## 5. Security and Privacy Analysis

In this section, we prove that the proposed scheme satisfies the three security models.


### 5.1. Bidirectional Auditability

Secure bidirectional auditability is provided through semisimultaneous billing procedure incorporated into our proposed scheme. Each charging plate is capable of transferring a fixed amount of electrical energy to the battery and billing the vehicle with a fixed amount. Since vehicles use either individual pseudonymsPSOBUi or the combined hash value XOBU, the final bill is the combination of the costs of individual charging plates. Each OBU knows the cost per charging plate, and it records the cost in its log as well. Both CSPA and OBU can verify the individual and final bill of the power transfer in a liable and a nonrepudiate manner. It is also worth noting that it is the duty of CSPA to make sure of the freshness of the session key and use different session keys for different charging plates for security reasons. For session key update frequency and mechanism, existing techniques can be used. The behavior of both charging plate and OBU from security perspective is depicted by the game G where they establish NE during charging transaction. For the detailed description of bidirectional auditability game, please refer to the Appendix.


### 5.2. Conditional Privacy

Our proposed scheme also preserves conditional privacy of the users during electric power transferring and billing process. We do not use any real identity that could lead to the actual user; instead we use a series of legitimate pseudonyms.Moreover in order to measure the privacy and the anonymity of the vehicles, we calculate the entropy of the user denoted byH. The anonymity set needed for entropy calculation is, the set of active vehicles at the certain time t that are in the process of charging their batteries. Let U be the anonymity set and let pUi be the probability that the node Ui is the target vehicle whose anonymity is being calculated or Ui is under surveillance by adversary A, where ∀Ui∈U, ∑i=1U‍pUi=1. The entropy H of the target user Ui in the anonymity set U is given by H=-∑i=1U‍pUi×log2⁡pUi. Since our anonymity set is U, the possible outcomes can be U assuming the fair distribution and the probability of each outcome will be 1/U. If the distribution is normal and the occurrence of the nodes to be related to the pseudonyms in question is equally likely, then the maximum entropy is also given by the following formula: Hmax=-∑i=1U‍pUi×log2⁡pUi=log2⁡pUi.Theorem 1.
Conditional privacy is always guaranteed by the proposed scheme and in case of any dispute, the node in question is revoked and the pseudonym in question is linkable to the actual user.Proof.
In order to proceed with revocation, RAs get the warrant from the authorities and then look into then values of the message in question that are provided to RAs in order to figure out which pseudonym was used. After that, RAs collude and construct x from individual xi related to the pseudonym in question and the session leader decrypts the keys from ciphertext c=δ1,δ2 as follows: PSOBUi=δ2⊕H(xδ1)=(Ksym∥KV)⊕H(rPK+)⊕H(rxP). When RAs decrypt the keys Ksym and KV, then revocation is almost done, and what all RAs have to do is to decrypt the (α)Ksym and then extract ID of the vehicle from the pseudonym.Lemma 2.
It is hard to impersonate other OBUs in the process of online power transfer. In other words, it is hard to get away with billing procedures manipulation.Proof.
Before starting the power transfer procedure, the vehicles have to register with CSPA in both direct and hash chain-based authentication and provide CSPA withXOBU. And at the authentication stage, OBU has to provide the CP with c1 and c3 that contain H2 and H3, respectively. At the registration phase, H2 is associated with the XOBU of the current authenticating vehicle. Therefore, for any adversary A with H2′ without knowing the secret s, it will be hard to calculate valid c1, c2, and c3 at the authentication phase. Thus the values sent to the CP for authentication will be c1′, c2′, c3′, and H3′ all of which must have association with the XOBU of the pseudonym PSOBUi. Arguing on the collision resistance of the hash function used, it can be inferred that the probability of calculating the right values with not knowing the XOBU is small (Section 5.3); therefore, it is hard for anybody to impersonate other OBUs with a pseudonym.The following corollary naturally follows.Corollary 3.
Replaying the power transfer request message and/or pseudonym will not benefit the malicious intent of the user.The argument is divided into two parts. Replaying a message will result in the existence of previous power transfer records with this information. Upon successful power transfer, the CSPA maintains a log with timestamp and billing information against the used pseudonym. Let an OBU charge its battery atCPx at particular time ti after successful authentication, and the log is recorded at CSPA with the used pseudonym and other credentials. At ti+j, the OBU again uses the message, then there are two possibilities. First, the OBU must have already been authenticated before sending this message; in that case, it will receive the power accordingly; secondly if it is not authenticated, then CSPA must have figured out that the record already existed and that the OBU was malicious. In either case, the OBU cannot benefit from such behavior. The same argument stands for the pseudonym as well.


### 5.3. Mutual Authentication

The most basic security requirement of our proposed scheme is mutual authentication between charging plate and OBU. With our proposed lightweight authentication protocol which is an extended version of Chuang and Lee’s [17] protocol, mutual authentication is guaranteed before starting the charging process. Our proposed scheme at its essence is based on hashing and XOR functions. We assumed that the hash function has the collision resistance and the one-wayness properties. Hence, the hash function satisfies following definition [31].Definition 4 (collision resistance one-way hash function).
On inputm,1∗, for a deterministic polynomial-time algorithm A, every positive polynomial p(·), and all sufficiently large n’s, a function f:0,1∗→0,1n satisfies the following probability: (20)PrAfm,1n∈f-1fm=Prfm=fm′<1pn,where m′ is another input of f.In the proposed scheme, each authentication interval contains 9 hash values. An attacker may try to pass the authentication session without any information. In this case, the attacker has to generate exactly same 9 values. The probability of success for this kind of attack is given by(21)∏i=19PrAfmi,1n=Ui<19·pn,where Ui is input of the algorithm A, and it is chosen by the attacker. Since the probability is a negligible if n is large enough, hence our proposed authentication can be considered secure. However, the effect of keys compromise can be critical for our proposed scheme. From the OBU perspective, compromising KV does not have dire consequences because the adversary A can get only a part of pseudonym, not the whole pseudonym. In case of compromising both Ksym and KV, A can not only manipulate pseudonyms, but can also reuse them. Moreover our system can prevent the secret sharing attack because a vehicle must authenticate itself prior to charging its battery. Since the charging plate authenticates the user, therefore, two users cannot use the same secret and/or reuse it because timestamp and the local log of the usage of charging plate or CSPA will stop the vehicles from doing so. In other words, the protocol must follow these steps: (i) registration, (ii) authentication, and (iii) power transfer.


## 5.1. Bidirectional Auditability

Secure bidirectional auditability is provided through semisimultaneous billing procedure incorporated into our proposed scheme. Each charging plate is capable of transferring a fixed amount of electrical energy to the battery and billing the vehicle with a fixed amount. Since vehicles use either individual pseudonymsPSOBUi or the combined hash value XOBU, the final bill is the combination of the costs of individual charging plates. Each OBU knows the cost per charging plate, and it records the cost in its log as well. Both CSPA and OBU can verify the individual and final bill of the power transfer in a liable and a nonrepudiate manner. It is also worth noting that it is the duty of CSPA to make sure of the freshness of the session key and use different session keys for different charging plates for security reasons. For session key update frequency and mechanism, existing techniques can be used. The behavior of both charging plate and OBU from security perspective is depicted by the game G where they establish NE during charging transaction. For the detailed description of bidirectional auditability game, please refer to the Appendix.


## 5.2. Conditional Privacy

Our proposed scheme also preserves conditional privacy of the users during electric power transferring and billing process. We do not use any real identity that could lead to the actual user; instead we use a series of legitimate pseudonyms.Moreover in order to measure the privacy and the anonymity of the vehicles, we calculate the entropy of the user denoted byH. The anonymity set needed for entropy calculation is, the set of active vehicles at the certain time t that are in the process of charging their batteries. Let U be the anonymity set and let pUi be the probability that the node Ui is the target vehicle whose anonymity is being calculated or Ui is under surveillance by adversary A, where ∀Ui∈U, ∑i=1U‍pUi=1. The entropy H of the target user Ui in the anonymity set U is given by H=-∑i=1U‍pUi×log2⁡pUi. Since our anonymity set is U, the possible outcomes can be U assuming the fair distribution and the probability of each outcome will be 1/U. If the distribution is normal and the occurrence of the nodes to be related to the pseudonyms in question is equally likely, then the maximum entropy is also given by the following formula: Hmax=-∑i=1U‍pUi×log2⁡pUi=log2⁡pUi.Theorem 1.
Conditional privacy is always guaranteed by the proposed scheme and in case of any dispute, the node in question is revoked and the pseudonym in question is linkable to the actual user.Proof.
In order to proceed with revocation, RAs get the warrant from the authorities and then look into then values of the message in question that are provided to RAs in order to figure out which pseudonym was used. After that, RAs collude and construct x from individual xi related to the pseudonym in question and the session leader decrypts the keys from ciphertext c=δ1,δ2 as follows: PSOBUi=δ2⊕H(xδ1)=(Ksym∥KV)⊕H(rPK+)⊕H(rxP). When RAs decrypt the keys Ksym and KV, then revocation is almost done, and what all RAs have to do is to decrypt the (α)Ksym and then extract ID of the vehicle from the pseudonym.Lemma 2.
It is hard to impersonate other OBUs in the process of online power transfer. In other words, it is hard to get away with billing procedures manipulation.Proof.
Before starting the power transfer procedure, the vehicles have to register with CSPA in both direct and hash chain-based authentication and provide CSPA withXOBU. And at the authentication stage, OBU has to provide the CP with c1 and c3 that contain H2 and H3, respectively. At the registration phase, H2 is associated with the XOBU of the current authenticating vehicle. Therefore, for any adversary A with H2′ without knowing the secret s, it will be hard to calculate valid c1, c2, and c3 at the authentication phase. Thus the values sent to the CP for authentication will be c1′, c2′, c3′, and H3′ all of which must have association with the XOBU of the pseudonym PSOBUi. Arguing on the collision resistance of the hash function used, it can be inferred that the probability of calculating the right values with not knowing the XOBU is small (Section 5.3); therefore, it is hard for anybody to impersonate other OBUs with a pseudonym.The following corollary naturally follows.Corollary 3.
Replaying the power transfer request message and/or pseudonym will not benefit the malicious intent of the user.The argument is divided into two parts. Replaying a message will result in the existence of previous power transfer records with this information. Upon successful power transfer, the CSPA maintains a log with timestamp and billing information against the used pseudonym. Let an OBU charge its battery atCPx at particular time ti after successful authentication, and the log is recorded at CSPA with the used pseudonym and other credentials. At ti+j, the OBU again uses the message, then there are two possibilities. First, the OBU must have already been authenticated before sending this message; in that case, it will receive the power accordingly; secondly if it is not authenticated, then CSPA must have figured out that the record already existed and that the OBU was malicious. In either case, the OBU cannot benefit from such behavior. The same argument stands for the pseudonym as well.


## 5.3. Mutual Authentication

The most basic security requirement of our proposed scheme is mutual authentication between charging plate and OBU. With our proposed lightweight authentication protocol which is an extended version of Chuang and Lee’s [17] protocol, mutual authentication is guaranteed before starting the charging process. Our proposed scheme at its essence is based on hashing and XOR functions. We assumed that the hash function has the collision resistance and the one-wayness properties. Hence, the hash function satisfies following definition [31].Definition 4 (collision resistance one-way hash function).
On inputm,1∗, for a deterministic polynomial-time algorithm A, every positive polynomial p(·), and all sufficiently large n’s, a function f:0,1∗→0,1n satisfies the following probability: (20)PrAfm,1n∈f-1fm=Prfm=fm′<1pn,where m′ is another input of f.In the proposed scheme, each authentication interval contains 9 hash values. An attacker may try to pass the authentication session without any information. In this case, the attacker has to generate exactly same 9 values. The probability of success for this kind of attack is given by(21)∏i=19PrAfmi,1n=Ui<19·pn,where Ui is input of the algorithm A, and it is chosen by the attacker. Since the probability is a negligible if n is large enough, hence our proposed authentication can be considered secure. However, the effect of keys compromise can be critical for our proposed scheme. From the OBU perspective, compromising KV does not have dire consequences because the adversary A can get only a part of pseudonym, not the whole pseudonym. In case of compromising both Ksym and KV, A can not only manipulate pseudonyms, but can also reuse them. Moreover our system can prevent the secret sharing attack because a vehicle must authenticate itself prior to charging its battery. Since the charging plate authenticates the user, therefore, two users cannot use the same secret and/or reuse it because timestamp and the local log of the usage of charging plate or CSPA will stop the vehicles from doing so. In other words, the protocol must follow these steps: (i) registration, (ii) authentication, and (iii) power transfer.


## 6. Evaluation

### 6.1. Computation and Communication Overhead

In this subsection, we consider the computation and communication overhead incurred by the OBU and CP in the process of mutual authentication and power transfer. Table1 shows the computation overhead incurred by our proposed scheme and Table 2 outlines the communication overhead incurred by our proposed scheme. In the computation overhead, we consider the authentication cost incurred by OBU and CP denoted by Tauth-OBU and Tauth-CP, respectively, and the cost of revocation denoted by Trev in the direct authentication method. When OBU mutually authenticates with CP, it performs 3H+2EO operations, where H denotes thehash operation and EO denotes theexclusive OR operation. CP performs 6H+5EO operations. The cost of revocation Trev in our proposed scheme is given by(22)Trev=2Tγ+2Tmul+2TH+2Tdec.Tγ is the time incurred by the pseudonym search table, Tmul is the time required for point multiplication, TH is the time required to calculate hash, and Tdec is the time required for symmetric decryption. In [26], Tmul is found for a supersingular curve with embedding k=6 over F397 to be equal to 0.78 ms. Hence the above equations can be written as (23)Trev=1.56+2Tγ+TH+Tdec.Table 1
Computation cost incurred by different operations.
Operation
Cost
T
a
u
t
h
-
O
B
U
T
a
u
t
h
-
C
P
CSPA
Direct authentication
3
H
+
2
E
O
6
H
+
5
E
O
—
2.28 μsec
4.56 μsec
Hash chain-based authentication
1
D
—
1
H
+
1
E
Revocation
T
r
e
v
=
1.56
+
2
T
γ
+
T
H
+
T
d
e
cTable 2
Communication cost incurred by the proposed scheme.
Operation
Cost
DMA
71
+
u
PHA
135 bytesWe also discuss the authentication processing time by both OBU and CP. According to [17], SHA2 hash operation takes 0.76 μsec. Therefore, OBU takes about 2.28 μsec and CP takes about 4.56 μsec. It is worth noting that since the XOR operation time is usually a single clock on CPUs which is infinitesimally small, therefore, we ignore it. In case of the hash chain-based authentication, OBU cost is only 1D, where D denotes the decryption operation. CSPA incurs 1H+1E, and E is the encryption operation.We also calculate the authentication overhead. In case of DMA, the communication overhead is equal to71+u, where u is the size of the pseudonym. We assume SHA-512 as a hash function and consider the [32] implementation of timestamp which is 6 bytes. Similarly, in case of PHA the communication overhead is fixed and incurs 135 bytes where timestamp is 6 bytes, ChargingReq. is 1 byte, XOBU is 64 bytes, and hKV(β) is also 64 bytes.


### 6.2. Comparison with Existing Mechanisms

To the best of our knowledge, the most relevant work to our proposed scheme is [24]. We compare our proposed scheme with [24] from performance, modeling, efficiency, and number of messages. Li et al. used cryptographic techniques to provide authentication between moving vehicles and charging pads. Furthermore, the length of the charging pad is 0.4 m in [24]. It is worth noting that keeping the length of the charging plate too short will not only increase the authentication overhead, but also make it difficult to manage the billing. Our proposed scheme on the other hand does not use cryptographic primitives for authentication and therefore with only XOR and hash operations, our proposed scheme clearly outperforms [24]. Additionally, in order to perform authentication, OBU and CP have to exchange 5 messages whereas 9 messages are exchanged in [24] during authentication. The speed is also a crucial factor to consider in [24]. With such a short charging pad, the vehicles will have no choice but to move slow on the charging pad to complete authentication.


### 6.3. Length of Charging Plate

The efficiency of the power transfer and the auditability depends upon the length of the charging plate. Therefore, the length of the charging plate must be a tradeoff between the authentication and billing delay and the time required to acquire the specified amount of electrical power from the charging plate. The plate should not be too short where a vehicle cannot receive the promised amount of power after spending most of the time on the authentication and billing. Similarly the plate should not be too long, where mutual auditability is at stake and semisimultaneous audit is not possible. To date, the size of the segment is not fixed; however, OLEV project considers the length of the segment to be5 m which is still controversial because of the authentication and billing overhead incurred by the number of segments. Another important point is that the length of the segment is a design feature where the amount of electrical power, authentication and billing delay, and the time to acquire the guaranteed charge should be taken into account. In our scenario, we argue that the authentication delay incurred by both OBU and charging plate is less than a microsecond (optimistically) due to the design of authentication scheme. Therefore, the uniformity of the pickup devices installed in the vehicles and the capacity of delivering electrical power by the charging plates will play a vital role in deciding the length of the plate.


### 6.4. Discussion

In this subsection, we analyze the effect of the two authentication strategies on the efficiency and the design parameters. In DMA, OBU and CP have to perform relatively more operations as compared to PHA; nevertheless the time consumed by these operations (hash and XOR) is less than encryption operation. That is why we argue that, in performance, DMA will outperform PHA. Secondly, in DMA, both parties are involved in setting up the session key with mutual agreement. The communication cost is minimum since OBU and charging plate are communicating directly. Therefore, the only parameter that could affect the performance of DMA and PHA is the length of the charging plate. If we consider the normal speed of the vehicle, then PHA will favor the lengthier charging plate than DMA, because of the communication delay incurred by the PHA. On the other hand, PHA does not cost any computation delay because the processing is carried out at resource rich CSPA and charging plate is only used as intermediary bridge between vehicles and CSPA. However, in case of PHA, the session key is constructed by one entity, CSPA. Moreover OBUs must save the hash chain of the currently used pseudonyms in the onboard storage thereby incurring storage cost. Therefore, we can argue that these two methods can be used in different circumstances that fit the necessary conditions for direct and hash-based authentication. For normal scenarios, DMA will be the fair choice because of its security, auditability guarantee, and robustness.


## 6.1. Computation and Communication Overhead

In this subsection, we consider the computation and communication overhead incurred by the OBU and CP in the process of mutual authentication and power transfer. Table1 shows the computation overhead incurred by our proposed scheme and Table 2 outlines the communication overhead incurred by our proposed scheme. In the computation overhead, we consider the authentication cost incurred by OBU and CP denoted by Tauth-OBU and Tauth-CP, respectively, and the cost of revocation denoted by Trev in the direct authentication method. When OBU mutually authenticates with CP, it performs 3H+2EO operations, where H denotes thehash operation and EO denotes theexclusive OR operation. CP performs 6H+5EO operations. The cost of revocation Trev in our proposed scheme is given by(22)Trev=2Tγ+2Tmul+2TH+2Tdec.Tγ is the time incurred by the pseudonym search table, Tmul is the time required for point multiplication, TH is the time required to calculate hash, and Tdec is the time required for symmetric decryption. In [26], Tmul is found for a supersingular curve with embedding k=6 over F397 to be equal to 0.78 ms. Hence the above equations can be written as (23)Trev=1.56+2Tγ+TH+Tdec.Table 1
Computation cost incurred by different operations.
Operation
Cost
T
a
u
t
h
-
O
B
U
T
a
u
t
h
-
C
P
CSPA
Direct authentication
3
H
+
2
E
O
6
H
+
5
E
O
—
2.28 μsec
4.56 μsec
Hash chain-based authentication
1
D
—
1
H
+
1
E
Revocation
T
r
e
v
=
1.56
+
2
T
γ
+
T
H
+
T
d
e
cTable 2
Communication cost incurred by the proposed scheme.
Operation
Cost
DMA
71
+
u
PHA
135 bytesWe also discuss the authentication processing time by both OBU and CP. According to [17], SHA2 hash operation takes 0.76 μsec. Therefore, OBU takes about 2.28 μsec and CP takes about 4.56 μsec. It is worth noting that since the XOR operation time is usually a single clock on CPUs which is infinitesimally small, therefore, we ignore it. In case of the hash chain-based authentication, OBU cost is only 1D, where D denotes the decryption operation. CSPA incurs 1H+1E, and E is the encryption operation.We also calculate the authentication overhead. In case of DMA, the communication overhead is equal to71+u, where u is the size of the pseudonym. We assume SHA-512 as a hash function and consider the [32] implementation of timestamp which is 6 bytes. Similarly, in case of PHA the communication overhead is fixed and incurs 135 bytes where timestamp is 6 bytes, ChargingReq. is 1 byte, XOBU is 64 bytes, and hKV(β) is also 64 bytes.


## 6.2. Comparison with Existing Mechanisms

To the best of our knowledge, the most relevant work to our proposed scheme is [24]. We compare our proposed scheme with [24] from performance, modeling, efficiency, and number of messages. Li et al. used cryptographic techniques to provide authentication between moving vehicles and charging pads. Furthermore, the length of the charging pad is 0.4 m in [24]. It is worth noting that keeping the length of the charging plate too short will not only increase the authentication overhead, but also make it difficult to manage the billing. Our proposed scheme on the other hand does not use cryptographic primitives for authentication and therefore with only XOR and hash operations, our proposed scheme clearly outperforms [24]. Additionally, in order to perform authentication, OBU and CP have to exchange 5 messages whereas 9 messages are exchanged in [24] during authentication. The speed is also a crucial factor to consider in [24]. With such a short charging pad, the vehicles will have no choice but to move slow on the charging pad to complete authentication.


## 6.3. Length of Charging Plate

The efficiency of the power transfer and the auditability depends upon the length of the charging plate. Therefore, the length of the charging plate must be a tradeoff between the authentication and billing delay and the time required to acquire the specified amount of electrical power from the charging plate. The plate should not be too short where a vehicle cannot receive the promised amount of power after spending most of the time on the authentication and billing. Similarly the plate should not be too long, where mutual auditability is at stake and semisimultaneous audit is not possible. To date, the size of the segment is not fixed; however, OLEV project considers the length of the segment to be5 m which is still controversial because of the authentication and billing overhead incurred by the number of segments. Another important point is that the length of the segment is a design feature where the amount of electrical power, authentication and billing delay, and the time to acquire the guaranteed charge should be taken into account. In our scenario, we argue that the authentication delay incurred by both OBU and charging plate is less than a microsecond (optimistically) due to the design of authentication scheme. Therefore, the uniformity of the pickup devices installed in the vehicles and the capacity of delivering electrical power by the charging plates will play a vital role in deciding the length of the plate.


## 6.4. Discussion

In this subsection, we analyze the effect of the two authentication strategies on the efficiency and the design parameters. In DMA, OBU and CP have to perform relatively more operations as compared to PHA; nevertheless the time consumed by these operations (hash and XOR) is less than encryption operation. That is why we argue that, in performance, DMA will outperform PHA. Secondly, in DMA, both parties are involved in setting up the session key with mutual agreement. The communication cost is minimum since OBU and charging plate are communicating directly. Therefore, the only parameter that could affect the performance of DMA and PHA is the length of the charging plate. If we consider the normal speed of the vehicle, then PHA will favor the lengthier charging plate than DMA, because of the communication delay incurred by the PHA. On the other hand, PHA does not cost any computation delay because the processing is carried out at resource rich CSPA and charging plate is only used as intermediary bridge between vehicles and CSPA. However, in case of PHA, the session key is constructed by one entity, CSPA. Moreover OBUs must save the hash chain of the currently used pseudonyms in the onboard storage thereby incurring storage cost. Therefore, we can argue that these two methods can be used in different circumstances that fit the necessary conditions for direct and hash-based authentication. For normal scenarios, DMA will be the fair choice because of its security, auditability guarantee, and robustness.


## 7. Conclusion and Future Directions

In this paper, we proposed a secure, privacy-aware, and bidirectional auditable mechanism for wireless power transfer in online electric vehicles. The power transfer technology is installed under the road in the form of charging plates where a segment of the road constitutes a charging plate containing a hardware module for communication and lightweight computation. In our proposed scheme, the vehicles use multiple pseudonymous strategy to mutually authenticate with the charging plate and then expedite the power transfer. Meanwhile electric power service provider bills the vehicles on per charging palate basis. Our proposed scheme provides secure and privacy-aware bidirectional auditability where the billing process is verifiable by both parties. Moreover we also present the game theoretic approach to validate the bidirectional auditability.In the future, we aim to implement the system to have a deeper insight into the performance issues. Moreover we also aim to relax the assumption of fixed per-plate charging cost. We will focus on a more robust mechanism where the vehicles will have choice to buy the charge according to their convenience. We will address the complexity involved in such robust charging and its billing mechanism.



---

*Source: 5676030-2017-10-31.xml*