DCMTSI

Data Channel Multimedia Telephony Service over IMS

Services →
Introduced in Rel-17

DCMTSI is a 3GPP standardized service enabling real-time multimedia telephony over IMS using WebRTC data channels to support voice, video, and data sharing within a single session.

Category
Services
Introduced
Rel-17
Where
Services › Codecs
Specifications
6 specs
DCMTSI Description Purpose Related Classification Detected Changes Specifications

Description

Data Channel Multimedia Telephony Service over IMS (DCMTSI) is a 3GPP service architecture that leverages the IP Multimedia Subsystem (IMS) to deliver multimedia telephony services using WebRTC (Web Real-Time Communication) data channels as a transport mechanism. It operates by establishing a multimedia session via IMS signaling (primarily SIP and SDP) between endpoints, such as web browsers or native applications, and then utilizing WebRTC data channels to carry real-time media streams (voice, video) and arbitrary data (e.g., file transfer, text chat) within that session. The service is defined to ensure interoperability between WebRTC-based clients and traditional IMS-based telephony networks, allowing for rich, conversational multimedia experiences.

Architecturally, DCMTSI integrates the IMS core (including CSCFs, HSS) with WebRTC-enabled endpoints. The IMS provides authentication, authorization, session control, and service orchestration. The WebRTC framework, specifically its data channel API built on SCTP over DTLS, provides the secure, bidirectional transport for media and data. Key components include the DCMTSI client (a WebRTC application implementing 3GPP profiles), the IMS core network elements, and often a WebRTC gateway or an IMS Application Server (AS) that may adapt protocols between the WebRTC world and the IMS network. The service uses standard IMS procedures for registration and session establishment, with SDP extensions to negotiate the use of data channels for media.

In operation, a DCMTSI session begins with IMS registration and authentication of the client. To initiate a call, the client sends a SIP INVITE containing an SDP offer that indicates support for media over WebRTC data channels. Upon acceptance, the IMS core routes the signaling and facilitates the session setup. The endpoints then establish a direct or relayed peer-to-peer WebRTC data channel connection for the media flow, using ICE for NAT traversal, DTLS for security, and SCTP for transport. This allows synchronous transmission of multiple media types within the same logical channel. The service supports essential telephony features like call hold, transfer, and multi-party calls, managed through IMS signaling while media flows over the data channels.

DCMTSI's role in the network is to extend IMS-based telephony services to WebRTC clients without requiring a full, traditional IMS User Equipment (UE). It enables service providers to offer carrier-grade multimedia communication (voice, video, data) to users on web browsers or lightweight apps, leveraging the existing IMS infrastructure for control and billing. This bridges the gap between telecom networks and internet-based communication, facilitating the convergence of services.

Purpose & Motivation

DCMTSI was created to address the growing demand for integrating web-based communication technologies, specifically WebRTC, with standardized telecom networks like IMS. Historically, IMS services were primarily accessed via dedicated UE with complex stacks, while WebRTC offered browser-based real-time communication but lacked standardized integration into carrier networks. This created a divide: web applications could not easily access rich telephony services (e.g., guaranteed QoS, emergency calling, inter-operator interoperability) provided by IMS. DCMTSI solves this by defining a standardized method to use WebRTC data channels as a media transport for IMS multimedia telephony, enabling web clients to become first-class citizens in IMS networks.

The motivation stems from the need for service providers to offer consistent, feature-rich communication experiences across all devices, including web browsers and mobile apps, without developing proprietary solutions. Prior to DCMTSI, integrating WebRTC with IMS was possible but not standardized, leading to fragmentation and interoperability challenges. DCMTSI provides a 3GPP-specified approach, ensuring that services like high-quality voice/video calls, instant messaging, and file sharing can be delivered seamlessly over IMS to WebRTC endpoints. It leverages the strengths of both: IMS for core network control, security, and service integration, and WebRTC for easy client deployment and advanced media capabilities.

Furthermore, DCMTSI addresses limitations of earlier approaches like Voice over LTE (VoLTE) and Video over LTE (ViLTE), which required specific UE implementations. By using WebRTC data channels, DCMTSI enables more flexible media handling (e.g., mixing data sharing with voice/video) and simplifies client development. It supports the evolution towards all-IP networks and the convergence of telecom and web services, allowing operators to deploy innovative multimedia services rapidly and extend their IMS investments to a broader range of devices and applications.

Classification

Part ofIMS

Detected Changes Across Releases

from 3GPP Change Requests

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

Studied in Rel-17, normative work from Rel-18.

Rel-18 20 changes

In Release 18, the DCMTSI function introduced several new capabilities and clarifications, including support for UE-centric AR telephony communication, roaming, and the multiplexing of IMS data channels. The release also defined procedures for establishing a data channel before the SIP 200 OK response, for termination, and for handling QoS, while updating bootstrap and application data channel setup processes. Furthermore, the architecture was refined by removing the MRF from the IMS data channel architecture and updating HSS service descriptions and subscription data for the service.

  • Architecture of IMS supporting data channel TS 23.228CR1263
  • Introduce Data Channel Related Definitions TS 23.228CR1275
  • Supporting UE centric AR Telephony Communication TS 23.228CR1284
  • Update of Bootstrap and application data channel setup procedures TS 23.228CR1301
  • Clarification on IMS Data Channel Service TS 23.228CR1278
  • UE trigger for IMS Data Channel setup TS 23.228CR1286

+ 14 more changes

Rel-19 8 changes

In Release 19, key enhancements for DCMTSI included the introduction of a Standalone IMS Data Channel feature, support for network-initiated IMS Data Channel establishment, and the ability to interwork data channels between DCMTSI and MTSI User Equipment. The release also introduced a specific "Data off" feature for the data channel and provided corrections to the signalling procedures for application data channel interworking and capability handling.

  • 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
  • Correction on standalone data channel description TS 23.228CR1627
  • Corrections to Signalling Procedure of Application Data Channel Interworking via MF TS 23.228CR1659

+ 2 more changes

Explore further

Broader topics and technologies where DCMTSI plays a role.

Defining Specifications

3GPP specifications that define or reference DCMTSI, 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 26.567 vj00 IMS-based Split Rendering Rel-19
TR 26.998 vj00 5G AR/MR Glasses Integration Study Rel-19
TR 33.890 vi00 Technical Report on Security Aspects Rel-18