Messaging & Entitlement MMS Suite

A complete MMS stack — MMSC, load balancer, transcoding agent and MM1/MM4/MM7 gateways — built for one specific job: replacing an end-of-life MMSC cleanly, at a cost proportionate to a declining traffic type.

MMSC with MM1, MM4, MM7 and MM9 interfaces
MMS load balancer and delivery agent for horizontal scale
Transcoding agent: format, resolution and codec adaptation per device profile
Interworking with legacy WAP-based clients and modern HTTP delivery
Multi-tenant, containerised, and instrumented for assurance

Scope an MMSC replacement

Messaging & Entitlement

MMSC

MM1 · MM4 · MM7 · MM9

Transcoding

MMS load balancer

Delivery agent

WAP and HTTP clients

Multi-tenant

Kubernetes

EOL replacement

A candid word about MMS

MMS traffic is in structural decline and RCS is where the picture messaging of the next decade goes. We are not going to build you a growth story around MMS and you should be suspicious of anyone who does.

What is real is this: a large number of operators are running an MMSC from a vendor who has ended support, on hardware nobody wants to re-certify, under a maintenance contract priced for 2010 volumes. The traffic is falling but it has not stopped, and it will not stop before the platform does.

For that situation there is a good answer: replace it with something small, containerised and cheap to run, get out of the support contract, and let the traffic decline on a platform that costs you almost nothing to keep. We maintain this suite, we deploy it, and we price it for exactly that job.

Components

MMSC

The core message centre: submission, storage, notification, retrieval and delivery reporting across MM1, MM4, MM7 and MM9.

MMS Load Balancer

Distributes submission and retrieval across MMSC instances, with session affinity and health-based routing.

Transcoding Agent

Adapts image, audio and video to the receiving device profile, with a maintained device capability database.

MM4 / MM7 Gateways

Interconnect with other operators and with content providers, including per-partner policy and rated records.

Logical architecture

MM1 front end. Device submission and retrieval over HTTP, with legacy WAP gateway interworking where the handset base still needs it.

Relay and store. Message persistence, notification scheduling, retry and expiry.

Transcoder pool. Stateless workers scaled on queue depth.

MM4 and MM7 edges. Interconnect and content-provider interfaces with per-partner authentication and rating.

Assurance plane. ProBee on every interface, with delivery quality per partner and per device class.

SMSC

Messaging & Entitlement

Stuck with an unsupported MMSC?

We have done this cutover several times, including at Tier-1 scale. Ask for the reference and the method.

Contact us

Case studies