UE THROUGHPUT CHECK

Basic Test
UE THROUGHPUT CHECK

 Test environment
Most applications used by the end-user is conducted over the TCP protocol. Example services are
http (web browsing), ftp, email and online speed tests. If possible, try to avoid testing over the internet
as we have no control after the traffic leaves the customer network.
Request a test server within the customer network, where we have control over equipment and
parameters affecting throughput.

 Run user traffic using UDP

Many factors can affect e2e throughput. As TCP packet loss may impact throughput heavily, we
prefer to use UDP traffic for test as UDP packet loss has no effect on delay. It also enables us to
conclude if the throughput problem affects both TCP and UDP or only TCP or UDP. TCP speed will
always be slightly lower than UDP speed. Therefore, if UDP speed is bad, TCP speed will also be bad.
For example, if we have bad throughput running TCP traffic and excellent throughput running UDP
traffic, we most likely have a well performing air interface.
UE THROUGHPUT CHECK

 Basic checks
 Is your current test setup verified as working (UE/SIM/Laptop)? Did you try another UE?
 Is the correct APN in use?
 What is the Aggregate Maximum Bitrate in DL/UL associated with your subscriber profile?
Check S1AP message InitialContextSetupRequest in TEMS/XCAL:

value InitialContextSetupRequest : {
protocolIEs {
value UEAggregateMaximumBitrate : {
uEaggregateMaximumBitRateDL 999000000, [999 Mbps]
uEaggregateMaximumBitRateUL 999000000 [999 Mbps]
}
UE THROUGHPUT CHECK

 Iperf
Iperf is a tool used to generate a constant stream of network traffic. It can be used for both
TCP and UDP traffic tests. A big advantage is that Iperf has a lot of parameters that can be
used to change the behavior of the network traffic. The parameters are set by giving an
input flag together with a value when you start Iperf. To download Iperf, see [5],[6],[7]. Iperf
is a command line tool. For Windows, extract Iperf.exe together with the .dll files into a
directory, i.e. C:\Iperf.
-s Indicates start as server
-c Indicates start as client, this has to be followed by the ip-address where the iperf-server is running (on the UE
side if running downlink).
-p Is the port nr, 5001 is standard but any port can be used.
-u Indicates UDP traffic
-i Is the update interval for which printouts of the received data is shown.
-b Is the bandwidth on how much traffic the client will try to push. 60M is 60 Mbit/s.
-t Is how many seconds it should run for.
-l Is buffer length - specify the length of send or receive buffer.
UE THROUGHPUT CHECK

 For UDP DL traffic test [MIMO, 20 MHz BW]

 Start Iperf server in UE/Laptop:
C:\Iperf\iperf –s -u -i 1 -p 5001
 Start Iperf client in test server:
C:\Iperf\iperf -c <UE/Laptop IP> -u -i 1 -l 1360 -b 100M -p 5001 -t 600 -u -i 1 -p 5001

 For UDP UL traffic test [MIMO, 20 MHz BW]

 Start Iperf server in test server:
C:\Iperf\iperf –s -u -i 1 -p 5001
 Start Iperf client in UE/Laptop:
C:\Iperf\iperf -c <test server IP> -u -i 1 -l 1360 -b 50M -p 5001 -t 600 -u -i 1 -p 5001

Note: Make sure UDP traffic is allowed in test server firewall. Create a rule or turn off if possible.
THANK YOU