UEsim LTE Handover - LTE to LTE

The overall callbox logic and 3GPP related with UEsim Handover is same as in Commercial UE handover. The main focus on this tutorial is to highlight on UEsim side configuration for LTE to LTE handover. Since the configuration on UEsim for handover can be a little bit complicated, I would like you to have some big picture on the call box and UEsim configuration and relationship between them as illustrated below.

What I want to highlight is that you need to configure multiple cells not only in eNB side, but also in UEsim side. In commercial UE, you don't have to care about this since all of those configuration is done internally.

NOTE : For the Handover with commercial UE, check out following tutorials.

• LTE to LTE Handover IntraFrequency (Commercial UE)
• LTE to LTE Handover InterFrequency (Commercial UE)
• LTE to NR Handover (UEsim)

Table of Contents

• UEsim LTE Handover - LTE to LTE
• Introduction
• Summary of the Tutorial
• Test Setup
• Key Configuration Parameters
• Test 1 : LTE to LTE Interband/Interfrequency Handover / Triggered by eNB Power Change
• Configuration
• Perform the Test
• Log Analysis
• Test 2 : LTE to LTE Intraband/Interfrequency Handover / Triggered by eNB Power Change
• Configuration
• Perform the Test
• Log Analysis
• eNB
• UEsim
• RRC / NAS Signaling
• RrcConnectionReconfiguration - Measurement Configuration
• RrcConnectionReconfiguration - Enabling Measurement Gap
• RrcConnectionReconfiguration - Handover
• Tips
• Triggering Handover from Screen Command

Introduction

LTE (Long Term Evolution) handover is a critical mechanism within cellular networks that enables User Equipment (UE) to maintain seamless connectivity while transitioning between different cells or base stations (eNodeBs) during mobility scenarios. In commercial network deployments, handover procedures are abstracted from the end user, with all relevant configurations handled internally by the device and the network infrastructure. However, when working with UEsim (User Equipment Simulator) and callbox test environments, a deeper understanding and explicit configuration of handover parameters become essential. UEsim platforms are employed to emulate real UE behavior for network validation, protocol conformance, and performance testing. In these scenarios, test engineers must manually define cell parameters, mobility settings, and handover triggers not only on the eNB side but also within the UEsim software itself. This approach provides granular control and transparency over the handover process, enabling detailed analysis of LTE mobility management, radio resource control, and interoperability between simulated and real network components. Mastery of UEsim configuration for LTE to LTE handover is fundamental for developers, testers, and researchers aiming to validate network reliability, optimize mobility performance, and ensure compliance with 3GPP standards in controlled laboratory environments.

• Technology Context
  • LTE is a 3GPP-defined wireless broadband standard widely adopted for high-speed mobile communication.
  • Handover is a process enabling continuous service as UEs move across different network cells, crucial for user experience and service reliability.
  • UEsim platforms simulate real device behavior, allowing controlled experimentation and validation of network procedures such as handover.
  • Callboxes act as programmable network emulators, facilitating comprehensive test scenarios for various network conditions and configurations.
• Relevance and Importance
  • Understanding and configuring UEsim for LTE handover is essential for testing network interoperability, performance optimization, and protocol conformance.
  • Explicit configuration of multiple cells on both the eNB and UEsim sides enables precise control over handover scenarios, which is not possible with commercial UEs where configurations are hidden.
  • This knowledge is invaluable for engineers developing, testing, or troubleshooting LTE networks and devices.
• Learning Outcomes
  • Gain a comprehensive understanding of how LTE to LTE handover is orchestrated and managed with UEsim and callbox environments.
  • Learn how to configure multiple cells and mobility parameters on the UEsim platform to emulate realistic handover conditions.
  • Develop skills to analyze, validate, and optimize handover procedures for LTE networks using simulation tools.
  • Acquire insight into the architectural relationship between UEsim, callboxes, and network infrastructure components during mobility scenarios.
• Prerequisite Knowledge
  • Familiarity with LTE architecture, including concepts such as eNodeB, UE, and cell configuration.
  • Basic understanding of radio access network mobility management and 3GPP standards.
  • Experience with UEsim or similar test tools and callbox environments is beneficial but not mandatory.
  • General competence with network testing methodologies and protocol analysis tools is recommended for optimal learning.

