Core Multimedia Engine

Mercury's fast, robust, scalable Mobile Multimedia engine includes network connectors that link 2G, 2.5G, 3G and internet environments via WAP/MMS, Java, H.324M and SIP protocols. Capable of thousands of transactions per second and consistently handling millions of multimedia transactions per hour, the engine has been designed for both horizontal and vertical N+1 scaling for maximum flexibility and cost-efficiency.


 

Routing Paths

MMS

The platform provides a fully featured traditional MMSC that supports all 3GPP protocols (MM1-MM7) – additionally designed to handle very high volume A2P (application-to-peer for content delivery) output. Platform throughput is benchmarked at a sustainable 300 MMS/second (at 40% CPU).

MMS delivery schemes include:

  • P2P: Peer-to-peer including MM4
  • A2P, P2A: Application-to-peer, peer-to-application
  • MMS Proxy: MMS Gateway 

 

PAT (Profile Address Translation)

3GPP MM1 protocol fix for multi MMSC environments

In a network architecture where more than one MMSC exists, the 3GPP MMS specifications fall short of defining more that one MMSC URP on the mobile device to indicate the MMSC ID. This means that if there is more than one MMSC in the MMS Environment (MMSE) the final "read" receipt from the device can only be sent to the present MMSC URL - which may be different from the actual originating MMSC. This results in incomplete stats for campaigns and has an adverse effect on the legacy MMSC - which will receive thousands of "read receipts" for messages that it did not send, crippling its operation. The PAT module sits in front of the MMSC and by intercepting all MMS traffic it brings the intelligence to the network to route read receipt messages to the correct MMSC. 

 

Load Balancer

Pat can also be used as a load balancer between MMSC's - distributing traffic statically and dynamically to multiple MMSCs. 

Mobile Number Portability

Pat can resolve destination addressed for Mobile Number Portability utilizing either one of the methods:

  • Using the MM5 protocol to query the HLR over signaling links to get MNP information
  • HTTP lookup to an external MNP database (shared or internal to the operator)

 

WAP Gateway

A fullly functional WAP Gateway capable of 600 transactions per second on a single server.

 

iSMS (P2P SMS content insertion)

Sits in front of an SMSC or Router to intercept P2P SMS and apply specific logic - such as advertising insertion.

FastSMS (unlimited TPS capacity)

  • Launch SMS (MT)
  • Get SMS (MO)
  • SMS Proxy

SMS routing functionality

Can be deployed as SMS MT for delivery of A2P SMS traffic, MMS, MM1 and OTA messages through to the core network OR can be deployed as MT + MO for P2P routing functionality.

NOTE: With the addition of the NewNet SMS retry module, iSMS can be extended to become a fully fledged SMSC.

 

VideoCenter

  • RTSP/RTP Proxy (unlimited)
  • H324.M (per 64 simultaneous sessions)
  • SIP (per 64 simultaneous sessions)
  • Streaming Gateway for streaming video etc.
  • Throughputs of 60+ simultaneous sessions per server for RTP and 60+ simultaneous sessions per card for H324.M

      •