Introduction

Every workflow in this section runs on the same GXC Onyx private 5G platform. They differ in their acceptance criteria, not in the radio.

A broadcast camera needs 25 Mbps of sustained uplink inside a 200 ms glass-to-glass budget. An AGV needs 2 Mbps inside a 10 ms budget with no handover gap. Those two requirements produce different TDD patterns, different QoS policies, and different RU layouts on the same hardware. These pages document that difference, workflow by workflow.

How to read a workflow page

Every page follows the same structure, so you can compare workflows directly. The first half answers how it works; the second answers how to deploy it.

Section	What it answers
Overview	What the workflow replaces, and why private 5G is the right transport for it
How It Works
· Reference architecture	A diagram of what connects to what
· What each component does	One line per block in the diagram
· The path, hop by hop	Every hop from source to destination - the actual interface at each one, and what happens there
· Where the latency goes	The end-to-end budget broken down by stage
· The decision that defines the design	The one architectural choice that determines whether the deployment works
Network Requirements	Throughput, latency, jitter, loss, availability, and 3GPP 5QI mapping
Deploying It	The sequence that gets it running, from survey to teardown
Devices & Ecosystem	The endpoint and application classes that terminate the workflow
Design Considerations	The decisions that determine whether the deployment succeeds
Validation Checklist	What to measure before you declare the workflow production-ready

Every diagram is also kept as an editable draw.io source alongside the published page.

Workflows by industry

Broadcast & Live Events

Live Video ProductionWireless Intercom and Talkback

Manufacturing

AGV and AMR fleet controlVisual Daily Inspection

Construction & Infrastructure

Drone Site InspectionJobsite Surveillance and Progress Capture

Enterprise & Campus

AR Remote Expert AssistCampus Video Surveillance

The three properties that carry every workflow

Across all ten workflows, the same three platform properties do the heavy lifting.

Local breakout at the edge. Onyx Edge integrates the 5G Core with the CU and DU in a single on-site appliance. Application traffic never leaves the site, so the latency budget is set by the radio and the application - not by a backhaul link to a regional data center. For AGV control and live talkback, this is the difference between working and not working.

Shared cell, not many cells. The Onyx shared-cell architecture presents multiple RUs as a single logical cell under one DU. Devices moving across a factory floor, a warehouse aisle, or an outside broadcast compound do not perform inter-cell handover, because there is no cell boundary to cross. Handover gaps are the most common cause of dropped video frames and stalled AGVs - this architecture removes the failure mode rather than tuning around it.

Per-workflow QoS. Onyx maps each application to a 3GPP 5QI with its own priority, packet delay budget, and error rate. A camera contribution flow, a push-to-talk floor grant, and a bulk firmware download share the same spectrum without competing for it. The Network Requirements at a Glance page lists the mapping for every workflow in this section.

Where to go next

These pages describe what each workflow demands of a network. Turning that into a design - a radio count, an architecture, and a bill of materials - is the subject of the Getting Started section.

Next	Why
Plan Your Network	Take a workflow's requirements through Capacity → Coverage → Architecture → Accessories to a preliminary BoM
Is Onyx right for you?	Check the fit before designing - private cellular against Wi-Fi, and LTE against 5G
Private 5G Spectrum	Which band you can obtain, and what channel bandwidth it gives you to work with
Deploy Your First Network	The sequence from installed hardware to a network carrying the workflow
End Devices	Whether the endpoints a workflow depends on support your band

Where a workflow's requirements are tighter than a single cell can deliver, the 5G Onyx Shared Cell / Super Cell Architecture Solution Brief covers how multiple RUs combine into one logical cell.

Contact GXC

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