Summary of the Tutorial

This tutorial describes procedures for testing LTE to LTE interband and intraband interfrequency handover using Amarisoft Callbox and UEsim. The focus is on measurement-based handover triggered by eNB (callbox) cell power changes and demonstrates both configuration and operational steps, including log analysis and tips for manual triggering.

• Test Setup
  • The test setup requires connecting at least two SDR cards on both the Callbox and UEsim sides. Appropriate antenna connections are mandatory for both sides to ensure two-cell operation.
• Key Configuration Parameters
  • Configuration involves parameters such as ncell_list (neighbor cell list), meas_config_desc (measurement configuration), meas_gap_config, ho_from_meas, cell_groups, and ue_list. Key measurement event thresholds (a1, a2, a3) and hysteresis/timers should be set according to desired handover conditions.
• Test 1: LTE to LTE Interband/Interfrequency Handover (Triggered by eNB Power Change)
  • Configuration Steps:
    • Configure the eNB with two cells, ensuring N_CELL is set to 2.
    • For each cell, set the neighbor cell in ncell_list to enable handover between the two.
    • In cell_default, set meas_config_desc to trigger handover based on specific measurement reports. Adjust inactivity_timer and RSRP thresholds as required by UEsim sensitivity.
    • UE configuration must match dl_earfcn and bandwidth with the Callbox cell settings.
  • Test Execution:
    • Verify cell configuration using the 'cell phy' and 'cell' commands.
    • Optionally, log SIB messages for a short period using 'log bcch' to verify correct system information broadcast.
    • Adjust cell powers via 'cell_gain' (not 'tx_gain') to avoid unexpected UE behavior due to SIB1 reference power changes.
    • Power on the UE and wait for initial attach completion.
    • Manually tweak cell power to cross measurement thresholds and trigger the measurement report and subsequent handover.
    • Confirm that the handover occurred by observing the change in the cell index (CL column) on the UEsim console.
  • Log Analysis:
    • Check for RRC Connection Reconfiguration messages containing correct measurement configuration for both source and target cells.
    • Verify that measurement reports for events a2 and a3 are triggered and received as expected.
    • Confirm that the handover is executed after the appropriate measurement report and that UE initiates access to the target cell.
• Test 2: LTE to LTE Intraband/Interfrequency Handover (Triggered by eNB Power Change)
  • Configuration Steps:
    • Configure eNB with two TDD cells (N_CELL set to 2), each referencing the other in ncell_list.
    • Set meas_config_desc to trigger handover when the expected measurement report is received. Adjust a2 RSRP or other measurement parameters for easier triggering based on test setup.
    • Match UE cell configuration (frequency, bandwidth, duplex mode) to the eNB's configuration.
  • Test Execution:
    • Verify correct cell configuration with 'cell phy' and 'cell' commands.
    • Optionally, briefly log SIB messages using 'log bcch' for verification.
    • Adjust cell power with 'cell_gain' to trigger measurement events.
    • Power on the UE, wait for initial attach, then adjust power to trigger measurement report and handover.
    • Confirm the handover by monitoring the CL column on UEsim console.
  • Log Analysis:
    • On eNB: Check that measurement configuration, gap support, and inter-frequency measurement are present; verify handover triggering based on measurement reports.
    • On UEsim: Enable detailed "Cell meas" logging to monitor measurement values, filtered measurements, and entry conditions for measurement events, facilitating troubleshooting for handover issues.
• Tips
  • You can force handover from the screen command line using the "handover" command, regardless of measurement conditions or cell power. Always check the current RAN UE ID before issuing the command to ensure the correct UE is targeted.

Note: For both tests, it is critical to align cell and UE configuration, validate neighbor cell lists, and adjust measurement thresholds to accommodate the UEsim’s radio characteristics. The procedures rely on dynamically controlling cell power to trigger measurement events, which in turn initiate the handover process as per standard LTE methodologies.

Test Setup

Test setup for this tutorial is as shown below.  (NOTE : The image is a little bit misleading. You need to connect antenna at least on two sdr cards on both Callbox and UEsim).

