Multimedia Telephony Service over IMS Client

Description

The MTSI client is defined in 3GPP TS 26.114 and TS 26.980 as a function in a terminal or in a network entity (e.g., a Media Resource Function Processor, MRFP) that supports the Multimedia Telephony Service over IMS (MTSI). MTSI is the 3GPP-defined service that provides real-time multimedia conversational services, such as voice and video telephony, over the IP Multimedia Subsystem (IMS). The MTSI client is the functional component that implements the media handling, session control, and interoperability required for MTSI.

In a terminal, the MTSI client is typically part of the UE's IMS stack, responsible for media negotiation (SDP), codec selection, media transport (RTP/RTCP), and adaptation mechanisms. It interacts with the IMS core via SIP for session establishment and control, and with the access network for QoS. In a network entity such as an MRFP, the MTSI client provides media processing functions like transcoding, mixing, and announcement playback, enabling services like conferencing and interworking with circuit-switched networks.

The MTSI client supports a wide range of codecs and features defined in TS 26.114, including AMR, AMR-WB, EVS for voice, and H.264, H.265 for video. It also implements robustness mechanisms such as RTP retransmission, forward error correction, and jitter buffer management to maintain quality over lossy networks. The client negotiates media parameters using SDP offer/answer, ensuring that both endpoints agree on codecs and media formats.

One of the key roles of the MTSI client is to ensure interoperability between different vendors and network domains. By adhering to 3GPP specifications, an MTSI client from one vendor can communicate with another, and with IMS core elements from different vendors. This is crucial for operator deployments where multi-vendor interoperability is required. The MTSI client also supports service continuity and interworking with legacy networks, such as when a call is handed over from LTE to 3G or when interworking with CS networks via the IMS Centralized Services (ICS) architecture.

In 5G, MTSI continues to be the basis for voice over NR (VoNR) and video telephony, with the MTSI client evolving to support new codecs and features like immersive video and low-latency communication. The MTSI client is thus a fundamental building block for real-time multimedia services in 3GPP networks, ensuring a consistent user experience across access technologies and devices.

Purpose & Motivation

The MTSI client exists to provide a standardized implementation of multimedia telephony services over IMS, ensuring interoperability and consistent quality across different devices and networks. Before MTSI, operators deployed proprietary or vendor-specific VoIP and video telephony solutions, which led to interoperability issues and fragmented user experiences. The 3GPP MTSI specification (TS 26.114) was created to define a common set of media handling procedures, codecs, and features that any compliant client must support, enabling seamless communication between users regardless of device or network vendor.

The MTSI client solves the problem of media negotiation and adaptation in heterogeneous networks. It defines how to negotiate codecs, handle packet loss, manage jitter, and adapt to changing network conditions. This is essential for maintaining acceptable voice and video quality over mobile networks, which are subject to varying radio conditions and congestion. By implementing these mechanisms, the MTSI client ensures that users experience reliable calls even when network conditions degrade.

Additionally, the MTSI client enables network-based media processing through MRFP, supporting services like conferencing, announcements, and transcoding for interworking with legacy networks. This flexibility allows operators to offer advanced services without requiring all endpoints to support every codec or feature. In summary, the MTSI client is the key enabler for interoperable, high-quality multimedia telephony in 3GPP networks, and its definition has remained stable since Rel-8, reflecting its mature and foundational role.