# Compacted Area with Effective Links (CAEL) for Data Dissemination in VANETs
## 1 Introduction  
Many people across the world are killed or injured every day due to traffic accidents [1]. These deaths and injuries could potentially be avoided if VANETs are used. Intelligent Transportation Systems (ITS) applications can benefit greatly from VANET's support capabilities, which is why academics and researchers are interested in it [2, 3, 4, 5]. VANETs are a cost effective means of providing communication amongst vehicles. Each vehicle on the road will be equipped with a wireless communication capability to facilitate the interconnection of wireless networks. A vehicle can receive or forward messages from nearby vehicles linked to the same network even if no supporting infrastructure is present. As a result, drivers will be able to keep track of changes in traffic conditions and other travel-related information as they are made accessible. VANETs have certain advantages in comparison to mobile ad hoc networks (MANETs), including enhanced computational power, increased transmission power, and a degree of projected mobility. The performance and quality of VANET generates major technical issues in existing systems which must be monitored to efficiently organize these types of connections. Frequent changes in network topology as well as the increased mobility of the network topology are likely to be the most difficult problems to solve [6]. When cars change their data rates or tracks in VANETs, the topology of the network also changes. Normally, the aforementioned modificationsare not planned ahead of time and are entirely dependent on the road conditions and the actions of the drivers. VANET communication requires a routing mechanism that is both dependable and accurate in representing the topological needs of the network's nodes, and development of such routing a mechanism is the major purpose of this research. Given that cars are driven at high speed on roads, disruptions in terms of data distribution facilities as a result of frequent interruptions in the connection are likely. VANET's architecture can be categorized as seen in Figure 1:  
1. \"Vehicle-to-Vehicle (V-2-V)\": The vehicles may directly communicate with other vehicles [7]. 2. \"Vehicle-to-Infrastructure (V-2-I)\": The local networks and cellular base towers make it possible for vehicles to communicate with one another at different geological locations. 3. \"Infrastructure-to-Infrastructure (I-2-I)\": In addition to information being sent between many and distant sites, communication may take place among peer-to-peer infrastructures [8]. There is a cost associated with the implementation of vehicular communication systems. Primarily, hardware and software equipment, i.e., the vehicles must be equipped with an onboard unit (OBU) to support wireless communication and a sufficient amount of processing capability to process the information received from other nodes. VANET also require a proper capacity for storage, so that the data can be stored and processed before transmitting for wireless communication. The roadside units (RSU) must be upgraded to support intercommunication between vehicles on the road to enable the exchange of information related to road safety and infotainment. VANET is different from traditional networks due to the absence of a centralized administrative authority that defines the rules for communication. This indicates that the node may act as a server and a client at the same time to share the information with other nodes. The following are some of the qualities of VANETs that make it more appealing:  
1. Vehicles in VANET have a tremendous amount of power and storage. 2. Vehicles have an unlimited source of power, and their capacity to compute for the purposes of sensing and communicating is well supported. 3. Vehicle mobility can be predicted using velocity and coordinate information because of the presence of roadways. Figure 1: VANET’s architecture. The routing method for VANETs offers a substantial challenge because of the unique properties that must be addressed before these networks can be implemented.