Key Configuration Parameters

Followings are important configuration parameters for this tutorial. You may click on the items for the descriptions from Amarisoft documents.

• ncell_list : In this link, you would get the descriptions for all the items listed below
• rat
• cell_id
• meas_config_desc : In this link, you would get the descriptions for all the items listed below
• a1_report_type
• a1_rsrp
• a1_hysteresis
• a1_time_to_trigger
• a2_report_type
• a2_hysteresis
• a2_time_to_trigger
• a3_report_type
• a3_offset
• a3_hysteresis
• a3_time_to_trigger
• meas_gap_config
• ho_from_meas
• cell_groups
• cells
• ue_list

Test 1 : LTE to LTE Interband/Interfrequency Handover / Triggered by eNB Power Change

This test is to show how to test LTE to LTE handover triggered by cell power change from callbox (eNB).

Configuration

I used the enb-2cell-ho-b7-b3.cfg on gNB which is copied and modified from enb-2cell-ho.cfg

I used the ue-ho-LL.cfg on gNB which is copied and modified from ue-2cc.cfg

In enb-2cell-ho-b7-b3.cfg , the configuration is done as follows. Since this is a scenario that requires 2 cells, you need to set N_CELL to 2.

This is the configuration of the first cell. It is important to note that you need to specify the second cell (n_id_cell : 2) into ncell_list(Neighbour cell list) configuration.

This is the configuration of the second cell. It is important to note that you need to specify the first cell cell (n_id_cell : 1) into ncell_list(Neighbour cell list) configuration.

In cell_default configuration, I set meas_config_desc to trigger the handover only when the expected measurement report is recieved. I also increased the value for inactivity_timer just to give user enough time to tweak cell power to trigger appropriate measurement report.

NOTE :  UEsim Rx dynamic range may not be as good as commercial UE. The radio link may get brocken if the cell power gets as low as the cell boundrary in the field. So I increased rsrp threshold for me measurement to trigger measurement report before cell power gets too low.

In ue-ho-LL.cfg, the configuration is done as follows. Since this is a scenario that requires 2 cells, you need to set N_CELL to 2.

This is the cell configuration of the first cell. It does not require any specific configuration. You only neet to set dl_earfcn and bandwidth to match the configuration of the first cell on Callbox.

This is the configuration of the first ue. It does not require any specific configuration. You only neet to set dl_earfcn and bandwidth to match the configuration of the second cell on Callbox.

Perform the Test

Check if the cell is configured as intended.  You can check these out with 'cell phy' and 'cell' command.

This is not mandatory, but I would recommend to log SIB messages for a short time and stop so that you can confirm all the sibs for each cells. But I would not recommend you to capture the SIB log all the time since it may make it difficult to analyze other RRC / NAS messages. So I would just collect SIB log just a few seconds at the beginning and stop logging. You can do it with 'log bcch' command.

Then adjust the cell power of each cell with 'cell_gain'. The exact cell power you need to set would vary depending on your test setup. I would suggest you to use cell_gain instead of tx_gain in this case because if you change the cell power with tx_gain, the reference power broadcast in SIB1 changes and UE may behave differently from what you expect.

You can confirm on the result of cell power changes done by cell_gain from the result of 'cell' command. You can confirm on it under dl_gain column.

Power on UE on UE sim. In this test, I wanted to make it sure that only one UE attempt to camp on. So I did 'power_on 1'.

Wait until the initial attach is complete.

Then tweak the cell power to trigger measurement report and handover. You cannot check if the result of the measurement report in 't' output (trace log), but if the measurement report comes in as expect and handover is properly done, you would see that cell ID under 'CL' column change to the destination cell.

You can confirm handover on UEsim console (screen window) as well. Once the handover is complete, you see that the cell index under 'CL' column switches to the target cell.

Log Analysis

Sample Log

Since this test is for Handover based on measurement report, check if eNB transmits RRC Connection Reconfiguration with measurement configuration and see if the contents of the messages are all set as intended.

First check measObjectToAddModList and see the frequency of both the source and target cells are configured.

Here you see that event a2 and a3 are configured.

