> For the complete documentation index, see [llms.txt](https://docs.gxc.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gxc.io/docs/application-notes/4g-handovers.md).

# 4G Handovers

## Introduction

Handovers are a core capability in mobile networks, enabling uninterrupted service continuity as active User Equipment (UE) move between cells. For mission-critical applications, such as autonomous systems, industrial automation, and enterprise communications, seamless handovers are essential to prevent service disruptions and maintain safety and operational standards.

GXC's Onyx solution delivers high-reliability, ultra-low latency handovers with seamless mobility management, ensuring optimal Quality of Experience (QoE) across enterprise, private, and mission-critical networks where connection loss can impact operations or safety. GXC's 4G architecture supports both intra-Access Point (AP) and inter-AP handovers using an optimized “make-before-break” approach. This design reduces interference between cells, improves spectral efficiency, minimizes signaling overhead, and enables precise mobility control. As a result, critical applications can operate without interruption, even in complex RF environments with overlapping coverage areas.

Neighbor cell relationships are configured in the Onyx Portal, providing operators with complete control over handover topology. The system automatically generates an initial all-to-all neighbor configuration that can be customized with prioritized neighbor lists for each cell. This approach ensures predictable, reliable handover behavior tailored to your specific network topology and operational requirements.

### Supported Handover Types

The 4G Onyx solution supports multiple handover mechanisms designed to ensure seamless mobility and service continuity as UE move across cells.

{% columns %}
{% column valign="middle" %}

#### Intra-AP Handovers

An intra-AP handover occurs when a UE moves between cells managed by the same AP. These handovers are internal to the AP, allowing for faster execution, reduced signaling delays, and minimal service impact. Intra-AP handovers are optimized for high-density environments where multiple cells per AP provide overlapping coverage.
{% endcolumn %}

{% column valign="middle" %}

<figure><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2Fxgc38RykJX60E89CYFNd%2Fimage.png?alt=media&amp;token=afa5a630-1f9a-426a-bd4c-d9221cc566d7" alt="" width="281"><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column valign="middle" %}

#### Inter-AP Handovers

An inter-AP handover occurs when a UE moves between cells managed by different APs. This process, requiring precise neighbor cell configuration and robust measurement reporting, involves coordination between APs via the Onyx Edge over the S1 interface. Inter-AP handovers ensure service continuity across wider coverage areas, supporting uninterrupted mobility as UE move between different coverage zones.
{% endcolumn %}

{% column valign="middle" %}

<figure><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FXZ9zxPWxSem9UcbbOOjM%2Fimage.png?alt=media&amp;token=f68c1d29-fca4-4490-9068-2cebbd54cec8" alt="" width="281"><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

GXC employs a "make-before-break" handover strategy that enhances spectral efficiency by establishing the new connection before terminating the existing one. This approach reduces interference and signaling overhead while providing more predictable network behavior. The method is particularly valuable in private and industrial networks, where efficient radio resource management and consistent performance are essential for service continuity.

### Neighbor Relation Tables

GXC APs maintain two types of neighbor relation tables:

* **Neighbor Frequency Table** – Contains the list of frequencies that UE should measure to detect neighboring cells. This table is automatically populated by the Onyx Edge based on Spectrum Access System (SAS) grants received by associated APs and cannot be edited manually.
* **Neighbor Cell Table** – Contains detailed information about neighboring APs and cells, including cell IDs, PCI, signal strengths, signal quality metrics, and other parameters necessary for handover decisions. This table is populated based on the neighbor relationships manually configured in the Onyx Portal.

### Special Configuration Cases

Dual-Carrier and Carrier Aggregation APs require specific neighbor table considerations when configuring handovers.

* **Dual-Carrier (DC) APs** – In DC APs, each cell maintains its own "Neighbor Frequency Table" and "Neighbor Cell Table". One cell's frequency is listed as a neighbor for the other cell within the same AP, enabling seamless intra-AP handovers. Neighbor relationships and advanced handover parameters must be configured for each cell independently.
* **Carrier Aggregation (CA) APs** – In CA APs, only the primary frequency is advertised to other APs. For example, if AP 1 uses frequency A as primary and B as secondary, and AP 2 uses X and Y respectively, then frequency X is included as a neighbor for AP 1, and frequency A as a neighbor for AP 2.

### Neighbor Relationship Configuration Modes

The Onyx Portal offers two modes for configuring neighbor relationships. Choose the mode that best fits your network topology and operational requirements.

* **Automatic Neighbor Configuration (Default)** – In this mode, the system automatically manages neighbor relationships.
  * All cells associated with the same Onyx Edge are configured as neighbors to each other
  * The system automatically assigns priority order
  * No manual neighbor selection required
  * Ideal for networks where all cells need connectivity to all other cells
  * Simplifies deployment and reduces configuration overhead
  * Use this mode when:
    * Your network has 16 or fewer cells per Onyx Edge. The AP “Neighbor Frequency Table” has a limit of eight unique frequencies. If the AP has more than eight neighbors with different frequencies, priority determines which frequencies are included.
    * You want to minimize manual configuration
* **Manual Neighbor Configuration (Explicit Neighbors)** – In this mode, you have full control over neighbor relationships.
  * Manually select which specific cells should be neighbors for each cell
  * Define priority order by arranging neighbors in your preferred sequence (Priority 1 = highest)
  * Add or remove neighbor relationships as needed
  * Control handover topology precisely
  * Use this mode when:
    * Your network has more than 16 cells (only 16 neighbors can be configured per cell). The AP “Neighbor Frequency Table” has a limit of eight unique frequencies. If the AP has more than eight neighbors with different frequencies, priority determines which frequencies are included.
    * You need to optimize handover paths based on physical layout or UE movement patterns
    * You want to prevent handovers to certain cells
    * You need asymmetric neighbor configurations (different neighbors for different cells)

{% hint style="info" %}
**NOTE:** Neighbor configuration is directional. Adding Cell-2 as a neighbor of Cell-1 does not automatically make Cell-1 a neighbor of Cell-2. Each directional relationship must be configured separately. For example, configuring Cell-A as a neighbor of Cell-B does not automatically make Cell-B a neighbor of Cell-A. If bidirectional handovers are needed, you must configure both relationships: Add Cell-B to Cell-A's neighbor list and Add Cell-A to Cell-B's neighbor list.
{% endhint %}

### Notes and Limitations

* Handovers are supported only between APs associated with the same Onyx Edge or the same Onyx Edge Pool.
* Manual neighbor configuration requires GXC APs running software version 3.1.14 or later.
* Onyx Edge running pre-3.1.3 release version will have ANR enabled. To manage neighbor relations, upgrade to Onyx Edge release 3.1.3 or later.
* The AP “Neighbor Frequency Table” is automatically populated by the Onyx Edge based on SAS grants and cannot be edited manually.
* The AP “Neighbor Frequency Table” has a limit of eight unique frequencies. If the AP has more than eight neighbors with different frequencies, priority determines which frequencies are included. Contact GXC Technical Support for assistance with multi-frequency deployments.
* The AP “Neighbor Cell Table” has a limit of 16 cell entries, with a constraint that the corresponding frequencies do not exceed eight. Priority order determines which neighbors are added when the limit is reached.
* If the full list of configured neighbors cannot be applied due to table limits, an alert is generated for the affected cell.
* UE must support the necessary hardware and software capabilities for handover functionality. Older or lower-end UE may lack adequate support.
* Changes to neighbor frequency or cell tables reboots the APs, resulting in service disruption during configuration updates. Plan all neighbor table changes during scheduled maintenance windows.

### How it Works

This section describes how inter-AP handovers work in conjunction with Onyx Portal-configured neighbor relationships for successful UE handovers.

Inter-AP handovers follow a two-phase process:

* [*Neighbor Relationship Configuration*](#neighbor-relationship-configuration)
* [*UE Handover Execution*](#ue-handover-execution)

#### Neighbor Relationship Configuration

Before handovers can occur, the Onyx Portal and Onyx Edge must establish which cells are neighbors and what frequencies they use, for each AP.

<p align="center"><strong>Neighbor Relationship Configuration Call Flow</strong></p>

<div data-with-frame="true"><figure><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FEfMPE2naRkjwpsRODSsK%2Fimage.png?alt=media&amp;token=14695c03-4f12-4860-94a4-5724746be9ad" alt=""><figcaption></figcaption></figure></div>

1. **Configure Neighbor Cell Relationships** — An Onyx Portal Administrator configures AP neighbor cell relationships using automatic or manual configuration modes. For more information, see [*Configuration Workflow*](#configuration-workflow).
2. **Populate Neighbor Tables** — When a TR-069 session is established with an AP, the Onyx Edge applies the neighbor cell and frequency table configurations:
   * The Onyx Edge populates each AP’s “Neighbor Cell Table” based on the neighbor relationships and priorities configured in the Onyx Portal. Priority order determines which neighbors are included when the 16-cell table limit is reached (with the constraint that corresponding frequencies do not exceed eight).
   * The Onyx Edge automatically populates each AP’s “Neighbor Frequency Table” based on SAS grants assigned to the neighbor cells.
   * Changes to the neighbor tables result in AP reboot.

#### UE Handover Execution

With neighbor tables in place, the network continuously monitors UE signal quality and executes handovers based on LTE measurement events: A1, A2, and A5.

For a description of each measurement event, the signal-level timeline, and a worked example, see [*Sample Handover Walkthrough*](#sample-handover-walkthrough). For detailed parameter definitions, default values, and tuning guidance, see [*Handover Parameters Reference*](#handover-parameters-reference).

The following call flow diagram summarizes the end-to-end UE handover execution sequence.

<p align="center"><strong>UE Handover Call Flow</strong></p>

<div data-with-frame="true"><figure><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FLxq66So1ki9ALwAVg7oR%2Fimage.png?alt=media&amp;token=0dc191f5-ca81-4ebd-9efb-762b3345987c" alt=""><figcaption></figcaption></figure></div>

1. **Send A1 Measurement Configuration** — The serving AP delivers a measurement configuration message to the UE containing the A1 RSRP threshold parameters. When the serving cell’s RSRP exceeds this threshold (Event A1), the UE stops measuring neighbor cells, reducing power consumption and measurement overhead.
2. **Send A2 Measurement Configuration** — The serving AP delivers a measurement configuration message to the UE containing the A2 RSRP threshold parameters. When the serving cell’s RSRP falls below this threshold (Event A2), the UE begins measuring neighbor cells to identify candidate target cells for handover.
3. **Trigger Neighbor Measurements (A2 Event Report)** — When the serving cell’s signal quality falls below the configured A2 threshold, the UE reports the condition to the serving AP.
4. **Configure Neighbor Cell Measurements (A5 Measurement Configuration)** — Upon receiving the A2 report, the serving AP configures the UE to perform neighbor cell measurements on frequencies listed in the AP’s “Neighbor Frequency Table”. The AP uses A5 event triggers to control when measurements are reported.
5. **Evaluate Handover Conditions (A5 Event Report)** — As the UE moves and signal strength changes, the UE continuously monitors both serving and neighbor cell signal levels. Event A5 is triggered when both A5 conditions are met simultaneously:

   * The serving cell’s RSRP drops below the A5 threshold, and
   * A configured neighbor cell’s RSRP exceeds the A5 threshold.

   This dual-condition approach ensures handovers occur only when the current cell is genuinely degrading and a stronger alternative is available. For a detailed example of how A5 conditions play out in practice, see [*Sample Handover Walkthrough*](#sample-handover-walkthrough).
6. **Execute Handover** — The serving AP initiates the handover procedure over the S1 interface. The Onyx Edge coordinates the handover between the serving and target APs using a make-before-break approach. The UE disconnects from the serving cell and connects to the target cell, maintaining service continuity.

For detailed parameter definitions, default values, and tuning guidance for each event's thresholds, see [*Handover Parameters Reference*](#handover-parameters-reference).

#### Sample Handover Walkthrough

This section walks through an example of a UE moving from AP-1 (serving cell) toward AP-2 (neighbor cell) in a typical deployment scenario, illustrating how each measurement event is triggered as signal conditions change."

{% hint style="info" %}
**NOTE:** Threshold values used in this section are illustrative and may differ from the defaults listed in [*Sample Configurations*](#sample-configurations). Actual trigger timing depends on the thresholds, hysteresis, and time-to-trigger configured for your deployment.
{% endhint %}

<p align="center"><strong>Example Threshold Values</strong></p>

| Threshold                      | Example Value |
| ------------------------------ | ------------- |
| A1 Threshold                   | −82 dBm       |
| A2 Threshold                   | −92 dBm       |
| A5 Threshold 1 (serving cell)  | −100 dBm      |
| A5 Threshold 2 (neighbor cell) | −96 dBm       |

The following diagram illustrates how RSRP levels drive each measurement event as the UE moves away from the serving AP and toward a neighbor AP.

<p align="center"><strong>LTE Handover Measurement Events — Signal Level Timeline</strong></p>

<div data-with-frame="true"><figure><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FsLC9S0FttGXVK9iaKKs5%2Fhandover-measurement-events-signal-level-timeline.png?alt=media&amp;token=4ebc1434-de52-48f7-9cb6-f640241718a9" alt=""><figcaption></figcaption></figure></div>

1. Initially, while the serving cell’s RSRP remains above the A1 threshold (−82 dBm), Event A1 is triggered, and the UE suspends neighbor cell measurements.
2. As the UE moves farther away from the serving cell, the serving cell signal level gradually decreases.
3. When the serving cell RSRP falls below the A2 threshold (−92 dBm), Event A2 is triggered, and the UE begins actively measuring neighbor cells. This measurement phase is represented by the shaded region.
4. Measurements continue until both A5 conditions are satisfied simultaneously:

   * The serving cell RSRP drops below A5 Threshold1 (−100 dBm), and&#x20;
   * The neighbor cell RSRP exceeds A5 Threshold2 (−96 dBm).

   At this point, Event A5 is triggered, and the serving AP initiates the handover procedure.

**Event A1: UE Close To Serving AP**

<p align="center"><strong>Event A1 - Serving Cell Becomes Better Than Threshold</strong></p>

<div data-with-frame="true"><figure><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FYY4g4zlcHQQQL4JZM6XK%2Fevent-a1.png?alt=media&amp;token=32fa7c1f-bfc8-42fc-b267-04698346467a" alt="" width="563"><figcaption></figcaption></figure></div>

<div data-with-frame="true"><figure><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FcrPgFNLEEWpWXJCtXQj1%2Fevent-a1-1.png?alt=media&amp;token=c57cdff9-4c96-4c27-bf4e-f5c8d9aceb1f" alt="" width="563"><figcaption></figcaption></figure></div>

The UE is in close proximity to AP-1, and the serving cell RSRP is above A1 threshold (−82 dBm), which satisfies the A1 threshold condition. Event A1 is triggered, and the UE stops neighbor cell measurements. Signal conditions are strong; no handover is needed.

**Event A2: UE Moves Away, Signal Degrades**

<p align="center"><strong>Event A2 — Serving Cell Becomes Worse Than Threshold</strong></p>

<div data-with-frame="true"><figure><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2F59AVAiI1Q5P4iJhVuJgH%2Fevent-a2.png?alt=media&amp;token=97cbb3c1-872e-43b6-a828-e80f6f6a687a" alt="" width="563"><figcaption></figcaption></figure></div>

<div data-with-frame="true"><figure><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2F5zjBMHcouYTaSo31XFTk%2Fevent-a2-1.png?alt=media&amp;token=cb12ce1e-0c0d-46e7-b3a3-8273c313b57e" alt="" width="563"><figcaption></figcaption></figure></div>

As the UE moves away from AP-1, serving cell RSRP gradually decreases. When it drops below the A2 threshold (−92 dBm), Event A2 is triggered. The UE reports this condition to AP-1, which instructs the UE to begin measuring neighbor cells on the frequencies listed in its “Neighbor Frequency Table”. During this phase, the UE actively evaluates AP-2 and other configured neighbors. This measurement process continues until either the serving signal exceeds the A1 threshold (thereby triggering Event A1) or a suitable handover candidate is identified, thereby triggering Event A5.

**Event A5: Both A5 Conditions Are Met, Handover Triggered**

<p align="center"><strong>Event A5 — Handover Triggered (Dual Threshold Condition Met)</strong></p>

<div data-with-frame="true"><figure><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2F2tVFDPaVBzjnanpS5qds%2Fevent-a5.png?alt=media&amp;token=556c741d-f4e1-47c7-83d5-8d4450297601" alt="" width="563"><figcaption></figcaption></figure></div>

<div data-with-frame="true"><figure><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FDwCuhrtyoBpUmsIsQ9sD%2Fevent-a5-1.png?alt=media&amp;token=f1180291-2dc9-4b3d-9244-772c67fe155e" alt="" width="563"><figcaption></figcaption></figure></div>

As the UE continues moving towards AP-2, Event A5 is triggered when both of the following conditions are met simultaneously:

* The serving cell (AP-1) RSRP drops below A5 Threshold1 (−100 dBm)
* The neighbor cell (AP-2) RSRP rises above A5 Threshold2 (−96 dBm)

This dual-condition mechanism ensures that handover occurs only when the current connection is clearly degrading and a better target cell is available.

Once both conditions are satisfied:

* The UE reports the measurement to AP-1
* AP-1 forwards the request to the Onyx Edge
* The Onyx Edge coordinates a make-before-break handover
* The UE transitions to AP-2 without service interruption

## Configuring Handovers

In the 4G Onyx architecture, handover configuration requires careful planning of neighbor relations, precise adjustment of mobility parameters, and thorough testing to ensure seamless transitions. While actual parameter ranges and GUI steps may vary based on the specific GXC equipment and network environment, this section outlines the foundational steps for configuring reliable handovers.

### Configuration Workflow

1. Add the APs.\
   See [*Add APs*](#add-aps).
2. Associate the APs with an Onyx Edge or an Onyx Edge Pool.\
   See [*Associate APs with Onyx Edge or Pool*](#associate-aps-with-onyx-edge-or-pool).
3. Configure neighbor relationships and handover parameters for each AP. Choose the configuration approach that best suits your network topology and mobility requirements:
   * Configure all cells associated with the Onyx Edge as the AP’s prospective neighbors and allow the Onyx Edge to decide on the neighbors.\
     See [*Edit APs to Use Automatic Neighbor Configuration*](#edit-aps-to-use-automatic-neighbor-configuration).
     * Keep the default advanced handover parameter configurations.
     * Edit the default advanced handover parameter configurations to configure optimal threshold values for the given radio environment.\
       See [*Configure Advanced Handover Parameters*](#configure-advanced-handover-parameters).
   * Configure specific cells as the AP’s neighbors.\
     See [*Edit APs to Use Manual Neighbor Configuration*](#edit-aps-to-use-manual-neighbor-configuration).
     * Keep the default handover advanced parameter configurations.
     * Edit the default advanced handover parameter configurations to configure optimal threshold values for the given radio environment.\
       See [*Configure Advanced Handover Parameters*](#configure-advanced-handover-parameters).

#### Add APs

This section describes the high-level steps to add an AP.

For detailed instructions, see *4G Onyx Portal Operations Guide > Add APs*.

**To add an AP:**

{% stepper %}
{% step %}
In the Onyx Portal’s navigation pane, click **Equipment** > **Access Points** tab.

The **Equipment** page > **Access Points** tab displays the summary details of all APs configured in the network.
{% endstep %}

{% step %}
In the upper-right corner of the page, click **Add Node** > **Add Access Point**.

The **Create Access Point** page > **Access Point** tab is displayed.

<div data-with-frame="true"><figure><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FgmGnOM0PcJpbiR0XZK7P%2F4g-ap-add-access-point-tab.png?alt=media&amp;token=e2a6fd59-e4c4-4ef9-a696-b081aed9366a" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
Enter the AP's details.

For detailed instructions, see *4G Onyx Portal Operations Guide > Add APs*.
{% endstep %}

{% step %}
In the lower-right corner of the page, click **Configure RAN**.

The **RAN** tab is displayed.

<div data-with-frame="true"><figure><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2F8OKcy2TiOECXmJ7NQx8G%2F4g-ap-add-ran-tab.png?alt=media&amp;token=d0ac1ff4-9907-4ed2-9b31-5284e0b47b90" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
Enter the RAN details.

For detailed instructions, see *4G Onyx Portal Operations Guide > Add APs*.

{% hint style="info" %}
**NOTE:** Do not configure the handover parameters at this time. You must first save the AP and associate it with an Onyx Edge or an Onyx Edge pool.
{% endhint %}
{% endstep %}

{% step %}
To save the AP, in the upper-right corner of the page, click **Save Access Point**.
{% endstep %}
{% endstepper %}

#### Associate APs with an Onyx Edge or Onyx Edge Pool

After you add the APs, you must associate them with an Onyx Edge or an Onyx Edge Pool.

**Associate APs with an Onyx Edge**

**To associate APs with an Onyx Edge:**&#x20;

{% stepper %}
{% step %}
In the navigation pane, click **Equipment**.

The **Equipment** page > **Onyx Edge** tab displays the summary details of all Onyx Edge configured in the network.
{% endstep %}

{% step %}
For the Onyx Edge that you want to edit, in the **Onyx Edge (n)** panel > **Actions** column, click the corresponding ⋮ (options) icon, then click **Edit**.

The **Edit Onyx Edge (*****\<Onyx Edge name>*****)** page displays the Onyx Edge’s details.
{% endstep %}

{% step %}
Click the **RAN** tab.
{% endstep %}

{% step %}
Click the **Associated Access Point** dropdown and select the APs to associate with the Onyx Edge.

<div data-with-frame="true"><figure><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FfduEopE2U8Q1mJu3Jxol%2Foe-edit-associate-ap.png?alt=media&amp;token=88541920-e738-45f3-aee6-0adea9b26694" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
To save your edits, in the upper-right corner of the page, click **Save Onyx Edge**.
{% endstep %}
{% endstepper %}

**Associate APs with an Onyx Edge Pool**

**To associate APs with an Onyx Edge pool:**

{% stepper %}
{% step %}
In the navigation pane, click **Equipment**.

The **Equipment** page > **Onyx Edge** tab displays the summary details of all Onyx Edge configured in the network. At the bottom of the page, the **Onyx Edge Pool** panel lists the available pools.
{% endstep %}

{% step %}
For the pool that you want to edit, in the **Onyx Edge Pool (n)** panel > **Actions** column, click the corresponding ⋮ (options) icon, then click **Edit**.

The **Edit Onyx Edge Pool** page is displayed.
{% endstep %}

{% step %}
Click the **Associated Access Points** dropdown and select the APs to associate with the Onyx Edge pool.

<div data-with-frame="true"><figure><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FmU97MY36kJgHjjTT5ZgO%2Foe-pool-edit-associate-ap.png?alt=media&amp;token=1cedddf9-88b8-4192-871b-361fade6f62d" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
To save your edits, click **Save Onyx Edge Pool**.
{% endstep %}
{% endstepper %}

#### Edit APs to Use Automatic Neighbor Configuration

This section describes how to edit an AP to configure every cell as a neighbor and allow the Onyx Edge to decide on a cell’s neighbors. Note that this is the default behavior.

{% hint style="info" %}
**NOTE:** A cell can be configured with up to 16 neighbor cells. By default, Onyx Edge configures all associated cells as neighbors to each cell. If more than 17 cells are associated with an Onyx Edge, it automatically selects any 16 cells as neighbors for each cell. To specify which specific cells should be neighbors, you must configure the neighbor cells explicitly. For more information, see [*Edit APs to Use Manual Neighbor Configuration*](#edit-aps-to-use-manual-neighbor-configuration).
{% endhint %}

**To edit an AP to configure every cell as a neighbor to the AP:**

{% stepper %}
{% step %}
In the Onyx Portal’s navigation pane, click **Equipment** > **Access Points** tab.

The **Equipment** page > **Access Points** tab displays the summary details of all APs configured in the network.
{% endstep %}

{% step %}
In the **Actions** column, for the AP that you want to edit, click the corresponding ⋮ (options) icon, then click **Edit**.

The **Edit Access Point** page displays the AP’s details.
{% endstep %}

{% step %}
Navigate to the **Handover** tab and configure the following details:

<div data-with-frame="true"><figure><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FsPsGDW3UrrqFqLDCr7iS%2Fimage.png?alt=media&amp;token=2a8f3ba1-726c-4193-a4c9-aa94a53afb01" alt=""><figcaption></figcaption></figure></div>

* **Explicit Neighbors** – When disabled, all cells associated with the Onyx Edge are automatically configured as the AP’s neighbors.
  {% endstep %}

{% step %}
To edit advanced handover parameters, see [*Configure Advanced Handover Parameters*](#configure-advanced-handover-parameters).
{% endstep %}

{% step %}
To save your edits, in the upper-right corner of the page, click **Save Access Point**.
{% endstep %}
{% endstepper %}

#### Edit APs to Use Manual Neighbor Configuration

This section describes how to edit APs to configure specific cells as neighbors.

{% hint style="warning" %}
**CAUTION:** Adding or editing APs restarts all APs, since tables are modified and updated across all units. This is a service-disrupting operation and must be planned accordingly.
{% endhint %}

**To edit an AP to configure specific cells as its neighbors:**

{% stepper %}
{% step %}
In the Onyx Portal’s navigation pane, click **Equipment** > **Access Points** tab.

The **Equipment** page > **Access Points** tab displays the summary details of all APs configured in the network.
{% endstep %}

{% step %}
In the **Actions** column, for the AP that you want to edit, click the corresponding ⋮ (options) icon, then click **Edit**.

The **Edit Access Point (*****\<AP name>*****)** page displays the AP’s details.
{% endstep %}

{% step %}
Navigate to the **Handover** tab and configure the following details:

<div data-with-frame="true"><figure><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FdrxJRwogEnk1fR4b8zAF%2Fimage.png?alt=media&amp;token=d49cfd24-2d86-40d9-953f-a516e956f3f9" alt=""><figcaption></figcaption></figure></div>

* **Explicit Neighbors** – Enable to manually configure specific neighbor cells for this AP. When enabled, you can explicitly select which cells should be neighbors and specify their priority order.
  * **Select Neighbor Cell (Priority Order)** – Click to select the AP’s neighbor cells from the list of cells associated with the Onyx Edge.

    The list order determines priority, with the first cell in the list assigned priority 1 (highest), the second cell priority 2, and so on.

    To reorder priorities, drag and drop cells up or down in the list as required.

<div data-with-frame="true"><figure><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2F1FVCCPxxOv6BBP9g7sGp%2Fimage.png?alt=media&amp;token=d9017f1e-e4c3-47e6-8e40-1b5b0ae48f51" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
To edit advanced handover parameters, see [*Configure Advanced Handover Parameters*](#configure-advanced-handover-parameters).
{% endstep %}

{% step %}
To save your edits, in the upper-right corner of the page, click **Save Access Point**.
{% endstep %}
{% endstepper %}

#### Configure Advanced Handover Parameters

Advanced handover parameters control the RSRP threshold values that govern when measurements are triggered and when handovers execute. This section describes how to edit APs to configure advanced handover parameters.

{% hint style="info" %}
**NOTE:** The default threshold values are optimized for typical deployment scenarios. Only adjust these values if you fully understand their impact on your specific radio environment. For optimization guidance or troubleshooting support, contact GXC Technical Support.
{% endhint %}

{% hint style="info" %}
**NOTE:** Each AP in your network may require different handover settings based on their role, coverage characteristics, and traffic patterns. This asymmetric approach enables fine-tuned optimization for specific network topology requirements.
{% endhint %}

#### **Portal Power Measurement Value Conversion**

In practice, power measurements are referred to in the dBm scale, typically ranging from -80 dBm (very good power) to -120 dBm (very poor power). To simplify GUI configuration in the Onyx Portal, these negative dBm values (which are hard to compare intuitively) are converted into positive values by adding an offset of 140. For example, -80 dBm becomes 60 in the Onyx Portal. The following table lists the default values.

Unlike absolute power thresholds (A1, A2, A5), the A3 Offset RSRP and Hysteresis parameters represent relative values measured in decibels (dB), not absolute power levels (dBm). The Onyx Portal values for these parameters are entered directly as dB offsets without the conversion used for absolute power measurements.

<p align="center"><strong>Portal Power Measurement Value Conversion</strong></p>

<table><thead><tr><th valign="top">Threshold</th><th valign="top">Power Level</th><th valign="top">Onyx Portal Value (power in dBm + 140)</th></tr></thead><tbody><tr><td valign="top">A1 RSRP</td><td valign="top">-85 dBm</td><td valign="top">55</td></tr><tr><td valign="top">A2 RSRP</td><td valign="top">-90 dBm</td><td valign="top">50</td></tr><tr><td valign="top">A5 RSRP Neighbor Cell</td><td valign="top">-97 dBm</td><td valign="top">43</td></tr><tr><td valign="top">A5 RSRP Serving Cell</td><td valign="top">-100 dBm</td><td valign="top">40</td></tr><tr><td valign="top">A3 Offset RSRP</td><td valign="top">N/A (relative value)</td><td valign="top">10 dB</td></tr><tr><td valign="top">Hysteresis</td><td valign="top">N/A (relative value)</td><td valign="top">1 dB</td></tr></tbody></table>

#### **Handover Parameters Reference**

The following table describes all advanced handover parameters — definitions, defaults, and tuning guidance. The [*Sample Configurations*](#sample-configurations) section provides ready-made profiles for common deployment scenarios.

<p align="center"><strong>Handover Parameters Reference</strong></p>

<table><thead><tr><th width="150.42852783203125" valign="top">Parameter</th><th width="150.238037109375" valign="top">Default (Onyx Portal value / dBm)</th><th valign="top">Purpose</th><th valign="top">Tuning Guidance (When to Increase or Decrease)</th></tr></thead><tbody><tr><td valign="top"><strong>A1 RSRP</strong></td><td valign="top">55 / −85 dBm</td><td valign="top"><p>The RSRP threshold above which the serving cell’s signal is considered acceptable. When this threshold is met, the UE is instructed to stop measuring neighbor cells. This optimizes battery life by stopping unnecessary measurements when signal is strong.</p><p>In DC mode, configure this parameter for Cell 1 and Cell 2.</p></td><td valign="top"><p><strong>Increase</strong> </p><p>In strong coverage environments, to reduce unnecessary neighbor measurements and improve UE battery life.
</p><p>When you want to prioritize stability over frequent measurements (e.g., stationary or slow-moving UE).</p><p><strong>Decrease</strong> </p><p>In challenging RF environments with frequent micro-mobility, to keep neighbor measurements active longer.
</p><p>When UE are moving fast or have high reliability demands (e.g., AGVs or autonomous machines), so they stay ready to handover earlier.</p></td></tr><tr><td valign="top"><strong>A2 RSRP</strong></td><td valign="top">50 / −90 dBm</td><td valign="top"><p>The RSRP threshold below which the serving cell’s signal quality is considered poor. When this threshold is met, the UE is instructed to start measuring neighbor cells in preparation for a potential handover.</p><p>In DC mode, configure this parameter for Cell 1 and Cell 2.</p></td><td valign="top"><p><strong>Increase</strong> </p><p>In stable environments with good coverage, to avoid triggering neighbor measurements too early.
</p><p>When reducing measurement overhead is more important than early preparation.</p><p><strong>Decrease</strong></p><p>In high-mobility or interference-prone areas, to start neighbor cell monitoring earlier, ensuring smoother handovers.
</p><p>To improve handover responsiveness for mission-critical applications.</p></td></tr><tr><td valign="top"><strong>A5 RSRP — Serving Cell</strong></td><td valign="top">40 / −100 dBm</td><td valign="top"><p>The serving cell’s signal strength must fall below this threshold to qualify for handover evaluation. Ensures handovers only occur when serving cell signal is genuinely weak.</p><p>In DC mode, configure this parameter separately for Cell 1 and Cell 2.</p><p></p><p></p></td><td valign="top"><p><strong>Increase</strong> </p><p>If UE stay too long on poor signals (delayed handovers), increasing this value will cause them to handover sooner.</p><p><strong>Decrease</strong> </p><p>To avoid unnecessary or premature handovers (ping-pong effect), especially if UE are stationary or moving slowly.</p></td></tr><tr><td valign="top"><strong>A5 RSRP — Neighbor Cell</strong></td><td valign="top">43 / −97 dBm</td><td valign="top"><p>The neighboring cell’s signal strength must exceed this threshold to be considered a valid handover target. This prevents handovers to cells with insufficient signal quality.</p><p>In DC mode, configure this parameter separately for Cell 1 and Cell 2.</p></td><td valign="top"><p><strong>Increase</strong> </p><p>To ensure UE only move to strong and stable cells, improving post-handover performance.
</p><p>In environments where overlapping cells have varying quality, to avoid weak target cells.</p><p><strong>Decrease</strong> </p><p>To allow handovers to weaker cells if no stronger options are available, preventing drops or service interruption.</p></td></tr><tr><td valign="top"><strong>A3 Offset RSRP</strong></td><td valign="top">10 dB</td><td valign="top"><p>The signal strength margin (in dB) by which the neighbor cell's RSRP must exceed the serving cell's RSRP to trigger a handover. This offset helps prevent unnecessary handovers due to minor signal fluctuations.</p><p>In DC mode, configure this parameter for Cell 1 and Cell 2.</p></td><td valign="top"><p><strong>Increase</strong></p><p>In stable RF environments to reduce ping-pong handovers caused by small signal variations.
</p><p>When prioritizing connection stability over signal optimization, particularly for stationary or slow-moving UE.
</p><p>In high-density deployments with significant cell overlap where frequent handovers would create excessive signaling overhead.</p><p><strong>Decrease</strong> </p><p>In environments where signal quality changes rapidly and UE need to switch to better cells quickly.
</p><p>For high-mobility scenarios where faster handover decisions improve service continuity.
</p><p>When optimizing for maximum signal quality is critical for application performance (e.g., high-throughput data applications).</p></td></tr><tr><td valign="top"><strong>Hysteresis</strong></td><td valign="top">1 dB</td><td valign="top">A buffer value that prevents handover flapping due to small signal fluctuations. The neighbor cell's signal must exceed the serving cell’s signal by this margin (in dB) for the handover to be triggered.</td><td valign="top"><p><strong>Increase</strong> </p><p>In highly variable RF conditions to reduce oscillating handovers.
</p><p>When UE experience frequent rapid changes in signal quality.</p><p><strong>Decrease</strong> </p><p>If handovers are delayed too long despite a neighbor being better, or if service continuity requires faster switching.</p></td></tr><tr><td valign="top"><strong>Time to Trigger</strong></td><td valign="top">480 ms</td><td valign="top">The time duration (in milliseconds) that a qualifying signal condition must persist before a handover is initiated. This prevents unnecessary handovers due to temporary signal variations.</td><td valign="top"><p><strong>Increase</strong> </p><p>To avoid unnecessary handovers caused by short-term fading or momentary interference.</p><p><strong>Decrease</strong> </p><p>To make handover reactions faster, especially for high-speed mobility scenarios.</p></td></tr></tbody></table>

**To configure advanced handover parameters:**

{% stepper %}
{% step %}
In the Onyx Portal’s navigation pane, click **Equipment** > **Access Points** tab.

The **Equipment** page > **Access Points** tab displays the summary details of all APs configured in the network.
{% endstep %}

{% step %}
In the **Actions** column, for the AP that you want to edit, click the corresponding ⋮ (options) icon, then click **Edit**.

The **Edit Access Point** page displays the AP’s details.
{% endstep %}

{% step %}
Click the **Handover** tab.
{% endstep %}

{% step %}
Click **Show Advanced Configuration** and configure the following details.

<div data-with-frame="true"><figure><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FRYoNBIMq2y9njyf5h9AW%2Fimage.png?alt=media&amp;token=19267e0f-5555-4a3f-a01c-01d88e622c75" alt=""><figcaption></figcaption></figure></div>

* **Neighbor Management** – Enable to allow Onyx Edge to manage neighbor relationships for this AP. When enabled, the Onyx Edge automatically populates and maintains this AP’s “Neighbor Frequency Table” and “Neighbor Cell Table” based on the other cells associated with it.

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>NOTE:</strong> If you need to disable neighbor management for a particular AP, you must disable this <strong>Neighbor Management</strong> toggle switch.</p></div>
* **Handover Thresholds** – Parameters that control the handover process, ensuring smooth transitions between cells when a UE moves out of the serving cell's coverage area.

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>NOTE:</strong> For detailed parameter descriptions, see <a href="#handover-parameters-reference"><em>Handover Parameters Reference</em></a> table.</p></div>

  * **A5 RSRP** – A handover is initiated when both of the following conditions are met simultaneously:
    * **Serving Cell** – (Required) When the serving cell RSRP falls below this threshold handover is evaluated. Ensures handovers only occur when the serving cell is genuinely weak. In DC mode, configure this parameter for Cell 1 and Cell 2. Default value: 40 (equivalent to –100 dBm).
    * **Neighbor Cell** – (Required) When the neighbor cell RSRP rises above this threshold it is considered a valid handover target. Prevents handovers to cells with insufficient signal. In DC mode, configure this parameter for Cell 1 and Cell 2. Default value: 43 (equivalent to -97 dBm).
  * **A1 RSRP** – (Required) When the serving cell RSRP rises above this threshold, the signal is considered acceptable. The UE stops measuring neighbors, conserving battery. Default value: 55 (equivalent to -85 dBm). In DC mode, configure this parameter for Cell 1 and Cell 2.
  * **A2 RSRP** – (Required) When the serving cell RSRP falls below this threshold, the signal is considered poor. The UE begins measuring neighbors in preparation for handover. Default value: 50 (equivalent to -90 dBm). In DC mode, configure this parameter for Cell 1 and Cell 2.
  * **A3 Offset RSRP** – (Required) The margin, in dB, by which the neighbor cell RSRP must exceed the serving cell RSRP to trigger a handover. Prevents unnecessary handovers from minor signal fluctuations. Default value: 10 dB. In DC mode, configure this parameter for Cell 1 and Cell 2.
  * **Hysteresis (dB)** – (Required) A buffer value, in dB, that prevents handover flapping from small signal fluctuations. The neighbor cell signal must exceed the serving cell signal by this margin before a handover is triggered. Default value: 1 dB.
  * **Time to trigger (ms)** – The duration, in milliseconds, that a qualifying condition must persist before a handover is initiated. Prevents handovers triggered by temporary fading or momentary interference. Default value: 480 ms.
    {% endstep %}

{% step %}
To save your edits, in the upper-right corner of the page, click **Save Access Point**.
{% endstep %}
{% endstepper %}

#### Sample Configurations

The following table provides recommended starting configurations for typical deployment environments. Use these as baselines and adjust based on field testing results and your specific network requirements.

* **Conservative (Stable Connection)** – Designed for stationary or slow-moving devices and mission-critical applications requiring maximum stability. Minimizes handover frequency and reduces ping-pong effects, though devices may stay on weaker signals longer.
* **Baseline (GXC Default)** – GXC-recommended starting point for general enterprise environments with mixed mobility patterns. Provides balanced performance across most scenarios with optimal trade-offs between stability and optimization.
* **Aggressive (Opportunistic)** – Optimized for high-density environments with excellent coverage overlap and performance-critical applications. Maximizes signal quality through quick handovers to better cells but increases handover frequency and signaling overhead.
* **High-Mobility** – Tailored for vehicular applications and fast-moving devices with faster reaction times. Optimized for movement patterns while maintaining reasonable stability but may not suit stationary devices.

<p align="center"><strong>Sample Configurations</strong></p>

| Parameter             | Conservative (Stable) | Baseline (GXC Default) | Aggressive (Opportunistic) | High-Mobility |
| --------------------- | --------------------- | ---------------------- | -------------------------- | ------------- |
| A1 RSRP               | 60 (-80 dBm)          | 55 (-85 dBm)           | 55 (-85 dBm)               | 53 (-87 dBm)  |
| A2 RSRP               | 45 (-95 dBm)          | 50 (-90 dBm)           | 50 (-90 dBm)               | 52 (-88 dBm)  |
| A5 RSRP Neighbor Cell | 48 (-92 dBm)          | 43 (-97 dBm)           | 45 (-95 dBm)               | 42 (-98 dBm)  |
| A5 RSRP Serving Cell  | 35 (-105 dBm)         | 40 (-100 dBm)          | 38 (-102 dBm)              | 40 (-100 dBm) |
| A3 Offset RSRP (dB)   | 12                    | 10                     | 6                          | 8             |
| Hysteresis (dB)       | 3                     | 1                      | 0.5                        | 2             |
| Time to Trigger (ms)  | 640                   | 480                    | 320                        | 240           |

## Testing and Validation

Proper testing is essential to confirm that handover performance meets requirements before full deployment. The recommended process combines theoretical modeling, field measurement, and portal-based monitoring.

**Recommended testing process:**

1. **Model parameters using the GXC Handover Visualization Tool**. Model parameters using the GXC Handover Visualization Tool to understand how threshold values affect the handover region before deploying to the field. See [*GXC Handover Visualization Tool*](#gxc-handover-visualization-tool).
2. **Plan and configure neighbor relationships**. Plan and configure neighbor relationships in the Onyx Portal based on your network topology and expected UE movement patterns.
3. **Apply initial handover parameter configuration**. Configure handover parameters in Onyx Portal for initial field testing. Start with model or default threshold values. See [*Configuring Handovers*](#configuring-handovers).
4. **Perform field testing.** Use the GXC Onyx Survey Tool across all coverage areas and mobility scenarios. The Onyx Survey Tool is purpose-built for GXC private cellular deployments and provides integrated handover measurement and reporting. For details on using the tool, see the *4G & 5G Onyx Survey Solution Application Note*.

   Alternatively, professional drive test tools such as TEMS Investigation or Nemo Outdoor may be used. Monitor the performance metrics – track handover success rates, timing, and signal levels to validate real-world performance against expectations. See [*Field Testing*](#field-testing).
5. **Monitor performance in the Onyx Portal.** Use Onyx Portal to analyze handover statistics, review neighbor table status, and track overall mobility performance. See [*Onyx Portal-Based Monitoring*](#onyx-portal-based-monitoring).
6. **Adjust and re-test.** Based on field test results, refine threshold values and neighbor priorities. Re-test until target performance levels are achieved. See [*Configure Advanced Handover Parameters*](#configure-advanced-handover-parameters).
7. **Validate mission-critical applications.** Confirm that applications requiring uninterrupted connectivity maintain acceptable connectivity and performance during handover transitions.

### GXC Handover Visualization Tool

GXC provides an interactive web-based tool to help visualize and understand LTE handover behavior before field deployment. Use this tool to understand the relationship between threshold parameters and handover regions before making any configuration changes.

<div data-with-frame="true"><figure><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2F2JXcUq6MF06xXXkstjzT%2Fimage.png?alt=media&amp;token=4d976286-baa6-4542-bebc-c598231813ce" alt=""><figcaption></figcaption></figure></div>

**Using GXC’s LTE Handover Region Visualization Tool:**

{% hint style="info" %}
**NOTE:** Each AP in your network may require different handover settings based on their role, coverage characteristics, and traffic patterns. This asymmetric approach enables fine-tuned optimization for specific network topology requirements.
{% endhint %}

{% stepper %}
{% step %}
Access the tool at: [*https://lte-handoff-vfa3mkxapbectiedyiptvj.streamlit.app/*](https://lte-handoff-vfa3mkxapbectiedyiptvj.streamlit.app/)
{% endstep %}

{% step %}
Under **Threshold Parameters**, use the sliders to adjust the threshold and hysteresis values to observe how changes affect the handover region.

For detailed information on these parameters, see [*Configuring Handovers*](#configuring-handovers).
{% endstep %}

{% step %}
The green region in the visualization shows where handovers will occur based on the relationship between Serving Cell Power (X-axis) and Neighbor Cell Power (Y-axis).
{% endstep %}

{% step %}
Experiment with different parameter combinations to understand:

* How hysteresis affects handover stability
* The relationship between serving and neighbor cell thresholds
* Optimal parameter ranges for different deployment scenarios
  {% endstep %}

{% step %}
Use the tool to identify starting parameters and understand parameter interactions before moving to field testing.
{% endstep %}
{% endstepper %}

### Field Testing

After initial parameters are configured, deploy and validate handover performance in the live network environment.

1. Deploy theoretical parameters in the actual network environment.
2. Perform field tests using the GXC Onyx Survey Tool to confirm real-world handover performance across your coverage area. The Onyx Survey Tool is purpose-built for GXC private cellular deployments and provides integrated measurement collection, handover event logging, and reporting. For full details on using the tool, see the *4G & 5G Onyx Survey Solution Application Note*. Alternatively, use third-party drive test tools such as TEMS Investigation or Nemo Outdoor.
3. During testing, monitor key performance indicators:
   * Handover success rate
   * Handover failure rate
   * Call drop rate during mobility
   * Time to complete handover
   * Signal strength at handover trigger points
   * Application continuity during handover
4. Test different mobility scenarios as per deployment requirements:
   * Pedestrian speed (3 km/h)
   * Vehicular speed (30-60 km/h)
   * Stationary to mobile transitions
   * High-density areas with multiple overlapping cells

### Onyx Portal-Based Monitoring

**To review and adjust the AP Handover settings in the Onyx Portal:**

{% stepper %}
{% step %}
In the Onyx Portal’s navigation pane, click **Equipment** > **Access Point** tab.

The **Equipment** page > **Access Points** tab displays the summary details of all APs configured in the network.
{% endstep %}

{% step %}
To view the details of a particular AP, click its name.

The ***\<AP name>*** page displays the AP’s details.
{% endstep %}

{% step %}
Click the **Handover** tab.

<div data-with-frame="true"><figure><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2Fu8P4qQm9WI49uEhAdFtw%2Fap-view-handover-tab.png?alt=media&amp;token=63ce2c24-431d-4478-9377-5cc240617978" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
Analyze handover measurements and adjust parameters based on observed performance.&#x20;

For details, see [*Configuring Handovers*](#configuring-handovers).
{% endstep %}
{% endstepper %}

## Best Practices and Optimization

The following recommendations help ensure reliable handover performance and simplify ongoing network optimization.

1. **Plan before you configure**. Plan neighbor relationships based on physical cell locations and expected UE mobility patterns before deployment.
2. **Start all-to-all, then refine**. Start with the default all-to-all neighbor configuration and refine based on traffic patterns and field testing.
3. **Use priority ordering to manage table limits**. Ensure the most likely handover targets appear within the 16-cell table limit.
4. **Configure bidirectional relationships**. Configure bidirectional neighbor relationships for cells where UE movement is expected in both directions.
5. **Start with GXC default thresholds**. Use GXC-provided default values as your baseline before adjusting them based on field test results. See [*Sample Configurations*](#sample-configurations).
6. **Use the Visualization Tool before field testing**. Leverage GXC's LTE Handover Region Visualization Tool to understand parameter relationships before field deployment. See [*GXC Handover Visualization Tool*](#gxc-handover-visualization-tool).
7. **Monitor continuously**. Track handover success rates, failure patterns, and mobility performance metrics to identify optimization opportunities.
8. **Test iteratively**. Combine theoretical modeling, field testing, and Onyx Portal analytics in an iterative cycle to achieve optimal performance.
9. **Validate application performance, not just connectivity**. Ensure mission-critical applications maintain service quality during handover transitions.
10. **Schedule table changes during maintenance windows.** All neighbor table changes cause AP reboots and service disruption.
11. **Document all changes**. Record all configuration changes, performance results, and rationale for future troubleshooting.
12. **Contact GXC Technical Support** for advanced tuning and optimization guidance.

## Related Documentation

* *4G Onyx Portal Operations Guide*
* *4G & 5G Onyx Survey Solution Application Note*
* *5G Spectrum Analyzer Application Note*
* *GXC Glossary*

## Contact GXC

To get in touch with GXC, please visit <https://gxc.io/contact-us/>.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.gxc.io/docs/application-notes/4g-handovers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.