Multimedia Telephony Service over IMS Client in Terminal

Description

The MTSI client in terminal is a functional entity defined in 3GPP TS 26.114 that represents the terminal-side implementation of the Multimedia Telephony Service over IMS (MTSI). MTSI is the 3GPP-defined service that provides real-time conversational multimedia services — including voice, video, text, and file sharing — over the IMS (IP Multimedia Subsystem) infrastructure. The MTSI client in terminal is the portion of the MTSI architecture that resides in the user equipment (UE), as opposed to network-side media processing entities such as the Media Resource Function Processor (MRFP), Media Resource Function Controller (MRFC), or media gateways.

The MTSI client in terminal encompasses a comprehensive set of media handling capabilities. It includes media encoding and decoding (codecs for speech, video, and text), media stream multiplexing and demultiplexing, jitter buffer management, packet loss concealment, and media adaptation mechanisms. It also handles session control interactions with the IMS core through SIP/SDP signaling, negotiating media parameters such as codec selection, media formats, and quality-of-service requirements. The client supports both conversational (e.g., two-way voice and video calls) and non-conversational (e.g., file transfer, video sharing) media services.

Architecturally, the MTSI client in terminal interacts with several network components. It communicates with the IMS core via the Gm interface for session control, with the PCRF/PCF for policy and charging control, and with the media transport network for bearer establishment. The client must support the media plane requirements defined in TS 26.114, including RTP/RTCP protocols, codec configurations, and media synchronization. It also supports the concept of media adaptation, where the client can dynamically adjust media parameters (bit rate, codec mode, packetization) in response to changing network conditions, ensuring acceptable quality of experience.

The distinction between the MTSI client in terminal and other MTSI entities is important for specification clarity. When 3GPP specifications refer to the MTSI client in terminal, they are specifically addressing requirements, capabilities, and behaviors that apply to the endpoint implementation — the software and hardware in the UE that handles media. This excludes network-side media processing functions that may also participate in an MTSI session, such as conference bridges (MRFP), media servers, or transcoding gateways. This distinction allows terminal vendors to implement the client with a clear understanding of their scope of responsibility.

Over successive releases, the MTSI client in terminal has evolved to support additional codecs (e.g., EVS for enhanced voice services in Rel-12, IVAS for immersive voice and audio in Rel-16), new media types, and enhanced adaptation mechanisms. The client must also support various access technologies (LTE, NR, Wi-Fi) and maintain service continuity across handovers. The MTSI client in terminal is fundamental to enabling interoperable, high-quality multimedia telephony services across different vendors' equipment and different network deployments, as it ensures a common baseline of media handling capabilities at the endpoint.

Purpose & Motivation

The MTSI client in terminal exists to define a standardized, interoperable implementation of multimedia telephony services at the endpoint. Before MTSI, multimedia telephony implementations were fragmented, with different vendors using proprietary codecs, media handling mechanisms, and session control procedures. This fragmentation led to interoperability problems, where a call between two different terminals might fail or degrade to a lowest-common-denominator service. MTSI, defined in 3GPP Release 7 and onwards, aimed to create a unified service specification that would guarantee baseline interoperability for conversational multimedia services over IMS.

The MTSI client in terminal specification serves several critical purposes. First, it provides a normative reference for terminal vendors, specifying exactly what media handling capabilities, codecs, and protocols must be implemented to claim MTSI compliance. This ensures that any MTSI-compliant terminal can interoperate with any other MTSI-compliant terminal and with network media functions. Second, it enables network operators to deploy IMS-based multimedia services with confidence that terminals will support the required media features, reducing the need for network-side transcoding and media adaptation. Third, it provides a framework for media adaptation and quality-of-service management, allowing terminals to dynamically adjust to network conditions and maintain acceptable quality.

The term "MTSI client in terminal" specifically addresses the need to distinguish endpoint implementations from network-side media processing. In an IMS multimedia session, media may be processed by both the terminal and network entities (e.g., for conferencing, transcoding, or recording). By defining the MTSI client in terminal as a distinct entity, 3GPP specifications can clearly delineate which requirements apply to the terminal and which apply to network functions. This clarity is essential for testing, certification, and regulatory compliance, as it allows stakeholders to verify that terminals meet the necessary requirements without conflating them with network equipment requirements.