Now check out measIDToAddModList and see if the measurement conditions are configured as intended. Here you see a2 measurement is registered as measId 2 and a3 measurement is registered as measId3.

Now you see that UE send measurement report for a2 event indicating that Serving becomes worse than threshold.

With the reception of a2 event, eNB enables measurement gap that is need to perform the measurement for interRAT target cell.

Now UE send measurement report for event 3 indicating that Neighbour becomes offset better than serving.

On reception of the measurement for the target cell(event a3), eNB send RRC Connection Reconfiguration for handover.

With the reception of RRC Connection Reconfiguration for handover, UE triggers RACH to the destination cell for handover.

Test 2 : LTE to LTE Intraband/Interfrequency Handover / Triggered by eNB Power Change

This test is to show how to test LTE to LTE handover triggered by cell power change from callbox (eNB). The main purpose of this tutorial is to introduce the measurement logging capability of Amarisoft UEsim (UE simulator) which is great helpful not only for troubleshooting but also for understanding the detailed process of measurement report before Handover.

Configuration

I used the enb-2cell-ho-b48-inter.cfg on gNB which is copied and modified from enb-2cell-ho.cfg

For the core network, I haven't changed anything and used the default configuration (mme-ims.cfg) as it is.

I used the ue-2cell-ho-b48-inter.cfg on gNB which is copied and modified from ue-2cc.cfg

In enb-2cell-ho-b48-inter.cfg, the configuration is done as follows. Since this is a scenario that requires 2 cells, you need to set N_CELL to 2. In this tutorial, I used two TDD cells (TDD  1), but you can configure it in anyway you like.

This is the configuration of the first cell. It is important to note that you need to specify the second cell (n_id_cell : 2) into ncell_list(Neighbour cell list) configuration.

This is the configuration of the second cell. It is important to note that you need to specify the first cell cell (n_id_cell : 1) into ncell_list(Neighbour cell list) configuration.

In cell_default configuration, I set meas_config_desc to trigger the handover only when the expected measurement report is recieved. Just to make it easy to configure cell power for the measurement report, I increased a2_rsrp but you can tweak the rsrp criteria in any way that suits your test setup.

NOTE :  UEsim Rx dynamic range may not be as good as commercial UE. The radio link may get brocken if the cell power gets as low as the cell boundrary in the field. So I increased rsrp threshold for me measurement to trigger measurement report before cell power gets too low.

In ue-2cell-ho-b48-inter.cfg , the configuration is done as follows. Since this is a scenario that requires 2 cells, you need to set N_CELL to 2 and I configured the cells to TDD (TDD 1) to match it to eNB configuration.

This is the cell configuration of the two cells. It does not require any specific configuration. You only neet to set dl_earfcn and bandwidth to match the configuration of the first cell on Callbox.

This is the configuration of the first ue. It does not require any specific configuration. You only neet to set dl_earfcn and bandwidth to match the configuration of the second cell on Callbox.

Perform the Test

Check if the cell is configured as intended.  You can check these out with 'cell phy' and 'cell' command.

This is not mandatory, but I would recommend to log SIB messages for a short time and stop so that you can confirm all the sibs for each cells. But I would not recommend you to capture the SIB log all the time since it may make it difficult to analyze other RRC / NAS messages. So I would just collect SIB log just a few seconds at the beginning and stop logging. You can do it with 'log bcch' command.

Then adjust the cell power of each cell with 'cell_gain'. The exact cell power you need to set would vary depending on your test setup. I would suggest you to use cell_gain instead of tx_gain in this case because if you change the cell power with tx_gain, the reference power broadcast in SIB1 changes and UE may behave differently from what you expect.

You can confirm on the result of cell power changes done by cell_gain from the result of 'cell' command. You can confirm on it under dl_gain column.

Power on UE on UE sim. In this test, I wanted to make it sure that only one UE attempt to camp on. So I did 'power_on 1'.

Wait until the initial attach is complete.

Then tweak the cell power to trigger measurement report and handover.

You cannot check if the result of the measurement report in 't' output (trace log), but if the measurement report comes in as expect and handover is properly done, you would see that cell ID under 'CL' column change to the destination cell.

You can confirm handover on UEsim console (screen window) as well. Once the handover is complete, you see that the cell index under 'CL' column switches to the target cell.

