Description
HRLLC, Hyper Reliable and Low Latency Communication, is a Rel-20 concept studied in 3GPP TR 38.914 that defines a service class demanding reliability and latency performance beyond the existing URLLC (Ultra-Reliable Low-Latency Communication) framework. While URLLC in 5G targets use cases such as factory automation and remote control with reliability around 99.999% and latency in the low milliseconds, HRLLC pushes toward even tighter bounds — for example, sub-millisecond latency and reliability approaching or exceeding 99.9999% — to support the most demanding cyber-physical applications.
Technically, HRLLC is not a single feature but a performance envelope that spans multiple layers of the protocol stack. At the physical layer, achieving hyper reliability requires robust modulation and coding, diversity across time, frequency, and space, and possibly redundant transmissions. Low latency requires short transmission time intervals, fast processing, and minimized HARQ round-trip times. At the MAC and RLC layers, scheduling must prioritize HRLLC traffic and avoid retransmission delays that would violate the latency budget. At the core network, QoS flows and 5G QoS Identifiers (5QIs) must be configured to guarantee the required treatment end to end.
The study in TR 38.914 examines whether the existing 5G NR framework can meet HRLLC requirements or whether new mechanisms are needed. Candidate techniques include enhanced scheduling, pre-emption, configured grants, and multi-connectivity across multiple transmission points. Deterministic networking concepts, such as those developed in IEEE 802.1 Time-Sensitive Networking (TSN), are also relevant because HRLLC applications often require bounded latency and jitter, not just low average latency.
HRLLC is closely related to URLLC but distinguished by its more extreme targets. It also overlaps with the broader 6G vision, where hyper-reliable and low-latency communication is expected to support immersive applications, collaborative robotics, and real-time control of critical infrastructure. The Rel-20 study is therefore both a refinement of 5G URLLC and a bridge toward 6G service requirements.
For network designers, HRLLC implies careful end-to-end engineering: radio access, transport, and core must all be dimensioned to meet the reliability and latency budget, and redundancy must be built in where a single failure would violate the guarantee. For vertical industries, HRLLC is the enabler for applications where a missed deadline or a lost packet has physical consequences, such as motion control in manufacturing, tele-surgery, or power grid protection.
Purpose & Motivation
HRLLC exists because some applications cannot tolerate even the small residual error and latency of URLLC. In industrial control, a command that arrives a few milliseconds late can cause a production line to malfunction; in power systems, a protection signal that is lost can damage equipment. URLLC was designed for reliability around 99.999% and latency of a few milliseconds, but emerging use cases demand tighter bounds.
The motivation for studying HRLLC in Rel-20 comes from two directions. First, vertical industries have continued to push requirements upward as they digitize more critical processes. Second, 6G research has identified hyper-reliable low-latency communication as a core capability, and 3GPP wants to understand the gap between current 5G performance and future needs. TR 38.914 provides a structured study of those requirements and potential solutions.
By defining HRLLC as a distinct service class, 3GPP gives operators and vendors a target to design against, and gives industries a vocabulary for specifying their needs. It also helps ensure that future releases can evolve the 5G system incrementally rather than requiring a disruptive redesign.
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference HRLLC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 38.914 vk10 | 6G Radio Scenarios and Requirements | Rel-20 read |