f view, this can be considered as an input, defined by the configuration offered in every case. MMS NETWORK PLANNING External Application Gateways and Services There is a need to establish and define connectivity between the MMSC and other servers which provide applications. Since every project will deploy different external applications, it must be defined case by case. VLAN separation offers the possibility of easier management and operation. The addressing plan should take into account the required allocation of IP addresses in both cases, when using VLAN or when using direct connections. SMSC should be considered part of the MMS solution, since it plays an active role in the MMS delivery process. SMS is the bearer for the transmission of notifications and delivery reports to subscribers. It is considered that the delivery of a 'mobile terminated' MMS within a network will generate additional SMS in the network. Thus, the plans and capacity forecasts of an SMS system must be reviewed in line with the penetration of MMS-capable phones. WAP Gateway The main connection is towards the WAP gateway, which will provide the WAP mechanism for MMS delivery. The MMS system relies on the existing WAP gateway to provide con- nectivity to the GPRS packet core and push functionality, for instance. An adequate MMS configuration should be set in the WAP Gateway. Inter-MMSC Connectivity and Roaming It can be considered that, where two PLMN are involved, there are also two MMSC involved in a mobile-to-mobile delivery process: the sender uses its own network MMSC and the receiver obtains the MMS from its own network MMSC. Sender and receiver may have different kinds of services provided in different ways, if they belong to different networks. If sender and receiver belong to the same network, the physical MMSC involved in both processes is likely to be the same, although in larger networks there could be more than one MMSC, thus required additional WAN networked connectivity. In terms of connectivity, several networking options a