Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Core Network

DCSF

Data Channel Server Control Function

Core Network →

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.

Introduced
Rel-18
Where
Services › Codecs
Specifications
19 specs
Also in
Security, Core Network, Management
DCSF Description Purpose What changed Neighbours 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.

What changed in its specifications

The latest release-to-release comparison of specifications that define DCSF. Each summary describes the whole specification, not only this term.

TS 23.228Rel-18 → Rel-19

Rel-19 TS 23.228 adds SBI service operations for IMS data channels, event subscription, and user information, plus HSS lookup of the serving IMS AS. It adds PS Data Off handling for IMS Data Channel services and Multimedia Priority Service for Messaging.

Full comparison in TS 23.228 →
TS 24.186Rel-18 → Rel-19

Adds IMS data channel establishment/update/release procedures, media add/remove and multiplexing handling, PS Data Off enforcement, and avatar communication support over data channels.

Full comparison in TS 24.186 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific 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.

Rel-18 6 changes
  • 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
  • Update the procedure to support DCSF get and update the repository data TS 29.562CR0139
  • Report the media HOLD to DCSF TS 29.175CR0010
  • Update the NrfInfo to include the information of DCSF, MF, MRF and MRFP TS 29.510CR1027
Rel-19 8 changes
  • 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
  • Clarification on PS Data Off status change reporting to DCSF TS 23.228CR1533
  • Clarify the calling and called identity notified to the DCSF TS 24.186CR0045
  • Report the QoS info to DCSF TS 29.175CR0020
  • Clarification on IMS data channel related LI at the remote end when DCSF is not present TS 33.127CR0320

+ 2 more changes

Rel-20 5 changes
  • NRF based DCSF discovery TS 23.228CR1734
  • Procedures for non-subscriber specific DCSF events TS 23.228CR1759
  • Completion of e2e procedures for DCSF events TS 23.228CR1785
  • Update on Service-Based DCSF Discovery and Selection TS 23.228CR1789
  • Clarification on DCSF Services TS 23.228CR1798

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 vk10 IP Multimedia Core Network Subsystem Rel-20 read
TS 23.392 vk10 MMTel Enabler Architecture and Procedures Rel-20 read
TS 23.700 vk10 AI/ML Application Layer Support Phase 2 Rel-20 read
TS 24.186 vk10 IMS Data Channel and AR Communication Rel-20 read
TS 26.264 vj41 IMS Conversational Augmented Reality Services Rel-19 read
TS 26.567 vj20 IMS-Based Split Rendering Rel-19 read
TR 26.927 vj00 AI/ML in 5G Media Services Study Rel-19 read
TS 28.851 vj10 Charging for Next Gen Real Time Communication Phase 2 Rel-19 read
TS 29.175 vk10 Nimsas Service Based Interface for IMS AS Rel-20 read
TS 29.330 vj00 Diameter-based Sc Interface Specification Rel-19 read
TS 29.510 vk10 NRF Service-Based Interface Rel-20 read
TS 29.562 vk10 HSS Nhss Services for IMS and GBA Rel-20 read
TS 32.260 vk10 IMS Charging Management Rel-20 read
TS 32.291 vk10 5G Charging Service-Based Interface Rel-20 read
TS 32.298 vk10 Charging Data Record Specification Rel-20 read
TS 33.127 vj80 Lawful Interception Architecture Rel-19 read
TS 33.128 vj80 Lawful Interception Protocols and Procedures Rel-19 read
TS 33.328 vk10 IMS Media Plane Security Rel-20 read
TR 33.890 vi00 Technical Report on Security Aspects Rel-18 read