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

Glossary term · Services

Application data channel

Application Data Channel

Services →

Application data channel is a data channel within an IMS session used to transfer data of data channel applications between UEs or between a UE and the network, enabling rich, application-specific data exchange alongside conversational services.

Introduced
Rel-18
Where
Services › IMS
Specifications
2 specs
Application data channel Description Purpose What changed Neighbours Detected Changes Specifications

Description

The Application Data Channel is a Rel-18 concept defined within the IMS (IP Multimedia Subsystem) architecture, primarily documented in TS 23.228 (IP Multimedia Subsystem architecture) and TS 23.700 (Study on enhancement of IMS). It represents a dedicated logical channel carried within an IMS session that is used to transfer data belonging to data channel applications. Unlike traditional media streams such as audio or video, the application data channel carries arbitrary application-layer payloads, enabling richer interactive services during an IMS session.

Architecturally, the application data channel is established as part of an IMS session between two UEs, or between a UE and the network. A key constraint specified in the definition is that the application data channel should be established only after the application has been downloaded. This ensures that the endpoints possess the necessary application logic to interpret and process the data carried on the channel before the channel is activated, avoiding wasted resources and undefined behaviour.

Identification of the channel relies on stream IDs. As specified in TS 26.114 (the Multimedia Telephony Service over IMS, MTSI specification), the stream ID for an application data channel can be integers starting from 1000. This range is reserved specifically for application data channels, distinguishing them from conventional media streams (audio, video, text) that use lower stream ID values. The use of a dedicated stream ID range allows the receiving endpoint to demultiplex the application data channel from regular media within the same IMS session.

The application data channel leverages the existing IMS session establishment procedures, including SDP (Session Description Protocol) offer/answer negotiation, to agree on the channel parameters. Once negotiated, the data flows over the underlying transport (typically UDP or TCP, depending on the application requirements) using the agreed stream ID. Because the channel is application-agnostic from the network's perspective, the network does not need to understand the application payload; it merely forwards the data according to the negotiated session parameters.

In terms of evolution, the Rel-18 definition described the channel functionally, including the constraint that it be established only after the application download and the stream ID range starting at 1000. In Rel-19, the wording was revised to a more concise formulation: 'A data channel within an IMS session used to transfer data of data channel applications between UEs or between the UE and the network.' This revision moved the operational details (application download prerequisite and stream ID range) out of the core definition, likely because those details are captured in the referenced specifications (TS 26.114) and procedural clauses. The Rel-20 definition carried over the Rel-19 wording unchanged. The application data channel is an enabler for interactive and immersive IMS services, allowing applications to exchange data in real time within the same session that carries voice and video.

Purpose & Motivation

The Application Data Channel exists to support a new class of IMS services where applications need to exchange data in real time alongside conversational media. Traditional IMS sessions were designed around standardized media streams—audio, video, and text—with well-defined codecs and stream ID ranges. As applications became richer and more interactive (for example, real-time collaboration, in-session data sharing, and immersive experiences), there was a need for a generic, application-agnostic data path within the IMS session itself, rather than relying on separate out-of-band connections.

Before Rel-18, applications that wanted to exchange data during an IMS call had to establish separate data connections (for example, via web sockets or separate packet data sessions), which introduced additional latency, complexity, and synchronization challenges with the media session. The application data channel solves this by integrating the data path directly into the IMS session, reusing the session negotiation and transport mechanisms already in place. This ensures that the data channel is synchronized with the session lifecycle and benefits from the same security and QoS treatment as the session.

The requirement that the channel be established only after the application has been downloaded addresses a practical concern: the receiving endpoint must be capable of processing the application data. By deferring channel establishment until the application is available, the standard avoids sending data to an endpoint that cannot interpret it. The reserved stream ID range starting at 1000 provides a clean demarcation between media and application data, simplifying implementation and interoperability.

What changed in its specifications

The latest release-to-release comparison of specifications that define Application data channel. 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 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-18 2 changes
  • Update of Bootstrap and application data channel setup procedures TS 23.228CR1301
  • Clarification on DC QoS Handling in Application Data Channel Setup Procedures TS 23.228CR1391
Rel-19 1 change
  • Corrections to Signalling Procedure of Application Data Channel Interworking via MF TS 23.228CR1659

Defining Specifications

3GPP specifications that define or reference Application data channel, 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.700 vk10 AI/ML Application Layer Support Phase 2 Rel-20 read