Log Analysis

Here I put both eNB log and UEsim log. For overall procedure of handover, I will describe based on eNB log. But I would suggest the readers to look into UEsim log and see what is exactly going on within the UE especially during the measurement process.

eNB

Sample Log

Since this test is for Handover based on measurement report, check if eNB transmits RRC Connection Reconfiguration with measurement configuration and see if the contents of the messages are all set as intended.

For handover test, it is always good practice to confirm that UE support the necessary feature which is required for the handover.

Ensure that measurement gap and inter-frequency meansurement report are supported.

First check measObjectToAddModList and see the frequency of both the source and target cells are configured.

The measurement object for the first and second cell are configured. The measObjectId 1 is for the first cell and the measObjectId 2 is for the second cell

Here you see that event a1,a2 and a3 are configured. The reportConfigID 1 is for Event A1, the reportConfigID 2 is for Event A2 and the reportConfigID 3 is for Event A3.

Now check out measIDToAddModList and see if the measurement conditions are configured as intended. Here you see a2 measurement is registered as measId 2 and a3 measurement is registered as measId3.

Now you see that UE send measurement report for a2 event indicating that Serving becomes worse than threshold.

With the reception of a2 event, eNB enables measurement gap that is need to perform the measurement for interRAT target cell.

Now UE send measurement report for event 3 indicating that Neighbour becomes offset better than serving.

On reception of the measurement for the target cell(event a3), eNB send RRC Connection Reconfiguration for handover.

With the reception of RRC Connection Reconfiguration for handover, UE triggers RACH to the destination cell for handover.

UEsim

The final decision to trigger the handover is supposed to be made by eNB, but the information required for the decision making is supposed to be collected and provided by UE.  For troubleshooting for handover failure (especially due to no measurement report from UE), it is important to get access to the detailed logging capability on UE side. Amarisoft UEsim provides great logging capability for the process.

Sample Log

In order to collect the log for this process on UEsim, enable "Cell meas" flags in logging configuration setup as shown below.

Amarisoft UEsim prints various information related to RRC measurement : Measurement Result, Measurement ID entering condition etc as shown below.

NOTE : You see two different measurement for RSRP and RSRQ. The first one is the last measurement and the second one is RRC Filtered Measurement based on 3GPP (Layer 3 filtering). For example, you see -84.8/-80.0 for RSRP in (A). -84.8 is the last measurement before the log print and -80.0 is filtered value.

RRC / NAS Signaling

Here I will just list required message from callbox and I haven't put the required messages from UE side. For the messages from UE, refer to the log analysis and check further with the sample log linked above.

This is the RrcReconfiguration sent by gNB  to configure measurement and handover. (NOTE : You would see some IEs that has a specific assigned vale here, but consider it as just an example value. Those values should vary depending on test requirement)

RrcConnectionReconfiguration - Measurement Configuration

