Intra and Inter eNB handover
version 2025-05-07*
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
2 Handover Intra eNB
3 Handover inter eNB
4 Handover using UE simulator
- 4.1 Hardware prerequisite
- 4.2 UE configuration file
5 Handover call flow
- 5.1 X2 Handover triggered by UE measurement
- 5.2 S1 Handover triggered by UE measurement
6 5G SA Handover
- 6.1 Intra gNB Handover
- 6.2 Inter gNB Handover
  - 6.2.1 XnAP Handover
  - 6.2.2 Handover procedures
7 Troubleshooting

1 Introduction

This application notes aims to provide the procedure for running intra and Inter eNB/gNB handover scenarios on Amarisoft products using commercial UE.

In the case where handover tests are run with Amarisoft UE simulator (instead of commercial UE), please See handover using UE simulator for UE prerequisites and parameters.

2 Handover Intra eNB

2.1 LTE Network architecture

Setup is composed of :

One MME and one eNB running on same PC and connected through S1 interface
One or Two SDR cards

2.2 Constraints

In order to test Inter Frequency/Band handover between two cells running on same eNB, one or two SDR cards are required depending on the spectrum used by both cells.

PCIe SDR cards have a bandwidth of 56Mhz (USRP N2x0 is 40Mhz). By consequence, if both cells can fit in this bandwidth, handover can be carried out with one SDR only. Otherwise, two SDR cards are required.

In the example above, there is no overlap between the two cells neither in Uplink nor in downlink. If a higher bandwidth had been used (20Mhz as instance), both cells would have overlapped, resulting in interference.

Others constraints:

The difference of the center frequencies of each cell must be a multiple of 300 kHz (hence the difference of their EARFCN must be a multiple of 3).
The difference between the center frequency of each cell and the average of center frequencies must be a multiple of 15 kHz.
The number of cells that could be configured in a frequency band depends on the total bandwidth of the lte band and the configured bandwidth of each cell + the offsets.
The cells must have the same prach-ConfigIndex (SIB2), i.e. their PRACH must have the same duration and transmitted in the same subframes.
Multiple cells can be set at the same frequency provided their physical cell identity (n_id_cell property) and PRACH rootSequenceIndex (SIB2) are different to minimize the inter-cell interference. In the current version, there is no resource reservation among the cells, so a performance degradation happens if they transmit at the same time in the same resource blocks. So it is currently better to use cells at different frequencies.

Let’s take the following example to configure 3 cells in band 7:

cell 1 DL frequency: 2627 MHz
cell 2 DL frequency: 2642 MHz
cell 3 DL frequency: 2657 MHz 
average_dl_freq = (2627+2642+2657)/3 = 2642 MHz
cell1_freq_offset = 2627-2642 = -15 MHz
cell2_freq_offset = 2642-2642 = 0 MHz
cell3_freq_offset = 2657-2642 = 15 MHz

We can observe that the difference between the center frequency of each cell and the average of center frequencies is indeed a multiple of 15 kHz and the difference between the DL EARFCNs are a multiple of 3.

2.3 MME configuration

For running intra eNB Handover, no specific configuration is required on MME side. Default configuration files can be used without customization

2.4 eNB configuration with both cells running on same SDR card

As described in previous section, it’s possible to configure two or more cells on the same SDR card as long as it fulfills the spectrum constraints. See constraints for more details.

2.4.1 Neighbor cell info

In enb.cfg file, for each cell, set neighbour cell info using ncell_list parameters:

/* high 24 bits of SIB1.cellIdentifier */
  enb_id: 0x1A2E0,

cell_list: [
  {
    dl_earfcn: 3350,  /* DL center frequency: 2680 MHz (Band 7) */

    n_id_cell: 1,
    cell_id: 0x01,
    tac: 0x0001,
    root_sequence_index: 204, /* PRACH root sequence index */

    /* Neighbour cell list (used for handover) */
    ncell_list: [
      { n_id_cell: 2, dl_earfcn: 3299, cell_id: 0x1a2e002, tac: 1 },
    ],
  },
  {
    dl_earfcn: 3299, /* DL center frequency: 2674.9 MHz (Band 7) */

    n_id_cell: 2,
    cell_id: 0x02,
    tac: 0x0001,
    root_sequence_index: 86, /* PRACH root sequence index */

    /* Neighbour cell list (used for handover) */
    ncell_list: [
      { n_id_cell: 1, dl_earfcn: 3350, cell_id: 0x1a2e001, tac: 1 },
    ],
  },
  ], /* cell_list */

