When you send an MMS Message request, a m-send-req Protocol Data Unit
(PDU) is sent to the MMS Gateway over WAP Post. The gateway accepts the
MMS for delivery and sends a confirmation back (m-send-conf).
2. Through a binary SMS known as WAP Push, the gateway sends a notification
(m-notification.ind) to the receiver that a new MMS Message is available.
The MMS client at the receiver end may opt to download the message later.
In this case a m-notifyResp.ind message is sent back to the gateway.
Essentially, the client is telling the gateway that "Oh yeah... I got your
notification. But I will see the message later, I'm kinda busy right now!".
3. When the client is ready to see the message, (which could be immediately
as well), it sends a request (m-retrieve.conf or HTTP Get.req) to the
gateway. The gateway picks up the MMS Message, sends it over the client,
and waits for the client to send m-acknowledge.ind.
4. Once the acknowledgement is received, the gateway passes back an
m-delivery.ind message to the originator, saying "Hey, I've done my job.
Your message is delivered!"
Don't you think MMS is much more involved than SMS? All those "m-*.
Pages:
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179