Testing Data Throughput
version 2026-04-02*
This document is based on the latest test release.
Features may not be present in your current installed software. You may check their availability in your release documentation.
If you require an up to date release, ask for it in a ticket.

1 Introduction
- 1.1 Background
2 Throughput Tests
3 Logging
4 Troubleshooting
5 Additional Information

1 Introduction

This application note explains the procedure for testing data throughput using Amarisoft eNodeB and EPC (Enhanced Packet Core). We will focus on testing DL (downlink), UL (uplink) and bidirectional data transfers. We will also present recommended applications to be used with UDP and TCP as well as optimal TCP settings to achieve maximum throughput. Some configuration changes may apply if you use Amarisoft eNodeB with a third party EPC or if you use Amarisoft EPC with an external eNodeB. The verification steps could also be different depending on the commands available on third party EPC and eNodeB.

Following section gives you a brief background. Next chapter gives you some hints on the configuration and tools to be used as well as a step by step procedure to execute your throughput tests. The last two chapters focus on logging and troubleshooting to ease the debug process.

1.1 Background

LTE is providing a very large increase in data transmission capacity of mobile networks. Advanced technologies such as MIMO (Multi-Input Multiple-Output) and CA (Carrier Aggregation) have yet enabled higher data rates.

The 3GPP TR (Technical Report) 37.901 document specifies application layer UE data throughput performance testing for both HSPA and LTE networks. It is proposed to test with both TCP and UDP as measurements utilizing each transport protocol are relevant.

TCP
- - TCP is mostly used in applications that need reliable data transfers.
- - TCP throughput is sensitive to the end-to-end delay and packet loss.
- - Bi-directional TCP tests in asymmetric data rate links would cause the downlink speed to be limited by uplink speed. For TCP data transfers in one direction, the TCP ACKs are transmitted in the other direction, therefore delay in receiving TCP ACK in one direction negatively impacts the throughput in the other direction.
UDP
- - Most multimedia and real-time applications use UDP protocol.
- - The performance of UDP based data transfer, unlike TCP based transfer, is Operating System agnostic and is not sensitive to end-to-end delay.
- - UDP Data Transfer in one direction is not dependent on the other direction, unlike with TCP.

There are several factors that could effectively affect the data throughput:

UE category,
Network configuration: cell bandwidth (variable from 1.4 to 20 MHz), transmission mode and CA configuration,
Number of users in the cell,
Signal level: channel and fading conditions, link loss, noise from other UEs, interference from other base stations or radio access technologies,
Application level configuration.

In the following chapter, we will go through all the above items giving recommendation on how to achieve the best throughput.

2 Throughput Tests

2.1 UE Category

First thing to check before starting your throughput tests is the UE category. The UE category indicates the maximum theoretical UL and DL data rates that the UE can achieve. It could be found in the RRC message UE Capability Information. The following example is an extract of OnePlus3 capability information.

