> 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/network-configuration-and-operations-guides/4g-onyx-edge-on-premises-4.x-installation-and-operations/introduction.md).

# Introduction

This guide describes how to install Onyx Edge software on Onyx-ES hardware for 4G networks.

## Intended Audience

This document is intended for personnel responsible for installing Onyx Edge software on Onyx-ES hardware and for managing Onyx Edge On-Premises systems. Management access to the Onyx Edge is required to perform the procedures described in this document. If you do not have management access, work with your GXC Technical Support representative.

## About Onyx Edge

The Onyx Edge provides mobile device management functions in the control plane and enables data packet exchanges between user equipment (UE) and applications in the packet network on the data plane.

The 4G Onyx Edge consists of the Mobility Management Entity (MME), Home Subscriber Server (HSS), Serving Gateway (SGW), and the Packet Data Network Gateway (PGW) network elements. The MME and HSS provide mobility and device access control. The SGW and PGW are the network elements providing actual bearer data transport for mobile devices by routing data packets between your private LTE network, your local network, and any connected networks such as the public Internet. In the GXC solution, these different network elements run integrated on a single Onyx Edge.

<figure><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FH1zjInAaYOyRYCyzkJOR%2Fimage7.png?alt=media&amp;token=6de4224b-16b0-499b-a8e8-022b2e76b807" alt=""><figcaption><p>GXC Private Network Architecture</p></figcaption></figure>


---

# 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/network-configuration-and-operations-guides/4g-onyx-edge-on-premises-4.x-installation-and-operations/introduction.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.
