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
Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (11 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 18, the DCSF was formally introduced as a new network function for data channel signalling control, establishing its key interfaces and capabilities within the IMS Service-Based Architecture. Specifically, this release defined the N72 reference point for the DCSF to interact with the HSS for retrieving and storing repository data, and enabled the IMS AS to notify the DCSF about events such as the UE's PS Data Off status. Furthermore, enhancements were made to support DCSF registration and discovery via the NRF, and the DCSF was integrated as a service consumer within the framework.
- 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
In Release 19, the DCSF was enhanced with new capabilities for session control and monitoring. Specifically, it can now instruct the IMS AS to terminate a session, and it receives notifications about changes to the UE's 3GPP PS Data Off status during an IMS session. Furthermore, clarifications were added regarding how the DCSF fetches the DC Application Server URL and the identities notified to it.
- 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
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.
| Specification | Title | Release |
|---|---|---|
| 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 |