What are the common tips for thoughput test ?

 

Followings are some common tricks we want you to keep in mind when you do throughput test

 

How can I test throughput?

 

Under your enb/doc directory, there is an application note for throughput testing. You can read it for a detailed explanation on how to test throughput with Amarisoft LTE 100.

The most convenient way to test throughput is to use iperf which is a common tool.
On the PC where MME is running, you can install iperf by typing the following command for Fedora:

yum install iperf

For Ubuntu you should use

sudo apt-get install iperf

To do a simple UDP downlink test in MIMO CAT 4 at 150 Mbps, run the following command on the MME PC

iperf -c -u -b 150M -t 60

You can obtain the UE IP address, by typing ue on MME monitor

If you want a simultaneous TCP test, you need to install iperf on your android phone (or on the remote PC if you have a dongle) and start:

iperf -s

Then on MME PC, type

iperf -c -d -t 60

 

I can not reach the full downlink throughput in my tests

• Verify correct settings of tx_gain. Usually for wired setup tx_gain is set to 70 and in wireless setup tx_gain is set to 90. You can also refer to wiki page for more details about signal level:

https://extranet.amarisoft.com/wiki/doku.php?id=info:enb_signal_power

• Cross check RF cables and make sure that the correct RF ports are cabled.
• Check your eNb config file to see if you have configured MIMO
• Use UDP with iperf to rule out any TCP or web server issue.
• Activate eNb log by typing t command on eNb PC. Check cqi, ri and retx parameters. Typically, you should get a high cqi, ri=2 and retx=0

 

How to set higher UL throughput ?

UL maximum throughput may be increased.
Make sure that UL received signal is not saturated. For more details refer to:

[[https://extranet.amarisoft.com/wiki/doku.php?id=info:enb_signal_power]]

The 16 resource blocks allocated for control in UL can be modified.
They are linked to nRB-CQI and n1PUCCH-AN parameters in sib2_3.
They could be decreased if you really want to try better throughput.

You may also have a look at t eNB command output:

UE_ID CL RNTI cqi ri mcs retx txok brate snr puc1 mcs retx rxok brate turbo phr 3 01 003f 15 2 28.0 0 202 101M 15.7 10.7 20.0 0 101 35.2M 1/1.5/3/ 20

In this case the UL MCS is at its maximum because it is limited by following parameter pusch_max_mcs of eNB config file.
So you can increase it or just comment it.

 

Still have low throughput !!!

You still have T-put issue, you can open a support ticket and share:- eNB log file with NAS/RRC/PHY traces:

log_options: "all.level=none,all.max_size=1,nas.level=debug,rrc.level=debug,phy.level=debug",

- config file- output of "cell phy", "t" & "t spl" command during T-put testing.