3GPP TR 26.814 V0.0.1 - Study on Enhancements to IMS Data Channel (Release 20)

Document Overview

This Technical Report is an early-stage study document (v0.0.1) from SA4 focusing on enhancements to the IMS Data Channel feature. The document builds upon Release 19 work that introduced architecture and procedure enhancements for IMS DC in TS 23.228 Annex AC, including Data Channel Signalling Function (DCSF), Media Function (MF), Data Channel Application Server (DC AS), and associated procedures.

Scope

The study aims to:
- Improve interoperability of IMS Data Channel specified in TS 26.114
- Close ambiguities identified after Release 19 stage 2 architecture work
- Address issues raised by external groups (e.g., GSMA) and other 3GPP working groups
- Align stage 3 specification work with the Release 19 stage 2 framework

Key focus areas include:
- Multi-application multiplexing
- Interworking between Data Channel enabled MTSI and MTSI-only endpoints
- HTTP subprotocol usage and handling of external resources
- Cross-specification alignment

Key Definitions

IMS Data Channel: A WebRTC data channel established within an IMS session according to TS 26.114, typically using DTLS/SCTP

Data Channel Application: An application identified and requested for use over the IMS Data Channel as described in TS 23.228 Annex AC

Data Channel Application Server (DC AS): An application server that provides DC application content and may participate in DC procedures

Data Channel Signalling Function (DCSF): A network function supporting IMS Data Channel application discovery, bootstrap, and policy handling

Media Function (MF): A network function for media anchoring, potentially supporting proxying and interworking functions for IMS Data Channel

Key Issues Identified

KI#1: Multiplexing Edge Cases for Multi-Application IMS DC (TS 23.228 Annex AC.7.10)

Issue Statement: [Empty - to be filled]

Solution Direction: [Empty - to be filled]

Potential Specification Impacts: [Empty - to be filled]

Open Points and Dependencies: [Empty - to be filled]

KI#2: Interworking Facilitation with MTSI (TS 23.228 Annex AC.7.9)

Issue Statement: [Empty - to be filled]

Solution Direction: [Empty - to be filled]

Potential Specification Impacts: [Empty - to be filled]

Open Points and Dependencies: [Empty - to be filled]

KI#3: Clarifications to HTTP Protocol Usage on IMS DC and Handling of External Resources

Issue Statement: [Empty - to be filled]

Solution Direction: [Empty - to be filled]

Potential Specification Impacts: [Empty - to be filled]

Open Points and Dependencies: [Empty - to be filled]

KI#4: Consolidate Release 19 Stage 3 Implications and Address Incoming Liaison Statement Topics

Issue Statement: [Empty - to be filled]

Solution Direction: [Empty - to be filled]

Potential Specification Impacts: [Empty - to be filled]

Open Points and Dependencies: [Empty - to be filled]

KI#5: Cross-Specification Alignment (TS 23.228, TS 26.114, TS 26.264, TS 26.567)

Issue Statement: [Empty - to be filled]

Solution Direction: [Empty - to be filled]

Potential Specification Impacts: [Empty - to be filled]

Open Points and Dependencies: [Empty - to be filled]

KI#6: New Media Use Cases and Gap Analysis for IMS DC

Issue Statement: [Empty - to be filled]

Solution Direction: [Empty - to be filled]

Potential Specification Impacts: [Empty - to be filled]

Open Points and Dependencies: [Empty - to be filled]

Conclusions and Recommended Way Forward

[Empty - to be filled]

Document Status

This is a skeleton/template document (v0.0.1) dated February 2026. All technical content sections are currently empty placeholders awaiting population with actual study results. The document has not been subject to any approval process and is provided for future development work within 3GPP only.

The document establishes the framework for studying six key issues related to IMS Data Channel enhancements, with focus on alignment between stage 2 (TS 23.228) and stage 3 (TS 26.114) specifications, as well as addressing practical implementation concerns around multiplexing, interworking, protocol usage, and cross-specification consistency.