TSC

Time Sensitive Communications

Services →
Introduced in R99 Also in: Services, Management, Radio Access Network, Security

TSC is a set of 3GPP capabilities that support applications with stringent requirements for latency, reliability, and timing synchronization by ensuring deterministic packet delivery within bounded end-to-end delays.

Category
Services
Introduced
R99
Where
Core Network › 5G Core
Also touches
4 segments
Specifications
33 specs
TSC Description Purpose Related Classification Detected Changes Specifications

Description

Time Sensitive Communications (TSC) refers to a comprehensive framework within 3GPP standards that enables deterministic data delivery over 3GPP networks. Determinism means guaranteeing that data packets are delivered within a strictly bounded end-to-end latency (often ultra-low, e.g., sub-1ms to 10s of ms) with extremely high reliability (e.g., 99.9999%) and precise timing synchronization between devices (e.g., ±1µs accuracy). This is a radical departure from traditional best-effort mobile communications.

The TSC architecture permeates multiple network domains. In the 5G Core Network (5GC), it leverages features like Ultra-Reliable Low Latency Communication (URLLC) service support, network exposure for deterministic communication, and the 5G QoS model with specific QoS flows for TSC traffic. Key architectural components include the Time Synchronization Function (TSF) defined in TS 23.501, which provides timing information to the RAN and UEs, and the support for time-sensitive networking (TSN) integration. The 5G system can act as a TSN bridge, participating in TSN networks for industrial LANs.

At the Radio Access Network (RAN) level, TSC is enabled by URLLC enhancements such as grant-free uplink transmission, mini-slot scheduling, redundant transmissions (via packet duplication over multiple paths), and advanced channel coding. The RAN uses specific scheduling algorithms to prioritize TSC packets and ensure they meet their deadlines. End-to-end, the system uses TSC Assistance Information (TSCAI) provided by the application function to the network, informing it of packet arrival times and deadlines, allowing for proactive resource reservation and scheduling.

How it works involves close coordination between the application, the core network, and the RAN. An application (e.g., a robotic controller) registers a TSC session with specific requirements. The network establishes dedicated QoS flows with guaranteed bit rate and packet delay budget. The application then provides TSCAI, signaling the expected pattern of critical packets. The RAN scheduler uses this information to allocate resources just in time for packet arrivals, minimizing queuing delays. Simultaneously, the network's time synchronization function distributes a common time reference, allowing all devices in a system to operate in a coordinated manner, which is essential for synchronized actions in automation.

Purpose & Motivation

TSC was created to enable 3GPP networks, primarily 5G, to serve as a communication backbone for vertical industries like factory automation, power distribution, and transportation. These industries have long relied on wired fieldbus or industrial Ethernet systems (e.g., PROFINET, EtherCAT) that offer deterministic latency and tight synchronization. The limitation of these wired systems is their inflexibility and high cost of deployment/reconfiguration.

The core problem TSC addresses is the inherent non-determinism in packet-switched mobile networks, where variable queuing delays, contention for shared resources, and radio channel fluctuations make predictable timing impossible with standard mechanisms. Previous cellular generations (4G and prior) were designed for human-centric traffic (web, video) which is tolerant of delay variations (jitter). This made them unsuitable for closed-loop control systems where a delayed sensor reading or actuator command could cause system failure or safety hazards.

Motivation for TSC standardization came from strong industry demand for wireless flexibility in automation. The vision is the "wireless factory" and "critical IoT." 3GPP, starting from Release 15 (5G Phase 1) and significantly enhancing in Release 16 (5G Phase 2 for URLLC and TSN integration), developed TSC capabilities to bridge this gap. It allows mobile networks to not just connect devices, but to become an integral part of time-critical control loops, unlocking new use cases like mobile robotics, augmented reality for remote maintenance, and smart grid protection.

Classification

Part ofURLLC
Related approachesTSN

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-16 24 changes

In Release 16, 3GPP introduced the foundational architecture and key capabilities for Time Sensitive Communications (TSC), including the definition of TSC Assistance Information (TSAI) transported between network functions. It specified deterministic QoS features such as Hold and Forward Buffers, UE/UPF residence time measurement, and the establishment of static TSC QoS Flows. The release also defined security provisions for TSC-enabled UEs and mandated that a TSC PDU session be established as always-on.

  • Introducing support TSC Deterministic QoS TS 23.501CR1007
  • Introducing support Hold and Forward Buffers for TSC Deterministic QoS TS 23.501CR1008
  • TSC definitions TS 23.501CR0870
  • TSC Architecture TS 23.501CR0871
  • Update to Support TSAI for TSC Deterministic QoS TS 23.501CR1212
  • Introducing support for UE and UPF Residence Time for TSC Deterministic QoS TS 23.501CR1214

+ 18 more changes

Rel-17 46 changes

