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

Glossary term · Services

ITT4RT client

Immersive Teleconferencing and Telepresence for Remote Terminals Client

Services →

ITT4RT client is an MTSI client that supports the ITT4RT feature for immersive teleconferencing and telepresence, enabling remote participants to experience immersive audio-visual telepresence sessions over 3GPP multimedia telephony.

Introduced
Rel-17
Where
Services › Codecs
Specifications
2 specs
ITT4RT client Description Purpose What changed Neighbours Specifications

Description

The ITT4RT client is a functional entity defined in 3GPP TS 26.114 (MTSI) and TS 26.862 that implements the Immersive Teleconferencing and Telepresence for Remote Terminals feature. ITT4RT is an extension of the MTSI (Multimedia Telephony Service for IMS) framework that allows a remote participant to join a conference or telepresence session with an immersive experience, even though the participant is not physically present in the room. The client is the endpoint software that captures, sends, receives, renders, and controls the media streams associated with such a session.

Architecturally, the ITT4RT client sits at the edge of the media path. It negotiates media capabilities using SDP through the IMS signalling plane (via SIP), and then exchanges media over RTP/RTCP with a remote endpoint or with an ITT4RT media resource function. The client supports multiple simultaneous media streams — for example, several camera views, spatial audio channels, and presentation or content-sharing streams — and provides the rendering and view-selection logic that turns these streams into an immersive experience for the user. It also handles synchronization across streams (using RTCP sender reports and RTP timestamps) so that audio and video remain lip-synced and spatially coherent.

The ITT4RT client is defined as a specialization of the MTSI client. This means it inherits all MTSI client behaviour: media negotiation, codec usage, error resilience (e.g., RTP retransmission, FEC), QoS handling, and interworking with IMS. On top of that baseline, the ITT4RT client adds capabilities specific to immersive teleconferencing: support for multiple video streams representing different viewpoints, spatial audio rendering, and control signalling that lets the user select a viewpoint or audio perspective. The client may also support the reception of a "room" representation where the remote terminal reconstructs the spatial layout of the conference room.

The client can be deployed in different host environments. When implemented in a terminal or UE, it is referred to as an "ITT4RT client in terminal". When implemented as network-side media processing functionality within an MRF (Media Resource Function), it is referred to as an "ITT4RT MRF". This distinction matters because the same ITT4RT feature set can be realized either at the user's device or in the network, depending on the deployment and the capabilities of the endpoints.

In the overall 3GPP service architecture, the ITT4RT client is the enabler that makes immersive teleconferencing interoperable across vendors and operators. By standardizing the client behaviour — media formats, negotiation, control protocols, and rendering expectations — 3GPP ensures that an ITT4RT-capable terminal from one vendor can participate in an immersive session hosted by another vendor's infrastructure. The client therefore plays a central role in bringing immersive collaboration services into the IMS multimedia telephony ecosystem.

Purpose & Motivation

The ITT4RT client exists to solve a concrete problem: traditional MTSI conferencing delivers a flat, single-view, single-perspective experience to remote participants. A remote user sees one camera feed and hears a downmixed audio stream, losing the spatial and contextual information that makes an in-person meeting effective. ITT4RT was created to close this gap by defining how immersive media — multiple viewpoints, spatial audio, and rich content — can be delivered to remote terminals over 3GPP networks.

Before ITT4RT, immersive teleconferencing was largely proprietary. Each vendor implemented its own multi-stream capture, transport, and rendering scheme, which meant that immersive sessions only worked within a single vendor's ecosystem. There was no standardized way to negotiate multiple camera streams, no standardized control channel for viewpoint selection, and no standardized rendering expectations. This fragmentation limited adoption and made operator-grade immersive services impractical.

The ITT4RT client addresses this by building on the already widely deployed MTSI client baseline. Operators and vendors can extend existing MTSI implementations rather than building entirely new stacks. The client abstraction also allows the same feature to be realized either in the terminal or in the network (as an ITT4RT MRF), giving deployments flexibility to support legacy endpoints that cannot render immersive media locally. In short, the ITT4RT client provides the standardized endpoint behaviour needed to make immersive teleconferencing an interoperable, operator-deployable service.

What changed in its specifications

The latest release-to-release comparison of specifications that define ITT4RT client. Each summary describes the whole specification, not only this term.

TS 26.114Rel-18 → Rel-19

Rel-19 adds a reference to the IVAS fixed-point C code specification in TS 26.114. It also lists that specification among supported specifications for MTSI immersive audio clients.

Full comparison in TS 26.114 →

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.

Rel-17 Initial

Initial definition introduced the ITT4RT client as an MTSI client supporting the Immersive Teleconferencing and Telepresence for Remote Terminals feature, as defined in Annex Y of the MTSI specifications. This established the baseline architecture and the relationship to the existing MTSI client.

The definition text carried over unchanged from Rel-17; the term continued to denote an MTSI client supporting the ITT4RT feature as defined in Annex Y.

The definition text is substantively identical to Rel-17 and Rel-18; only line-wrapping/formatting of the quoted text differs, with no change in meaning.

The definition text carried over unchanged; the ITT4RT client remains defined as an MTSI client supporting the ITT4RT feature per Annex Y.

Defining Specifications

3GPP specifications that define or reference ITT4RT client, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 26.114 vk11 IMS Multimedia Telephony Client Rel-20 read
TR 26.862 vh00 Immersive Teleconferencing & Telepresence for Remote Terminals Rel-17 read