DCSF

Data Channel Server Control Function

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

DCSF is a control plane function within the 5G Core Network's Data Channel Server that manages the establishment, modification, and release of data channels for application-specific communication.

Category
Core Network
Introduced
Rel-18
Where
Core Network › 5G Core
Also touches
2 segments
Specifications
19 specs
DCSF Description Purpose Related Classification Detected Changes Specifications

Description

The Data Channel Server Control Function (DCSF) is a 5G Core Network control plane function introduced as part of the Data Channel Server (DCS) framework. The DCS architecture is designed to provide enhanced support for application-aware data delivery, particularly for services with stringent requirements like eXtended Reality (XR), cloud gaming, and real-time interactive media. The DCSF acts as the central controller within this architecture. It interfaces with the Session Management Function (SMF) via the Ndcsf interface and with the Data Channel Server User Plane Function (DCSU) via the Ndcsu interface. Operationally, the DCSF receives session-related requests and policies from the SMF. These requests are triggered based on Application Function (AF) requests or PCF policies that identify a need for an application-specific data channel. The DCSF is responsible for the logical control of these data channels. Its key tasks include selecting an appropriate DCSU instance based on load, location, and capability, and then instructing that DCSU to establish, modify, or release a data channel for a specific PDU Session or a group of UEs. A data channel is a dedicated communication path between the DCSU and the UE (via the UPF and RAN) that can be optimized for specific traffic patterns, such as low-latency periodic flows for XR video. The DCSF manages the lifecycle of these channels, including QoS enforcement, traffic steering rules, and potential aggregation of multiple media streams. It also handles coordination for multicast/broadcast data delivery scenarios. The function works in conjunction with the DCSU, which performs the actual user plane packet processing, forwarding, and adaptation according to the rules set by the DCSF. The DCSF itself does not handle user data packets. Its role is purely control-oriented: translating application requirements (e.g., frame rate, latency budget) into network resource commands. It is a key enabler for network exposure, allowing the 5G system to dynamically create tailored data paths based on real-time application needs, going beyond the static QoS Flow model of basic 5G.

Purpose & Motivation

The DCSF was created to address the limitations of the standard 5G QoS model when handling complex, dynamic applications like XR and cloud gaming. While 5G introduced QoS Flows, their configuration is relatively static and managed per PDU session. Advanced interactive services require rapid setup and teardown of multiple, simultaneous data streams with distinct and stringent requirements (e.g., separate channels for video, audio, and haptic feedback), often synchronized and needing precise traffic steering. The purpose of the DCSF is to provide a dedicated control function that can dynamically manage these application-specific 'data channels' upon request. It solves the problem of rigid, session-level QoS management by introducing a more granular and agile channel control layer. The motivation stems from industry demand for network support that is deeply aware of application context. By having a control function (DCSF) that interfaces with the SMF and PCF, the network can respond to AF requests in real-time, establishing optimized data paths that reduce latency, jitter, and improve resource efficiency for demanding services. It addresses the previous approach's limitation where such optimization would require complex AF-SMF interaction and potentially slow reconfiguration of the entire PDU session. The DCSF provides a standardized, scalable control plane for the Data Channel Server architecture, enabling new revenue-generating services with enhanced quality of experience.

Classification

Part ofSMF
Related approachesAF

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 2 changes

In Release 15, the DCSF (Data Channel Server Control Function) was newly introduced as part of the framework for IMS Data Channel applications, which manage data channel traffic handling and interworking. This function interacts with a DC Application Server and a DC media function to support the establishment of application data channels and bootstrap data channels within an IMS session. The introduction enables services like standalone IMS Data Channel Sessions for transferring application data between UEs or between the UE and the network.

  • WebRTC Web Server Function discovery TS 23.228CR1173
  • NRF servers clause in OpenAPI TS 29.510CR0054
Rel-16 2 changes

