URLLC

Ultra Reliable Low Latency Communication

Services →
Introduced in Rel-14 Also in: Services, Core Network, Security

URLLC is a 3GPP service category for mission-critical applications that require extremely high reliability and very low latency, enabling uses like industrial automation and autonomous vehicles.

Category
Services
Introduced
Rel-14
Where
Radio Access Network › NG-RAN (5G)
Also touches
3 segments
Specifications
23 specs
URLLC Description Purpose Related Detected Changes Specifications

Description

Ultra Reliable Low Latency Communication (URLLC) is a foundational service category within the 5G system architecture, defined to support applications with stringent requirements for end-to-end latency, reliability, and availability. Unlike enhanced Mobile Broadband (eMBB) which focuses on high data rates, URLLC prioritizes deterministic performance, often targeting latencies as low as 1 millisecond for the radio interface and reliability levels up to 1-10^-5 or 1-10^-6 (99.999% to 99.9999% success probability). The architecture supporting URLLC permeates both the Radio Access Network (RAN) and the Core Network (5GC), requiring coordinated enhancements in scheduling, transmission schemes, and network resource management.

At the physical and MAC layer, URLLC employs several key techniques to achieve low latency. These include grant-free or configured grant uplink transmissions, which allow a User Equipment (UE) to transmit data immediately without waiting for a scheduling grant, drastically reducing signaling delay. Short Transmission Time Intervals (TTIs), such as mini-slots, enable faster packet encoding and decoding. For reliability, robust modulation and coding schemes (MCS), along with techniques like repetition coding, frequency diversity, and multi-connectivity (where a UE is simultaneously connected to multiple gNBs or cells), are utilized. Packet duplication over multiple paths, managed by the Packet Data Convergence Protocol (PDCP) layer, is a critical feature where identical data packets are sent via different radio links or carriers to increase the chance of successful delivery.

In the Core Network, URLLC support involves network functions like the Access and Mobility Management Function (AMF) and Session Management Function (SMF) being aware of URLLC Quality of Service (QoS) profiles. The 5G QoS Identifier (5QI) includes standardized values specifically for URLLC flows, which map to precise packet delay budget, packet error rate, and default priority levels. The core network ensures that user plane functions (UPF) are deployed appropriately, potentially using edge computing (via Multi-access Edge Computing - MEC) to localize traffic processing and further reduce latency. Network slicing is intrinsically linked with URLLC, allowing the creation of dedicated, logically isolated network slices with reserved resources and tailored configurations to guarantee the required performance independently from other service types.

Purpose & Motivation

URLLC was created to address the growing demand for wireless connectivity in industrial and mission-critical applications that cannot tolerate the variable latency and reliability of traditional mobile broadband services. Prior to 5G, cellular networks (2G, 3G, 4G) were optimized for human-centric communication—voice and mobile internet—where delays of tens or hundreds of milliseconds were acceptable. The advent of Industry 4.0, autonomous systems, and remote real-time control exposed the limitations of these networks for applications like factory automation, smart grids, and tele-surgery, where a missed deadline or a lost packet could lead to catastrophic failure, safety hazards, or significant economic loss.

