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

Glossary term · Core Network

ITT4RT MRF

Immersive Teleconferencing and Telepresence for Remote Terminals Media Resource Function

Core Network →

ITT4RT MRF is an ITT4RT client implemented as network-side functionality within the MRFC and MRFP, enabling immersive teleconferencing for terminals that cannot render immersive media locally by processing and adapting streams in the network.

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

Description

The ITT4RT MRF is the network-side realization of the ITT4RT client. It is defined in 3GPP TS 26.114 and TS 26.862 as an ITT4RT client implemented by functionality included in the MRFC (Media Resource Function Controller) and the MRFP (Media Resource Function Processor). In other words, the immersive client behaviour is not hosted on the user's device but is distributed across the control-plane and media-plane components of the IMS Media Resource Function.

The MRF is a well-established IMS entity. The MRFC handles signalling and control — it receives instructions via the Mr interface from the IMS application server (typically using SIP and H.248), manages media resources, and coordinates session-level operations. The MRFP handles the actual media processing — receiving, mixing, transcoding, and forwarding RTP streams. The ITT4RT MRF leverages this split: the MRFC portion manages the immersive session control (e.g., stream selection, viewpoint control signalling, and resource allocation), while the MRFP portion performs the media-plane work of receiving multiple immersive streams, processing them, and delivering an appropriate stream to the remote terminal.

The primary role of the ITT4RT MRF is to bridge the gap between immersive-capable sources and non-immersive or thin terminals. In a typical scenario, a conference room is equipped with multiple cameras and spatial audio capture. A remote participant with a legacy terminal cannot receive or render all of these streams. The ITT4RT MRF can terminate the immersive streams, select or compose a view, adapt the media to the terminal's capabilities, and deliver a single, renderable stream. It can also relay control messages from the remote terminal (such as viewpoint selection) back to the immersive source, so the remote user can still influence what they see and hear even though the heavy processing happens in the network.

Because the ITT4RT MRF is an ITT4RT client, it implements the same core capabilities as the in-terminal variant: multi-stream reception, synchronization, viewpoint and audio-perspective handling, and media negotiation. The difference is location and scale. Being in the network, the MRF can serve many terminals simultaneously, apply operator policies, perform transcoding between codecs, and provide a consistent immersive experience regardless of device capability. This makes it a key enabler for operator-deployed immersive conferencing services.

In the overall architecture, the ITT4RT MRF sits on the media path between the immersive conference source and the remote terminals. It is controlled by the IMS application server through the MRFC, and it exchanges media with endpoints through the MRFP. Its presence allows operators to offer immersive teleconferencing as a network service rather than requiring every endpoint to be upgraded, which is essential for widespread adoption and for interworking with the existing MTSI installed base.

Purpose & Motivation

The ITT4RT MRF exists to make immersive teleconferencing deployable at scale. The fundamental obstacle to immersive services is device heterogeneity: most terminals in the field cannot receive, decode, synchronize, and render multiple high-resolution video streams plus spatial audio. If immersive teleconferencing required every participant to have a capable device, adoption would be limited to a small set of high-end users and the service would not be economically viable for operators.

Before the ITT4RT MRF concept, network-side media processing existed for conventional conferencing — mixing audio, switching video, transcoding codecs — but there was no standardized way to perform immersive-specific processing in the network. Proprietary media servers could approximate some functions, but they lacked standardized control signalling for viewpoint selection, standardized handling of multiple immersive streams, and standardized interworking with MTSI endpoints. This meant that immersive services could not be offered interoperably across vendors.

The ITT4RT MRF solves this by defining immersive client functionality as a first-class capability of the MRF, using the existing MRFC/MRFP split that operators already deploy. This has several advantages. First, it reuses established IMS architecture and control interfaces, reducing deployment complexity. Second, it allows the network to adapt immersive media to each terminal's capabilities, so legacy devices can participate in immersive sessions with a degraded but usable experience. Third, it centralizes processing, which is more efficient than requiring every device to perform heavy rendering. Finally, it enables operators to control quality, apply policies, and charge for immersive services. The ITT4RT MRF is therefore the architectural mechanism that turns immersive teleconferencing from a device-centric feature into an operator-grade network service.

What changed in its specifications

The latest release-to-release comparison of specifications that define ITT4RT MRF. 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 MRF as an ITT4RT client implemented by functionality included in the MRFC and the MRFP, establishing the network-side counterpart to the in-terminal ITT4RT client.

The definition text carried over unchanged from Rel-17; the ITT4RT MRF remained defined as an ITT4RT client implemented by MRFC and MRFP functionality.

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 ITT4RT MRF remains an ITT4RT client implemented by functionality included in the MRFC and the MRFP.

Defining Specifications

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