> 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/5g-onyx-portal-4.x-operations/overview.md). # Overview GXC's 5G Onyx Solution is a fully integrated enterprise-grade private 5G platform designed to deliver secure, high-performance wireless connectivity. Tailored for industrial, campus, and large commercial deployments, the architecture combines 5G NR radio infrastructure with an on-premises 5G Core and centralized orchestration tools. The Onyx architecture consists of several key components that work together to provide secure connectivity, centralized management, and scalable private 5G deployment.

GXC 5G Private Network Architecture

## 5G Onyx Edge Core The 5G Onyx Edge Core provides the centralized control and user plane functions required for standalone (SA) 5G network operation. It performs subscriber authentication, session management, mobility control, and data routing between the radio access network and external data networks. The platform integrates key 5G Core network functions, including: * Access and Mobility Management Function (AMF) * Session Management Function (SMF) * User Plane Function (UPF) * Authentication Server Function (AUSF) * Unified Data Management (UDM) Together, these functions enable secure device authentication, mobility management, policy enforcement, and efficient routing of user traffic between the private 5G network, enterprise LAN, and external networks. The Onyx Edge 5G Core is supported only for on-premises deployment on ONYX-ES hardware. Deployment Models: * **Onyx Edge NR+Core** — This is GXC's standard 5G deployment model, in which the Onyx Edge hosts both the 5G Core and gNB functions. The Central Unit (CU) and Distributed Unit (DU) functions run on the Onyx Edge platform, while the Radio Unit (RU) provides the radio interface to user equipment (UE). This model provides a compact and integrated solution that simplifies installation while supporting full 5G standalone functionality. * **Onyx Edge Core** — In this model, the Onyx Edge provides only the 5G Core network functions and interfaces with an external gNB infrastructure. This architecture enables integration with third-party radio access equipment and supports modular network deployments. GXC provides limited support for this deployment model. For details, contact GXC Technical Support. {% hint style="info" %} **NOTE:** In this release, Onyx Edge 5G is supported only for on-premises deployment on ONYX-ES hardware. Cloud-native deployment is not yet supported. {% endhint %} ## Fronthaul Multiplexer (FHM) The Fronthaul Multiplexer (FHM) is used in deployments that implement disaggregated RAN architectures with separate Radio Units (RUs) and Distributed Units (DUs). The FHM aggregates multiple fronthaul connections from RUs and consolidates them into a single interface toward the DU or integrated CU/DU system. Key Functions: * **Fronthaul Aggregation** — Aggregates high-bandwidth fronthaul traffic from multiple RUs into a single uplink toward the DU. * **Precision Timing and Synchronization Optimization** — Provides precise timing synchronization using mechanisms such as IEEE 1588 Precision Time Protocol (PTP) or SyncE, which are required for time-division duplex (TDD) coordination and beamforming. * **Scalable Deployment** — Supports deployment of multiple RUs across large sites or campuses while maintaining centralized DU or CU processing. Deployment Scenarios: * In large-scale indoor deployments, the FHM simplifies cabling and centralizes fronthaul management for ceiling- or wall-mounted RUs. * In industrial outdoor environments, the FHM connects ruggedized RUs to a centrally located DU for streamlined network control and performance. By decoupling the RU from the DU while maintaining high fronthaul fidelity, the FHM plays a pivotal role in delivering modular, scalable, and high-performance 5G networks tailored for complex enterprise needs. ## 5G RAN Architecture – CU, DU, and RU GXC's 5G solution implements the disaggregated Radio Access Network (RAN) architecture defined by 3GPP and O-RAN standards. This architecture separates the traditional baseband processing into three functional components: * **Radio Unit (RU)** — The RU provides radio frequency (RF) transmission and reception functions, including analog/digital conversion and beamforming. The RU is deployed at the network edge (e.g., light poles, towers, building rooftops) and connects to the DU over the fronthaul (e.g., eCPRI or Ethernet) interface. * **Distributed Unit (DU)** — The DU is responsible for real-time processing tasks such as scheduling, MAC, and portions of the PHY layer. It is often deployed close to the RU (in the field or at edge data centers) to minimize latency. GXC's DU software runs on COTS hardware, either co-located with or separate from the RU. * **Central Unit (CU)** — The CU performs non-real-time functions including RRC signaling, mobility control, and interface management with the 5G Core. It connects with the DU via the midhaul interface and typically resides in a centralized location, such as an enterprise data center or cloud region. The GXC architecture supports multiple RAN deployment configurations, including: * Integrated CU+DU+RU on Onyx Edge NR+Core for compact, turnkey deployments * Split CU/DU with external RU for hybrid and distributed topologies * Compatibility with O-RAN compliant third-party RUs in Onyx Edge Core deployments This flexible architecture enables enterprises to optimize deployments based on coverage requirements, latency constraints, and physical site characteristics. ## 5G Access Points GXC 5G Access Points function as gNB radio access nodes within the network. Depending on the deployment architecture, these devices may incorporate RU functionality or operate as integrated gNB nodes supporting CU, DU, and RU components. GXC 5G access infrastructure supports 5G NR frequency bands including n48 (CBRS), n77, n78. They support advanced features such as multiple-input multiple-output (MIMO) antenna systems and beamforming technologies to improve coverage and network capacity. Select 5G APs can also operate as Mesh APs, serving as gateway nodes for Mesh Node backhaul. This mode is currently supported on the G228 low-power outdoor AP and the G244 high-power outdoor AP. GXC's 5G AP lineup includes indoor APs with a compact form factor, ideal for smart factories and large indoor spaces, and ruggedized outdoor APs for industrial yards, campuses, and extended-range needs. ### 5G Mesh Nodes Mesh Nodes enable wireless backhaul for APs where wired connectivity is unavailable. Each Mesh Node integrates a G244 or G228 AP with a mesh-capable radio to wirelessly connect back to the Onyx Edge. Using self-interference mitigation techniques, Mesh Nodes support simultaneous access and wireless backhaul traffic over the same CBRS band. This architecture supports flexible and rapid deployment of network infrastructure, making it ideal for temporary setups or complex physical environments. 5G Onyx networks support the Mesh Node GM03, a hardened mesh node providing higher power output and improved backhaul performance for demanding outdoor or industrial environments. For more information, see the *GM03 Mesh Node Hardware Installation and Configuration Guide*. {% hint style="info" %} **NOTE:** Mesh Node GM03 is available only for early adopter trials in this release. For more information, contact GXC Technical Support. {% endhint %} ## Spectrum Access and SAS Integration For deployments operating in CBRS Band 48, the GXC solution integrates with certified Spectrum Access Systems (SAS) for dynamic spectrum allocation and interference coordination. The SAS integration enables automated spectrum authorization and real-time coordination with other CBRS systems, ensuring compliance with FCC regulatory requirements. SAS registration is handled seamlessly via the Onyx Platform, simplifying deployment and ongoing operation. ## Subscriber and SIM Management The Onyx system supports physical SIM cards and embedded SIM (eSIM), with centralized policy management via the Onyx Portal. The UDM and AUSF functions in Onyx Edge manage subscriber identities, profiles, and authentication, while network slicing and QoS are enforced to match enterprise-level access control policies. ## Onyx Orchestrator The Onyx Orchestrator is GXC's cloud-hosted backend service that manages the entire network infrastructure. It maintains configuration data, synchronizes settings across network components, and ensures policy enforcement. Onyx Edge and APs communicate regularly with the orchestrator to report their operational status and receive configuration updates. This orchestration layer is critical for maintaining network integrity, applying real-time configuration changes, and monitoring performance metrics. ## Onyx Portal The Onyx Portal provides a centralized, web-based interface for monitoring and managing the private network. It is designed for intuitive control and visibility across all connected components, enabling simplified operation of enterprise private 5G deployments. --- # 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/5g-onyx-portal-4.x-operations/overview.md?ask=&goal= ``` `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.