In Release 16, the DCSF function was enhanced with new rate control capabilities for data channel sessions. Specifically, the Serving PLMN Rate Control information was added to the List of Traffic Data Volumes, and mechanisms were introduced to include Rate-Control information and triggers within Charging Data Records (CDRs). These updates provided operators with more granular policy and charging control for IMS data channel traffic.

  • Adding Rate-Control information and triggers to CDRs TS 32.298CR0720
  • Serving PLMN Rate Control in List of Traffic Data Volumes TS 32.298CR0729
Rel-18 39 changes

In Release 18, the DCSF (Data Channel Server Control Function) was formally integrated into the IMS architecture with new definitions and procedures. Key enhancements included the introduction of a reference point between the HSS and DCSF, updates to bootstrap and application data channel setup procedures, and the enabling of DCSF registration and discovery via the NRF. The release also specified support for roaming, duration-based charging principles, and procedures for data channel termination and QoS requirements.

  • Architecture of IMS supporting data channel TS 23.228CR1263
  • Introduce Data Channel Related Definitions TS 23.228CR1275
  • Update of Bootstrap and application data channel setup procedures TS 23.228CR1301
  • Reference point between HSS and DCSF TS 23.228CR1305
  • Enhancement of NRF services to support DCSF registration and discovery TS 29.510CR0828
  • Add DCSF as service consumer TS 29.562CR0130

+ 33 more changes

Rel-19 45 changes

In Release 19, the DCSF (Data Channel Server Control Function) was enhanced to support the new Standalone IMS Data Channel feature, enabling sessions with only data channel media components. Key additions include procedures for network-initiated peer-to-peer application data channel establishment and support for data channel interworking between different UE types. The release also introduced specific handling for the PS Data Off feature and duration-based charging for these standalone data channel sessions.

  • Support of IMS data channel interworking between DCMTSI UE and MTSI UE TS 23.228CR1418
  • KI#6: Support of Standalone IMS Data Channel feature TS 23.228CR1422
  • Supporting of network initiated IMS Data Channel TS 23.228CR1425
  • KI#5: Support of Data off feature for data channel TS 23.228CR1421
  • DCSF instructing the IMS AS to terminate the session at the IMS AS TS 23.228CR1498
  • Clarification on how DCSF fetch DC AS URL if not pre-configured TS 23.228CR1563

+ 39 more changes

Explore further

Broader topics and technologies where DCSF plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 23.228 vj50 IMS Stage-2 Service Description Rel-19
TS 23.392 vj20 MMTel Application Enablement Rel-19
TS 23.700 vk00 XR Services Application Enablement Layer Rel-20
TS 24.186 vj60 IMS Data Channel applications Rel-19
TS 26.264 vj20 IMS-based AR Real-Time Communication Rel-19
TS 26.567 vj00 IMS-based Split Rendering Rel-19
TR 26.927 vj00 AI/ML in 5G Media Services Study Rel-19
TS 28.851 vj10 Charging for Next Gen Real Time Communication Phase 2 Rel-19
TS 29.175 vj40 IMS AS Service-Based Interface Protocol Rel-19
TS 29.330 vj00 Diameter-based Sc Interface Specification Rel-19
TS 29.510 vj50 NRF Service Based Interface Protocol Rel-19
TS 29.562 vj40 HSS Services for IMS & GBA Interworking Rel-19
TS 32.260 vj10 IMS Charging Management Rel-19
TS 32.291 vj40 Charging Management: Service-Based Interface Protocol Rel-19
TS 32.298 vj30 Charging Data Record (CDR) Parameter Specification Rel-19
TS 33.127 vj50 Lawful Interception Architecture and Functions Rel-19
TS 33.128 vj50 3GPP TS 33.128: Lawful Interception Protocols Rel-19
TS 33.328 vj10 IMS Media Plane Security Specification Rel-19
TR 33.890 vi00 Technical Report on Security Aspects Rel-18