{

  message c1: rrcConnectionReconfiguration: {

    rrc-TransactionIdentifier 0,

    criticalExtensions c1: rrcConnectionReconfiguration-r8: {

      measConfig {

        measObjectToAddModList {

          {

            measObjectId 1,

            measObject measObjectEUTRA: {

              carrierFreq 3100,

              allowedMeasBandwidth mbw100,

              presenceAntennaPort1 TRUE,

              neighCellConfig '01'B

            }

          },

          {

            measObjectId 2,

            measObject measObjectEUTRA: {

              carrierFreq 1575,

              allowedMeasBandwidth mbw100,

              presenceAntennaPort1 TRUE,

              neighCellConfig '01'B

            }

          }

        },

        reportConfigToAddModList {

          {

            reportConfigId 1,

            reportConfig reportConfigEUTRA: {

              triggerType event: {

                eventId eventA1: {

                  a1-Threshold threshold-RSRP: 80

                },

                hysteresis 0,

                timeToTrigger ms640

              },

              triggerQuantity rsrp,

              reportQuantity both,

              maxReportCells 1,

              reportInterval ms120,

              reportAmount r1

            }

          },

          {

            reportConfigId 2,

            reportConfig reportConfigEUTRA: {

              triggerType event: {

                eventId eventA2: {

                  a2-Threshold threshold-RSRP: 80

                },

                hysteresis 0,

                timeToTrigger ms640

              },

              triggerQuantity rsrp,

              reportQuantity both,

              maxReportCells 1,

              reportInterval ms120,

              reportAmount r1

            }

          },

          {

            reportConfigId 3,

            reportConfig reportConfigEUTRA: {

              triggerType event: {

                eventId eventA3: {

                  a3-Offset 6,

                  reportOnLeave FALSE

                },

                hysteresis 0,

                timeToTrigger ms480

              },

              triggerQuantity rsrp,

              reportQuantity both,

              maxReportCells 8,

              reportInterval ms120,

              reportAmount r1

            }

          }

        },

        measIdToAddModList {

          {

            measId 2,

            measObjectId 1,

            reportConfigId 2

          },

          {

            measId 3,

            measObjectId 2,

            reportConfigId 3

          }

        },

        quantityConfig {

          quantityConfigEUTRA {

          }

        },

        measGapConfig release: NULL

      },

      dedicatedInfoNASList {

        '2776859E94010742013E060000F110000100445....'H

      },

      radioResourceConfigDedicated {

        srb-ToAddModList {

          {

            srb-Identity 2,

            rlc-Config explicitValue: am: {

              ul-AM-RLC {

                t-PollRetransmit ms60,

                pollPDU pInfinity,

                pollByte kBinfinity,

                maxRetxThreshold t32

              },

              dl-AM-RLC {

                t-Reordering ms45,

                t-StatusProhibit ms0

              }

            },

            logicalChannelConfig defaultValue: NULL

          }

        },

        drb-ToAddModList {

          {

            eps-BearerIdentity 5,

            drb-Identity 1,

            pdcp-Config {

              discardTimer infinity,

              rlc-AM {

                statusReportRequired TRUE

              },

              headerCompression notUsed: NULL

            },

            rlc-Config am: {

              ul-AM-RLC {

                t-PollRetransmit ms80,

                pollPDU p64,

                pollByte kB125,

                maxRetxThreshold t32

              },

              dl-AM-RLC {

                t-Reordering ms35,

                t-StatusProhibit ms10

              }

            },

            logicalChannelIdentity 3,

            logicalChannelConfig {

              ul-SpecificParameters {

                priority 15,

                prioritisedBitRate kBps8,

                bucketSizeDuration ms100,

                logicalChannelGroup 3

              }

            }

          }

        },

        physicalConfigDedicated {

          antennaInfo-r10 explicitValue-r10: {

            transmissionMode-r10 tm3,

            codebookSubsetRestriction-r10 '11'B,

            ue-TransmitAntennaSelection release: NULL

          },

          cqi-ReportConfig-r10 {

            nomPDSCH-RS-EPRE-Offset 0,

            cqi-ReportPeriodic-r10 setup: {

              cqi-PUCCH-ResourceIndex-r10 0,

              cqi-pmi-ConfigIndex 44,

              cqi-FormatIndicatorPeriodic-r10 widebandCQI-r10: {

              },

              ri-ConfigIndex 483,

              simultaneousAckNackAndCQI TRUE

            }

          },

          cqi-ReportConfigPCell-v1250 {

            altCQI-Table-r12 allSubframes

          }

        }

      }

    }

  }

}

 

 

RrcConnectionReconfiguration - Enabling Measurement Gap

{

  message c1: rrcConnectionReconfiguration: {

    rrc-TransactionIdentifier 0,

    criticalExtensions c1: rrcConnectionReconfiguration-r8: {

      measConfig {

        measIdToRemoveList {

          2

        },

        measIdToAddModList {

          {

            measId 1,

            measObjectId 1,

            reportConfigId 1

          }

        },

        measGapConfig setup: {

          gapOffset gp0: 0

        }

      }

    }

  }

}

 

 

RrcConnectionReconfiguration - Handover