where:

n_id_cell is n_id_cell of neighbour cell
dl_earfcn is the downlink earfcn of neighbour cell
cell_id is the EUTRAN cell identifier (concatenation of the enb_id and cell_id of neighbour cell)

Please refer to lteenb.pdf for more details about cell list parameters

2.4.2 Measurement configuration

In order to trigger measurement reports (a1,a2 and a3) at UE side when cells level will fluctuate, set meas_config_desc parameters in enb.cfg file (under cell_default object) :
Example:

    /* measurement configuration */
    meas_config_desc: {
        a1_report_type: "rsrp",
        a1_rsrp: -70,
        a1_hysteresis: 0,
        a1_time_to_trigger: 640,
        a2_report_type: "rsrp",
        a2_rsrp: -80,
        a2_hysteresis: 0,
        a2_time_to_trigger: 640,
        eutra_handover: {
          a3_report_type: "rsrp",
          a3_offset: 6,
          hysteresis: 0,
          time_to_trigger: 480
        }
    },

    /* measurement gap configuration */
    meas_gap_config: "gp0",

    /* if true, initiate a handover when a suitable measurement report
       is received */
    ho_from_meas: true,

Please refer to lteenb.pdf for more details about meas_config_desc parameters

2.5 eNB configuration with cells running on two SDR card

For Inter frequency/band handover two SDR cards may be required if spectrum used by both cells is larger than SDR bandwidth (56Mhz for PCIe SDR card) .
In that case, cell configuration is slightly different and rf_port used by each cell must be defined.

Others parameters (Neighbor cell info and Measurement configuration) remain identical.

