Lynx: Authenticated Anonymous Real-Time Reporting of Electric Vehicle Information

Lynx: Authenticated Anonymous Real-Time Reporting of Electric Vehicle Information

2015 IEEE International Conference on Smart Grid Communications (SmartGridComm): Cyber Security and Privacy Lynx: Authenticated Anonymous Real-Time Reporting of Electric Vehicle Information Hongyang Li Gy¨orgy D´an Klara Nahrstedt University of Illinois Urbana-Champaign KTH Royal Institute of Technology University of Illinois Urbana-Champaign [email protected] [email protected] [email protected] Abstract—With the proliferation of electric vehicles (EVs), EV ture authentication. However, digital signature is computation- battery charging will be a significant load on the power grid, and ally expensive [7] and identity-revealing. Several works [8], [9] thus it will have to be optimized. Many proposed optimizations improve authentication efficiency by using symmetric keys, but rely on predicted EV information, such as future trip start time and battery State-of-Charge (SoC), for load management, charg- do not provide anonymity protection. Portunes [10] uses utility- ing scheduling, V2G profit optimization, etc. Prediction in turn issued pseudonyms to protect the EV’s privacy from third-party would benefit from real-time information about the EVs, while entities, but the utility knows the mapping between pseudonym they are on the road, i.e., before arriving at the charging facility. and EV’s true identity. Token-based approaches [11], [12] let A real-time reporting framework is thus necessary so that EVs the EV authenticate itself by revealing an authentication token can report status information to the utility in a timely fashion. In this paper we present Lynx, an authenticated anonymous real- to the utility, but the token revealing process is computationally time reporting protocol. Lynx allows an EV to send anonymous intensive and is not efficient for real-time reporting (e.g., in reports using pseudonyms that are unlinkable to its true identity. dynamic charging scenario [10] the EV needs to send a report At the same time, the utility can verify that the reports come from to a new charging pad every tens of milliseconds). some authentic EV without knowing the exact identity of the EV In this paper, we propose Lynx, an efficient and secure that sends the report. To encourage EV participation, Lynx allows the utility to issue anonymous receipts to EVs, which can be used anonymous real-time reporting protocol for EVs to submit real- later by the EVs to anonymously claim credits. Lynx minimizes time reports to the utility. Lynx achieves efficient real-time computation overhead during real-time reporting, and our imple- reporting by performing computationally intensive pseudonym mentation on Raspberry Pi 2 shows that report generation and and session key allocation during the night when the EV is verification can be done within 10 ms. parked at home, which allows the EV to use efficient symmetric key authentication for real-time reporting on the road without I. INTRODUCTION invoking additional key exchange protocols. To protect the Charging electric vehicles (EVs) will put a significant load EV’s anonymity, Lynx uses partially blind signatures and an on the future power grid. To ensure efficient grid operation, anonymous authenticated version of the Diffie-Hellman key there is an emerging consensus that EV charging/discharging exchange protocol during the session key negotiation so that will have to be coordinated, in order to reduce power losses the utility does not know the mapping between the EV’s true caused by uncontrolled EV charging [1], to avoid congestion in identity and its pseudonym/session key. Finally, to support the distribution network [2], [3], to adjust real-time electricity various incentive mechanisms, Lynx allows the utility to issue price [4], to minimize the EVs’ waiting times at charging anonymous receipts to EVs, and these receipts do not reveal stations [5], and to optimize V2G energy and ancillary service any information about the EV’s identity or about the task that scheduling [6], etc. A prerequisite for efficient coordination the EV has performed (otherwise the utility could advertise is accurate prediction of the EVs’ activities, such as arrival, a special task only to a specific area, and a receipt showing departure, and battery State-of-Charge (SoC), which requires that the EV has performed that particular task gives away the the EVs to report real-time status information to the utility upon information that the EV was at that area). request. The rest of our paper is organized as follows: in Section II To gain acceptance, the real-time reporting of EV infor- we review security background and related work; in Section III mation must be secure, efficient, and privacy-preserving. The we describe the system model and design goals of Lynx; in utility must be able to authenticate the reports to make sure Section IV we present the Lynx protocol; in Section V we that it only uses reports from authorized EVs. At the same analyze security and privacy properties of Lynx; in Section VI time, since the report may contain sensitive information (e.g., we evaluate the performance of Lynx, and conclude our paper the EV’s current location), the EV has a natural incentive to in Section VII. remain anonymous. Real-time reporting should also have a low II. SECURITY BACKGROUND AND RELATED WORK communication overhead to be bandwidth efficient. Last but not least, the utility may want to reward the EVs for the information A. Security Background provided, and thus the reporting system should support the Authenticated Encryption: Encryption and Message Au- implementation of an incentive mechanism. thentication Code (MAC) can be combined in different ways The most straightforward approach would be to let each EV to provide both message integrity and authenticity. In Encrypt- submit its own report directly to the utility using digital signa- then-MAC (EtM) the sender sends E[m], MAC(E[m]),where 978-1-4673-8289-2/15/$31.00 ©2015 IEEE 599 2015 IEEE International Conference on Smart Grid Communications (SmartGridComm): Cyber Security and Privacy the plaintext is first encrypted, and the MAC on the ciphertext is information is a key requirement. PEPSI [20] assumes that appended. EtM was proved to be more secure than both MAC- the participating mobile nodes and the querier do not share a then-Encrypt (MtE) and Encrypt-and-MAC (E&M) [13], and common secret, and thus chooses an Identity-Based Encryption thus Lynx adopts EtM for real-time reporting. (IBE) approach for anonymous reporting. In our scenario it is Blind Signature: Blind signature [14] allows the user to reasonable to assume that the utility and the EV know each request a signature of a message from the signer without the other (i.e., they know the public key of each other). With this signer learning about the content of the message. The signa- assumption Lynx is able to establish anonymously a session key ture requester generates a secret pair of blinding/unblinding and uses efficient symmetric cryptography to authenticate real- operations (b, b−1), and applies the blinding operation b to time reports. SPPEAR [21] uses oblivious transfer [22] to allow the plaintext message m. The requester then sends the blinded an EV e to obtain an authorization token τ from a set of tokens message b(m) to the signer. The signer signs the blinded Πe generated by the utility, and then uses the authorization message with operation s and produces a signature s(b(m)), token to establish a pseudonym. The use of oblivious transfer and returns the signature to the requester. The requester now unnecessarily complicates the protocol design, as the protocol applies the unblinding operation b−1 to the signature to obtain must guarantee that (i) for any two different EVs e and e, −1 b (s(b(m))) = s(m), which is a signature on the plaintext the corresponding token sets Πe, Πe from which they obtain message. Note that the signer only knows the blinded message the token have non-empty intersection, i.e., Πe ∩ Πe = ∅; b(m), not the plaintext message m. Only the original requester and (ii) no two EVs can obtain the same token. Anonymous can unblind a signature s(b(m)) to obtain s(m). The requester e-Tokens [12] allows a participant to show the token at most can further verify that s(m) is indeed a valid signature on m, n times anonymously, where n is a system parameter. If the but cannot forge such a signature. participant attempts to show the token more than n times, Partially Blind Signature: Partially blind signature its identity can be inferred. However, the verification of e- (PBS) [14] is similar to blind signature in that the signer does Token requires an online zero-knowledge proof, which does not not learn the content of the signed message. However, PBS satisfy our efficiency requirement due to its computation and allows the signer to include some common message in the communication overhead. Li and Cao [11] proposed a privacy- signature. The signer and the requester first agree on the content aware incentive mechanism using token-based authentication of the common message m0. The requester submits blinded for real-time reporting, but their design requires the EV to message b(m), the signer generates signature s(b(m),m0),and reveal all unused tokens at the end of each iteration, which returns it to the requester. The requester applies the unblinding incurs additional communication overhead. −1 operation to obtain b (s(b(m),m0)) = s(m, m0). Lynx differs from previous works in that it allows the com- Diffie-Hellman Key Exchange: Diffie-Hellman key ex- putationally intensive part of the protocol to be performed a change (DHKE) allows two parties to establish a common priori. This design choice is motivated by the common ob- secret.

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    6 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us