{

  message c1: rrcConnectionReconfiguration: {

    rrc-TransactionIdentifier 0,

    criticalExtensions c1: rrcConnectionReconfiguration-r8: {

      ......

      mobilityControlInfo {

        targetPhysCellId 2,

        carrierFreq {

          dl-CarrierFreq 1575

        },

        t304 ms1000,

        newUE-Identity '003E'H,

        radioResourceConfigCommon {

          prach-Config {

            rootSequenceIndex 28

          },

          pdsch-ConfigCommon {

            referenceSignalPower -31,

            p-b 1

          },

          pusch-ConfigCommon {

            pusch-ConfigBasic {

              n-SB 1,

              hoppingMode interSubFrame,

              pusch-HoppingOffset 8,

              enable64QAM TRUE

            },

            ul-ReferenceSignalsPUSCH {

              groupHoppingEnabled FALSE,

              groupAssignmentPUSCH 0,

              sequenceHoppingEnabled FALSE,

              cyclicShift 0

            }

          },

          p-Max 10,

          ul-CyclicPrefixLength len1,

          pusch-ConfigCommon-v1270 {

            enable64QAM-v1270 true

          }

        },

        sameSFN-Indication-r14 true

      },

      radioResourceConfigDedicated {

        mac-MainConfig explicitValue: {

          ul-SCH-Config {

            maxHARQ-Tx n5,

            periodicBSR-Timer sf20,

            retxBSR-Timer sf320,

            ttiBundling FALSE

          },

          drx-Config release: NULL,

          timeAlignmentTimerDedicated infinity,

          phr-Config setup: {

            periodicPHR-Timer sf500,

            prohibitPHR-Timer sf200,

            dl-PathlossChange dB3

          }

        },

        physicalConfigDedicated {

          pdsch-ConfigDedicated {

            p-a dB-3

          },

          pucch-ConfigDedicated {

            ackNackRepetition release: NULL

          },

          pusch-ConfigDedicated {

            betaOffset-ACK-Index 9,

            betaOffset-RI-Index 6,

            betaOffset-CQI-Index 6

          },

          uplinkPowerControlDedicated {

            p0-UE-PUSCH 0,

            deltaMCS-Enabled en0,

            accumulationEnabled TRUE,

            p0-UE-PUCCH 0,

            pSRS-Offset 3

          },

          soundingRS-UL-ConfigDedicated setup: {

            srs-Bandwidth bw3,

            srs-HoppingBandwidth hbw0,

            freqDomainPosition 0,

            duration TRUE,

            srs-ConfigIndex 47,

            transmissionComb 0,

            cyclicShift cs4

          },

          schedulingRequestConfig setup: {

            sr-PUCCH-ResourceIndex 0,

            sr-ConfigIndex 15,

            dsr-TransMax n64

          },

          antennaInfo-r10 explicitValue-r10: {

            transmissionMode-r10 tm3,

            codebookSubsetRestriction-r10 '11'B,

            ue-TransmitAntennaSelection release: NULL

          },

          cqi-ReportConfig-r10 {

            nomPDSCH-RS-EPRE-Offset 0,

            cqi-ReportPeriodic-r10 setup: {

              cqi-PUCCH-ResourceIndex-r10 0,

              cqi-pmi-ConfigIndex 44,

              cqi-FormatIndicatorPeriodic-r10 widebandCQI-r10: {

              },

              ri-ConfigIndex 483,

              simultaneousAckNackAndCQI TRUE

            }

          },

          cqi-ReportConfigPCell-v1250 {

            altCQI-Table-r12 allSubframes

          }

        }

      },

      securityConfigHO {

        handoverType intraLTE: {

          keyChangeIndicator FALSE,

          nextHopChainingCount 0

        }

      },

      nonCriticalExtension {

        nonCriticalExtension {

          otherConfig-r9 {

            powerPrefIndicationConfig-r11 release: NULL

          }

        }

      }

    }

  }

}

 

 

Tips

 

Triggering Handover from Screen Command

 

You can trigger the handover regardless of measurement configuration / report or cell power. You can force eNB to triggger handover by screen command "handover" as shown below.

 

 

 

 

 

NOTE :  I would suggest you to double check on UE ID for the current connection. If there was not any issues, it is likely for the UE to be the RAN_UE_ID of 1 but it may have been changed if the call dropped and reconnected before you try out this command. If you run the command 'ue', it will return the current RAN UE ID.