A.2 MMS Proxy-Relay - Open Mobile Alliance

More documents

Recommendations

Info

OMA-TS-MMS-CTR-V1_3-20050617-C Page 12 (70) 4. Introduction This section is informative. The Multimedia Messaging Service (MMS) is intended to provide non-real-time messaging services to consumers utilising WAP technologies. It is an application level service that fits into the current WAP architecture. The following figure shows the general MMS Architecture. MMS Server MMSM MMS Proxy Relay MMS Store Legacy Wireless Messaging systems MMSM Other MMS Systems Internet Email Server Figure 1: MMS Network Diagram with MMS Client to MMS Proxy-Relay Link Highlighted The MMS client transactions described by this document take place on the interface labelled MMS M in the preceding diagram. The following figures present an amplified view of the MMS M link. It is built on top of the WAP architecture, which permits several possible protocol stack configurations. In its role as an application, MMS provides for the delivery and services related to messaging and the data schemes that will permit presentation methods that provide for the multimedia user experience. These presentation methods are separate from MMS. 2005 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. [OMA-Template-Spec-20050101-I]
OMA-TS-MMS-CTR-V1_3-20050617-C Page 13 (70) MMS Client Wireless Network Payload WSP WAP 1.x Gateway Internet /Intranet Payload HTTP MMS Proxy-Relay Figure 2: Implementation of MMS M Interface Using WAP 1.x Gateway This figure includes a few items that need to be described. The MMS Proxy-Relay is the network entity that interacts with the user mailbox and is responsible for initiating the notification process to the MMS Client. The WAP 1.x Gateway provides standard WAP services needed to implement MMS in the original WAP architecture, these include: WSP invocation of HTTP methods, see [WAPWSP]; WAP PUSH services, see [PUSHARCH]; OTA security, see [WTLS]; and, Capability Negotiations, see [UAPROF]. The above figure also shows a payload that is carried by WSP and HTTP. This payload represents the MMS application layer PDUs, which are described in the MMS Message Encapsulation [MMSENCAPS] document. It is expected that this data will be transported in its entirety between the MMS Proxy-Relay and the MMS Client. In a different architectural configuration HTTP is used to carry MMS PDUs directly between the MMS Client and the MMS Proxy-Relay, and a gateway is only needed for push functionality. The following figure outlines such an implementation of MMS M; note that the gateway needed for push services is omitted from the figure. Also note that a PEP may be included in the MMS M link to provide performance enhancements, as described in [WAPARCH]. MMS Client Wireless Network Payload HTTP Internet /Intranet Payload HTTP MMS Proxy-Relay Figure 3: Implementation of MMS M Interface Using HTTP Based Protocol Stack The MMS application layer is the same in the different architectural configurations; the differences are contained in the two transport stacks, i.e., the WSP based protocol stack and the HTTP based protocol stack. The bindings of the MMS PDUs to these protocol stacks are defined in section 8. This description does not address issues related to the movement or acquisition of MMs beyond the MMS Proxy-Relay as these are outside the scope of the MMS M link. 2005 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. [OMA-Template-Spec-20050101-I]
Page 1 and 2: Multimedia Messaging Service Client
Page 3 and 4: OMA-TS-MMS-CTR-V1_3-20050617-C Page
Page 11: OMA-TS-MMS-CTR-V1_3-20050617-C Page
Page 63 and 64:
OMA-TS-MMS-CTR-V1_3-20050617-C Page
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
show all

A.2 MMS Proxy-Relay - Open Mobile Alliance

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?