## 3 Proposed Architecture
### IFS-CMR Parameters  
The parameters of IFS-CMR are described in detail in the following. Link Latency (LL): Latency is a strong requirement in VANETs. Many applications, especially those related to safety, must run in real-time and the network must provide a very low latency despite the rapid and high topology changes. Therefore, the time it takes the first bit to get from the sender to the destination is crucial in providing high QoS. Radio Interference (RI): Radio Interference indicates the unwanted signals that come from transmissions of adjacent vehicles and disrupt the reception of information. These signals can cause problems from low data speed transmissions to even complete loss of information. Effective Reliability (ER): We define effective reliability as the capacity of the network to successfully deliver messages to its destination. There are many factors that influence ER that include the bandwidth of transmission medium, number of collisions, and buffer size, among others. Update Information for Vehicle Position (UIVP): It is necessary for vehicles to have the coordinates of other surrounding vehicles in order to detect dangerous situations or to monitor traffic. However, too many packets occupy more bandwidth, whereas few packets cannot accurately discover the position of neighboring vehicles. Quality of Service (QoS): Each application has different requirements in terms of latency, bandwidth, throughput, and so on. Safety applications, for example, require real-time communications over reliable links. The latency constraints for such applications are in the range of a few milliseconds [45; 46]. However, satisfying QoS requirements at all  
Figure 3: Structure of fuzzy integrated system. times is not a straightforward task given the highly dynamic topology and interference on these networks. Available Computing Power (ACP): Recent VANET applications require significant computational resources and real-time processing. The intelligent vehicles in the new generation of VANETs are capable of handling some of these applications. Vehicles use their computing power to run their own applications, but they can also allocate some of it for other vehicles to help them in case they need additional computing power to complete certain tasks. When vehicles are willing to share their resources, they let their neighbors know by sending them information about the amount they want to share. In other words, they decide the number of physical processor cores and the amount of memory that other vehicles can use. Predicted Contact Duration (PCD): In a V2V communication, the duration of the communication session is important since it determines the amount of data to be exchanged and the services that can be performed. A vehicle in need of additional resources (_the vehicle_) will have to set up virtual machines on the neighbors that are willing to lend their resources; therefore, the contact duration becomes even more important since much more time is needed to accomplish these tasks than just performing a data exchange. Since the vehicles change their direction or speed, we can only make a prediction of their contact duration based on the value of the parameters at the time when the beacon message was transmitted (for more accuracy, the PCD is updated each time a new beacon message from that neighbor is received). To calculate the PCD between _the vehicle_ and a neighbor vehicle \(i\) (see Figure 4 for illustration), we first calculate the relative speed between these two vehicles using the law of cosines, as given in Equation (1). \[RSV_{i}=\sqrt{V^{2}+V_{i}^{2}-2 VV_{i}\cos\theta_{i}} \tag{1}\]  
where \(V\) is the speed of _the vehicle_, \(V_{i}\) is the speed of neighbor \(i\), and \(\theta_{i}\) is the angle between their directions. Then, we use the law of cosines once again to calculate the PCD, as given in Equation (2).