Description
The ITT4RT-Rx client is a functional entity within the 3GPP Immersive Telepresence and Teleoperation for Real-Time (ITT4RT) framework. ITT4RT defines media handling for immersive applications such as remote-controlled robotics, teleoperation, and immersive video conferencing, where low-latency video, audio, and control data must be exchanged over 3GPP networks. The ITT4RT-Rx client is the receive-only endpoint: it consumes immersive video streams but does not originate them. It is specified in TS 26.114 (Media Handling and Interaction, MTSI) and TS 26.862 (ITT4RT media handling), which together define the media codecs, transport, and session control for immersive services.
Architecturally, the ITT4RT-Rx client sits at the media consumption side of an ITT4RT session. It receives immersive video over RTP/UDP/IP, typically using MTSI-based media negotiation (SDP via IMS or a WebRTC-style signaling path). The client is responsible for decoding the immersive video stream, which may be a single view, a multi-view tiled stream, or a viewport-dependent stream where the client signals its viewport orientation to the sender so that only relevant regions are transmitted at high quality. The Rx client therefore implements viewport tracking, tile selection, and rendering, and may interact with the sender via feedback messages (e.g., RTCP or application-layer feedback) to request viewport-dependent media.
The client is defined as receive-only, meaning it does not send immersive video. This distinction matters for resource-constrained devices such as head-mounted displays, remote viewing terminals, or monitoring stations that only need to display the immersive feed. By defining a separate Rx client profile, 3GPP allows interoperability between senders (ITT4RT-Tx clients) and receivers without requiring every endpoint to implement full bidirectional immersive media capability. The Rx client may still send control and feedback information (e.g., viewport orientation, network feedback), but its media capability is limited to reception.
In the ITT4RT architecture, the Rx client interacts with the ITT4RT-Tx client through a media session established using MTSI procedures. The session negotiation determines codecs, resolution, frame rate, and viewport-dependent streaming parameters. The Rx client also participates in QoS handling: it can request QoS via the network (e.g., using MTSI QoS preconditions) and report reception quality to adapt the sender's encoding. For teleoperation, the Rx client may be co-located with a control interface that sends control commands back to the remote robot, but the immersive video itself is only received.
The ITT4RT-Rx client was introduced in Release 17 as part of the broader ITT4RT work item, which aimed to standardize immersive telepresence and teleoperation media handling over 3GPP networks. It continues to be maintained in Releases 18, 19, and 20 with the same core definition, reflecting a stable architectural role. Its existence enables a clear separation of concerns: senders focus on capture and encoding, receivers focus on decoding and rendering, and both interoperate through standardized MTSI and ITT4RT media profiles.
Purpose & Motivation
The ITT4RT-Rx client exists to standardize the receive side of immersive telepresence and teleoperation media sessions. Before ITT4RT, immersive video applications over 3GPP networks relied on proprietary or non-standard media handling, which limited interoperability and made it difficult to guarantee QoS for low-latency teleoperation. By defining a receive-only client profile, 3GPP enables devices that only need to display immersive content—such as monitoring stations, remote viewers, or lightweight headsets—to interoperate with standardized senders without implementing full bidirectional media capability.
The receive-only designation also simplifies device certification and reduces implementation complexity for endpoints that do not capture immersive video. It allows network operators and service providers to deploy asymmetric immersive services (e.g., remote inspection, telemedicine viewing, or surveillance) where the receiver is a dedicated display terminal. The client's ability to signal viewport orientation and reception feedback supports viewport-dependent streaming, which is essential for bandwidth efficiency in immersive applications.
Historically, immersive video delivery over mobile networks faced challenges in session negotiation, codec selection, and QoS signaling. ITT4RT-Rx builds on MTSI (TS 26.114) to reuse established IMS-based session control and QoS mechanisms, while TS 26.862 adds immersive-specific media handling. This layered approach allows the Rx client to benefit from mature 3GPP media infrastructure while supporting new immersive use cases.
What changed in its specifications
The latest release-to-release comparison of specifications that define ITT4RT-Rx client. Each summary describes the whole specification, not only this term.
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.
Defining Specifications
3GPP specifications that define or reference ITT4RT-Rx client, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 26.114 vk11 | IMS Multimedia Telephony Client | Rel-20 read |
| TR 26.862 vh00 | Immersive Teleconferencing & Telepresence for Remote Terminals | Rel-17 read |