AR Remote Expert Assist
Overview
Specialist expertise is scarce, and it is almost never in the same building as the problem. A machine goes down, and the person who understands it is three time zones away. The options are to fly them in (losing a day or a week of production) or to talk the local technician through it on a phone call, which works about as well as describing a knot over the radio.
Remote expert assist replaces the phone call with shared sight. The technician wears a headset or holds a tablet; the expert sees exactly what they see, in real time, and annotates it, drawing on the actual component, placing an arrow on the actual valve, overlaying the schematic on the actual panel. The annotation stays anchored to the object as the technician moves. Hands stay on the work.
This is the workflow with the tightest latency requirement in this section, and the reason is human perception rather than machine control. An annotation that lags the technician's head movement does not merely feel wrong; it induces discomfort within minutes and the headset comes off. The 10 ms packet delay budget of the low-latency eMBB QoS class exists for exactly this class of application, and it is only achievable with the rendering and session infrastructure on the edge, next to the radio.
How It Works
The latency chain
What each component does
Headset or tablet
The technician's endpoint at the asset. Captures the live view, displays annotations anchored to real components
Onyx RU
Coverage where the equipment is: plant rooms, machine halls, basements, roof plant. Rarely where coverage is best
FHM / shared cell
The technician walks around the machine without handover, so the spatial anchor and the session hold
Onyx Edge · 5G Core
5QI 80: non-GBR low-latency eMBB with a 10 ms packet delay budget: the 3GPP class defined for augmented reality
Session and rendering service
On the Onyx Edge. This is the component that makes the budget achievable at all
Expert workstation
On site, at a regional support center, or at a vendor's support desk
Content library
Pre-authored overlays: schematics, exploded views, work instructions, torque specifications
CMMS / EAM
Sessions and outcomes recorded against the asset
Onyx Portal
Latency, jitter, and throughput per session, so a poor session is diagnosed rather than tolerated
The session path, hop by hop
1
Technician → Headset
Camera + IMU
Live view captured; head pose tracked
2
Headset → Onyx RU
5G NR Uu, symmetric
10–25 Mbps per session on the 5QI 80 bearer. Roughly balanced up and down, unlike most workflows here
3
RU → Onyx Edge
eCPRI, aggregated fronthaul
No handover as the technician moves around the asset
4
UPF → Session service
N6 local breakout
Session and rendering on the appliance beside the core
5
Session service → Expert
IP
Expert receives the technician's live view
6
Expert → annotates
Annotation on the shared spatial anchor
Arrows, outlines, and text attached to real components
7
→ Rendered at the edge
Composition
Overlay composed against the current head pose
8
→ Headset
Downlink on the same bearer
Annotation appears anchored to the object and stays anchored as the technician moves
The budget, stage by stage
Capture
3–5 ms
5G uplink
4–6 ms
Edge render
3–6 ms
5G downlink
4–6 ms
Display
2–4 ms
Motion-to-photon
< 20 ms
End-to-end annotation latency
< 100 ms from expert action to technician display
Why 20 ms is a threshold, not a target
Above roughly 20 ms motion-to-photon, users report discomfort within minutes and the headset comes off. This is not a quality target that can be traded for capacity: it is the point at which the workflow stops being used, and everything else on this page is subordinate to it.
Which is why edge rendering is not an optimization here. A wide-area round trip to a cloud region consumes the entire budget before any processing happens. If the session and rendering infrastructure cannot be hosted on the Onyx Edge, the right answer is a tablet-based workflow with a relaxed budget, not a headset experience that will be rejected.
A tablet delivers most of the value anyway. It works everywhere, needs no head-mounted hardware in a hard-hat area, and removes the motion-to-photon constraint almost entirely. Start with tablets; add headsets where hands-free is genuinely required.
Network Requirements
Per-session throughput
10–25 Mbps, roughly symmetric
Aggregate, 10 concurrent sessions
100–250 Mbps
One-way network latency
< 20 ms
Motion-to-photon latency
< 20 ms for headset-rendered content
End-to-end annotation latency
< 100 ms from expert action to technician display
Jitter
< 10 ms
Packet error rate
10-6
Availability during a session
99.9%
AR QoS
5QI 80: non-GBR, low-latency eMBB, 10 ms PDB, 10-6 PER, priority 68
Conversational video QoS
5QI 2: GBR, 150 ms PDB
Voice QoS
5QI 1: GBR, 100 ms PDB
TDD pattern
Symmetric or lightly uplink-weighted, DDSUU
Bands
n77, n78, n48 (CBRS), n40
Deploying It
Define eligible procedures
Identify where the workflow pays: high-value assets where downtime is expensive, procedures needing rarely-available expertise, commissioning and acceptance. Then define which procedures are approved for remote support and which require physical attendance regardless. That is a competence and safety decision, agreed with plant safety before deployment, so the boundary is not decided under pressure during a breakdown.
Define the external expert path deliberately
Live video of production equipment leaving the site to a vendor's support desk is a security and commercial decision. Define the path, the authentication, the recording policy, and what the external party may retain, before the first session, not during an outage.
Run sessions and record them
The technician works hands-free; the expert confirms each step visually rather than by description. Where a procedure exceeds remote support it escalates to attendance, with the diagnosis already complete, which is a saving even when travel still happens. Record findings and actions against the asset in the CMMS.
Devices & Ecosystem
AR headsets: hands-free, and where the environment demands it, intrinsically safe or hard-hat mounted.
Rugged 5G tablets: the pragmatic alternative where a headset is impractical or unwelcome; most of the value at a fraction of the friction.
Remote expert platform: session management, annotation, and recording, hosted on Onyx Edge.
Expert workstation: on site, at a regional support center, or at a vendor's support desk.
Content authoring: for pre-built overlays, work instructions, and 3D models.
CMMS / EAM integration: sessions and outcomes recorded against the asset.
Digital twin or 3D model source: where overlays are generated from engineering models rather than authored by hand.
Design Considerations
The latency budget is a human factors requirement. Above roughly 20 ms motion-to-photon, users report discomfort, and headsets come off. This is not a quality target that can be relaxed for capacity; it is the threshold at which the workflow stops being used. Everything else on this page is subordinate to it.
Edge rendering is what makes the budget achievable. The wide-area round trip to a cloud region consumes the entire budget before any processing happens. The session and rendering infrastructure must be on the Onyx Edge. If it cannot be, choose a tablet-based workflow with a relaxed budget instead of shipping a headset experience that will be rejected.
Coverage where the equipment is. Plant rooms, machine halls, basements, and roof plant are where this workflow happens and where coverage is typically weakest. Survey those, not the office floor.
AR is symmetric; most of this site's workflows are not. A campus TDD pattern optimized for surveillance uplink will handicap the downlink that carries annotations and overlays. Where AR is a primary workflow, plan the TDD split for it, and where it shares a carrier with heavy uplink workflows, verify the AR session under that load rather than in isolation.
A tablet delivers most of the value. Headsets are better when they fit the environment and the technician accepts them. Tablets work everywhere, need no head-mounted hardware in a hard-hat area, and remove the motion-to-photon constraint almost entirely. Start with tablets, add headsets where hands-free is genuinely required.
Design the external expert path deliberately. Live video of production equipment leaving the site to a vendor's support desk is a security and commercial decision. Define the path, the authentication, the recording policy, and what the external party may retain, before the first session, not during an outage.
The library is the compounding return. Live assist saves a trip. A library of recorded sessions and authored overlays saves the call. Budget authoring time from the start, and treat each session as an opportunity to add to it.
Approve procedures explicitly. Some work requires a qualified person physically present regardless of how good the video is. Define which procedures are eligible for remote support with plant safety and competence management before deployment, so the boundary is not decided under pressure during a breakdown.
Validation Checklist
Next steps
Size it. Take these requirements through Plan Your Network: capacity, coverage, architecture, and a preliminary bill of materials.
Compare it. Network Requirements at a Glance puts every workflow side by side, for sites carrying more than one.
Talk to us. For a validated design and a quote, contact GXC.
Related reading
Was this helpful?