Beyond the Hype: Use Cases That Are Live in Production
The 5G promise of eMBB, URLLC, and mMTC has matured from proof-of-concept trials into revenue-generating production deployments. This article catalogs ten use cases that are actively operational as of early 2026, mapping each to its 3GPP service category, QoS requirements per 3GPP TS 23.501 clause 5.7 (5QI values), network slice type per 3GPP TS 23.501 clause 5.15, and at least one real-world operator deployment. We include detailed technical analyses for manufacturing and healthcare to illustrate how KPI requirements translate into network configuration.
Master Use Case Table
| # | Use Case | 3GPP Category | Required DL (Mbps) | Required Latency (ms) | Reliability | 5QI Value | S-NSSAI SST | Operator Example |
|---|---|---|---|---|---|---|---|---|
| 1 | Enhanced Mobile Broadband (FWA) | eMBB | 100--300 | < 20 | 99.9% | 9 (default) | SST=1 (eMBB) | T-Mobile US (Home Internet) |
| 2 | Immersive Stadium Experience | eMBB | 50--150 per user | < 15 | 99.9% | 7 | SST=1 | SK Telecom (Seoul World Cup Stadium) |
| 3 | Autonomous Mobile Robots (AMR) | URLLC | 10--50 | < 5 | 99.999% | 84 | SST=2 (URLLC) | Siemens + Deutsche Telekom (Amberg) |
| 4 | Remote Robotic Surgery | URLLC | 20--100 | < 2 | 99.9999% | 82 | SST=2 | China Mobile (PLA Hospital, Beijing) |
| 5 | Smart Port Container Tracking | mMTC + eMBB | 5--20 | < 50 | 99.9% | 9 | SST=3 (mMTC) | China Unicom (Qingdao Port) |
| 6 | Connected Vehicles (V2X) | URLLC | 10--50 | < 3 | 99.999% | 83 | SST=2 | KT (Seoul C-V2X pilot) |
| 7 | Private 5G Smart Factory | URLLC + eMBB | 50--200 | < 5 | 99.999% | 85 | SST=1 + SST=2 | Nokia + Lufthansa Technik (Hamburg) |
| 8 | AR/VR Cloud Rendering | eMBB | 200--1000 | < 10 | 99.99% | 6 | SST=1 | Verizon (NFL Stadiums, 5G Ultra Wideband) |
| 9 | Massive IoT Smart Metering | mMTC | 0.01--0.1 | < 10,000 | 99.9% | 9 | SST=3 | Vodafone Germany (NB-IoT, 700k meters) |
| 10 | Network Slicing as a Service | All | SLA-dependent | SLA-dependent | SLA-dependent | Per-slice | Operator-defined | SK Telecom (slicing marketplace) |
The 5QI (5G QoS Identifier) values above are standardized in 3GPP TS 23.501 Table 5.7.4-1. Values 1--9 are non-GBR (Guaranteed Bit Rate) flows suitable for best-effort broadband, while values 65--89 are GBR flows designed for deterministic services like URLLC.
Detailed Example 1: Smart Factory -- Siemens Amberg Plant
Siemens's electronics factory in Amberg, Germany, partnered with Deutsche Telekom to deploy a private 5G SA network on band n78 (3.7 GHz) with 100 MHz bandwidth. The factory operates over 1,200 autonomous mobile robots (AMRs) that transport components between production lines.
Network configuration:- RAN: 12 indoor gNBs with 32T32R Massive MIMO panels, cell radius 40--80 m.
- Core: On-premises 5G Core (UPF co-located at factory edge), AMF/SMF in Deutsche Telekom regional DC.
- Slice: Dedicated URLLC slice with SST=2, SD=0x000001. PDU session type IPv4, DNN = "amr-control".
- QoS: 5QI=84 (delay-critical GBR), GFBR = 10 Mbps DL / 5 Mbps UL, PDB = 5 ms, PER = 10^-5.
| Component | Latency (ms) |
|---|---|
| Sensor capture + encoding | 0.8 |
| UE UL processing (SCS 30 kHz) | 0.5 |
| Air interface UL (1 slot) | 0.5 |
| gNB-to-UPF (fronthaul + backhaul) | 0.3 |
| Edge application processing | 1.5 |
| UPF-to-gNB DL | 0.3 |
| Air interface DL (1 slot) | 0.5 |
| UE DL processing + actuator command | 0.6 |
| Total round-trip | 5.0 |
This timing budget meets the 5 ms URLLC requirement defined in 3GPP TR 22.804 clause 5.2 for factory automation. Siemens reported a 15% increase in production throughput and a 40% reduction in AMR collision events after migrating from Wi-Fi 6 to 5G SA, primarily due to deterministic latency and seamless handover between cells.
Worked capacity calculation for the Amberg floor:The factory floor spans 10,000 m-squared. With 1,200 AMRs each requiring 10 Mbps DL GBR:
- Total DL demand: 1,200 x 10 Mbps = 12 Gbps.
- Per gNB capacity (100 MHz, 32T32R, MU-MIMO, 8 UE pairing): approximately 2.8 Gbps DL with realistic scheduling.
- Required gNBs: 12 Gbps / 2.8 Gbps = 4.3 -- rounded up to 5 for coverage redundancy.
- Deployed: 12 gNBs (providing 2.4x capacity margin and N+1 redundancy).
Detailed Example 2: Remote Surgery -- China Mobile
China Mobile partnered with the PLA General Hospital in Beijing to demonstrate 5G-assisted robotic surgery, performing a procedure where the surgeon operated from a console 50 km away. The system uses a dedicated URLLC slice with the following configuration:
Network parameters:- Band: n41 (2.6 GHz), 160 MHz bandwidth.
- Slice: SST=2, 5QI=82 (delay-critical GBR with PDB = 2 ms, PER = 10^-6).
- Redundancy: Dual PDU sessions over two independent gNBs for path diversity (per 3GPP TS 23.501 clause 5.33 redundant transmission).
- Edge compute: Surgical control application at MEC node within 5 km of hospital, 0.3 ms fiber latency.
| Segment | Latency (ms) |
|---|---|
| Haptic encoder (surgeon console) | 0.3 |
| UE UL processing (SCS 30 kHz) | 0.4 |
| Air interface UL (mini-slot, 2 symbols) | 0.07 |
| Transport to MEC | 0.3 |
| Surgical AI processing | 0.5 |
| MEC to remote hospital gNB (50 km fiber) | 0.25 |
| Air interface DL (mini-slot) | 0.07 |
| Robot arm actuator response | 0.3 |
| Total one-way | 2.19 |
The 2.19 ms one-way latency marginally exceeds the 2 ms target, but with pre-buffering of haptic feedback at the surgeon console (adding 0.5 ms perceived latency), the system operates within clinically acceptable bounds per IEEE 1918.1 tactile internet standards.
China Mobile reported successful completion of over 200 remote procedures across 15 hospitals by end of 2025. The dual-PDU-session redundancy achieved 99.9999% reliability over 10,000 hours of operation.
Stadium Use Case: SK Telecom Multi-View
SK Telecom deployed 5G at Seoul World Cup Stadium with 48 mmWave gNBs (n257, 28 GHz) and 24 mid-band gNBs (n78, 3.5 GHz) to serve 60,000 spectators. Each user can access multi-angle replays streamed at 150 Mbps per view.
Capacity planning:- Simultaneous active users (peak): 15,000 (25% of stadium).
- Per-user DL: 50 Mbps average (multi-view streaming).
- Aggregate demand: 750 Gbps.
- mmWave sector capacity (400 MHz, 8 layers, 256QAM): ~8 Gbps per sector.
- Mid-band sector capacity (100 MHz, 4 layers): ~2.8 Gbps per sector.
- Total capacity: (48 x 3 sectors x 8 Gbps x 0.6 utilization) + (24 x 3 sectors x 2.8 Gbps x 0.6 utilization) = 691 + 121 = 812 Gbps.
This provides a 1.08x margin over peak demand, which is tight but supplemented by MEC caching of popular replay angles (reducing backhaul by 70%).
Port Automation: China Unicom at Qingdao
China Unicom's 5G deployment at Qingdao Automated Container Terminal covers 4.5 km-squared of port area with 36 macro gNBs on n78. The system handles:
- Remote-control crane operations (12 cranes, each requiring 20 Mbps UL for 4K camera feeds and < 20 ms round-trip latency).
- Container tracking via 5G RedCap sensors (per 3GPP TS 38.300 clause 4.4a) -- 50,000 sensors at 100 bytes per report, 1 report per minute.
- AGV (Automated Guided Vehicle) navigation: 35 AGVs with URLLC slice, 5QI=85, PDB = 10 ms.
China Unicom reported 30% faster container turnaround time and a 50% reduction in labor costs for crane operations after full 5G migration from Wi-Fi + LTE.
5G QoS Architecture Enabling These Use Cases
All ten use cases rely on the 5G QoS framework defined in 3GPP TS 23.501 clause 5.7. The key difference from LTE's QCI model is per-flow QoS rather than per-bearer QoS. Each PDU session can carry multiple QoS flows, each identified by a QFI (QoS Flow Identifier) mapped to a 5QI.
| QoS Attribute | LTE (EPC) | 5G (5GC) | Benefit |
|---|---|---|---|
| Granularity | Per-bearer (EPS bearer) | Per-flow (QoS flow) | Finer control, less signaling |
| Identifier | QCI (1--9 standard) | 5QI (1--255, 1--89 standardized) | More service types |
| Reflective QoS | Not supported | Supported (clause 5.7.5) | Reduced signaling for UL |
| Notification control | Limited | MFBR/GFBR notifications | Dynamic rate adaptation |
| Slice awareness | Not applicable | Per-slice QoS policy | Isolation between services |
This per-flow model enables a single UE to simultaneously participate in an eMBB video stream (5QI=9) and a URLLC control channel (5QI=84) without requiring separate bearers -- a fundamental enabler for multi-service use cases like smart factories.
Emerging Revenue Models
SK Telecom launched a network slicing marketplace in 2025, allowing enterprise customers to self-provision slices with guaranteed KPIs via API (per 3GPP TS 29.536 NSSF services). Pricing is based on a combination of bandwidth commitment, latency SLA, and reliability tier. Early adopters include automotive OEMs (V2X slices at $8,000/month) and media companies (eMBB stadium slices at event-based pricing).
T-Mobile US reported $3.2 billion in Fixed Wireless Access (FWA) revenue for 2025, serving 6.2 million home internet subscribers -- the largest single 5G revenue category outside traditional mobile broadband for any US operator.
Summary
These ten use cases demonstrate that 5G has moved beyond technology demonstration into measurable business impact. The combination of network slicing, per-flow QoS, edge computing, and flexible numerology allows a single physical network to serve radically different service requirements -- from sub-2 ms surgery control to 10-second smart meter reports. Understanding the mapping between use case KPIs, 5QI values, slice types, and deployment architectures is critical for certification and for designing production 5G networks.