More Instant Messaging Interoperability

Description

More Instant Messaging Interoperability (MIMI) is a 3GPP service framework introduced in Release 18 to facilitate direct communication between users of different, proprietary instant messaging (IM) services. Its architecture is based on a federated model where participating service providers (SPs) interconnect through standardized interfaces defined in 3GPP specifications. The core of MIMI involves the MIMI Application Server (AS), which resides within an SP's network and acts as the gateway for interoperability. This AS communicates with the SP's native IM system and, crucially, with the MIMI ASes of other SPs using protocols specified in 3GPP TS 26.143 and related specs. The framework defines essential functions for message routing, identity mapping, security, and delivery status reporting across administrative domains.

From a technical perspective, MIMI works by establishing trust and standardized communication channels between service providers. When a user on Service A sends a message to a user on Service B, the message is first processed by Service A's native system and then handed to its MIMI AS. The MIMI AS performs necessary protocol conversions, applies end-to-end encryption as per the framework's security model, and routes the message to the recipient's MIMI AS based on a federated identifier. The recipient's MIMI AS then delivers the message to Service B's native IM system for presentation to the end user. This process ensures the message format, security, and features are translated appropriately between the two potentially different underlying technologies.

Key components of the MIMI architecture include the MIMI Application Server, the MIMI Gateway Function for protocol adaptation, and the Identity Management Function for mapping user identities between different domains (e.g., converting a phone number to a service-specific identifier). The framework also specifies a common set of baseline messaging features—such as one-to-one and group messaging, file transfer, read receipts, and typing indicators—that must be supported for interoperability. Its role in the network is as an overlay service enabler, sitting above the core connectivity provided by the 5G System (5GS) or other access networks, leveraging the network for transport but adding the application-layer logic for cross-service communication.

Purpose & Motivation

MIMI was created to solve the pervasive problem of messaging silos, where users are confined to communicating only with others on the same proprietary platform (e.g., WhatsApp, iMessage, WeChat). This fragmentation is a significant user experience issue and a barrier to universal communication. Historically, interoperability was attempted through third-party bridges or multi-protocol clients, but these were often unsanctioned, insecure, and unreliable. MIMI provides a standardized, secure, and carrier-grade alternative endorsed by the telecommunications standards body.

The motivation stems from regulatory pressures in various regions demanding interoperability for dominant messaging services to foster competition and user choice, as well as from the telecom industry's desire to remain relevant in the OTT-dominated messaging space. Previous approaches lacked a unified technical standard, leading to inconsistent implementations and security vulnerabilities. MIMI addresses these limitations by providing a comprehensive specification that covers the entire interoperability stack—from identity and discovery to message format, transport, and end-to-end encryption—ensuring that services can interconnect in a predictable and secure manner while allowing providers to differentiate on features within their own ecosystems.

Key Features

• Federated architecture enabling interconnection between independent service providers
• Standardized protocol suite (specified in 3GPP TS 26.143) for message exchange between MIMI Application Servers
• End-to-end encryption framework to ensure message confidentiality across domains
• Identity mapping and discovery mechanisms to resolve user identifiers between different services
• Support for baseline feature set including 1:1 chat, group messaging, and delivery status notifications
• Backward compatibility and feature negotiation to handle disparities in supported capabilities between services

Evolution Across Releases

Defining Specifications