Content Centric Networking Based Secure Decentralized Data Management In V2G Environment

Abstract

Due to the increasing popularity of Electric vehicles (EVs) around the globe, vehicle-to-grid (V2G) has emerged as one of the most promising technologies of the modern era in modern smart grid ecosystems. In such systems, timely communications among different entities play a pivotal role in efficient decision-making. However, with an exponential increase in the number of EVs around the globe, it is challenging to assign a unique IP address to each EV for content delivery in V2G environment. Also, with an increase in the number of EVs, the traffic load on the network local area aggregator (LAG), (which aggregates the data between charging stations (CS), EVs and disseminates it among different participating entities) increases manyfold. Most of the existing solutions reported in the literature for the aforementioned problems are based upon traditional Internet Protocol (IP)-based architecture, which may have a performance degradation with an increase in the number of nodes in the network. Also, if the contents (for example, power, voltage profile measurements, and hourly electricity charges) need to be shared with multiple entities, then these contents are transmitted from a central source to each entity instantly, leading to wastage of resources. Also, the current Internet architecture lacks in-network caching, which is pre-requisite to take efficient decisions for fast content delivery. Hence, the model shift from existing TCP/IP-based architecture is required to solve the concerns raised in the current Internet architecture, for example, routing, address assignment, congestion, high data delay, scalability, and security. In comparison to traditional IP-based networks, content-centric networks (CCN) are widely used for efficient cache-based content sharing for the successful execution of efficient decisions in V2G network scenarios. In CCN, EVs can cache content to serve other nodes as per the requirements. As the same named data is cached at multiple locations in the network, so it can be retrieved from