The motivation for standardizing URLLC within 3GPP, starting from Release 14 as a study item and evolving through subsequent releases, was to transform cellular technology into a universal connectivity fabric capable of supporting both human and machine-type communication with guaranteed performance. It solves the problem of providing 'deterministic' wireless communication over a shared, statistical multiplexing medium. By defining clear targets and standardizing the enabling mechanisms across the entire protocol stack, URLLC allows diverse vertical industries to rely on 5G as a replacement for or complement to wired fieldbus systems (like PROFINET, EtherCAT) and proprietary wireless solutions, enabling greater flexibility, mobility, and scalability in automated environments.

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (32 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 2 changes

In Release 15, foundational enhancements for URLLC were introduced, including specific fixes for 5G Quality of Service (QoS) attributes such as Packet Delay Budget (PDB), Packet Error Rate (PER), Maximum Data Burst Volume (MDB), and the standardized 5G QoS Identifier (5QI). Additionally, the release defined new capabilities for Channel Quality Indicator (CQI) and Modulation and Coding Scheme (MCS) specifically optimized to meet the stringent reliability and latency requirements of URLLC services.

  • 5G QoS fixes for URLLC services related attributes - PDB, PER, MDB, 5QI TS 23.501CR0087
  • CQI and MCS for URLLC TS 38.300CR0154
Rel-16 18 changes

In Release 16, the URLLC function was enhanced with the introduction of QoS Monitoring to assist the URLLC service, including specific support for monitoring on the GTP-U path. The release also defined optimizations for handling redundancy, such as associating URLLC traffic to redundant PDU sessions and new procedures for PDU session failure handling and UPF selection. Furthermore, it provided clarifications on URLLC support and introduced interworking with TSN (Time-Sensitive Networking) through ETSUN.

  • New clause for URLLC supporting TS 23.501CR0810
  • Introduction of QoS Monitoring to assist URLLC Service TS 23.501CR0990
  • New Solution for Key Issue #7-URLLC Always on Control for the GBR QoS Flow TS 23.725CR0015
  • QoS Monitoring support for URLLC TS 29.512CR0338
  • Security of 5G URLLC TS 33.501CR0783
  • 5G URLLC: Optimizing Redundancy TS 23.501CR1217

+ 12 more changes

Rel-17 3 changes

In Release 17, the URLLC function was enhanced by introducing the use of Redundant Transmission Experience analytics for URLLC service and by making corrections for NGAP parameters related to 5G URLLC Redundant PDU Sessions. Furthermore, the specifications for Industrial IoT (IIoT) and URLLC were formally introduced into the high-level technical description document, TS 38.300.

  • Adding the usage of Redundant Transmission Experience analytics for URLLC service TS 23.501CR2581
  • Introduction of Rel-17 IIoT/URLLC to TS 38.300 TS 38.300CR0416
  • 5G URLLC Redundant PDU Session correction for NGAP parameters TS 23.501CR3035
Rel-18 2 changes

In Release 18, the primary URLLC enhancements focused on introducing the new concept of Timing Resiliency to improve reliability. This was complemented by a correction to the Uplink Assistance Information (UAI) procedure specific to URLLC.

  • Introduction of Timing Resiliency and URLLC enhancements TS 38.300CR0730
  • Correction on UAI for URLLC TS 38.300CR0793
Rel-19 7 changes

In Release 19, the key URLLC enhancements introduced the "SEALDD enabled URLLC transmission" capability, which defines new policy-based procedures for connection establishment and deletion. These procedures are specified to operate using both HTTP and CoAP protocols. Furthermore, the release added required features to support URLLC for direct UE-to-UE communication via satellite links.

  • SEALDD enabled URLLC transmission connection deletion based on policy procedure based on HTTP TS 24.543CR0015
  • SEALDD enabled URLLC transmission connection establishment based on policy procedure based on HTTP TS 24.543CR0012
  • SEALDD enabled URLLC transmission connection establishment based on policy procedure based on CoAP TS 24.543CR0014
  • SEALDD enabled URLLC transmission connection deletion based on policy procedure based on CoAP TS 24.543CR0016
  • Corrections on SEALDD enabled URLLC transmission connection establishment TS 24.543CR0072
  • Data semantics for SEALDD enabled URLLC transmission connection establishment based on policy procedure TS 24.543CR0013

+ 1 more changes

Explore further

Broader topics and technologies where URLLC plays a role.

Defining Specifications

3GPP specifications that define or reference URLLC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TR 21.905 vj00 3GPP Technical Terms and Definitions Rel-19
TS 22.261 vk30 5G System Service Requirements Rel-20
TS 22.830 vg10 Business Role Models for Network Slicing Rel-16
TS 23.501 vk00 5G System Architecture Stage 2 Rel-20
TS 23.700 vk00 XR Services Application Enablement Layer Rel-20
TS 23.725 vg20 Study on URLLC Architecture Enhancements Rel-16
TR 23.745 vh00 Study on App Layer Support for Factories of the Future in 5G Rel-17
TS 24.543 vj50 SEAL Data Delivery Management Protocol Rel-19
TR 26.806 vi00 Technical Report on Smartly Tethering AR Glasses Rel-18
TS 29.512 vj40 5G Session Management Policy Control Service Rel-19
TS 29.892 vg00 Study on User Plane Protocol in 5GC Rel-16
TS 33.501 vk00 5G Security Architecture and Procedures Rel-20
TS 33.825 vg01 Security for 5G URLLC Services Rel-16
TR 37.910 vj00 5G SRIT and NR RIT Self-Evaluation Report Rel-19
TS 38.300 vj00 NG-RAN Overall Description Rel-19
TR 38.802 ve20 Study on New Radio Access Technology Physical Layer Aspects Rel-14
TR 38.804 ve00 Study on New Radio Access Technology; Radio Interface Protocol Aspects Rel-14
TS 38.811 vf40 Study on NR Support for Non-Terrestrial Networks Rel-15
TR 38.812 vg00 Study on NOMA for NR Rel-16
TR 38.825 vg00 Study on NR Industrial IoT Rel-16
TR 38.890 vh00 NR QoE Management and Optimization Rel-17
TR 38.912 vj00 Study on New Radio Access Technology Rel-19
TR 38.913 vj00 Next Gen Access Tech Scenarios & Requirements Rel-19
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.