Bug 1992

Summary: LTE throughput not affected by distance
Product: ns-3 Reporter: vagelis.ioannou
Component: lteAssignee: Nicola Baldo <nicola>
Status: RESOLVED INVALID    
Severity: normal CC: ns-bugs
Priority: P5    
Version: ns-3-dev   
Hardware: PC   
OS: Linux   
Attachments: The modified lena-simple-epc file

Description vagelis.ioannou 2014-09-23 10:07:53 UTC
Created attachment 1885 [details]
The modified lena-simple-epc file

I tried to run the lena-simple-epc example and I found that the reception is not affected by distance.

In order to test I changed the src/lte/examples/lena-simple-epc.cc file to include application layer logging:

    LogComponentEnable ("UdpClient", LOG_LEVEL_ALL);
    LogComponentEnable ("PacketSink", LOG_LEVEL_ALL);

at line 50.

I tested with the following command:

    ./waf --run 'src/lte/examples/lena-simple-epc --distance=1e10'

with different values of the distance parameter. The result is that for any distance, the performance is exactly the same, i.e. the packets are received at the exact same time instance.

I would expect that for distance over the LTE range, communication would be imposible, and for smaller distances the throughput would increase, thus affecting packet reception times (even marginally). However this is not the case. The simulation seems unaffected by the distance between the nodes.
Comment 1 Nicola Baldo 2014-09-23 10:29:38 UTC
There are so many tests that validate the performance of the LTE model vs distance
http://www.nsnam.org/docs/models/html/lte-testing.html#system-tests
that I am highly confident that the behavior is ok. 
So I will close this bug as invalid, unless you can provide clear evidence that the expected performance (with reference expected values, and an explanation of how you calculated them) is different than the measured one.
Comment 2 Nicola Baldo 2014-09-29 08:02:46 UTC
*** Bug 1993 has been marked as a duplicate of this bug. ***
Comment 3 Nicola Baldo 2014-09-29 08:04:45 UTC
Closing as invalid for the previously mentioned reasons. Feel free to reopen it if you can provide clear evidence of an actual bug.