URLLC
Also known as: Ultra-Reliable Low-Latency Communication
A 5G service category engineered to deliver extremely low latency and extremely high reliability, typically around 1 millisecond air-interface latency with 99.999% reliability, for applications where message timeliness and delivery certainty are operationally critical.
- One of three headline 5G service categories, alongside enhanced Mobile Broadband (eMBB, prioritizing throughput) and massive Machine-Type Communication (mMTC, prioritizing device density), each optimized for a different combination of latency, reliability, throughput, and device density
- Targets latency and reliability figures — commonly cited around 1 millisecond air-interface latency with 99.999% reliability — far beyond what general mobile broadband service requires or is optimized for
- Achieving these targets typically requires trading away throughput and spectral efficiency, since techniques that improve reliability and reduce latency (shorter transmission intervals, aggressive retransmission schemes, dedicated resource reservation) consume capacity that could otherwise carry more data
- Initially defined in Release 15 and significantly enhanced in Release 16 specifically to meet the more demanding requirements industrial automation use cases require beyond the initial baseline
- A network slice or dedicated resource allocation is commonly used to guarantee URLLC performance characteristics for specific traffic, rather than expecting best-effort network capacity to reliably meet URLLC targets
Where enhanced mobile broadband optimizes for raw throughput and massive machine-type communication optimizes for supporting enormous numbers of simple, infrequent-reporting devices, URLLC optimizes for the specific combination of speed and certainty that safety-critical and industrial control applications need — a remote-controlled machine or a safety interlock signal needs its command delivered within a tight, guaranteed time window far more than it needs high throughput, and URLLC's design tradeoffs reflect that priority explicitly.
The reliability and latency targets URLLC pursues come at a real, unavoidable capacity cost, which is why URLLC traffic is typically isolated through network slicing or dedicated resource reservation rather than competing for capacity alongside best-effort mobile broadband traffic — mixing URLLC's latency-sensitive, reliability-critical traffic with general best-effort traffic on shared, contended resources would undermine the very guarantees URLLC exists to provide. This is conceptually the wireless counterpart to what time-sensitive networking accomplishes on wired industrial Ethernet — both exist because standard best-effort networking, whether wireless mobile broadband or standard Ethernet, cannot reliably guarantee the timing determinism industrial control applications require, and both solve this through dedicated scheduling and resource reservation rather than simply adding more capacity. For CE verticals, URLLC capability is directly relevant wherever wireless connectivity needs to support real-time industrial control — remote equipment operation in mining and energy sites, safety interlock signaling, and time-critical automation — applications where a "good enough most of the time" connectivity profile is operationally unacceptable regardless of average network performance.
URLLC. ConnectedEarth Knowledge Base. https://connectedearth.space/knowledge-base/urllc/ (updated 13 September 2026).