Differentiated Services Code Point

Description

The Differentiated Services Code Point (DSCP) is a standardized field within the Type of Service (ToS) byte of an IPv4 header or the Traffic Class byte of an IPv6 header. It utilizes six bits, allowing for up to 64 distinct code points (values 0-63). Within the 3GPP architecture, the DSCP is a crucial tool for implementing end-to-end Quality of Service (QoS) across the transport segments that interconnect network functions, such as between the eNodeB and the S-GW/UPF, or within the core network itself. It operates as part of the broader IETF Differentiated Services (DiffServ) model, which provides scalable service differentiation in IP networks without requiring per-flow state in every router.

The mechanism works by marking packets as they enter a DiffServ domain (e.g., the mobile transport network). A 3GPP network function, such as a Packet Data Network Gateway (P-GW) or User Plane Function (UPF), classifies uplink and downlink user traffic based on QoS rules associated with an EPS bearer or 5G QoS Flow. This classification determines the appropriate DSCP value to write into the IP header of the user plane packets. Routers and switches in the transport network are then configured with Per-Hop Behaviors (PHBs) that correspond to specific DSCP values. These PHBs define how packets are queued, scheduled, and potentially dropped, providing behaviors like Expedited Forwarding (EF) for low-latency traffic, Assured Forwarding (AF) for guaranteed throughput, or Default (BE) for best-effort.

In 3GPP systems, the mapping between the QoS parameters of a radio bearer (QCI in 4G, 5QI in 5G) and the DSCP value is a critical configuration item. This ensures that the QoS intended by the radio and core network is appropriately signaled to, and honored by, the underlying IP transport infrastructure. For example, a QoS Flow for Voice over NR (5G VoIP) with a 5QI of 1 (conversational voice) would be marked with a DSCP value corresponding to the EF PHB (often DSCP 46) to prioritize it through the transport network. This creates a cohesive QoS hierarchy from the application layer down through the radio, core, and transport layers.

Purpose & Motivation

DSCP was adopted within 3GPP to solve the problem of maintaining consistent QoS treatment for user traffic as it traverses the IP-based transport networks that interconnect RAN and core nodes. Early mobile networks had more monolithic, circuit-switched transport where QoS was implicit. With the move to all-IP architecture in 3GPP Release 5 and beyond, a standardized, IP-layer marking mechanism was necessary to signal packet priority to routers and switches.

Its use was motivated by the need for scalability. The DiffServ model, using DSCP, does not require transport routers to maintain state for millions of individual user bearers, unlike the earlier Integrated Services (IntServ) model. This makes it perfectly suited for large-scale mobile networks. DSCP allows the mobile network's intricate QoS framework (with QCIs/5QIs, ARP, etc.) to be seamlessly translated into a simple, widely supported IP networking standard, ensuring that latency-sensitive or high-priority traffic receives appropriate treatment on every hop of its journey through the operator's backbone network.