science

MMS Architecture

MMS Architecture is a science topic covered in the lgStudy science library. This page brings together a partial reference excerpt, illustrations, worked examples, real-world applications and a short study plan, so you can understand MMS Architecture rather than just read about it. In short: The MMS Architecture is the set of standards used by the Multimedia Messaging Service in mobile networks. The standards are prepared by 3GPP.

Key takeaways

MMS Architecture belongs to science; place it in that map before memorising details.
Learn the definition first, then one example that makes the definition concrete.
Connect MMS Architecture to a quantity you can measure, compute or draw — that is where exam questions come from.
Reproduce the core statement of MMS Architecture from memory before moving on to harder problems.

Reference excerpt

The MMS Architecture is the set of standards used by the Multimedia Messaging Service in mobile networks. The standards are prepared by 3GPP.

Overview

The standard consists of a number of interfaces between components found in the mobile network:

MM1: the interface between MMS User Agent and MMS Center (MMSC, the combination of the MMS Relay & Server). Delivered as HTTP over a packet switched data session. MM2: the interface between MMS Relay and MMS Server. MM3: the interface between MMSC and other messaging systems. Using SMTP. MM4: the interface between MMSC and foreign network providers. Using SMTP. MM5: the interface between MMSC and HLR. MM6: the interface between MMSC and user databases. MM7: the interface between MMS Value-added service applications and MMSC. Typically Content Providers using HTTP / SOAP for delivery. MM8: the interface between MMSC and the billing systems. MM9: the interface between MMSC and an online charging system. MM10: the interface between MMSC and a message service control function. MM11: the interface between MMSC and an external transcoder.

MM1 MM1 is the interface between a Mobile Station (MS) and an MMSC. MM1 is used in the following actions:

The sender subscriber sends an MMS to the MMSC The MMSC notifies the recipient subscriber that they have an MMS waiting for retrieval The recipient subscriber retrieves the MMS from the MMSC The MMSC notifies the sender that the recipient has retrieved the message The recipient subscriber manages their mailbox in the MMSC (uploads MMS, deletes MMS, ...) The MM1 interface is based on the WAP protocol. It includes the PAP notifications that are transformed to SMS's by the WAP gateway for the notifications.

MM2 MM2 is an interface between a MMS Relay (MMS-R) and an MMS storage database, two components of an MMSC platform.

MM3 MM3 is the interface between MMSC and external servers such as Email server or SMS Centers SMSC. This interface typically uses TCP/IP based protocols for e.g. Simple Mail Transfer Protocol ( SMTP ) Generally, it is the responsibility of MMSC to do the transformation of MMS multi-part binary data to MIME format of email in both the direction MM3 is used in the following actions:

To exchange messages with external servers such as Email Server or SMS Centers

MM4 MM4 is the interface used to exchange messages between two different MMSCs. These MMSCs are generally located in two distinct Mobile Networks This interface is also known as the MMSR interface in the Wireless Application Protocol (WAP) and the Open Mobile Alliance (OMA) standards.

MM5 MM5 is the interface between MMSC and other network elements like HLR or Domain Name Server. The communication over MM5 Interface is generally to fetch the routing information. MM5 has been defined by the 3GPP in TS 23.140 as a simple reference to Mobile Application Part.

MM7 MM7 is the interface between MMSC and a value-added service provider (VASP). The MM7 interface is used to send MMS from 3rd party providers (e.g., a bank sending a statement or an advertiser sending publicity). It is based on SOAP with attachments, using HTTP as the transport protocol. HTTP request shall be a POST. The message is a MIME which encapsulates the SOAP envelope and the encoded attachments. The SOAP envelope is an XML where tags are the MM7 protocol data.

MM11 MM11 is specified by OMA STI (Standard Transcoding Interface) 1.0. MM11 is designed to ensure compatibility of transcoders with MMSCs. Integration with a transcoder without using MM11 is possible by implementing the transcoder as a proxy server. By placing the transcoder on the MM1 interface between the user equipment and the MMSC, messages can be transparently transcoded. A possible disadvantage of this implementation is that transcoders are typically licensed in transactions per second. All transactions will be sent through the transcoder, rather than just those marked to allow adaptations.

Worked examples

Example 1 — a first encounter with MMS Architecture

Start with the simplest possible case. Write down what MMS Architecture claims or describes in one sentence, then invent the smallest concrete situation in which that sentence is true. In science, the smallest case is usually a single object, a single equation or a single measurement. Check that every symbol or term in your sentence has a meaning in that case.

Example 2 — changing one variable

Take the situation from Example 1 and change exactly one quantity: double it, halve it, or set it to zero. Predict what should happen to MMS Architecture before you calculate. Comparing your prediction with the result is the fastest way to find out whether you understand the idea or only the words.

Example 3 — an exam-style question

Typical questions about MMS Architecture ask you to (a) state it precisely, (b) apply it to given data, and (c) explain a limitation. Practise writing all three answers in under five minutes; the third part is what separates a full-mark answer from an average one.

Applications of MMS Architecture

In research: MMS Architecture appears in science research whenever the underlying quantities have to be modelled precisely. Papers usually cite it as a starting assumption and then explore where it breaks down.
In technology and industry: Engineering practice reuses MMS Architecture in design rules, simulations and safety margins. Knowing the idea lets you read a specification sheet and understand why the numbers look the way they do.
In the classroom: MMS Architecture is common in secondary-school and first-year university syllabi. It links to neighbouring topics 3GPP standards, Application layer protocols, GSM standard, so understanding it makes those chapters shorter.
In everyday life: Look for MMS Architecture outside the textbook — in sport, cooking, traffic, electronics or the sky above you. An example you found yourself is remembered far longer than one you were given.

Affiliate

Preply — study more efficiently by working with a personal tutor. 50% off.

How to study MMS Architecture in 20 minutes

Read the reference excerpt below once, without taking notes.
Close the page and write down what MMS Architecture means in your own words.
Compare your version with the excerpt and mark what you missed.
Work through the three examples above with pen and paper.
Explain MMS Architecture out loud to somebody else — or to Teacher Smith in the lgStudy chat.

Frequently asked questions

What is MMS Architecture in simple terms?

The MMS Architecture is the set of standards used by the Multimedia Messaging Service in mobile networks. The standards are prepared by 3GPP.

Why does MMS Architecture matter?

Because it connects several science ideas at once: it gives you a definition you can apply, a quantity you can calculate, and a way to check whether a result is plausible.

How should I study MMS Architecture?

Read the excerpt, restate it from memory, then work through the examples and applications listed on this page. The five-step study plan above takes about twenty minutes.

What does this page cover?

It gives you a compact reference excerpt plus original lgStudy explanations, examples, applications and study material on MMS Architecture.