7.2 WAP Architectural Support for MMS

23.1403GPPFunctional descriptionMultimedia Messaging Service (MMS)Stage 2TS

WAP support for MMS is based upon the services of its supporting technology. Therefore, the scope of WAP, as it addresses MMS, is as shown in figure 7. It does not cover activities or network elements beyond those shown and no such dependencies or expectations should be inferred or implied.

Figure 7 shows an MMS Relay which in the WAP architecture’s terminology is referred to as an MMS Server. The WAP architecture also refers to the MMS User Agent as an MM Client. These cover equivalent functionalities.

Figure 7: Scope of WAP Support for MMS

Figure 7 shows two links. The first, between the wireless MMS User Agent and the WAP Gateway, is where the “WAP Stack” is used to provide a common set of services over a variety of wireless bearers. For application oriented services, like MMS, the interest is primarily in services offered by WAP Session Protocol (WSP) [23].

The second link connects the WAP Gateway and the MMS Relay. In the WAP architecture the MMS Relay is considered an Origin Server. These entities are connected over an IP network such as the Internet or a local Intranet. HTTP is used for data transfer and data can be originated from either entity.

End-to-end connectivity, for the MMS application, between the wireless MMS User Agent and the MMS Relay is accomplished by sending data over WSP and HTTP. This is accomplished using the WSP/HTTP POST method for data originating at the wireless MMS User Agent and by using the WAP Push Access Protocol [24] in the other direction.

The WAP Gateway, which enables the needed interworking, should not modify the data transfer via these transactions.

The WAP view of MMS is constrained to the interactions between the MMS User Agent and the MMS Relay. It makes no representations as to services that are provided to or required of any other network elements.