UE Capability Information
{
  message c1: ueCapabilityInformation: {
    rrc-TransactionIdentifier 0,
    criticalExtensions c1: ueCapabilityInformation-r8: {
      ue-CapabilityRAT-ContainerList {
        {
          rat-Type eutra,
          ueCapabilityRAT-Container {
            accessStratumRelease rel11,
            ue-Category 4,
            ... 
            },           
            nonCriticalExtension {
              ...                      
                nonCriticalExtension {
                  ue-Category-v1020 6,
                  ...                     
                  rf-Parameters-v1020 {
                    supportedBandCombination-r10 {
                      ...
                      {
                        {
                          bandEUTRA-r10 7,
                          bandParametersUL-r10 {
                            {
                              ca-BandwidthClassUL-r10 a
                            }
                          },
                          bandParametersDL-r10 {
                            {
                              ca-BandwidthClassDL-r10 a,
                              supportedMIMO-CapabilityDL-r10 twoLayers
                            }
                          }                    
                        }
                        {
                          bandEUTRA-r10 3,
                          bandParametersDL-r10 {
                           {
                             ca-BandwidthClassDL-r10 a,
                             supportedMIMO-CapabilityDL-r10 twoLayers
                           }
                          }
                        }
                      },
                      ...
                    }
                  },            
                  ...                                                   
                  nonCriticalExtension {
                    ...                            
                    nonCriticalExtension {
                      nonCriticalExtension {
                        ...                                
                        nonCriticalExtension {
                          nonCriticalExtension {
                            ...
                            nonCriticalExtension {
                              nonCriticalExtension {
                                rf-Parameters-v1250 {
                                  supportedBandListEUTRA-v1250 {
                                    ...
                                    {
                                      dl-256QAM-r12 supported,
                                      ul-64QAM-r12 supported
                                    }
                                  }
                                },
                                ue-CategoryDL-r12 13,
                                ue-CategoryUL-r12 5
                              }
                              ...

The field ue-Category of the UE Capability Information defines a combined uplink and downlink capability. The parameters set by the UE Category are defined in 3GPP TS 36.306. The following table depicts the DL physical layer parameters set by ue-Category.

Table 4.1-2 of 3GPP TS 36.306 v13.5: Downlink physical layer parameter values set by the field ue-Category

The following table depicts the UL physical layer parameters set by ue-Category.

Table 4.1-2: Uplink physical layer parameter values set by the field ue-Category

As can be seen in the above UE Capability Information message, the OnePlus3 phone declares to be a category 4 and category 6 device. LTE category 6 has only been added to the specification in release 10. As such, a category 6 device is required to report category 4 as well to be backward compatible with release 8 networks.

As a category 4 device, OnePlus3 is capable to support 150 Mbps in DL and 51 Mbps in UL at physical layer. DL throughput is achieved by using two layers spatial multiplexing and 64QAM modulation. As a category 6 device, OnePlus 3 device should achieve a max theoretical throughput of 301 Mbps in DL and 51 Mbps in DL.

The above ue-category tables only indicate the maximum theoretical throughput, but do not give any detail about the specific MIMO or CA configuration. As an example, a throughput of 301 Mbps in DL could be achieved either by combining two 20 MHZ carriers with each carrier supporting two layers spacial multiplexing or by using four layers spacial multiplexing in a single cell.

The most common case among commercial devices is to aggregate two carrier components of 20 MHZ each to achieve 301 Mbps in category 6. Looking back at OnePlus3 capabilities, we can see that the device is supporting carrier aggregation with two carrier components as seen in IE (Information Element) supportedBandCombination-r10. Its supported MIMO capability in DL in each carrier is two layers.

Starting from Release 12, a UE can indicate its DL category and UL category separately. The following table depicts the physical layer parameter values corresponding to ue-CategoryDL.

Table 4.1A-1 of 3GPP TS 36.306 v13.5: Downlink physical layer parameter values set by the field ue-CategoryDL.

The following table depicts the physical layer parameter values corresponding to ue-CategoryUL.

Table 4.1A-2 of 3GPP TS 36.306 v13.5: Uplink physical layer parameter values set by the field ue-CategoryUL.

OnePlus3 device is also declaring to be category 13 in DL with 391 Mbps in DL. This category requires support of 256QAM in DL allowing transport blocks to carry up to 97896 bits. As can be seen in OnePlus3 UE Capability Information message, it declares to support 256QAM modulation on top of CA with two carriers and two layers spacial multiplexing in DL. Combining all these features, the OnePlus3 device is able to receive a maximum of 4 transport blocks with 256QAM modulation in a TTI, ie. two transport blocks per TTI per carrier. This will give a DL rate of 4 x 97896 x 1000 = 391 Mbps.

Oneplus3 device is also declaring to be category 5 in UL with 75 Mbps in UL. This category requires support of 64QAM in UL allowing transport blocks to carry up to 75376 bits.

Once the device maximum supported data rate in UL and DL is figured out, next step would be to configure Amarisoft network. This is discussed in the next section.

It would be worthy to note that these throughput numbers are theoretical. All DL/UL TTIs do not carry only user data, there are also a certain portion of overhead due to control part such as SIBs, Signaling as well as user plane protocol headers. So real throughput you get will be less than the one listed in the above tables.

2.2 Network Configuration

The eNodeB configuration plays an important role to achieve best performance. Once the UE category is deduced, it is important to start eNodeB with the right configuration file. The following parameters are important to achieve maximum throughput.

Cell bandwidth: The cell bandwidth has a direct impact on the maximum capacity of the cell. The higher the cell bandwidth, the higher will be the maximum throughput. In Amarisoft solution, the cell bandwidth is configured with the n_rb_dl parameter giving the number of resource blocks. This parameter is available in eNodeB configuration file.
- - Use n_rb_dl = 6, 15, 25, 50, 75, 100 for the bandwidths 1.4, 3, 5, 10, 15, 20 MHz.
- - To ease the bandwidth change, the enb.cfg configuration file has a define at the top named N_RB_DL that can be set to 6, 15, 25, 50, 75, 100.
- - In order to achieve the highest data rate within a cell, the cell bandwidth parameter should be set to 20 MHZ.
Transmission mode: In the downlink, LTE uses technologies such as MIMO to achieve high data rates. In LTE jargon, this is called transmission mode. It is configured with the transmission_mode and transmission_mode_opt parameters in the eNodeB configuration file.
- - For two layers spacial multiplexing, transmission_mode parameter could be set to 3 or 4.
- - Transmission modes 3 and 4 need rank indicator reporting for proper operation. m_ri parameter configures the periodicity of CQI/PMI reports and it should be set to a non-zero value.
- - A typical example to enable 2x2 MIMO in DL is the file enb.cfg which is suitable for a cat 4 device. To use it in 2x2 DL MIMO 20MHz configuration, edit the file and change N_RB_DL to 100 and N_ANTENNA_DL to 2.
Carrier aggregation: there are a lot of parameters to set in this case. A typical example is provided in file enb-2cc.cfg for a category 6 device. This file enables two cells with 5 MHZ bandwidth and in bands 3 and 7. To use it in 2x2 DL MIMO 20MHz configuration, edit the file and change N_RB_DL to 100 and N_ANTENNA_DL to 2.
Number of resource blocks allocated to control: Indeed, not all the resource blocks within a cell could be allocated to user data:
- - In DL, typically some resource blocks should be dedicated to SIBs, PDCCH, etc. Amarisoft eNodeB allows you to specify the number of OFDM symbols for PDCCH. This is controlled with the n_symb_cch parameter in eNodeB configuration file. A value of 0 means that eNodeB will automatically adjust the number of OFDM symbols. A value of 1 is the minimum that you can set for this parameter. The more UEs you have in your cell, the more OFDM symbols are required for PDCCH. So a value of 1 is useful for capacity testing to increase the number of resources blocks used for user data but in real life, this value should be set to 0 or > 1.
- - in UL, some resource blocks are allocated to CQI reporting and PUCCH. This is controlled by nRB-CQI and n1PUCCH-AN parameters in SIB2. Example below is taken from the default SIB2 and SIB3 configuration file sib2_3.asn used for a 20 MHZ cell in Amarisoft eNodeB. We can see that there are 20 resource blocks allocated for control in UL.
```
pucch-ConfigCommon {
  deltaPUCCH-Shift ds2,
  nRB-CQI 8,
  nCS-AN 0,
  n1PUCCH-AN 12
},
```
  nRB-CQI and n1PUCCH-AN parameters could be decreased to 1 to gain a better UL throughput by editing the eNB configuration file and setting the parameters cqi_pucch_n_rb and n1_pucch_sr_count to 1. The more UEs you have in your cell, the more resources are required for PUCCH and CQI. So a value of 1 for nRB-CQI and n1PUCCH-AN is useful for capacity testing but in real life, this value should be set to > 1. You can as well check that the UL MCS is not limited by parameter pusch_max_mcs of eNodeB config file. If this is the case, you can comment the line.
Support of 256QAM in DL: It is configured with dl_256qam parameter in eNodeB configuration file. If set to true, it allows 256QAM DL support for the release 12 UEs supporting this feature.
Support of 64QAM in UL: It is configured with ul_64qam parameter in eNodeB configuration file. If set to true, it allows 64QAM UL support for the release 12 UEs supporting this feature.
Please note that
- - if uplink 64QAM is not activated in the cell or the UE does not support it, eNodeB could allocate up to MCS 24 (even if MCS 21 to 24 are hardly usable on real network deployments as the coding rate starts to be quite high because you use the number of bits of a 64QAM MCS with a 16QAM modulation; the real last 16QAM MCS being MCS 20).
- - if both cell and UE support uplink 64QAM, MCS could go up to MCS 28.

2.3 Number of users in the cell

An LTE cell has a certain capacity based on its configuration. As an example a 20 MHZ cell, could provide a theoretical maximum rate of 151 Mbps. If there is one single UE in the cell, then potentially the eNodeB could allocate all the cell resources to this single UE. If there are more than 1 UE in the cell, then the resources are shared among them and based on the scheduling algorithm used by the eNodeB, they can get a share of the cell capacity.

2.4 Signal Level

A perfect radio channel is required to achieve high throughput. If you are using antennas and there are some interference in the LTE band that you are testing or if you are not in Line of Sight, then you can not achieve high rates.

We recommend the following setups in order to minimize the impact of interference in your testing

If you are using antennas for transmission and reception, you can use a shielded box to isolate your device from outside interference.
You can RF cables to connect your UE to the eNodeB. In this case, please make sure to use attenuators and to tune the transmission gain at both sides in order not to saturate the signal. The parameters tx_gain and rx_gain are configurable in eNodeB configuration file.

2.5 Application Level Configuration

iPerf tool is a commonly used network testing tool that can create TCP and UDP data streams and measure the end to end throughput. iPerf has a client and server functionality, and can measure the throughput between the two ends, either unidirectionally or bidirectionally. We recommend using iPerf for throughput tests as it is simple to use and install on a handset device.

In the following, we focus on throughput testing using iPerf.

2.5.1 iPerf Install on Network side

First, you need to install iPerf on the PC where your core network is running. This is the PC where you have installed LTEMME component.

Assuming you are using a Fedora distribution, you can use the following command:

sudo dnf install iperf

For Ubuntu, the following command can be used:

sudo apt-get install iperf

2.5.2 iPerf Install on UE side

You also need to install iPerf on your device under test. iPerf is available in Google Play for Android as shown below.

2.6 UDP/TCP configuration

UDP does not require any particular configuration neither on the operating system side nor on iPerf side.

For TCP, in order to achieve maximum throughput, the TCP advertised receiver window size must be equal to or greater than the BDP (Bandwidth Delay Product), which can be expressed as follows:

BDP = TCP Bandwidth * RTT

Where
TCP bandwidth is the portion of the radio bearer used to send TCP data. This is the data rate that you would like to achieve based on your UE category and cell configuration. RTT is the Round Trip Time between TCP end-points as seen by the TCP sender. In order to have an idea of the RTT of your link, you can ping your UE from the core network PC.

Please note that some operating systems have limitations on max TCP window size. You can of course tweak your phone if you are root. If you have an Android device, you can check the following parameters with root privilege:

- /proc/sys/net/ipv4/tcp_rmem: memory reserved for TCP receive buffers
- /proc/sys/net/ipv4/tcp_wmem: memory reserved for TCP send buffers
- /proc/sys/net/core/rmem_max: maximum receive window
- /proc/sys/net/core/wmem_max: maximum send window

Parallel TCP connections could certainly help improve the TCP throughput if you can not change the above parameters in your device. With iPerf, you can use the -P <n> option to start n parallel TCP connections.

2.7 Step by Step Throughput Testing

This section provides step by step instructions to test throughput using iPerf.

2.7.1 DL throughput test

To do a simple downlink test in MIMO CAT 4 at 150 Mbps in UDP, you can proceed as follows:

Edit the configuration file enb.cfg and change N_RB_DL to 100 and N_ANTENNA_DL to 2
Start your eNodeB using the configuration file enb.cfg
run iPerf in server mode at the UE side
```
iperf -s -u -i 1
```
Run iPerf in client mode on your core network PC
```
iperf -c <UE IP address> -u -b 150M -i 1 -t 100
```
You can obtain the UE IP address, by typing ue command on MME monitor.
Run the t command in eNodeB screen to activate UE statistics

You can check brate field in DL eNodeB stats for downlink throughput. You can as well check the iPerf application level throughput at the server window.

For a TCP connection, the steps are the same as above except for iPerf command. At UE side, you need to start iPerf in server mode as below:

iperf -s -i 1

The command to be used at core network PC side is:

iperf -c <UE IP address> -i 1 -t 100

2.7.2 UL throughput test

To do a simple uplink test in MIMO CAT 4 at 50 Mbps in UDP, you can proceed as follows.

Edit the configuration file enb.cfg and change N_RB_DL to 100
Start your eNodeB using the configuration file mimo-2x2-20mhz.cfg
Run the following command on your core network PC
```
iperf -s -u -i 1
```
run iPerf in client mode at the UE side
```
iperf -c <PDN Gateway IP address> -u -b 50M -i 1 -t 100
```
Where the PDN Gateway IP address could be found by looking at gateway parameter of the pdn object in LTEMME config file. In default configuration files, the gateway parameter is not set for PDNs. In this case, the first IP of the subnet in IPv4 will be used as gateway IP address.
Run the t command in eNodeB screen to activate UE statistics.

You can check brate field in UL eNodeB stats for uplink throughput. You can as well check the iPerf application level throughput at the server window.

For a TCP connection, the steps are the same as above except for iPerf command. At the core network PC side, you can type the following command:

iperf -s -i 1

At the UE side, the command to run is as below:

iperf -c <PDN GATEWAY IP address> -i 1 -t 100

2.7.3 Simultaneous UL/DL throughput test

For simultaneous UL/DL test, you need to either run two instances of iPerf, one in UL and one in DL as described above or to use the -d option. The below example is for bi-directional TCP test. On your core network PC, you can run

iperf -c <UE IP address> -d -i 1 -t 100

On your device, you can run

iperf -s -i 1

Following is an example of UE statistics when running simultaneous UL/DL throughput test:

3 Logging

The Amarisoft eNodeB generates a log file at /tmp/enb0.log that could be used for for further analysis and debugging. Best is to activate physical layer debug traces by adding phy.level=debug to log_options field in your eNodeB config file.

4 Troubleshooting

Below are some of the most common issues encountered during testing with recommended actions to address each issue.

Issue Cause/Correction

Can not achieve maximum data rate in DL

Issue	Cause/Correction
Can not achieve maximum data rate in DL	Check eNodeB configuration to see if you have the right cell configuration: cell bandwidth, MIMO, etc. Activate eNodeB stats by typing `t` command in eNodeB screen. You should be seeing a `CQI` of 15 and an `ri` of 2 for MIMO. If this is not the case, check your signal level. Use UDP with iPerf to rule out any TCP or web server issue.
Can not achieve maximum data rate in UL	Check eNodeB configuration to see if you have the right cell configuration: - No `pusch_max_mcs` should be defined as otherwise you will be limiting the maximum UL data rate. - Check that the number of RBs reserved for control are reduced in SIB2. Activate eNodeB stats by typing `t` command in eNodeB screen. You should be seeing a high `SNR` and a non-negative power headroom `phr`. If this is not the case, check your signal level. Use UDP with iPerf to rule out any TCP or web server issue. Check the UL signal level by typing `t spl` command in eNodeB screen. The RX MAX reported by the command should be < 0, otherwise it means that the UE is transmitting too high.

Check eNodeB configuration to see if you have the right cell configuration: cell bandwidth, MIMO, etc.
Activate eNodeB stats by typing t command in eNodeB screen. You should be seeing a CQI of 15 and an ri of 2 for MIMO. If this is not the case, check your signal level.
Use UDP with iPerf to rule out any TCP or web server issue.

Can not achieve maximum data rate in UL

Check eNodeB configuration to see if you have the right cell configuration:
- - No pusch_max_mcs should be defined as otherwise you will be limiting the maximum UL data rate.
- - Check that the number of RBs reserved for control are reduced in SIB2.
Activate eNodeB stats by typing t command in eNodeB screen. You should be seeing a high SNR and a non-negative power headroom phr. If this is not the case, check your signal level.
Use UDP with iPerf to rule out any TCP or web server issue.
Check the UL signal level by typing t spl command in eNodeB screen. The RX MAX reported by the command should be < 0, otherwise it means that the UE is transmitting too high.

5 Additional Information

This document is available without any express or implied warranty and is subject to change without notice. In no event will Amarisoft be held liable for any damages arising from the use of this document.

For any technical issue, please raise a ticket from our support site at https://support.amarisoft.com/.
To learn more about our technology and solutions, e-mail us at customer@amarisoft.com or visit https://www.amarisoft.com.

License terms

Amarisoft SAS - www.amarisoft.com
16-18 rue Rivay, 92300 LEVALLOIS PERRET, France SAS with a capital of 300,000 Euros - VAT FR21753998269 - SIREN: 753998269 (RCS Nanterre) - NAF 6201Z – DUNS 264482426

SOFTWARE LICENSE TERMS
NOTICE: THE AMARISOFT SOFTWARE PRODUCT, TOGETHER WITH ITS ACCOMPANYING DOCUMENTATION,
(THE "PRODUCT") IS THE PROPERTY OF AMARISOFT. THE PRODUCT IS MADE AVAILABLE TO YOU, THE
PURCHASER, SUBJECT TO THE FOLLOWING LICENSE AGREEMENT ("LICENSE AGREEMENT"). PLEASE READ
THIS LICENSE CAREFULLY BEFORE INSTALLING OR USING THE PRODUCT. A COPY OF THIS LICENSE IS
AVAILABLE FOR YOUR FUTURE REFERENCE IN THE "LICENSE.TXT" FILE PROVIDED WITH THE PRODUCT.
IF YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND
CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW,
THEN YOU MAY NOT USE THE PRODUCT. ANY USE BY YOU OF THIS PRODUCT OR INSTALLATION OF THE
PRODUCT ALSO CONSTITUTES YOUR ACCEPTANCE OF THESE TERMS.
AMARISOFT is only willing to grant you a license under this License Agreement if you obtained the Product
from AMARISOFT or an AMARISOFT authorized distributor or reseller, a list of which is available on
AMARISOFT website. If you obtained the Product from any other source you may not install or use the
Product.

1. GRANT OF LICENSE AND SCOPE OF USE
For each license that you acquire to use the Product, you will be provided with a License Certificate (a "License
Certificate"), which may be either a certificate, the installation and licensing instructions, your invoice, or an
activation file and which may be provided to you either with the Product media or separately by AMARISOFT
or its authorized distributors or resellers. The License Certificate will contain information specific to the
Product, the type of license under which you may use the Product and the number of licenses that you have
acquired. In order to activate and use the Product as set forth in this License Agreement, you must follow the
instructions when prompted by the Product.
The type of license you may acquire is a Standard License or a Floating License, all defined in Sections 1.1 and
Section 1.2 of this License Agreement. Unless your License Certificate identifies your acquisition of another
license type, you have acquired a Standard License. For more information on which license types, if any, is
included with the Product media, you should contact AMARISOFT or your AMARISOFT authorized distributor or
reseller.
Unless otherwise agreed, one (1) AMARISOFT license provides the right to use only one instance of the Product
software at a time.
Subject to the other terms and conditions of this License, you may make a reasonable number of copies of the
Product to backup devices such as hard disks, optical media, or tape and one (1) physical CD media backup
copy of the Product solely to replace the original copy provided to you if the original copy is damaged or
destroyed. All rights not specifically granted to you herein are retained by AMARISOFT.

1.1 Standard License
The terms of this Section 1.1 are applicable to you only if you have purchased a Standard License, as defined
below, for the Product directly from AMARISOFT or an AMARISOFT authorized distributor or reseller.
Subject to the terms and conditions of this License, AMARISOFT grants you, if you are an individual or if you
are an entity, a personal, non-exclusive, non-transferable and limited license to use the Product solely with
one (1) designated single hardware in your organization (a "Standard License"). This hardware is either a
Personal Computer that you hold in your organization or that AMARISOFT has supplied you. This hardware can
also be a USB device supplied by AMARISOFT.
You may purchase from AMARISOFT or an AMARISOFT authorized distributor or reseller additional licenses to
permit multiple hardware to use the Product. This right shall be agreed in writing. The Standard License shall
provide you with the right to access and use the Product, only for the number of hardware for which you have
paid the applicable license fees and obtained a License Key Certificate. The Product may be used exclusively by
the specifically designated hardware, subject to all the terms and conditions of this License Agreement. You
agree that you will not designate more hardware than the number of Standard Licenses that AMARISOFT or an
AMARISOFT authorized distributor or reseller has expressly granted you and you will not allow the Product to
be used by any hardware other than the hardware designated by you.

1.2 Floating License
The terms of this Section 1.2 are applicable to you only if you have purchased a Floating License, as defined
below, for the Product directly from AMARISOFT or an AMARISOFT authorized distributor or reseller.
Subject to the terms and conditions of this License, AMARISOFT grants you, if you are an individual or if you
are an entity, a personal, non-exclusive, non-transferable and limited license to use the Product from our
floating license server in your organization ("FLS"). Our floating license server will allow you to run the license
on a virtual machine and thus use it on any hardware in your organization (an "FLS License").
You may purchase from AMARISOFT or an AMARISOFT authorized distributor or reseller additional licenses
and place them on our license server to permit multiple hardware to use the Product.

2. SPECIAL TERMS
The following terms and conditions ("Special Terms") are specific to certain editions, versions and components
of the Product and are in addition to the provisions of Section 1. If any provision of the Special Terms
applicable to the Product conflicts with any other provision of this License, then the provision of the Special
Terms will supersede and control.

2.1 Additional license terms applicable to third party software
Certain components of the Product use or incorporate third-party software programs and/or libraries ("Third-
Party Software"), which are loaded or integrated (in both object and source code form) on the Product. You
agree that AMARISOFT's third-party licensors and suppliers are intended third party beneficiaries of all terms
and conditions of this License intended to protect intellectual property rights in the Product (including the
Third-Party Software) and limit certain uses thereof.

3. LIMITATIONS
You may not:
(a) modify, adapt, alter, translate or create derivative works of the Product or merge the Product with other
software other than as described in the Product's accompanying documentation or as approved of in writing
by AMARISOFT;
(b) lease, rent or loan the Product to any third party;
(c) sublicense, distribute or otherwise transfer the Product or any component thereof to any third party except
as expressly authorized in this Agreement;
(d) reverse engineer, decompile, disassemble or otherwise attempt to derive the source code of the Product;
(e) remove, alter or obscure any confidentiality or proprietary notices (including copyright and trademark
notices) of AMARISOFT or its licensors or suppliers on or accompanying the Product;
(f) allow third parties to access or use the Product including but not limited to using the Product in a time-
sharing arrangement, operating the Product as part of a service bureau or, except as expressly authorized
under Sections 1 and 2 otherwise using the Product for the use or benefit of third parties;
(g) reproduce or use the Product except as expressly authorized under Sections 1 and 2;
(h) use the Product with any other hardware than the hardware designated in your organization; or
(i) disclose or publish performance benchmark results for the Product. The rights granted under this License
apply only to this Product.
You must procure a separate license to use other AMARISOFT software. Furthermore, you may not permit end
users of the Product ("End Users") to conduct the restricted activities limited by items (a) through (e), (g) and
(i) above insofar as they apply to certain files, libraries and/or source code specifically designated as
"redistributables" by AMARISOFT in the accompanying printed or on-line documentation and that are
necessary to use your own application programs and other works created using the Product
("Redistributables"), and such End User's sublicense rights to the Redistributables are conditioned upon
compliance with such limitations. The limitations in this Section 3 apply equally to your use of the Product, in
whole or in part, including any component or Redistributable.

4. LIMITED WARRANTY AND DISCLAIMER
AMARISOFT warrants you, the initial purchaser and no other party, that any physical media included with the
Product, as and when provided to you, will be free of physical defects in materials and workmanship for a
period of thirty (30) days after the date that you initially acquire the Product.
Your exclusive remedy and AMARISOFT's sole liability for breach of this warranty is that AMARISOFT will
replace any defective media returned to AMARISOFT within the thirty (30) day warranty period. This warranty
does not apply to damages resulting from misuse, abuse or neglect. Any replacement media will be warranted
as above for the remainder of the original warranty period or twenty (20) days from the date we ship it to you,
whichever is longer.
EXCEPT FOR THIS EXPRESS LIMITED WARRANTY, THE PRODUCT IS PROVIDED "AS IS" AND WITHOUT
WARRANTY OF ANY KIND. AMARISOFT HEREBY EXCLUDES AND DISCLAIMS ALL IMPLIED OR STATUTORY
WARRANTIES, INCLUDING ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE,
QUALITY, NONINFRINGEMENT, TITLE, RESULTS, EFFORTS OR QUIET ENJOYMENT. THERE IS NO WARRANTY
THAT THE PRODUCT WILL BE ERROR-FREE OR WILL FUNCTION WITHOUT INTERRUPTION. YOU ASSUME THE
ENTIRE RISK FOR THE RESULTS OBTAINED USING THE PRODUCT. TO THE EXTENT THAT AMARISOFT MAY NOT
DISCLAIM ANY WARRANTY AS A MATTER OF APPLICABLE LAW, THE SCOPE AND DURATION OF SUCH
WARRANTY WILL BE THE MINIMUM PERMITTED UNDER SUCH LAW.

5. SERVICES, UPDATES AND PRODUCT CHANGES
AMARISOFT is not required under this License Agreement to provide any installation, maintenance service,
training or other services to you, except those expressly provided herein. Such services, if available, must be
purchased separately.
If, pursuant to a separate support agreement or otherwise, AMARISOFT provides you with a new release, error
correction, update, upgrade or other modification to the Product, such modification will be deemed part of the
Product, and subject to the terms of this License Agreement, unless the modification is expressly provided
subject to a separate License Agreement.
AMARISOFT reserves the right at any time not to release or to discontinue release of any Product and to alter
prices, features, specifications, capabilities, functions, licensing terms, release dates, general availability or
other characteristics of any future releases of the Product.

5.1 Support extension
Unless otherwise indicated, AMARISOFT License includes a one-year email support period and update.
You can subscribe to an additional one-year support and update period, at the latest within the four months
following the expiry date of the initial purchase. You can then renew subscription to this extension every year,
with the same four-month deadline. The extended support and update period starts on the day after the initial
expiry date.
Once this four-month deadline is over, an extra administrative reactivation fee is invoiced in addition to the
extension cost. The extended support and update period starts when payment of the corresponding invoice is
received.

6. REGISTRATION
You must register the Product with AMARISOFT as a condition to your rights to use the Product.
For all concerned, you will be asked to provide identification information on the hardware (serial number,
internal inventory number, other) you plan to install the Product on.

7. CONFIDENTIALITY
You acknowledge that if part of the Product in source code form exists, it remains a confidential trade secret of
AMARISOFT. You agree to hold this information in confidence, not to disclose it to any person, and not to use it
for any purpose other than the use and operation of the Product as permitted under this License Agreement.

8. LIMITATION OF LIABILITY
IN NO EVENT WILL AMARISOFT BE LIABLE TO ANY PARTY FOR ANY INDIRECT, INCIDENTAL, CONSEQUENTIAL,
EXEMPLARY, SPECIAL OR PUNITIVE DAMAGES, INCLUDING ANY LOSS OF PROFIT, REVENUE, BUSINESS
OPPORTUNITY OR DATA, ARISING FROM OR RELATING TO THIS LICENSE AGREEMENT OR THE PRODUCT,
WHETHER IN CONTRACT, IN TORT, NEGLIGENCE OR OTHERWISE, EVEN IF AMARISOFT KNEW, SHOULD HAVE
KNOWN OR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. AMARISOFT'S TOTAL CUMULATIVE
LIABILITY ARISING FROM OR RELATED TO THIS LICENSE AGREEMENT OR THE PRODUCT, WHETHER IN
CONTRACT, IN TORT OR OTHERWISE, WILL NOT EXCEED THE FEES ACTUALLY PAID BY YOU UNDER THIS
LICENSE AGREEMENT. THIS SECTION 8 WILL APPLY EVEN IF AN EXCLUSIVE REMEDY HEREUNDER HAS FAILED
OF ITS ESSENTIAL PURPOSE.

9. TERM AND TERMINATION

9.1 Term
The term of this License Agreement will begin as of the date that you receive the Product and will remain in
effect unless terminated under this Section 9.

9.2 Termination for Convenience
You may terminate this License Agreement for any reason, or for no reason, by giving AMARISOFT a five-day
(5) written notice. You shall not be entitled to request repayment of any fee or payment made to AMARISOFT.

9.3 Termination for Cause
AMARISOFT may terminate this License Agreement if you breach your obligations hereunder. AMARISOFT will
affect such termination by giving you notice of termination, specifying therein the alleged breach. If your
breach is curable, you will have a grace period of thirty (30) days after such notice is served to cure the breach
described therein. If the breach is cured within the thirty (30) day grace period, then this License Agreement
will remain in effect; otherwise, this License Agreement will automatically terminate upon the conclusion of
the thirty (30) day grace period.

9.4 Effect of Termination
Upon the termination of this License Agreement for any reason the following terms shall apply:
(a) all rights granted under this License Agreement will immediately terminate and you must stop all use of the
Product and any Redistributables;
(b) you must return to AMARISOFT or destroy all copies of the Product provided to or made by you, and will,
within ten (10) days after the effective date of termination, provide AMARISOFT with written certification that
all such copies have been returned or destroyed; and
(c) all provisions of this License Agreement with the exception of the licenses granted in Sections 1 and 2, will
survive termination of this License Agreement for any reason.

10. GENERAL PROVISIONS

10.1 Audit
If you are entering into this License Agreement as an entity other than an individual (e.g., as a corporation, a
partnership, or other organization), during the term of this License and for three (3) years thereafter,
AMARISOFT or its outside auditors will have the right to conduct an audit of your records and computer
systems to verify that you have paid to AMARISOFT the correct amounts owed under this License Agreement
and determine whether the Products are being used in accordance with the terms of this License Agreement.
Any audit will be conducted during regular business hours at your facilities, with reasonable notice. You agree
to provide the audit team access to the relevant records and facilities and to provide reasonable assistance to
AMARISOFT in connection with this provision. You agree to pay the cost of the audit if any underpayments
during the period covered by the audit amount to more than five percent (5%) of the fees actually owed or if
the number of deployments of the Products is more than five percent (5%) of that licensed.

10.2 Hazardous Uses
The Product is not intended for use in connection with any application requiring fail-safe performance such as
the operation of nuclear power facilities, air traffic control or navigation systems, weapons control systems,
life support systems, or any other system whose failure could lead to injury, death, environmental damage or
mass destruction. You agree that AMARISOFT will have no liability of any nature, and you are solely
responsible, for any expense, loss, injury or damage incurred as a result of such use of the Product.

10.3 Entire License and Severability
This License Agreement constitutes the entire, final and exclusive agreement between you and AMARISOFT
regarding the specific license transaction described herein. If any provision of this License Agreement is held to
be illegal, invalid or unenforceable for any reason, then such provision will be enforced to the maximum extent
permissible and the remainder of the provisions of this License Agreement will remain in full force and effect.

10.4 Assignment
You may not transfer the Product, assign this License Agreement or assign any of your rights or delegate any of
your obligations under this License Agreement, by operation of law or otherwise (including by merger, sale of
assets or consolidation), without AMARISOFT's prior written consent. Any attempted assignment in violation
of this Section 10.4 will be void.

10.5 Export Control
You may not directly or indirectly transfer the Product, including its documentation, to any country if such
transfer would be prohibited by applicable law. You agree to the foregoing and you are representing and
warranting that you are not located in, under the control of, or a national or resident of any such country. You
will be solely responsible for identifying and complying with all laws of any jurisdiction regarding the import,
export or use of Products and technical data supplied by AMARISOFT. You will obtain at your own expense all
licenses, permits or approvals required by any government to use the Product.

10.6 Waiver and Modifications
All waivers must be in writing. Any waiver or failure to enforce a provision of this License Agreement on one
occasion shall not be deemed a waiver of any other provision or such provision on any other occasion. This
License Agreement may only be amended by a written document signed by both parties.

11. CRYPTOGRAPHY
The Product and the content provided by AMARISOFT may contain encryption software. The country in which
you are currently may have restrictions on the import, possession, and use, and/or re-export to another
country, of encryption software. BEFORE using any encryption software, please check the country's laws,
regulations and policies concerning the import, possession, or use, and re-export of encryption software, to
see if this is permitted.

12. NON-RECURRING ENGINEERING
The intellectual property of all items designed, developed and manufactured by AMARISOFT resides and
remains with AMARISOFT. The payment of Non-Recurring Engineering (NRE) charges by you does not confer
any rights to the intellectual property of any designs which emanate directly or indirectly from the
development. As part of any contract, whether it includes the payment of NRE or not, you must accept
without reservation that AMARISOFT is the rightful owner of all intellectual property rights for the Product
and/or other products which are supplied under this Licence Agreement or standard supplies to you. You must
not copy, or allow any third party to copy the designs of any AMARISOFT's products.

Testing Data Throughput version 2026-04-02*This document is based on the latest test release.Features may not be present in your current installed software. You may check their availability in your release documentation.If you require an up to date release, ask for it in a ticket.

Table of Contents