LTE Callbox Classic User guide version 2024-09-04*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.
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
- 1 Introduction
- 2 Hardware setup
- 2.1 Power supply
- 2.2 Sim card
- 2.3 Wireless RF connection
- 2.4 Wired RF connection
- 2.4.1 Selection and combination of SDR cards
- 2.4.2 RF connection for one cell 2x2 MIMO in FDD mode
- 2.4.3 RF connection for one cell 2x2 MIMO in TDD mode
- 2.4.4 RF connection for two cells 2x2 MIMO in FDD mode
- 2.4.5 RF connection for three cells 2x2 MIMO in FDD mode
- 2.4.6 RF connection for one cell 4x4 MIMO in FDD mode
- 2.4.7 RF Antenna gain
- 3 Connection to AMARI callbox
- 4 LTE service
- 5 eNodeB/gNodeB configuration
- 6 Core network configuration
- 7 UE configuration
- 8 Monitoring
- 9 Troubleshooting
- 10 Software Upgrade
- 11 Throughput tests
1 Introduction
AMARI Callbox Classic is a 3GPP compliant eNodeB, gNodeB EPC and 5GC allowing functional and performance testing of LTE, LTE-M and NB-IoT devices. It also includes an integrated IMS server as well as an eMBMS gateway for VoLTE and eMBMs testing.
![img/classic2](img/classic2.jpg)
The callbox Classic is a turnkey solution running on Fedora 39 operating system. It embeds three SDR cards and all software components and licenses required to emulate your LTE network.
This document describes the first steps to start and configure your Amarisoft LTE Callbox. For advanced configurations and testing, please refer to the application notes and other documents available under extranet.amarisoft.com or under the /root/<components>/doc/ folders of your callbox.
2 Hardware setup
2.1 Power supply
Plug the external power cable provided with the callbox in the AC-in
Connector located in the rear panel and press the Power on
button on the top left corner of the front panel to turn it on.
The led will light up blue once callbox is powered ON .
Power adapter specifications:
Input: 100~240 V AC, 50~60 Hz
2.2 Sim card
The callbox is delivered with a test sim card that is already provisioned in the EPC database. No additional configuration is required for authenticating devices using this SIM card.
SIM card specifications:
- IMSI: 001010123456789
- K: 00112233445566778899aabbccddeeff
- sim_algo: XOR
- Non programmable USIM card
- Support both 1.8V and 3V voltage
Note: It is possible to use other SIM cards for your testing. In that case please See Provisioning of new SIM cards for more details.
2.3 Wireless RF connection
When tests are run in wireless condition, RF connection just consists in connecting the twelve LTE antennas provided to the SMA connectors (TX1, RX1, TX2, RX2) located on the rear panel of the callbox.
![jpg](img/classic-rear.jpg)
2.4 Wired RF connection
When tests are run in wired condition, three important points have to be taken into account:
- The selection and combination of the SDR card(s) (among the three available)
- The RF cabling
- The setting of TX and RX gains to avoid saturation or Bler
Each SDR card has two RX and two TX SMA connectors plus one GPS connector.
-
Rx1
is the main receive antenna port. -
Rx2
is the diversity receive antenna port. -
Tx1
is the main transmit antenna port. -
Tx2
is the diversity transmit antenna port. -
GPS
is used for connecting an external GPS clock. See trx_sdr.pdf document for more details.
Note: When using RF combiners, unused ports of the combiners must be terminated with RF terminator or absorber especially when using frequency above 2.5Ghz. Otherwise big insertionlosses may happen and downgrade the RF performances. |
The following sections describes how to connect and configure your callbox when device is connected using RF cables.
2.4.1 Selection and combination of SDR cards
The callbox Classic is delivered with three SDR cards supporting 20Mhz MIMO 2x2 each.
For basic scenarios running one cell 2x2 MIMO only, the eNodeB will only use one SDR card (in that case, it’s not required to connect all SMA connectors to your device)
Otherwise, by combining multiple cards, it possible to run test scenarios such as Multi cells, Carrier aggregation, 4x4 mimo or interfrequency handover.
The selection of the SDR card is made in the eNodeB configuration file, per cell, using the parameter "rf_port
". See Cell and SDR mapping for more details.
Note: the default |
Examples of SDR card combination and RF cabling are provided in the following section.
2.4.2 RF connection for one cell 2x2 MIMO in FDD mode
![jpg](img/Connection-1cellFDD.jpg)
Note: For SISO test, connection between DUT antenna2 and Callbox Tx2 is not required |
2.4.3 RF connection for one cell 2x2 MIMO in TDD mode
![jpg](img/Connection-1cellTDD.jpg)
Note: in TDD mode, as both TX and RX are sent on the same channel, only TX1 and TX2 ports are needed.
However, with Amarisoft SDR card, it’s possible to force the DL signal reception on RX port and Uplink signal transmission on TX port when rx_antenna: "rx"
is set in the RF driver configuration file.
This improves the performance of the SDR card as we don’t have to switch the RF several times per radio frame.
When |
2.4.4 RF connection for two cells 2x2 MIMO in FDD mode
This RF cabling corresponds to a Carrier aggregation scenario (2CC) or 2 interfreq/interBand neigbhor cells as instance
Note: RX2 port connection is optional as Uplink MIMO is not supported in this software version |
2.4.5 RF connection for three cells 2x2 MIMO in FDD mode
This RF cabling corresponds to a Carrier aggregation scenario (3CC) or 3 interfreq/interBand neigbhor cells as instance
Note: RX2 port connection is optional as Uplink MIMO is not supported in this software version |
2.4.6 RF connection for one cell 4x4 MIMO in FDD mode
As described above, it’s possible to combine two sdr cards to setup a MIMO 4x4 cell. In that case, eNodeB will use automatically two consecutive SDR cards and only the first rf_port
must be defined.
![jpg](img/Connection-1cellFDD4x4.jpg)
Note: RX2 port connexion is optional as Uplink MIMO is not supported on this software version |
2.4.7 RF Antenna gain
In conducted mode, TX and RX gains must be adjusted according to your setup. See TX/RX gain setting for more details.
3 Connection to AMARI callbox
3.1 Locally
You can connect locally to your callbox by connecting a monitor and a keyboard to the PC.
To login as root, please use root
/ toor
as login / password.
There is also a user account with user/resu as login/password.
Note: The Amarisoft software suit is installed and executed under root account.
3.2 Remotely
The Ethernet interface of the callbox is configured with DHCP.
If you know the IP address allocated to your callbox, you can directly make a SSH
connection in Linux by typing
ssh root@<IP address>
or by using PuTTY
on Windows.
If you don’t know the IP address of the callbox, then you need to access the PC locally first (see above) and type the following command to retrieve the IP address of the PC.
ifconfig
3.3 Web GUI
The web GUI to display logs is available through web access at the following URL:
http://<IP address>/
3.3.1 Set a password
To add authentication to the web portal:
Edit /etc/httpd/conf/httpd/conf and look for <Directory "/var/www/html">
section.
Inside it, add AuthConfig
to AllowOverride directive so that it becomes AllowOverride None AuthConfig
.
Then restart HTTP daemon:
service httpd restart
Create /var/www/html/lte/.htaccess file with following content:
AuthType Basic AuthName "Amarisoft Web GUI" AuthUserFile /etc/httpd/.htpasswd Require valid-user
To add a user and its password, type the following command:
htpasswd -c /etc/httpd/.htpasswd <username>
4 LTE service
Callbox is configured to provide an automatic LTE service. At each reboot of the PC, LTE network is turned on automatically.
Note that even if the service is named "LTE" it actually serves both Radio access technologies: 4G LTE and 5G NR |
4.1 Manage LTE automatic service
4.1.1 Status
You can check the LTE service status this way:
service lte status
The command will return "active (running)
" status if service is running
4.1.2 Stop
You can stop all LTE components this way:
service lte stop
4.1.3 Start
You can start them again this way:
service lte start
4.1.4 Disable
You may also prevent them to start at boot time:
systemctl disable lte
NB: lte service remains enable until next reboot
NB2: this command is not available on Ubuntu version <= 14
4.1.5 Enable
You may enable service at boot time this way:
systemctl enable lte
NB: lte service remains disable until next reboot
NB2: this command is not available on Ubuntu version <= 14
5 eNodeB/gNodeB configuration
5.1 Selection of eNodeB/gNodeB configuration file
The default file used by the lte
automatic service for configuring the eNodeB and gNodeB is enb.cfg
(available under /root/enb/config directory).
This file aims to set eNodeB and gNodeB parameters such as frequency, cell bandwidth, number of layer and others.
Note: Both eNodeB and gNodeB are built in the same component named enb
(for legacy reason).
Please note that this file is a symbolic link to real configuration file as depicted below
![img/symb_link_config](img/symb_link_config.png)
Some examples of configuration file (for Carrier aggregation with 2CC or 3CC and multi-cell as instance) are provided in Amarisoft releases as a starting point.
To change the eNodeB configuration and select one of these files, update the enb.cfg symbolic link using the "ln -sfn <config file> enb.cfg"
command
Default cell configuration is one Cell, LTE band 7, 20MHz bandwidth, MIMO mode |
5.2 Customization of eNodeB/gNodeB parameters
Once enb.cfg
configuration file has been selected (as a starting point), you can now edit it and customize key parameters such as:
- Frequency : dl_earfcn
- Cell bandwidth : n_rb_dl
- Number of layer : n_antenna_dl
- Others..
All parameters available are described in the lteenb.pdf document.
You will also find a generic enb.default.cfg file that can be easily tuned using the #defines in the header
#define TDD 0 // Values: 0 (FDD), 1(TDD) #define N_RB_DL 25 // Values: 6 (1.4 MHz), 15 (3MHz), 25 (5MHz), 50 (10MHz), 75 (15MHz), 100 (20MHz) #define N_ANTENNA_DL 1 // Values: 1 (SISO), 2 (MIMO 2x2) #define N_ANTENNA_UL 1 // Values: 1, 2 #define CHANNEL_SIM 0 // Values: 0 (channel simulator disabled), 1 (channel simulator enabled)
For example, to configure a 20mhz MIMO TDD cell, just set the #defines this way:
#define TDD 1 #define N_RB_DL 100 #define N_ANTENNA_DL 2 #define N_ANTENNA_UL 1 #define CHANNEL_SIM 0
5.3 Cell and SDR mapping
As described in the Hardware setup section, it’s possible to declare multiple cells on different bands by using up to three SDR cards.
In the enb.cfg file, for each cell declared in the cell_list
array, rf_port
field must be set to select the SDR card(s) that will broadcast the cell signal.
Note: an rf_port
is composed of N
consecutive SDR card(s) depending of the number of downlink antenna configured for the cell.
- in SISO (
n_dl_antenna: 1
), RF port is composed ofN=1
SDR card - in 2x2 MIMO (
n_dl_antenna: 2
), RF port is composed ofN=1
SDR card - in 4x4 MIMO (
n_dl_antenna: 4
), RF port is composed ofN=2
consecutive SDR cards
This means that for an eNodeB configuration using 3 cells 2x2 MIMO, we will have :
- rf_port0 –> SDR0
- rf_port1 –> SDR1
- rf_port2 –> SDR2
However, if the first cell is 4x4 MIMO and second cell is 2x2 MIMO, we will have
- rf_port0 –> SDR0 + SDR1
- rf_port1 –> SDR2
Example of cell configuration (from enb-2cc.cfg reference file) where cell#1 (band2) and cell#2 (band4) use the SDR0 and SDR1 respectively.
/* list of cells */ cell_list: [ { rf_port: 0, /* SDR0 */ cell_id: 0x01, /* low 8 bits of SIB1.cellIdentifier */ tac: 0x0001, /* SIB1.trackingAreaCode */ n_id_cell: 1, root_sequence_index: 204, /* PRACH root sequence index */ dl_earfcn: 900, /* DL center frequency: 1960 MHz (Band 2) */ /* carrier aggregation configuration (for rel 10 UEs) */ /* list of secondary available cells */ scell_list: [ { cell_id: 0x02, cross_carrier_scheduling: false, }, ], }, { rf_port: 1, /* SDR1 */ cell_id: 0x02, /* low 8 bits of SIB1.cellIdentifier */ tac: 0x0001, /* SIB1.trackingAreaCode */ n_id_cell: 2, root_sequence_index: 28, /* PRACH root sequence index */ dl_earfcn: 2150, /* DL center frequency: 2130 MHz (Band 4) */ /* list of secondary available cells */ scell_list: [ { cell_id: 0x01, cross_carrier_scheduling: false, }, ], }, ], /* cell_list */
5.4 TX/RX gain setting
TX and RX antenna gain values must be customized in order to avoid saturation when set too high or Bler when set too low. Those two values actually depend on your setup:
- Conducted vs wireless conditions
- Physical RF attenuator(s) used
- Combiner(s)/divider(s) used
TX and RX gain values are defined in RF configuration file located under /root/enb/config/rf_driver directory.
To know which files is used by LTE service, just look at enb.cfg file.
Example:
include "rf_driver/1chan.cfg",
5.4.1 Wired test
When the device under test is connected to the callbox using RF cables, the recommended RX and TX antenna gain values are :
tx_gain: 60.0, /* TX gain (in dB) */ rx_gain: 0.0, /* RX gain (in dB) */
If physical RF attenuators (or RF combiners) are used, additional gain must be added to these default values equivalent to the path loss introduced
Note: max SDR input is -10 dBm, max SDR output is 5dBm (depending on the frequency). |
5.4.2 Wireless test
In Wireless test conditions (i.e when LTE antennas are used), the recommended RX and TX antenna gain values are :
tx_gain: 90.0, /* TX gain (in dB) */ rx_gain: 60.0, /* RX gain (in dB) */
6 Core network configuration
LTEMME is a LTE MME (Mobility Management Entity) implementation. It has a built-in SGW (Serving Gateway), PGW (Packet Data Network Gateway), PCRF (Policy and Charging Rule Function), HSS (Home Subscriber Server) and EIR (Equipment Identity Register). It is used with the Amarisoft LTE eNodeB and NR gNodeB to build a highly configurable LTE/NR test network.
LTEMME also includes a NR 5GC (5G Core Network). It has a build-in AMF (Access and Mobility Management Function), AUSF (Authentication Server Function), SMF (Session Management Function), UPF (User Plane Function).
6.1 Selection of MME configuration file
The default file used by the lte automatic service for configuring the Core network is mme.cfg
(available under /root/mme/config directory).
This file aims to set parameters such as PLMN ID, network name, PDN list, APN name and others.
Note: Both EPC and 5GC are built in the same component named mme
(for legacy reason).
Please note that this file is a symbolic link to real configuration file as depicted below
![img/symb_link_config-mme](img/symb_link_config-mme.jpg)
6.2 Customization of MME parameters
6.2.1 PLMN ID
Default PLMN ID of callbox is 001 01.
If the test sim card provided with the AMARI callbox is used, you can skip this section. No customization is required
If your test SIM card has a different HPLMN, you can change the PLMN of the box.
in /root/mme/config/mme.cfg
file, change plmn: "00101"
value and replace 00101 by your MCC/MNC code .
Note : Same modification must be done at eNodeB/gNodeB side:
|
6.2.2 Adding new SIM card to the database
If the test sim card provided with the AMARI callbox is used, you can skip this section. No customization is required.
Same if you want to connect multiple UE using the same sim card model (and same IMSI by consequence). The MME will allow each UE to attach with the same IMSI (001010123456789).UE are distinguished with their IMEI in that case.
Otherwise, if other test SIM cards with different IMSI or secret key values are used, they must be declared in the EPC database (HSS)
For that, open the /root/mme/config/ue_db-ims.cfg
and add an entry for each sim card in the ue_db
array .
Example :
{ sim algo: "milenage", imsi: "001010000000001", opc: "000102030405060708090A0B0C0D0E0F", amf: 0x9001, sqn: "000000000000", K: "00112233445566778899AABBCCDDEEFF", },
Note: Secret key parameters are mandatory as both UE and Network need to authenticate each other . |
6.2.3 Commercial SIM card
Any SIM card can be used with the AMARI callbox as long as it’s been declared in the UE database as described in the section above.
However, it is very unlikely that you get the secret key parameters from the network operator required for the authentication and the security mechanism.
In that case, you can try to disable the authentication using one of the two methods described below (note that this no more complies with 3GPP specifications,
so it requires an explicit support on the UE side also):
1) If the UE accepts the use of EIA0 (Null Integrity algorithm) in the NAS/RRC security mode control procedures outside of an emergency call without authentication, then set the following option in your MME configuration file:
authentication_mode: "skip",
2) If you know the command at UE side to skip both the authentication and security mode control procedures, then set the following options in your MME configuration file:
authentication_mode: "skip", skip_smc_proc: true,
and set the following option in your eNB configuration file (eNB configuration object, not the cell configuration object)
skip_smc_proc: true,
6.2.4 APN configuration
MME is configured by default with four APN :
- Default
- Internet
- IMS
- SOS
For connecting your device to the callbox, one of these APN must be configured at UE side. See UE configuration for more details.
Otherwise, if for any reason, the device under test must use a specific APN, the modification can be done at MME side:
- Open /root/mme/config/mme.cfg file.
- Replace the preconfigured "internet" APN name as instance with the expected APN name or create a new entry in the pdn_list array.
- Restart the system with "service lte restart" command
6.3 VoLTE call
AMARI Callbox embeds an IMS server that can be used for running basic IMS tests such as VoLTE, ViLTE or SMS over IMS.
For more information about the IMS functionality, please refer to appnote_ims.pdf document .
Also, See VoLTE setting for more details about UE configuration.
7 UE configuration
7.1 Internet setting
For connecting your device to internet, APN setting must be configured at UE side to match callbox setting.
As described in previous section, the callbox is preconfigured with four APN :
- "Default": This APN name is frequently used by the UE when no specific APN is set. However, some UEs doesn’t expose an internet connection when this generic APN is used. In that case, we recommend to create a "internet" apn as described below.
- "Internet": Second APN name preconfigured in order to route internet IP traffic.
- "IMS": APN for VoLTE call
- "SOS": APN for emergency services
AT UE side, go in setting menu to add a new APN:
Example on Samsung S5 device:
- Go to
Settings
/More networks
/Mobile networks
- Turn on Data roaming
- Go back to Mobile network.
- Add the first APN with the following parameters:
- Name = Internet
- APN = internet
- APN type = internet,default
- Save it and select it.
![img/s5-volte](img/s5-volte.png)
7.2 VoLTE setting
If handset supports VoLTE, you just need to check VoLTE Call
is ticked on your handset menu as depicted in the picture below.
However, most of the commercial devices are locked and behave differently. Some devices have a white list of authorized PLMN, some require that "UE operation mode" byte is set to "type approval operations" in USIM Elementary File Administrative Data(EFad).
To overcome this issue, a reference UE can be provided by Amarisoft . Please contact support team for more details.
![img/oneplus3_volte_menu](img/oneplus3_volte_menu.jpg)
8 Monitoring
Once all eNodeb/gNodeB and MME parameters have been configured, you can restart the lte service with service lte restart
command to reload the configuration files and connect your device(s).
To monitor your eNodeB/gNodeB/EPC or troubleshoot any issues, several tools and logs are available as described in the following sections.
8.1 Access to software monitors
Once you are logged on your callbox, you can access software components (eNB, MME, IMS or MBMSGW) using screen command:
screen -x lte
This will connect you to different component monitor.
![img/screen](img/screen.jpg)
Next sections show you basic methods. For more information please refer to screen
documentation (https://www.gnu.org/software/screen/manual/screen.html).
8.1.1 Select component
Each component monitor is inside a window. You can switch from a window to another with the command:
ctrl+a <window index>
Where window index is:
- 0 MME
- 1 eNB
- 2 MBMSGW
- 3 IMS
Note: press simultaneously |
You can also switch to next window:
ctrl+a <space>
Each component screen offers a list of commands that can be used either to get status or trigger action. Each of them are documented in the component documentations (example lteenb.pdf) or inline with the "help" command
![img/help](img/help.jpg)
8.1.2 Exit screen
ctrl+a d
8.2 Command line monitor
In eNB component, t
command provides key logging information (See the list of parameter using t help
command.
8.2.1 t command
t
command (without argument) provides key information about the Uplink and downlink transfer
(enb) t Press [return] to stop the trace ----DL----------------------- ----UL--------------------------------------------------- UE_ID CL RNTI C cqi ri mcs retx txok brate C snr puc1 nl mcs rxko rxok brate #its phr pl ta 3 001 003f 1 15 2 28.0 0 202 151M 1 15.6 11.9 1.0 20.0 0 1 8.40k 1/1.0/1 40 59 0.0 3 001 003f 1 15 2 28.0 0 4000 149M 1 15.7 12.8 1.0 20.0 0 25 10.5k 1/1.0/1 40 59 0.0 3 001 003f 1 15 2 28.0 0 4000 150M 1 14.7 13.0 1.0 20.0 0 25 10.5k 1/1.0/1 40 59 0.0 3 001 003f 1 15 2 28.0 0 4000 149M 1 16.1 11.2 1.0 20.0 0 25 10.5k 1/1.0/1 40 59 0.0 3 001 003f 1 15 2 28.0 0 4000 150M 1 15.5 11.0 1.0 20.0 0 25 10.5k 1/1.0/1 40 59 0.0
Where for downlink:
-
UE ID
is the identifier allocated by the eNodeb/gNodeB to each UE. Note: This value changes each time RRC connection is released. -
CL
is the number of aggregated DL cells -
RNTI
is the (c) RNTI of each UE -
C
is the number of carriers used by the UE -
cqi
is the last Channel Quality Indicator reported by the UE, between 0 (bad) and 15 (very good). If there are several aggregated DL cells, the minimum cqi is displayed. -
ri
is the last Rank Indicator (number of layers for MIMO). If there are several aggregated DL cells, the minimum rank indicator is displayed. -
mcs
(Modulation Coding Scheme) is the average MCS value used in downlink during the measurement interval period. More details about MCS range are available in 3GPP TS 36.213 -
retx
(retransmission) is the number of retransmission requested by the UE. This parameter gives indications about the channel quality. -
txok
is the number of transmissions successfully acknowledged by the UE. -
brate
is the average bitrate (at the MAC layer), in bits per second.
Where for uplink:
-
C
is the number of carriers used by the UE -
snr
is the measured Signal to Noise Ratio for the uplink from the PUSCH reference signals and the SRS. -
puc1
is the measured Signal to Noise Ratio for the last PUCCH1. -
nl
is the average number of layers used in uplink during the measurement interval period. -
mcs
(Modulation Coding Scheme) is the average MCS value used in uplink during the measurement interval period. More details about MCS range are available in 3GPP TS 36.213 -
rxko
is the number of received uplink transport blocks with CRC errors. -
rxok
is the number of received uplink transport blocks without CRC error. -
#its
gives the minimum, average and maximum number of iterations of the turbo or LDPC decoder. -
phr
is the content of the last Power Headroom MAC control element sent by the UE. It is expressed in dB. Negative values indicate that the UE could not transmit with the required power. -
pl
is the Uplink Path Loss in dB. It is measured from the reported PHR and the measured uplink power level. It is meaningful only if the RF interface correctly reports the absolute received power level. -
ta
is the average of the uplink timing advance measured for the UE in TA units.
8.2.2 t spl command
Once UE got attached to the cell, Uplink and Downlink signal levels have a direct impact on decoding performances. In order to reach full throughput in both ways, TX and RX antenna gain values must be set correctly (as described in section "TX/RX gain setting") in order to avoid saturation when set too high or Bler when set too low. The command ât splâ under eNB terminal helps to monitor the RX and TX signal power:
(enb) t spl Press [return] to stop the trace --P0/TX 1-- --P1/TX 2-- dBFS --P0/RX 1-- --P1/RX 2-- RMS MAX RMS MAX SAT RMS MAX RMS MAX -24.6 -7.7 -24.6 -8.3 0 -42.7 -30.4 -42.7 -30.4 -24.6 -7.7 -24.6 -8.4 0 -42.7 -30.5 -42.7 -29.7 -24.6 -7.7 -24.6 -7.9 0 -42.7 -30.2 -42.7 -29.8 -24.6 -7.7 -24.6 -8.4 0 -42.7 -30.4 -42.6 -29.7 -24.6 -7.7 -24.6 -8.4 0 -42.7 -30.8 -42.7 -30.2 -24.6 -7.7 -24.6 -8.4 0 -42.7 -30.4 -42.7 -30.5 -24.6 -7.2 -24.6 -8.3 0 -42.7 -30.7 -42.7 -30.5
TX columns provides information about transmitted signal power.
-
TX RMS
: stands for transmitted Root-Mean-Square. This is the mean value in dB FS (full Scale) will happen -
TX MAX
: stands for Maximum. Displays the maximum sample value during the measurement interval period. -
TX SAT
: stands for Saturation. Displays the number of saturation events during the measurement interval. If SAT value is different of 0, it means that the transmitted signal in Downlink is saturated. In this case, cell_gain should be decreased until SAT is equal to 0.
RX columns provides information about received signal power.
-
RX RMS
: stands for Received Root-Mean-Square. This is the mean value in dB FS (full Scale) -
RX MAX
: stands for Maximum. Displays the maximum sample value during the measurement interval period. If RX MAX value equals to 0, it means that the received signal in UL is saturated. In this case, rx_gain should be decreased until RX MAX is below 0.
In Wireless test conditions, the recommended values for PCIe SDR cards are :
tx_gain: 90.0, /* TX gain (in dB) */ rx_gain: 60.0, /* RX gain (in dB) */
In RF cables test conditions, the recommended values for PCIe SDR cards are :
tx_gain: 60.0, /* TX gain (in dB) */ rx_gain: 00.0, /* RX gain (in dB) */
Note : tx_gain and rx_gain commands can be used in eNB screen to decrease or increase the TX gain and RX gain respectively |
8.2.3 t cpu command
t cpu command provides key information about the CPU load .This is useful for verifying that PC is not running out of CPU when expected KPI are not reached.
-Proc- ---RX-------- ---TX-------- ---- TX/RX diff (ms) CPU MS/s CPU MS/s CPU min/avg/max sigma 51.8% 23.040 6.6% 23.040 1.6% 2.23/2.8/3.3 0.2 52.9% 23.040 6.6% 23.039 1.6% 1.97/2.8/3.3 0.2 52.3% 23.040 6.6% 23.041 1.5% 2.20/2.8/3.3 0.2 51.4% 23.040 6.6% 23.040 1.6% 2.20/2.8/3.3 0.2 50.8% 23.040 6.6% 23.039 1.6% 2.19/2.8/3.3 0.2
t cpu
shows CPU consumption for the main LTE task (Proc), the reception chain (RX) or transmission chain (TX). Units are MS/s (Million of sample per second)
On top of that, t cpu
command provides information on TX-RX delay: The min, average and max values are given in milliseconds.
In other words, in LTE FDD mode as instance, eNodeB receives data in Uplink and must acknowledge (or nack) them 4ms later to the UE. eNodeB has by consequence 4ms to decode the uplink samples and send the ack/nack answer in downlink. The RX/TX delay is the remaining time before data are processed and time they must be sent in downlink.
If this value decreases to zero, this means that PC is too slow and physical layer is running out of CPU to process the data within this period. The higher is the TX/RX value is , the better it is.
8.3 logging
eNodeB/gNodeB and MME generate log files under /tmp/ directory (enb0.log/gnb0.log, ims.log and mme.log) that could be used for further analysis and debugging.
The verbosity if these logs can be customized by modifying the log_options
field available in the enb.cfg and mme.cfg configuration files (See lteenb.pdf or ltemme.pdf for more details).
Note: We recommend to activate physical layer debug traces by adding phy.level=debug in your enb.cfg config file.
8.4 Real time logging
The LTE web interface allows to analyze Amarisoft LTE software logs and get real time information from the system.
For more details about the Graphical user interface please refer to ltewww.pdf document available under Extranet.
![img/gui_ltewww_def](img/gui_ltewww_def.png)
9 Troubleshooting
9.1 Amarisoft Wiki page
A wiki page is available under https://extranet.amarisoft.com/wiki. It aims to answer frequently asked questions and provide useful information regarding the configuration of the Callbox. Before raising a ticket or analysing logs, do not hesitate to have a look at this wiki page.
9.2 Amarisoft Support
If you encounter issues with your setup and can’t find the root cause in the wiki page or after investigation of the logs, you can raise a ticket through our support web portal. See https://extranet.amarisoft.com/wiki/doku.php?id=info:redmine for more details .
10 Software Upgrade
To upgrade your callbox with the latest release, please follow the procedure:
- Download your release from Amarisoft Extranet at
https://extranet.amarisoft.com/
The downloaded file would be a tarball file: amarisoft.YYYY-MM-DD.tar.gz where YYYY-MM-DD is the release date. - Put this file on the PC at any place using the method you want (scp, http, USB key...)
- Log as
root
on your PC - Extract it:
tar xzf amarisoft.YYYY-MM-DD.tar.gz
This would create a directory called YYYY-MM-DD.
- Go to the directory YYYY-MM-DD and execute the provided script install.sh as follows:
./install.sh <path> --default
- - By default if no
<path>
is specified, components are installed under/root
, you can choose other directories by specifying a new destination in<path>
. Please note thatwww
component will always be located under/var/www/html
in Fedora or/var/www
in Ubuntu. - - The
--default
option forces answer to default for all questions asked during install phase. The default answers forlteenb
are depicted below:
Take a look at messages at the end of install phase, you may be requested to power on/off your PC. This would be the case if there is, for example, an FPGA upgrade of your PCIe SDR card.
If you would like to have a custom install, you can run the script without--default
option and answer each question separately. Forlteenb
product, this would typically be the case if you do not want to enable automatic LTE service or if you would like to install eNB and MME components on different PCs. - - By default if no
10.1 Rollback a release
It is possible to rollback or swap from different software releases easily.
If you go under /root
folder and enter "ll
" command, you will see that each component (enb
, mme
, trx_sdr
, etc..
) is actually a symbolic link to a folder that correspond to a release.
After each release installation, a new folder is created and the symbolic link is updated.
11 Throughput tests
For testing data throughput and reach the maximum uplink and downlink bitrate, please refer to the appnote_throughput.pdf document