# 4G & 5G Onyx Edge 3.1.0 Release Notes

## Release Information

This release note provides information about the Onyx Edge 3.1.0 4G & 5G release.

### Component Compatibility Information

This release has been verified to be compatible with the following component releases.

<p align="center"><strong>Component Compatibility Information for 4G Networks</strong></p>

<table><thead><tr><th valign="top">Component</th><th valign="top">Release</th></tr></thead><tbody><tr><td valign="top">Onyx Portal</td><td valign="top">3.1.0</td></tr><tr><td valign="top">Onyx Edge</td><td valign="top">3.1.0</td></tr><tr><td valign="top">GM01 Mesh Node</td><td valign="top">3.0.0</td></tr><tr><td valign="top">G100 Indoor Access Point</td><td valign="top">BaiBLQ_3.1.14</td></tr><tr><td valign="top">G101 Outdoor Access Point</td><td valign="top">BaiBLQ_3.1.14</td></tr><tr><td valign="top">G501 Outdoor Access Point</td><td valign="top">BaiBLQ_3.1.14</td></tr></tbody></table>

<p align="center"><strong>Component Compatibility Information for 5G Networks</strong></p>

<table><thead><tr><th valign="top">Component</th><th valign="middle">Release</th></tr></thead><tbody><tr><td valign="top">Onyx Portal</td><td valign="middle">3.1.0</td></tr><tr><td valign="top">Onyx Edge</td><td valign="middle">3.1.0</td></tr><tr><td valign="top">Onyx FHM (Beta Release)</td><td valign="middle">1.5.3<br><br>For details, contact GXC Technical Support.</td></tr><tr><td valign="top">G105-n48F Indoor Access Point<br><br>G105-n48P Indoor Access Point<br><br>G105-n78F Indoor Access Point<br><br>G105-n78P Indoor Access Point<br><br>G505-n48P Outdoor Access Point<br><br>G505-n78P Outdoor Access Point<br><br>G506-n77 Outdoor Access Point</td><td valign="middle">For details, contact GXC Technical Support.</td></tr></tbody></table>

## New Features, Enhancements, and Behavior Changes

This section describes new features, enhancements, and behavior changes introduced in the ONYX Edge in this release.

### Onyx Edge in Core-only Configuration

{% hint style="info" %}
**NOTE:** This change is applicable only to 5G networks.
{% endhint %}

This release supports the following Onyx Edge deployment configurations:

* **Onyx Edge Core** – New in this release. This deployment configures the Onyx Edge to function as 5G Core-only, with the gNB external to the Onyx Edge. It is used when integrating third-party gNB and is offered with limited support. For more information on this deployment configuration, please contact GXC Technical Support.
* **Onyx Edge NR+Core** – Previously supported in 5G Onyx 3.0.0 release. This is the standard 5G deployment configuration, where an Onyx Edge runs both New Radio (NR) and 5G Core on the same server.

Administrator users can add, edit, delete Onyx Edge (Core), and manage software upgrades for Onyx Edge (Core) equipment in their 5G networks. For more information, refer to the *5G Onyx Portal Operations Guide*.

### Onyx Edge 5G in VLAN Mode

{% hint style="info" %}
**NOTE:** This change is applicable only to 5G networks.
{% endhint %}

In addition to the NAT networking mode available in 5G Onyx 3.0.0 release, 5G Onyx Edge now supports the VLAN mode, providing greater flexibility for Onyx Edge deployments. For more information, refer to the *5G Onyx Portal Operations Guide*.

### "S1 Same as SGi" Configuration Support in VLAN Mode

{% hint style="info" %}
**NOTE:** This change is applicable only to 4G networks.
{% endhint %}

In previous releases, the Onyx Edge in VLAN mode configuration required separate configurations for S1 and SGi interfaces. With this release, a "S1 same as SGi" configuration is now supported, which can be configured provided SGi uses the same VLAN as the management interface. This enhancement enables a completely flat network that expects only a single interface on the Onyx Edge. For more information, refer to the *4G Onyx Portal Operations Guide*.

### CBRS 2.0 Extended Heartbeat Timer and Enhanced Transmission Resilience

{% hint style="info" %}
**NOTE:** This change is applicable to both 4G and 5G networks.
{% endhint %}

