Description
The Data Transport Service (DTS) in 3GPP is not a single protocol or node, but a comprehensive service layer concept that abstracts the end-to-end transport of data packets. It is defined across numerous specifications, including service requirements (22.x series), architecture (23.700), and, most critically, the Policy and Charging Control (PCC) framework (29.212, 29.213, 29.214). DTS represents the network's capability to deliver IP packets between a User Equipment (UE) and a Packet Data Network (PDN) with specific Quality of Service (QoS) characteristics, charging rules, and policy enforcement.
Architecturally, DTS is realized through the interaction of several core network functions. The Packet Data Network Gateway (PGW) in EPC or the Session Management Function (SMF) and User Plane Function (UPF) in 5GC serve as the anchor points for the data transport service. The Policy and Charging Rules Function (PCRF in EPC) or Policy Control Function (PCF in 5GC) is the brain of the DTS, determining the policies that govern the service. These policies are enforced at the Gateway nodes (PGW/UPF) and the Radio Access Network (eNodeB/gNB) via the Policy and Charging Enforcement Function (PCEF) or its equivalents. The DTS framework defines Service Data Flows (SDFs), which are aggregates of IP packets matching a filter, and binds them to QoS Flows (in 5G) or EPS Bearers (in 4G).
How it works involves a multi-step process. First, a UE requests a PDN connection or PDU Session. The network (SMF/MME) interacts with the policy function (PCF/PCRF) to establish the appropriate policies for this session. The policy function provides Policy and Charging Control (PCC) rules, which include parameters like QoS Class Identifier (QCI/5QI), bitrate limits, charging keys, and gating controls (allow/block). These rules are installed in the user plane gateways and the RAN. Every packet traversing the user plane is inspected and classified into an SDF. Based on the SDF classification, the corresponding PCC rule is applied, ensuring the packet receives the mandated QoS treatment (scheduling priority, packet delay budget handling), and is accounted for charging purposes.
The role of DTS is central to the 3GPP architecture's shift to all-IP networks. It decouples the application layer (e.g., IMS, web browsing) from the underlying transport mechanics. This allows for the creation of standardized, network-controlled QoS profiles for diverse services—from low-latency gaming to massive IoT sensor reporting—on a common IP infrastructure. The DTS framework ensures that transport resources are allocated efficiently, fairly, and in accordance with operator policies and subscriber profiles, forming the backbone of monetizable service differentiation.
Purpose & Motivation
The Data Transport Service concept was created to address the fundamental challenge of managing diverse IP-based services over a shared mobile network infrastructure. In early mobile data networks, transport was often a "best-effort" pipe with limited ability to differentiate traffic. As services like VoIP, video streaming, and enterprise VPNs emerged, there was a critical need for standardized mechanisms to guarantee specific performance levels (latency, jitter, loss) and to apply differentiated charging.
Historically, pre-3GPP IP networks or early GPRS lacked a unified policy control framework. Service differentiation was ad-hoc or impossible, leading to poor experience for real-time applications and inability to create tiered service offerings. The DTS framework, crystallized around the PCC architecture introduced in Release 7 and expanded thereafter, was motivated by the need for a centralized, dynamic, and application-aware policy control system. It solved the problem of how to translate high-level service requirements (e.g., "this is an IMS voice call") into concrete network-level actions (e.g., "assign a Guaranteed Bitrate bearer with high priority").
Furthermore, DTS enables network slicing in 5G by providing the underlying service mechanism to instantiate and control isolated data transport paths with specific characteristics for different slices. It addresses the business need for operators to move beyond simple data bucket charging to sophisticated service-based charging and partnership models (e.g., sponsored data). In essence, DTS exists to bring order, control, and monetization capability to the chaotic flow of IP packets in a mobile network, making advanced, reliable services commercially and technically viable.
Classification
Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (19 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 17, the specifications introduced comprehensive Policy and Charging Control (PCC) support for the Multimedia Priority Service for Data Transport Service (MPS for DTS). This includes defining the authorization procedures and enabling control via the Application Function (AF) session, PCRF, and PCF to manage the priority service. The enhancements ensure MPS for DTS can be invoked for priority on the default bearer or QoS flow and controlled end-to-end based on operator policy.
- 29.212 PCC Support for MPS for DTS TS 29.212CR1700
- 29.212 MPS for DTS QoS update failure TS 29.212CR1705
- PCRF control of MPS for DTS TS 29.213CR0743
- 29.213 MPS for DTS note fix TS 29.213CR0744
- AF Session for Control of MPS for DTS TS 29.214CR1654
- 29.214 Authorization for MPS for DTS TS 29.214CR1656
+ 8 more changes
In Release 18, the new work for the Data Transport Service (DTS) function focused on aligning and detailing the signaling flows for the Multimedia Priority Service (MPS) for DTS. Specifically, this included providing a formal description for the MPS for DTS service and defining the associated Application Function (AF) signaling flow, including its flow description and flow number. These enhancements served to formally specify the procedures for invoking this generic priority packet transport service.
In Release 19, the enhancements for the Data Transport Service (DTS) specifically clarified and defined the feature applicability and data handling for Multimedia Priority Service (MPS) when applied to DTS. This included detailing the support for MPS for DTS for authorized users both with and without an MPS subscription, and for scenarios like VPN access to enterprise networks and IoT device communications. The release further specified the invocation methods and conditions under which this generic priority packet transport service operates for both EPS and 5GS.
Explore further
Broader topics and technologies where DTS plays a role.
Defining Specifications
3GPP specifications that define or reference DTS, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 22.153 vk00 | Multimedia Priority Service (MPS) requirements | Rel-20 |
| TR 22.854 vh10 | Feasibility Study on Multimedia Priority Service - Phase 2 | Rel-17 |
| TR 22.953 vj00 | Multimedia Priority Service Feasibility Study | Rel-19 |
| TS 23.700 vk00 | XR Services Application Enablement Layer | Rel-20 |
| TS 29.212 vj00 | Gx/Gxx/Sd/St Diameter Protocol | Rel-19 |
| TS 29.213 vj20 | PCC Signalling Flows and QoS Mapping | Rel-19 |
| TS 29.214 vj20 | Policy and Charging Control over Rx | 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 |
| TR 45.913 vj00 | Optimized Transmit Pulse Shape for EGPRS2-B | Rel-19 |
| TR 45.914 vj00 | MUROS Feasibility Study for Voice Capacity | Rel-19 |