In the interference case(one of the reasons for packet loss) the calculation of packets dropped due to radio resource collision is not correctly implemented.
When two or more packets are arriving simultaneously having the same subframe and subchannel, in such a scenario the last packet is always getting accepted, which is increasing the total number of successfully decoded packets and indirectly producing the high PDR values, which is unacceptable.
The below figure explains this case. While running the experiment for a small scale scenario i.e. three cars within 300m range and two out of three cars are using the same subframe and subchannel combination. The Mode4App has started at the same time. Also, minor changes have been done in the config_channel.xml file to use the analytical model for filtering the packets based on their SNR value.
The PDR values reported by three cars are 0.5, 1,~1 for Car0, Car1 and Car2 respectively. Ideally, the expected PDR values should be 0.0, 0.5 and 0.5.
In the interference case(one of the reasons for packet loss) the calculation of packets dropped due to radio resource collision is not correctly implemented.
When two or more packets are arriving simultaneously having the same subframe and subchannel, in such a scenario the last packet is always getting accepted, which is increasing the total number of successfully decoded packets and indirectly producing the high PDR values, which is unacceptable.
The below figure explains this case. While running the experiment for a small scale scenario i.e. three cars within 300m range and two out of three cars are using the same subframe and subchannel combination. The Mode4App has started at the same time. Also, minor changes have been done in the config_channel.xml file to use the analytical model for filtering the packets based on their SNR value.
The PDR values reported by three cars are 0.5, 1,~1 for Car0, Car1 and Car2 respectively. Ideally, the expected PDR values should be 0.0, 0.5 and 0.5.
