Description
The ITT4RT-Tx client is the transmit-only endpoint in the 3GPP Immersive Telepresence and Teleoperation for Real-Time (ITT4RT) framework. ITT4RT standardizes media handling for immersive applications such as teleoperation, remote inspection, and immersive conferencing, where low-latency video and control data are exchanged over 3GPP networks. The Tx client captures, encodes, and sends immersive video streams but does not receive them. It is specified in TS 26.114 (MTSI media handling) and TS 26.862 (ITT4RT media handling), which define codecs, transport, and session control for immersive services.
Architecturally, the ITT4RT-Tx client sits at the media source side of an ITT4RT session. It captures immersive video—potentially from multiple cameras, 360-degree cameras, or depth sensors—and encodes it for transmission over RTP/UDP/IP. The client supports viewport-dependent streaming: it receives viewport orientation feedback from the ITT4RT-Rx client and adapts the transmitted media accordingly, prioritizing the region of interest. This may involve tiled encoding, where the immersive scene is divided into tiles and only high-quality tiles covering the viewport are sent, or asymmetric encoding with a high-quality viewport stream and lower-quality background.
The Tx client uses MTSI procedures for session negotiation, including SDP-based codec and parameter negotiation, and may use IMS for session establishment. It also participates in QoS handling, requesting appropriate QoS from the network for the uplink media stream. In teleoperation scenarios, the Tx client is often co-located with the controlled device (e.g., a robot or vehicle) and sends immersive video to a remote operator. The transmit-only designation means the client does not need to implement immersive video reception, simplifying devices that only capture and send.
In the ITT4RT architecture, the Tx client interoperates with the ITT4RT-Rx client through a standardized media session. The Tx client is responsible for encoding, packetization, and transmission, as well as for processing feedback (e.g., RTCP receiver reports, viewport orientation) to adapt the stream. It may also implement congestion control and rate adaptation based on network feedback. The separation of Tx and Rx client profiles allows asymmetric deployments where, for example, a camera-equipped robot only sends video while a monitoring station only receives it.
The ITT4RT-Tx client was introduced in Release 17 alongside the Rx client as part of the ITT4RT work item. It continues to be maintained in Releases 18, 19, and 20 with the same core definition, indicating a stable architectural role. Its existence enables standardized immersive video capture and transmission over 3GPP networks, supporting use cases from teleoperation to immersive broadcasting.
Purpose & Motivation
The ITT4RT-Tx client exists to standardize the transmit side of immersive telepresence and teleoperation media sessions. Before ITT4RT, immersive video capture and transmission over 3GPP networks relied on proprietary protocols, which hindered interoperability and made it difficult to guarantee low-latency, high-quality delivery for teleoperation. By defining a transmit-only client profile, 3GPP enables devices that only capture and send immersive video—such as robots, drones, or remote cameras—to interoperate with standardized receivers without implementing full bidirectional media capability.
The transmit-only designation simplifies device design and certification for source endpoints that do not need to display immersive content. It allows service providers to deploy asymmetric immersive services where the sender is a dedicated capture device and the receiver is a display terminal. The client's support for viewport-dependent streaming and feedback processing is essential for bandwidth efficiency, as it avoids sending full high-quality immersive video when only a viewport is needed.
Historically, immersive video uplink over mobile networks faced challenges in session negotiation, codec selection, and QoS signaling. ITT4RT-Tx builds on MTSI to reuse established IMS-based session control and QoS mechanisms, while TS 26.862 adds immersive-specific media handling. This layered approach allows the Tx client to leverage 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-Tx 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-Tx 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 |