Uplink Throughput measure with FlowMonitor

[akada...@sabanciuniv.edu]

Dear ns3 community,

I would like to ask the outcome of my simulation in order to clarify the reason behind the UL throughput value. The DL measurement is fine but for the UL i get strange results. Application is creating a UDP traffic at a rate of 10.528 Kbps in two-way. I would share my initial configuration to help others to understand how the simulation starts at the beginning.


Any help would be appreciated,

Kindly regards
Aykut

Config::SetDefault ("ns3::LteEnbRrc::EpsBearerToRlcMapping", EnumValue (ns3::LteEnbRrc::RLC_UM_ALWAYS)); //
Config::SetDefault ("ns3::LteHelper::UseIdealRrc", BooleanValue (true));
Config::SetDefault ("ns3::LteAmc::AmcModel", EnumValue (LteAmc::PiroEW2010));
Config::SetDefault ("ns3::LteAmc::Ber", DoubleValue (0.00005));
Config::SetDefault ("ns3::LteEnbRrc::DefaultTransmissionMode", UintegerValue (0));
Config::SetDefault ("ns3::LteSpectrumPhy::DataErrorModelEnabled", BooleanValue (true));
Config::SetDefault ("ns3::LteSpectrumPhy::CtrlErrorModelEnabled", BooleanValue (false));
Config::SetDefault ("ns3::LteEnbPhy::TxPower", DoubleValue(60.0));
Config::SetDefault ("ns3::LteUePhy::TxPower", DoubleValue(23.0));
Config::SetDefault ("ns3::LteUePhy::EnableUplinkPowerControl", BooleanValue (false));
Config::SetDefault ("ns3::LteRlcUm::MaxTxBufferSize", UintegerValue (2*1000000)); // 2 MB

Results:

AVERAGE CQI: 15,RNTI:,1,CELL_ID:3
AVERAGE CQI: 13,RNTI:,1,CELL_ID:3
/NodeList/3/DeviceList/0/LteUePhy/ReportUeMeasurementseNB Cell ID  1  RNTI  1  RSRP  -126.322  RSRQ  -43.2283  isServing  0
/NodeList/3/DeviceList/0/LteUePhy/ReportUeMeasurementseNB Cell ID  2  RNTI  1  RSRP  -89.778  RSRQ  -6.68483  isServing  0
/NodeList/3/DeviceList/0/LteUePhy/ReportUeMeasurementseNB Cell ID  3  RNTI  1  RSRP  -89.7894  RSRQ  -6.6962  isServing  1
---------UPLINK TRAFFIC----------------RNTI: 1
Flow ID            : 1 ; 7.0.0.2 -----> 1.0.0.2
Tx Packets = 10990
Tx Bytes = 14770560
Rx Packets = 57
Rx Bytes = 76608
Duration        : 10.989
Last Received Packet    : 10.999 Seconds
Lost Packet : 934
Throughput: 54.4639 Kbps
---------------------------------------------------------------------------
---------DOWNLINK TRAFFIC----------------RNTI: 1
Flow ID            : 2 ; 1.0.0.2 -----> 7.0.0.2
Tx Packets = 10990
Tx Bytes = 14770560
Rx Packets = 10921
Rx Bytes = 14677824
Duration        : 10.989
Last Received Packet    : 10.999 Seconds
Throughput: 10436.9 Kbps
---------------------------------------------------------------------------

[Tommaso Pecorella]

Hi,

from the look of it, the difference in Tx power from eNB and UE is too large. The eNB range is large enough to reach users that are extremely impaired.

T.

[Aykut]

Hello Tommaso,

Thanks for the reply

What i see in the simulator is that if the link budget does not meet with the traffic requirement Flow Monitor just shows the last throughput value. Normally it should show 0 Kbps for throughput but, it is still giving the last transmission value. Because first uplink traffic starts to print the same throughput values then dowlink traffic starts (which is logical DL link budget is more than UL link budget) Do you have any idea about why this Flow Monitor is always printing the same values ?


We can also see that when CQI:0 we still see a value for throughput in the Flow Monitor

/NodeList/3/DeviceList/0/LteUePhy/ReportUeMeasurementseNB Cell ID  3  RNTI  1  RSRP  -241.555  RSRQ  -121.326  isServing  1
AVERAGE CQI: 0,RNTI:,1,CELL_ID:3
UE IS OUT OF COVERAGE !

---------UPLINK TRAFFIC----------------

Flow ID            : 1 ; 7.0.0.2 -----> 1.0.0.2

Tx Packets = 76990
Tx Bytes = 103474560
Rx Packets = 10084
Rx Bytes = 13552896
Duration        : 76.989
Last Received Packet    : 76.999 Seconds
Lost Packet : 56907
Throughput: 1518.35 Kbps
End-to-End Delay: +4086929785.0ns
---------------------------------------------------------------------------
---------DOWNLINK TRAFFIC----------------

Flow ID            : 2 ; 1.0.0.2 -----> 7.0.0.2

Tx Packets = 153980
Tx Bytes = 206949120
Rx Packets = 26979
Rx Bytes = 36259776
Duration        : 76.9895
Last Received Packet    : 76.9995 Seconds
Lost Packet : 106981
Throughput: 4316.11 Kbps
End-to-End Delay: +2421999999.0ns
---------------------------------------------------------------------

What I don't understand why the counter does not update itself when there is physically no connection at the LTE stack

Btw: Calculations are made in every second

Regards
Aykut

[Tommaso Pecorella]

Hi,

FlowMonitor is made to perform calculation for the whole simulation, not every second. If you want to have (for example) a throughput per second, you have to do the math by yourself, picking the values from the previous call and doing... the math.

T.

[dingxi...@gmail.com]

Hello Aykut

I am somehow new to ns3, and now I need to get the values of CQI, SINR and RSSI, but I don't know how to get them. Could you tell me how to get this result or send your script to me? That will be very helpful. Thank you!

Best regards.

Ding xiang.

在 2017年1月2日星期一 UTC+8下午7:24:52，Aykut写道：