Example:

 cell_list: [
  {
    rf_port: 0, /* means that cell 0x01 will use dev0=/dev/sdr0 */
    dl_earfcn: 3350,  /* DL center frequency: 2680 MHz (Band 7) */
    n_id_cell: 1,
    cell_id: 0x01,
    tac: 0x0001,
    root_sequence_index: 204, /* PRACH root sequence index */
    /* Neighbour cell list (used for handover) */
    ncell_list: [
      { n_id_cell: 2, dl_earfcn: 3299, cell_id: 0x1a2e002, tac: 1 },
    ],
  },
  {
    rf_port: 1,  /* means that cell 0x02 will use dev1=/dev/sdr1 */
    dl_earfcn: 3299, /* DL center frequency: 2674.9 MHz (Band 7) */
    n_id_cell: 2,
    cell_id: 0x02,
    tac: 0x0001,
    root_sequence_index: 86, /* PRACH root sequence index */

    /* Neighbour cell list (used for handover) */
    ncell_list: [
      { n_id_cell: 1, dl_earfcn: 3350, cell_id: 0x1a2e001, tac: 1 },
    ],

In config/rf_driver, both SDR cards must be defined as well. See trx_sdr.pdf for more details.

rf_driver: {
    name: "sdr",

    /* list of devices. 'dev0' is always the master. */
    args: "dev0=/dev/sdr0,dev1=/dev/sdr1",

Note: When two SDR cards are used on same eNB, SDR1 must be connected to SDR0 through USB cable provided by Amarisoft in order to synchronize the Radio frames. See installguide.pdf for more details.

2.6 Handover triggered by UE measurement report

In order to carry out handover based on UE measurement report, once enb is configured, the only thing to do is to decrease step by step cell gain at eNB side (command cell_gain cell_id gain on eNB screen) . Example : cell_gain 1 -20

Note: To perform handover and not a reselection, it’s recommended to run uplink or downlink transfer using iperf as instance in order to keep UE in RRC connected state

2.7 Blind handover triggered by eNB

In order to carry out blind handover, eNB command can be used. To do this:

Start downlink or Uplink transfer (with iperf as instance) in order to keep UE in RRC connected state
On eNB screen, enter ue command to identify UE id at eNB level (eNB_UE_ID)
Enter handover command with the following parameters : eNB_UE_ID pci dl_earfcn type

Where :

eNB_UE_ID is UE ID at eNB level
pci is physical Cell ID of target cell (neighbor cell).
dl_earfcn is downlink earfcn of target cell (neighbor cell).
type is handover type. Use intra here.

Example of handover command : handover 14 2 3299 intra

3 Handover inter eNB

3.1 Prerequisites

In order to test handover between two different eNB, some prerequisites must be fulfilled:

Each eNB must be running on a different PC (host). It’s not possible to run 2 eNB components on same Hardware.
By consequence two eNB licenses are required to run inter eNB handover scenario. Only one MME license is needed.
Radio frames must be synchronized between eNB1 and eNB2.
The most convenient way is to use GPS antenna on both eNB. Any active GPS antenna accepting a 3.3V DC supply can be used,
Each eNB is configured with one cell (using one SDR card). UE can attach on each cell independently

Note: MME component can be run on same PC as eNB. This will be the setup described in this document

3.2 LTE Network architecture

Setup is composed of :

One MME and one eNB (named eNB1) running on the same PC (IP address 192.168.30.1)
A second eNB (eNB2) running on a different PC (IP address 192.168.30.2)

MME and both eNB connected through S1 interface
eNB1 and eNB2 connected through X2 interface

3.3 MME configuration

In order to connect both eNB to same MME, default (loopback) GTP address must be changed and replaced with IP address of PC where MME component is running.

in mme.cfg file, change :

  gtp_addr: "127.0.1.100",

with

  gtp_addr: "192.168.30.1",

Note: If another MME component is running on PC where eNB2 is running, this one must be turned off.

3.4 eNB1 configuration

This section aims to describe the modifications required on eNB to carry out inter eNB handover.
The initial setting of eNB (cell, earfcn , gain, SDR configuration, etc.. ) are not covered in this document.
Please refer to lteots.pdf document for more details on basic configurations.

3.4.1 MME address

In enb.cfg file, replace default (loopback) MME address with IP address of PC1 (192.168.30.1).

mme_list: [ 
    { 
      /* address of MME for S1AP connection. Must be modified if the MME
         runs on a different host. */
      mme_addr: "192.168.30.1",
    },
  ],

3.4.2 GTP address

As for MME, default GTP address must be changed and replaced with IP address of the PC1 (instead of using loopback IP address).

However, as IP address of PC1 is already used by MME, it’s not possible to reuse it.
The solution is to create an IP alias (192.168.30.3 as instance) and use this alias as gtp_addr for eNB1.

To create the alias:

Run ifconfig command
Check ethernet interface name (example "eth2:" )
Enter command ifconfig eth2:1 192.168.30.3/24
Check alias has been created with ifconfig command

Note: This hint is not needed if MME is running on its own PC and don’t have, as consequence, the same IP address as eNB1.

Once the IP alias has been created , update enb.cfg file and replace default gtp_addr with this value

/* GTP bind address (=address of the ethernet interface connected to
     the MME). Must be modified if the MME runs on a different host. */
  gtp_addr: "192.168.30.3",

3.4.3 X2 address

In order to connect both eNB through X2 interface, X2 peer IP address (eNB2) must be set . In enb.cfg file , add the following parameter :

  x2_peers:["192.168.30.2"],

3.4.4 eNB ID

Each eNB must have a unique ID. The default value is:

enb_id: 0x1A2D0

3.4.5 Neighbor cell info

In enb.cfg file, set neighbour cell (eNB2 cell) info using ncell_list parameters:

cell_list: [
  {
    dl_earfcn: 3350,  /* DL center frequency: 2680 MHz (Band 7) */

    n_id_cell: 1,
    cell_id: 0x01,
    tac: 0x0001,
    root_sequence_index: 204, /* PRACH root sequence index */

    /* Neighbour cell list (used for handover) */
    ncell_list: [
      { n_id_cell: 2, dl_earfcn: 6300, cell_id: 0x1A2D102, tac: 1 },
    ],
  },

where:

n_id_cell is n_id_cell of eNB2 cell
dl_earfcn is the downlink earfcn of eNB2 cell
cell_id is the EUTRAN cell identifier (concatenation of the enb_id and cell_id of eNB2 cell)

3.4.6 Measurement configuration

In order to trigger measurement reports (a1,a2 and a3) at UE side when cells level will fluctuate, set meas_config_desc parameters in enb.cfg file (under cell_default object) : Example:

    /* measurement configuration */
    meas_config_desc: {
        a1_report_type: "rsrp",
        a1_rsrp: -70,
        a1_hysteresis: 0,
        a1_time_to_trigger: 640,
        a2_report_type: "rsrp",
        a2_rsrp: -80,
        a2_hysteresis: 0,
        a2_time_to_trigger: 640,
        eutra_handover: {
          a3_report_type: "rsrp",
          a3_offset: 6,
          hysteresis: 0,
          time_to_trigger: 480
        }
    },

    /* measurement gap configuration */
    meas_gap_config: "gp0",

    /* if true, initiate a handover when a suitable measurement report
       is received */
    ho_from_meas: true,

Please refer to lteenb.pdf for more details about meas_config_desc parameters

3.4.7 SDR clock setting

As described in hardware prerequisite section, both eNB must be synchronized using a GPS clock antenna.
If PCIe SDR cards are used on your setup, the synchronization source must be changed.

In /root/enb/config/rf_driver folder, open config file used by enb.cfg file and uncomment sync parameter.

 /* synchronization source: internal, gps, external (default = internal) */
     sync: "gps",

Whith this modification, PCIe SDR card will get its clock from the GPS antenna.

3.5 eNB2 configuration

3.5.1 MME address

As for eNB1 , in enb.cfg file, replace default (loopback) MME address with IP address of PC where MME component is running (192.168.30.1).

mme_list: [ 
    { 
      /* address of MME for S1AP connection. Must be modified if the MME
         runs on a different host. */
      mme_addr: "192.168.30.1",
    },
  ],

3.5.2 eNB ID

As both eNB are connected to same MME component, their ID must be different.
In enb.cfg file change enb_id to be different of eNB1

/* high 24 bits of SIB1.cellIdentifier */
  enb_id: 0x1A2D1,

3.5.3 GTP address

As for eNB1 , GTP address must be changed.
However, as there is no MME component on this PC (eNB2 only), the IP constraint encountered with eNB1 is not present and GTP address can be the one of PC2

/* GTP bind address (=address of the ethernet interface connected to
     the MME). Must be modified if the MME runs on a different host. */
  gtp_addr: "192.168.30.2",

3.5.4 X2 address

As for eNB1, X2 peer IP address (eNB1) must be set.
In enb.cfg file, add the following parameter:

  x2_peers:["192.168.30.1"],

3.5.5 Neighbor cell info

As for eNB1, in enb.cfg file, set neighbour cell (eNB1 cell) info using ncell_list parameters:

cell_list: [
  {
    dl_earfcn: 6300,  /* DL center frequency: 2680 MHz (Band 7) */

    n_id_cell: 2,
    cell_id: 0x01,
    tac: 0x0001,
    root_sequence_index: 204, /* PRACH root sequence index */

    /* Neighbour cell list (used for handover) */
    ncell_list: [
      { n_id_cell: 1, dl_earfcn: 3350, cell_id: 0x1A2D001, tac: 1 },
    ],
  },

where:

n_id_cell is n_id_cell of eNB1 cell
dl_earfcn is the downlink earfcn of eNB1 cell
cell_id is the EUTRAN cell identifier (concatenation of the enb_id and cell_id of eNB1 cell),

3.5.6 Measurement configuration

As for eNB1 , in enb.cfg file, under cell_default object, set meas_config_desc parameters: Example :

    /* measurement configuration */
    meas_config_desc: {
        a1_report_type: "rsrp",
        a1_rsrp: -70,
        a1_hysteresis: 0,
        a1_time_to_trigger: 640,
        a2_report_type: "rsrp",
        a2_rsrp: -80,
        a2_hysteresis: 0,
        a2_time_to_trigger: 640,
        eutra_handover: {
          a3_report_type: "rsrp",
          a3_offset: 6,
          hysteresis: 0,
          time_to_trigger: 480
        }
    },

    /* measurement gap configuration */
    meas_gap_config: "gp0",

    /* if true, initiate a handover when a suitable measurement report
       is received */
    ho_from_meas: true,

Please refer to lteenb.pdf for more details about meas_config_desc parameters

3.6 GPS antenna connection

3.6.1 Connection

Place your GPS antenna in a place where GPS signal is likely to be found (outdoor).
Connect each GPS antenna to SMA connector GPS of PCIe SDR card on eNB1 and eNB2.

3.6.2 GPS test

Once connection is done, you can check if GPS clock is locked. To do this :

Stop LTE service on your PC (service lte stop)
Go under /root/trx_sdr folder
Enter the command ./sdr_util -c 0 gps_state

If GPS clock is locked, date and time will be displayed :

    GPS locked
    TAI: 2018-11-20 16:18:29
    UTC: 2018-11-20 16:17:52

Note: The GPS takes a few minutes to lock if the GPS antenna is connected.

3.7 S1 and X2 connection check

Once eNB1,eNB2 and MME have be configured, you can start each component and check the connections.

On MME screen, enter enb command. Both eNB should be listed
On both eNB screen, enter s1 command. S1 connection state should be "setup_done"
On both eNB screen, enter x2 command. X2 Peer connection state should be "setup_done"
If X2 peer connection state is "disconnected", just enter x2connect command and check again with x2 command afterwards.

Your setup is now completed ! You can connect your UE and run handover test .

3.8 S1/X2 Handover triggered by UE measurement report

In order to carry out Handover based on UE measurement report, the only thing to is to decrease step by step cell gain at eNB side (command cell_gain cell_id gain on eNB screen) . Example : cell_gain 1 -20

To trigger a S1 handover rather than X2, just remove the x2_peers connection in eNB configuration files

Note: To perform Handover and not a reselection, it’s recommended to run uplink or downlink transfer with iperf as instance in order to keep UE in RRC connected state

3.9 Blind S1/X2 Handover triggered by eNB

In order to carry out blind X2 or S1 handover, eNB command can be used. To do this:

Start downlink or Uplink transfer (with iperf as instance) in order to keep UE in RRC connected state
On eNB screen, enter ue command to identify UE id at eNB level (eNB_UE_ID)
Enter handover command with the following parameters : eNB_UE_ID pci dl_earfcn type

Where :

eNB_UE_ID is UE ID at eNB level
pci is physical Cell ID of target cell (eNB2).
dl_earfcn is downlink earfcn of target cell (eNB2).
type is handover type. Can be intra, s1 or x2.

Example of X2 handover command : handover 14 2 3350 x2

4 Handover using UE simulator

4.1 Hardware prerequisite

When Amarisoft UE simulator is used for testing handover, two SDR cards are required. SDR1 card will be connected to cell 1, SDR2 card will be connected to cell 2.

4.2 UE configuration file

In ue.cfg file, both cells must be declared
Example :

cells: [
    {
      dl_earfcn: 6300,
      n_antenna_dl: 2,
      n_antenna_ul: 1,
    },
    {
      dl_earfcn: 3350,
      n_antenna_dl: 2,
      n_antenna_ul: 1,
    },
  ],

On top of that, SDR mapping must be defined :
Example :

rf_driver: {
    name: "sdr",
    args: "dev0=/dev/sdr0,dev1=/dev/sdr1",
    },

The mapping between Cells and SDR cards is made automatically and follows the same order as the declaration in the configuration file.

The example here above results in:

SDR card#0 listening on earfcn 6300
SDR card#1 listening on earfcn 3350

The RF connection must be done accordingly.

For 5G SA handover similar concepts apply, for that please refer to the provided example configuration file ue-nr-2cc-sa.cfg.

Note: When two cells are declared on UE side, both cells must be active otherwise UE will remain in SIB detection state indefinitely

5 Handover call flow

5.1 X2 Handover triggered by UE measurement

RRC Connection Reconfiguration:

Sent by eNB to UE to configure measurement report events
Three event reports a1, a2, a3 are configured in RRC Connection Reconfiguration
Two event reports a2, a3 are activated

Example of a1 report configuration within RRC Connection Reconfiguration message:

reportConfigToAddModList {
          {
            reportConfigId 1,
            reportConfig reportConfigEUTRA: {
              triggerType event: {
                eventId eventA1: {
                  a1-Threshold threshold-RSRP: 90
                },
                hysteresis 0,
                timeToTrigger ms640
              },
              triggerQuantity rsrp,
              reportQuantity both,
              maxReportCells 1,
              reportInterval ms120,
              reportAmount r1
            }

Measurement Report A2:

Sent by UE to eNB when the serving cell becomes worse than a threshold

 message c1: measurementReport: {
    criticalExtensions c1: measurementReport-r8: {
      measResults {
        measId 2,
        measResultPCell {
          rsrpResult 79,
          rsrqResult 34
        }
      }

RRC Connection Reconfiguration:

Upon reception of a2 meas report, network reconfigures UE event report (deactivate a2, activate a1 and activate Measurement Gap) through RRC Connection Reconfiguration message
Note: Measurement Gap have an impact on throughput as no transmission and reception happens during gap periods

Measurement Report A3:

Sent by UE to eNB when a neighbouring cell becomes better than the serving cell by an offset
Upon reception of a3 meas report, network trigger the Handover through X2 interface

message c1: measurementReport: {
    criticalExtensions c1: measurementReport-r8: {
      measResults {
        measId 3,
        measResultPCell {
          rsrpResult 79,
          rsrqResult 34
        },
        measResultNeighCells measResultListEUTRA: {
          {
            physCellId 2,
            measResult {
              rsrpResult 90,
              rsrqResult 34
            }

Handover request:

Sent by eNB1 to eNB2 to set up the inter eNB handover through X2AP interface (X2AP trace level must be set to "debug" to see this message)
Handover request acknowledge:
Sent by eNB2 to eNB1 to acknowledge eNB handover
RRC Connection Reconfiguration:

Once eNB2 acknowledges the X2 handover request, eNB1 triggers a handover at UE side by sending the RRCconnectionReconfiguration.
This message provides mobility information as described below as well as target cell information for UE to establisgh a RRC connection request on target cell.
```
mobilityControlInfo {
        targetPhysCellId 2,
        carrierFreq {
          dl-CarrierFreq 3350
        },
```
RRC Connection Reconfiguration Complete:

Once UE has moved from eNB1 to eNB2 , it sends the RCC Connection Reconfiguration Complete on the target cell (eNB2)
To see this message, a log must be captured on eNB2 this time

Traffic should be now resumed on target cell.

5.2 S1 Handover triggered by UE measurement

S1 inter eNB handover has the same call flow as X2 handover when it comes to the messages exchanged between UE and eNB (See X2 handover call flow for more details).

The main difference is on the Handover procedure at eNB side. Handover request is sent to MME through S1 interface and not to peer eNB through X2 interface.

Handover required:

Upon reception of Measurement Report A3, eNB1 triggers a Handover by sending a Handover required to MME. The source eNodeB indicates which bearers are subject to data forwarding.
Handover Request:

MME sends Handover Request message to the target eNodeB. This message creates the UE context in the target eNodeB, including information about the bearers, and the security context
Handover Request Acknowledge:

Target eNodeB responds back to the MME with a Handover Request Acknowledge message. This message carries the Handover Command message (RRC Connection Reconfiguration Request) in a transparent container
Handover Command:

MME sends a Handover Command message to the source eNodeB.
RRC Connection Reconfiguration:

Upon reception of the Handover command, source eNB sends the RRC Connection Reconfiguration message to the UE. The message contains a new C-RNTI and new DRB IDs. Upon reception of this message the UE will remove any EPS bearers for which it did not receive the corresponding EPS radio bearers in the target cell.
RRC Connection Reconfiguration Complete:

UE uses the preamble assigned in the handover command to send a RACH to the target eNodeB. The target eNodeB accepts the request and responds back with a timing adjustment and an uplink resource. UE uses the assigned resources to transmit the RRC Connection Reconfiguration Complete (Handover Confirm message)
Handover Notify:

Target eNodeB sends a Handover Notify message to MME. Handover is successful

6 5G SA Handover

6.1 Intra gNB Handover

The gNodeB can run several NR cells. The cells can be configured individually and share the same NG interfaces with the Core Network.

Cells can be configured on one (intra-band) or several (intra/inter band) SDR cards. Refer to lteenb.pdf, section 7.6.1, for limitations related to intra-band cells configured on the same SDR card.

An example of multi cell configuration for SA handover is given in config/gnb-sa-ho.cfg.

For each cell, a list of neighbor cells can be provided as in the example below:

ncell_list: 
[
  {
    rat: "nr", 
    cell_id: 0x02,
  } 
],

where cell_id is the cell_id of the neighbor cell.

The handover can be manually initiated with the handover monitor command, the handover remote API, or automatically initiated based on UE measurements.

In case of handover based on UE measurement reports, a measurement object can be configured as in the example below:

/* measurement configuration */
    meas_config_desc: {
      a1_report_type: "rsrp",
      a1_rsrp: -60,
      a1_hysteresis: 10,
      a1_time_to_trigger: 100,
      a2_report_type: "rsrp",
      a2_rsrp: -70,
      a2_hysteresis: 0,
      a2_time_to_trigger: 100,
      nr_handover: {
        a3_report_type: "rsrp",
        a3_offset: 6,
        hysteresis: 0,
        time_to_trigger: 100
      }
    },
    meas_gap_config: {
      pattern_id: 0
    },

For handover procedure triggered by UE measurement report refer to Handover triggered by UE measurement report.

To perform blind intra gNB handover triggered by gNB, the handover command or remote API can be used, refer to lteenb.pdf for more details.

6.2 Inter gNB Handover

The same prerequisites as per inter-eNB Prerequisites apply.

In case of inter gNB Handover (XnAP or NGAP), each gNB runs on a different host and they are both connected to the same AMF. AMF can run on one of the gNB machine or on a third one. The gtp_address defined in each gNB configuration has to be set to the address of the ethernet interface connected to the AMF.

/* GTP bind address (=address of the ethernet interface connected to
     the AMF). Must be modified if the AMF runs on a different host. */
  gtp_addr: "192.168.30.1",

As both gNBs are connected to same AMF component, their ID must be different. Use a unique gnb_id on each configuration file.

gnb_id: 0x12345,

Each gNB configuration must define the serving cell and a list of fully described neighbor cells, as in the example below:

nr_cell_list: [
{
  rf_port: 0,
  cell_id: 0x01,
  n_id_cell: 500,
    
  band: 78,
  dl_nr_arfcn: 621300,

  ncell_list: [ 
  {
    ssb_nr_arfcn: 525850,
    dl_nr_arfcn: 526000,
    ul_nr_arfcn: 502000,
    n_id_cell: 501,
    gnb_id_bits: 28,
    nr_cell_id: 0x1234502,
    tac: 1,
    band: 7,
    ssb_subcarrier_spacing: 15,
    ssb_period: 5,
    ssb_offset: 0,
    ssb_duration: 1
        
   }],
}

6.2.1 XnAP Handover

To perform XnAP handover, a Xn connection between the gNBs is needed, for that xn_peers parameter has to be set to the ip address of the other gNB (refer to lteenb.pdf).

  xn_peers:["192.168.30.2"],

6.2.2 Handover procedures

The handover can be manually initiated with the handover monitor command, the handover remote API, or automatically initiated based on UE measurements.

In case of handover based on UE measurements, the same measurement configuration as for intra gNB handover can be used on both gNB.

/* measurement configuration */
    meas_config_desc: {
      a1_report_type: "rsrp",
      a1_rsrp: -60,
      a1_hysteresis: 10,
      a1_time_to_trigger: 100,
      a2_report_type: "rsrp",
      a2_rsrp: -70,
      a2_hysteresis: 0,
      a2_time_to_trigger: 100,
      nr_handover: {
        a3_report_type: "rsrp",
        a3_offset: 6,
        hysteresis: 0,
        time_to_trigger: 100
      }
    },
    meas_gap_config: {
      pattern_id: 0
    },

To trigger an handover based on UE measurement report refer to Handover triggered by UE measurement report.

For details about handover monitor and remote API command refer to lteenb.pdf.

7 Troubleshooting

7.1 Preconditions

Before to start handover testing, you must check first that UE can connect on each eNB/gNB independently and run Uplink/Downlink transfer.
If UE can’t attach, check that:

For 4G, eNB and MME are connected using s1 command on eNB screen. S1 connection state should be "setup_done"
For 5G, gNB and 5GS are connected using xn command on eNB screen. Xn connection state should be "setup_done"
(For inter eNB/gNB handover) Check GPS clock is locked using ./sdr_util gps_state command under /root/trx_sdr folder (LTE service must be turned off previously) . If GPS clock is locked, date and time will be displayed

7.2 Measurement reports not triggered

If measurement reports are not sent by UE, check that :

Measurement configuration parameters have been set in enb.cfg file
Thresholds set in Measurement configuration are not too low and that UE doesn’t lose the RRC connection before sending the events. a1_rsrp: -70 and a2_rsrp: -80 can be used as instance.
UE is in connected mode during the test and not it idle when cell conditions fulfill handover conditions.

7.3 Handover is triggered but UE fails to move on target cell

If after handover, UE is not seen on target cells check that

Radio frame are synchronized on both cells thanks to GPS antenna clock
UE can attach previously on target cell.
Cell power of target cell is good enough for UE to handover (may happen when consecutive handover are triggered between two cells)

7.4 TRX discontinuity too wide

This message may happen if both cells running on two different SDR cards of same enB are not synchronized. In that case, check that USB cable is connected between OUT and IN of master and slave SDR card respectively. See installguide.pdf for more details.

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.

Intra and Inter eNB handover version 2025-05-07*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

1 Introduction

2 Handover Intra eNB

2.1 LTE Network architecture

2.2 Constraints

2.3 MME configuration

2.4 eNB configuration with both cells running on same SDR card

2.4.1 Neighbor cell info

2.4.2 Measurement configuration

2.5 eNB configuration with cells running on two SDR card

2.6 Handover triggered by UE measurement report

2.7 Blind handover triggered by eNB

3 Handover inter eNB

3.1 Prerequisites

3.2 LTE Network architecture

3.3 MME configuration

3.4 eNB1 configuration

3.4.1 MME address

3.4.2 GTP address

3.4.3 X2 address

3.4.4 eNB ID

3.4.5 Neighbor cell info

3.4.6 Measurement configuration

3.4.7 SDR clock setting

3.5 eNB2 configuration

3.5.1 MME address

3.5.2 eNB ID

3.5.3 GTP address

3.5.4 X2 address

3.5.5 Neighbor cell info

3.5.6 Measurement configuration

3.6 GPS antenna connection

3.6.1 Connection

3.6.2 GPS test

3.7 S1 and X2 connection check

3.8 S1/X2 Handover triggered by UE measurement report

3.9 Blind S1/X2 Handover triggered by eNB

4 Handover using UE simulator

4.1 Hardware prerequisite

4.2 UE configuration file

5 Handover call flow

5.1 X2 Handover triggered by UE measurement

5.2 S1 Handover triggered by UE measurement

6 5G SA Handover

6.1 Intra gNB Handover

6.2 Inter gNB Handover

6.2.1 XnAP Handover

6.2.2 Handover procedures

7 Troubleshooting

7.1 Preconditions

7.2 Measurement reports not triggered

7.3 Handover is triggered but UE fails to move on target cell

7.4 TRX discontinuity too wide

License terms

Intra and Inter eNB handover
version 2025-05-07*
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.