Description
The Data Channel Application is a service-layer concept introduced in 3GPP Release 18 within the data channel framework specified in TS 23.228 (IMS) and studied in TR 23.700. It represents a web-based application — an HTML page containing JavaScript, and optionally images and style sheets — that is delivered from the network to the User Equipment (UE) through a dedicated bootstrap data channel. Rather than being pre-installed on the device, the application is fetched at runtime, enabling the network to control and update the service logic without requiring a native app installation or app-store distribution.
The application is structured as standard web content. The HTML document defines the graphical user interface (GUI) that the user interacts with, while the embedded JavaScript implements the interactive service logic — handling user input, managing state, and communicating with network-side functions. Optional images and style sheets provide the visual presentation. Because the content is accessible at the HTTP root ("/") URL through the bootstrap data channel, the UE can retrieve the entry point of the application with a simple, well-defined request, after which the HTML page references its dependent resources.
The bootstrap data channel is the key architectural enabler. It is established between the UE and the network before the application is needed, and it serves as the transport over which the application content is downloaded. This separation of concerns — a bootstrap channel for application delivery and the application itself for service logic — allows the network to host, version, and update the application independently of the UE software. The UE only needs a generic web-rendering capability and data channel support, not service-specific code.
In operation, the UE establishes or is provided with the bootstrap data channel, issues an HTTP request to the root URL, and receives the HTML/JavaScript application. The application then runs in the UE's web runtime environment, rendering the GUI and executing service logic. Any subsequent interaction with network services can occur through the data channel infrastructure, keeping the service experience consistent and network-controlled.
The concept matters because it turns the UE into a thin, generic client for data-channel services. Service providers gain the ability to deploy and evolve services rapidly on the network side, while users benefit from services that work without installing dedicated applications. This aligns with broader industry trends toward web-based service delivery and reduces fragmentation across device types.
Purpose & Motivation
The Data Channel Application exists to solve the problem of delivering rich, interactive services to UEs without requiring native application installation or device-specific software. Traditionally, enabling a new service on a UE required either a pre-installed client or an app-store download, both of which create friction, delay service rollout, and fragment the user experience across device vendors and operating systems. By delivering the application as standard web content over a bootstrap data channel, 3GPP enables a network-controlled, device-agnostic service model.
A second motivation is service agility. When the application logic lives on the network and is downloaded at runtime, operators and service providers can update the GUI and service logic centrally, roll out fixes and new features quickly, and ensure all users run a consistent version. This is particularly valuable for emerging data-channel-based services where requirements may evolve rapidly and where standardization must accommodate innovation without forcing UE firmware updates.
The concept also addresses the need for a standardized entry point. Specifying that the application is reachable at the HTTP root URL through the bootstrap data channel gives the UE a deterministic, simple retrieval mechanism, reducing interoperability risk between UE vendors and network implementations. The Rel-19 rewording, which reframed the definition around downloading an HTML page from the network to the UE, reflects maturation of the concept toward a clearer delivery-centric description.
What changed in its specifications
The latest release-to-release comparison of specifications that define Data channel application. Each summary describes the whole specification, not only this term.
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
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Initial definition introduced the Data Channel Application as HTML web content including JavaScript(s) and optionally image(s) and style sheet(s), accessible at the HTTP root ("/") URL through a bootstrap data channel, describing the graphical user interface and interactive service logic.
Wording changed: the definition was reframed from describing content 'accessible at the HTTP root URL' to 'A HTML page including JavaScript(s) and optionally image(s) and style sheet(s)' that 'is downloaded from the network to the UE through the bootstrap data channel', shifting emphasis to the download delivery model.
Defining Specifications
3GPP specifications that define or reference Data channel application, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| 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 |