14-04-2014, 12:58 PM
KEY MANAGEMENT AUTHENTICATION USING VANETs
KEY MANAGEMENT AUTHENTICATION.docx (Size: 665.58 KB / Downloads: 22)
Abstract
Vehicular Ad Hoc network is commonly used network among the vehicles in a centralized way. This network is built in order to send and receive messages from the vehicles which are present in the network. Since it is a centralized network, hence many problems will occurs in the network. Introducing a distributed key management framework based on group signature to provide message privacy in vehicular ad hoc networks (VANETs). Distributed key management is expected to facilitate the revocation of malicious vehicles, maintenance of the
system, and security policies. The road side unit (RSU) which is present distributes the keys to the vehicles. Authorities will be there which generate the group public key and private keys for rsu’s. Tracing key will be there only with authority to maintain security purpose and authority will check which vehicle will send false information. Thus by developing secure key distribution protocol with the capability of preventing RSUs from misbehaving. The protocol guarantees to detect compromised RSUs and their colluding malicious vehicles. A practical cooperative message authentication protocol is thus proposed to reduce the verification burden, where each vehicle just needs to verify a few messages.
Introduction
In roads traffic congestion is more and accidents occur due to it. Rash driving causes loss of lives so to prevent that safety driving applications are made[1].
To avoid accidents Vanets are used which have attracted a lot of attentions due to their interesting
and promising functionalities including vehicular safety, traffic congestion avoidance, and location based services[2][3][6].
Vanets focus on safety driving application, where each vehicle periodically broadcasts messages including its current position, direction and velocity, as well as road information [3].
Network Model
The infrastructure of VAETs is based on the entities and those can be classified into three categories: authorities, road side infrastructure, and nodes. Authorities are responsible for key generation and malicious vehicle judgment. Authorities have powerful firewalls and other security protections. Road side infrastructure consists of RSUs deployed at the road sides which are in charge of key management in the framework. Traffic lights or road signs can be used as RSUs. RSUs communicate with authorities through wired network. Nodes are ordinary vehicles on the road that can communicate with each other and RSUs through radio. Vehicle should check other vehicle message by using rsu group keys and encrypt the messages. If any vehicle is sending false information means other vehicle will update the false information to rsu.
Group Signature Based Privacy System
The communications can be divided into key distribution phase and the regular broadcast phase. Vehicles get keys dynamically in the key distribution phase and then start to broadcast their geographic and road condition messages periodically in the regular broadcast phase. Members of a group sign messages under the name of the group. In a group, there are one group public key and many corresponding group private keys. A message that is signed by any group private keys can be verified with the unique group public key, and the signer’s identifier will not be revealed. However, authorities hold a tracing key which can be used to retrieve the group private key from the signature. If one group private key is to only one user, the signer can be identified after authorities get its group private key.
Registration Procedure
Authorities make decisions according to the registration information that vehicles provide..
Message 1: RSUs broadcast I-public keys, G-public keys of themselves and their neighbor RSUs with certificates and identities of revoked RSUs in their neighborhoods regularly.
Message 2: When a vehicle detects the hello message, it starts r`egistration by sending its I-public key and the certificate to the RSU if the RSU is not revoked. Each vehicle’s I-public key is unique, so it is also an identifier of the vehicle.
Message 3: The RSU sends the hash value of the G-private key which plans to be assigned to the vehicle and the signature of the hash value, vehicle’s I-public key and RSU’s I-public key to the vehicle. RSU’s I-public key is also unique.
Message 4: The vehicle encrypts its Npri and the timestamp by using authorities’ public key.
Conclusion
Finding out the semi-trust RSUs using short group signature and if rsu is revoke then vehicle will not send any information. Using Visual studio tool and C# has the language showing the process that occurs inside the vehicles and rsu’s and showed how authority generate keys and rsu distributes key. If any vehicle sends false message other vehicle will sends information to authority that vehicle is send wrong information. Authority uses tracing key and check the false message. The graph is showed which shows the performance of RBM,CAM and how many messages are verified with time.