rminal MMS-C copies/forwards MMS-C HTTP, PAP selected MM to E- receives MM mail box(es) content from Access network WAP GW mobile for MMS-C immediate Multimedia delivery to content destination server MMS-C receives mobile or to push MM content distribution list SMPP = Short message peer-to peer protocol from servers for PPG = Push proxy gateway immediate delivery PAP = Push access protocol to terminal Figure 8.25 Mobile multimedia service. UM = unified messaging The MMS server is responsible for the storage and handling of incoming and outgoing messages. Several MMS servers can be included within an MMSE, e.g. MMS server, e-mail server, SMS centre (SMSC) and fax servers. The MMS user databases may consist of lots of different data including user pro- file database, subscription database and home location register (HLR) information for mobility management. The MMS user agent is an application layer function that provides users with the ability to view, compose and handle multimedia messages (MMs), e.g. sending, receiv- ing, deleting. This architecture allows multimedia access to all types of information with a range of servers providing access to new and legacy services. This allows operators to consolidate access to multiple applications from a single architecture, e.g. SMS-C, unified messaging, e-mail, see Figure 8.25. 8.8 SPECIFIC FUNDAMENTAL TECHNICAL PLANS 8.8.1 PROJECT RULE HANDBOOK For a lot of staff involved in the implementation of a project FP information is highly valuable. In fact it could be a common tool, similar to a baton in a relay race. Such a handbook might consider: Business aspects Existing network and associated development tracks Target network Main traffic cases Service Implementation Fundamental technical plans with QoS, security, numbering, functional distribution and configuration, interconnect with roaming, SLA (service level agreement), interconnect charges, management and other FPs. A few examples of content are given below: Numbering - IPv4, IPv6, PDP context with network address and