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

Glossary term · Services

ITT4RT client in terminal

Immersive Teleconferencing and Telepresence for Remote Terminals Client in Terminal

Services →

ITT4RT client in terminal is a client implemented in a terminal or UE rather than in the network, used to exclude network-side entities such as the ITT4RT MRF when describing endpoint behaviour.

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

Description

The "ITT4RT client in terminal" is a refinement of the general ITT4RT client concept. It denotes an ITT4RT client whose implementation resides in the user's terminal equipment or UE — that is, in the device that the remote participant actually uses. The term is deliberately used in 3GPP TS 26.114 and TS 26.862 when the specification needs to refer to endpoint behaviour while explicitly excluding network-side entities such as the ITT4RT MRF.

This distinction is important because the ITT4RT feature can be realized in two fundamentally different places. In one deployment, the terminal itself receives the immersive media streams and performs rendering, viewpoint selection, and spatial audio processing locally. In another deployment, a network-side ITT4RT MRF receives the immersive streams, processes them, and delivers a simplified or adapted stream to a terminal that may not support immersive rendering. When the specification says "ITT4RT client in terminal", it is unambiguously referring to the first case: functionality that runs on the device.

Functionally, an ITT4RT client in terminal performs the full set of ITT4RT client operations locally. It negotiates media capabilities via SDP over IMS SIP signalling, receives multiple RTP streams (e.g., multiple camera views and spatial audio channels), synchronizes them, and renders them to the user's display and audio output. It also implements the user-facing controls for selecting viewpoints or audio perspectives, and it sends the corresponding control messages back toward the media source or conference server. Because all of this happens on the device, the terminal must have sufficient processing power, memory, display capability, and audio rendering capability to handle immersive media.

The term also has implications for capability negotiation and interworking. A terminal that hosts an ITT4RT client in terminal can advertise its immersive capabilities during session setup, allowing the conference server to decide whether to send immersive streams directly or to route them through an ITT4RT MRF for adaptation. This makes the "in terminal" concept a key building block for hybrid deployments where some participants have immersive-capable devices and others do not.

In the broader 3GPP ecosystem, the explicit naming of "ITT4RT client in terminal" reflects a general specification-writing discipline: when a feature can be implemented in multiple locations, the standard defines precise terms so that requirements, test cases, and interoperability clauses can target the correct entity. For engineers implementing ITT4RT, understanding this term is essential to correctly interpreting which requirements apply to the device and which apply to the network.

Purpose & Motivation

The term "ITT4RT client in terminal" exists primarily to remove ambiguity. The base term "ITT4RT client" covers any implementation of the ITT4RT feature, whether on the device or in the network. But many requirements in the MTSI specifications apply specifically to the device — for example, rendering behaviour, user interface controls, and device-side capability negotiation. Without a precise term, readers could mistakenly apply device requirements to a network-side MRF, or vice versa.

Historically, MTSI specifications already distinguished between terminal-side and network-side media handling. The MRF (Media Resource Function) has long been a network entity that provides media processing such as conferencing, transcoding, and mixing. When ITT4RT was introduced, it was natural to allow the same immersive client functionality to be hosted either in the terminal or in an MRF. The term "ITT4RT client in terminal" was therefore created to preserve the clarity of the existing MTSI vocabulary while extending it to immersive services.

From a deployment perspective, the term also helps operators and vendors reason about capability distribution. Devices vary widely in their ability to render immersive media. By explicitly naming the in-terminal variant, the standard makes it possible to describe scenarios where immersive processing is pushed to the network for thin clients, while still allowing capable devices to take full advantage of local rendering. This supports a gradual migration path toward immersive teleconferencing without forcing every endpoint to be upgraded at once.

What changed in its specifications

The latest release-to-release comparison of specifications that define ITT4RT client in terminal. 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 established the term as an ITT4RT client implemented in a terminal or UE, explicitly used when network entities such as the ITT4RT MRF are excluded. This provided the device-side counterpart to the network-side ITT4RT MRF concept.

The definition text carried over unchanged from Rel-17; the term continued to denote an ITT4RT client implemented in a terminal or UE, excluding entities such as the ITT4RT MRF.

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

The definition text carried over unchanged; the term remains an ITT4RT client implemented in a terminal or UE, used when entities such as the ITT4RT MRF are excluded.

Defining Specifications

3GPP specifications that define or reference ITT4RT client in terminal, 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