In previous releases, CBRS devices had to reauthorize with the Spectrum Access System (SAS) every four minutes. If the Onyx Edge-Orchestrator (DP) connection was lost, APs stopped transmitting immediately, even if the grant's transmit timer had not yet expired.

The Onyx solution now implements CBRS 2.0, supporting an extended heartbeat capability. APs will continue transmitting until the latest transmit expiry (up to six hours in certain cases) even if the DP connection is lost, ensuring greater uptime in case of temporary connection failures.

New behavior:

* For grants in the 3550-3700 MHz band (outside Dynamic Protection Area neighborhoods): transmitExpireTime = 6 hours, heartbeatInterval = 30 minutes.
* For grants in the 3650-3700 MHz band (inside DPAs): transmitExpireTime = 6 hours, heartbeatInterval = 30 minutes.
* For grants in the 3550-3650 MHz band (inside DPAs): transmitExpireTime = 220 seconds, heartbeatInterval = 190 seconds.

These improvements reduce service disruptions and enhance network reliability, particularly for mission-critical deployments.

### SUCI (Concealed Identity) Support

{% hint style="info" %}
**NOTE:** This change is applicable only to 5G networks.
{% endhint %}

The Onyx solution now supports Subscription Concealed Identifier (SUCI) for UE in 5G networks, enhancing privacy by protecting subscriber identity during authentication. This implementation aligns with *3GPP TS 23.003 Section 2.2B* and *TS 33.501 Section 6.12.2*.

This update significantly enhances 5G subscriber security and identity protection by encrypting the Subscription Permanent Identifier (SUPI) into SUCI before transmission. This ensures IMSI protection, mitigates IMSI catching attacks, and strengthens UE anonymity. The system also supports home network public key-based encryption, preventing subscriber identity exposure during initial NAS messaging while aligning with 5G security frameworks and 3GPP standards to improve overall privacy.

### New Onyx 5G Platform

{% hint style="info" %}
**NOTE:** This change is applicable only to 5G networks.
{% endhint %}

With this release, the Onyx solution supports the ONYX-ES7 hardware platform for 5G Onyx Edge (NR+Core) deployments. For detailed specifications, please contact GXC Technical Support.

## Resolved Issues

There are no new resolved issues reported in this release.

## Open Issues

{% hint style="info" %}
**NOTE:** Open issues reported in previous releases, unless subsequently reported as resolved, may exist in this release.
{% endhint %}

The following new open issues were reported in this release.

### **Incorrect Subscriber State Reporting After MME Restart**

Sometimes, after the MME service on the Onyx Edge restarts, the state of some UE/subscriber that have transitioned to Idle state due to inactivity is incorrectly reported as Connected.

**Workaround**: None. This issue will be addressed in an upcoming release.

If a subscriber's reported state appears inaccurate or inconsistent, users are advised to contact GXC Technical Support to verify the actual status.

### **UE Data Transfer Stalls After Re-Registration Following Idle State Transition**

In certain scenarios, UE data transfer stalls after the UE re-registers following a transition to idle state in the Core.

Steps to reproduce:

{% stepper %}
{% step %}
Attach and connect the UE.
{% endstep %}

{% step %}
Stop gNB services, causing the UE to move to idle state.
{% endstep %}

{% step %}
Enable airplane mode on the UE to prevent a mobility update.
{% endstep %}

{% step %}
Restart gNB services.
{% endstep %}

{% step %}
Disable airplane mode to trigger a fresh registration.
{% endstep %}

{% step %}
Registration and PDU session establishment succeed, but data transfer does not work. Packets appear at the GTP-U interface, but none are seen at the eth0 interface.
{% endstep %}
{% endstepper %}

**Workaround**: To recover, enable and disable airplane mode on the UE or trigger a PDU session release and re-establish. This action clears the invalid session and restores data flow.

## Revision History

<p align="center"><strong>Revision History</strong></p>

<table><thead><tr><th width="250.166748046875" valign="top">Date</th><th valign="top">Updates</th></tr></thead><tbody><tr><td valign="top">2025-03-20</td><td valign="top">Initial release.</td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://docs.gxc.io/release-notes/release-notes-archive/onyx-edge-release-notes/4g-and-5g-onyx-edge-3.1.0-release-notes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.