In Release 17, the TSC function was expanded with new service operations including Create_TSC_Stream, Delete_TSC_Stream, and Discover_TSC_Stream_Availability, along with their associated data models and OpenAPI definitions. The release also introduced explicit support for UE-UE TSC communication and generalized support for TSC networks other than TSN, including provisions for Bridge ID and MIC (BMIC/PMIC) functionality without an IEEE TSN network. Furthermore, it added clarifications on QoS determination for TSC and scenarios where TSC and time synchronization are not supported.

  • Unified support for TSC/TSN services TS 23.434CR0064
  • KI#2 Supporting UE-UE TSC TS 23.501CR2606
  • KI#2 BMIC and PMIC for TSC without IEEE TSN network TS 23.501CR2618
  • KI#3A - TSC Assistance container determined by NEF TS 23.501CR2619
  • Update for support of TSC other than TSN TS 23.501CR2768
  • Terminology on the TSC MIC and Bridge ID TS 23.501CR2817

+ 40 more changes

Rel-18 27 changes

In Release 18, the TSC (Time Sensitive Communications) function introduced a new direct event notification mechanism for TSC management information, allowing the UPF to report directly to the TSN AF or TSCTSF. Enhancements were made to the Create_TSC_Stream and Delete_TSC_Stream service operations to improve time synchronization capabilities, and PER (Packet Error Rate) was added as a QoS input for TSC streams. Furthermore, the release specified a complete architecture and charging information for TSC traffic charging.

  • SEAL NRM determines time synchronization activation for TSC stream TS 23.434CR0223
  • UPF event exposure service for TSC management TS 23.501CR3720
  • Updates on TSC management information TS 23.501CR4404
  • Direct reporting of TSC Management Information from UPF to TSN AF or TSCTSF TS 29.244CR0725
  • Support of the direct event notification of TSC management information TS 29.512CR1071
  • Support of the direct event notification of TSC management information TS 29.514CR0503

+ 21 more changes

Explore further

Broader topics and technologies where TSC plays a role.

Defining Specifications

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

SpecificationTitleRelease
TR 21.904 v1300 3GPP UE Baseline Capability Requirements Rel-4
TR 21.905 vj00 3GPP Technical Terms and Definitions Rel-19
TS 23.434 vk00 Service Enabler Architecture for Verticals Rel-20
TS 23.501 vk00 5G System Architecture Stage 2 Rel-20
TR 23.745 vh00 Study on App Layer Support for Factories of the Future in 5G Rel-17
TS 24.501 vj50 5G NAS Protocols Specification Rel-19
TS 24.519 vh10 TSN AF to DS-TT/NW-TT Protocol Aspects Rel-17
TS 24.535 vj00 TS 24535: (g)PTP Message Delivery Protocol Rel-19
TS 24.539 vj30 NW-TT Protocol Aspects Rel-19
TR 28.839 vi10 Technical Report Rel-18
TR 28.843 vi10 Technical Report on Charging Aspects for Vertical Scenarios Rel-18
TR 28.865 vi10 Technical Report on Deterministic Communication Service Assurance Rel-18
TS 29.122 vj40 T8 Reference Point for Northbound APIs Rel-19
TS 29.244 vj40 PFCP Specification for Control/User Plane Separation Rel-19
TS 29.512 vj40 5G Session Management Policy Control Service Rel-19
TS 29.513 vj40 5G PCC Signalling Flows & QoS Mapping Rel-19
TS 29.514 vj40 5G System; Policy Authorization Service; Stage 3 Rel-19
TS 29.522 vj40 5G NEF Northbound APIs Stage 3 Rel-19
TS 29.549 vj40 SEAL API Specification for Vertical Applications Rel-19
TS 29.565 vj40 Time Synchronization Function Services Rel-19
TS 32.255 vk10 Telecom Management; Charging for 5G Data Connectivity Rel-20
TS 32.282 vi20 Charging management; Time Sensitive Networking Rel-18
TS 32.291 vj40 Charging Management: Service-Based Interface Protocol Rel-19
TS 33.501 vk00 5G Security Architecture and Procedures Rel-20
TS 33.514 vk00 5G Security Assurance for UDM Rel-20
TS 33.819 vg10 5GS Security for Vertical & LAN Services Rel-16
TR 33.851 vh10 Security for Industrial IoT in 5G Rel-17
TS 44.060 vj00 GERAN RLC/MAC Protocol Specification Rel-19
TS 45.860 vb50 Precoded EGPRS2 Downlink Study Rel-11
TS 45.871 ve00 MIMO for GSM/EDGE Downlink Study Rel-14
TR 45.903 vj00 SAIC Feasibility Study for GSM Networks Rel-19
TR 45.914 vj00 MUROS Feasibility Study for Voice Capacity Rel-19
TS 52.021 vj00 GSM A-bis Interface Network Management 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.