MMS Transaction.pptx

MMS TransactionsAgendaMMS Client TransactionsImplementation of MMS transactionHow to analyze MMS’s transaction bugsMMS Client TransactionsOverview of the general MMS ArchitectureMMS Client Sending Message to MMS Proxy-RelayMMS Proxy-Relay Sending Notification to MMS ClientMMS Client Retrieving Message from MMS Proxy-RelayMMS Proxy-Relay Sending Delivery Reports to MMS ClientRead ReportsOverview of the general MMS ArchitectureThe Multimedia Messaging Service (MMS) is intended to provide non-real-timemessaging services to consumers utilizing WAP technologies. It is anapplication level service that fits into the current WAP architecture.Overview of the general MMS ArchitectureMMS Client Sending Message to MMS Proxy-RelayThe MMS Client that wishes to send an MM SHALL include the MM in an M-Send.reqand submit the resulting PDU to the MMS Proxy-Relay that supports the specificMMS Client.MMS Proxy-Relay Sending Notification to MMS ClientTo inform an MMS Client that an MM is available and for it to return back information,a set of asynchronous PDUs, MNotification.ind and M-NotifyResp.ind, are utilized.This provides the mechanism for the MMS Proxy-Relay to notify the MMS Client with certain factors about the new MM. This will let the MMS Client retrieve the MM.MMS Client Retrieving Message from MMS Proxy-RelayImmediate RetrievalDeferred RetrievalImmediate Retrieval FlowA receiving MMS Client is said to perform immediate retrieval of a new MM when itretrieves the data from the MMS Proxy-Relay before acknowledging the messagenotification.Deferred Retrieval FlowA receiving MMS Client is said to perform deferred retrieval of a new MM when itfirst acknowledges the notification and at some later point retrieves the messagefrom the MMS Proxy-Relay. A specific type of deferred retrieval is the manualretrieval, which requires the recipient users confirmation prior to retrieving themessage.Deferred Retrieval FlowMMS Proxy-Relay Sending Delivery Reports to MMS ClientThe M-Delivery.ind