<p>I am not familiar with the <a href="https://github.com/VeReMi-dataset" rel="nofollow noreferrer">VeReMi project</a>, so I do not know what value it is referring to as "the RSSI" when a frame is received. The accompanying <a href="https://arxiv.org/abs/1804.06701" rel="nofollow noreferrer">ArXiV paper</a> paper mentions no more details than that "the RSSI of the receiver" is logged on frame receptions.</p>

<p>Cursory inspection of the <a href="https://github.com/VeReMi-dataset/veins/blob/24e49cb4a140419d9cc88f0bbe54990c4ac63007/src/veins/modules/phy/Decider80211p.cc#L476" rel="nofollow noreferrer">code for logging the dataset you mentioned</a> shows that, on every reception of a frame, a method is called that <a href="https://github.com/VeReMi-dataset/veins/blob/24e49cb4a140419d9cc88f0bbe54990c4ac63007/src/veins/base/phyLayer/BaseDecider.cc#L271" rel="nofollow noreferrer">sums up the power levels of all transmissions currently present at the receiver</a>.</p>

<p>From this, it appears quite straightforward that (a) how far a frame traveled when it arrives at the receiver has only little relation to (b) the total amount of power experienced by the receiver at this time.</p>

<p>If you are interested in the Received Signal Strength (RSS) of every frame received, there is a much simpler path you can follow: Taking Veins version 5 alpha 1 as an example, your application layer can access the ControlInfo of a frame and, from there, its RSS, e.g., as follows:
<code>check_and_cast&lt;DeciderResult80211*&gt;(check_and_cast&lt;PhyToMacControlInfo*&gt;(wsm-&gt;getControlInfo())-&gt;getDeciderResult())-&gt;getRecvPower_dBm()</code>. The same approach should work for Veins 4.6 (which, I believe, the VeReMi dataset you are referring to is based) as well.</p>

<p>In simulations that only use <code>SimplePathlossModel</code>, Veins' version of a free space path loss model, this will result in the familiar curve:</p>

<p><a href="https://i.stack.imgur.com/D15zF.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/D15zF.png" alt="enter image description here"></a></p>
How does veins calculate RSSI in a Simple Path Loss Model?
<p>We are working on an application based on Veins framework which needs RSSI value of received signal and the distance between sender and receiver. </p>

<p>We referred to the VeReMi project which also calculates RSSI value and sends it to upper level. </p>

<p>We compared our simulation result (RSSI vs Distance) with the VeReMi dataset and they look quite different. Can you help us to explain how RSSI is calculated and whether our result is normal?</p>

<p>In our application, we obtain the distance and rssi value by</p>

<pre><code>auto distance = sender.getPosition().distance(receiverPos);
auto senderRSSI = sender.getRssi(); 
</code></pre>

<p>In the lower level, the rssi is set in the Decider80211p::processSignalEnd(AirFrame* msg) method as in the VeReMi project.</p>

<pre><code>if (result-&gt;isSignalCorrect()) {
    DBG_D11P &lt;&lt; "packet was received correctly, it is now handed to upper layer...\n";
    // go on with processing this AirFrame, send it to the Mac-Layer

    WaveShortMessage* decap = dynamic_cast&lt;WaveShortMessage*&gt;(static_cast&lt;Mac80211Pkt*&gt;(frame-&gt;decapsulate())-&gt;decapsulate());

    simtime_t start = frame-&gt;getSignal().getReceptionStart();
    simtime_t end = frame-&gt;getSignal().getReceptionEnd();
    double rssiValue = calcChannelSenseRSSI(start, end);
    decap-&gt;setRSSI(rssiValue);

    phy-&gt;sendUp(frame, result);
}
</code></pre>

<p>Regarding the simulation configuration, our config.xml differs from VeReMi and there is no the following lines in our case.</p>

<pre><code>&lt;AnalogueModel type="VehicleObstacleShadowing"&gt;
        &lt;parameter name="carrierFrequency" type="double" value="5.890e+9"/&gt;
&lt;/AnalogueModel&gt;.
</code></pre>

<p>The 11p specific parameters and NIP settings in the omnetpp.ini are the same.</p>

<p>Also, our simulation is based on Boston map. </p>

<p>The scatter plot of our simulation result of RSSI_vs_Distance is shown in the following figure.</p>

<p><a href="https://i.stack.imgur.com/3uoLD.jpg" rel="nofollow noreferrer">RSSI vs Distance from our simulation shows that even at distance beyond 1000 meters we still have received signal with strong RSSI values</a></p>

<p>In comparison, we extract data from VeReMi dataset and plot the RSSI vs Distance which is shown in following pic.</p>

<p><a href="https://i.stack.imgur.com/XPqnb.jpg" rel="nofollow noreferrer">VeReMi dataset RSSI vs Distance is what we were expecting where RSSI decreases as distance increases</a></p>

<p>Can you help us explain whether our result is normal and what may cause the issue we have now? Thanks!</p>