Nokia Multimedia Terminal Gateway Release 1Part of the Multimedia Messaging Service Application Suite

Product DescriptionIntroductory Document1Issue 0-1 en Copyright Nokia Corporation 2002.

PURPOSE. This document describes the product(s) defined in the introduction of this document and is subject to change without notice. This document is intended for the use of Nokia Corporations customers for the sole purposes of the agreement under which it is submitted. It has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it.PROVIDED AS IS. Nokia Corporation has used reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. This document is provided on an AS IS basis, with no warranty of any kind. NOKIA CORPORATION SPECIFICALLY DISCLAIMS ANY AND ALL IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF FITNESS, MERCHANTABILITY AND TITLE. Further, the information or statements contained in this document concerning the suitability, capacity or performance of the product(s) concerned are not binding, except as may explicitly be agreed to by Nokia Corporation in the agreement under which this document is submitted.Limitation of Liability. Nokia Corporation liability for any errors in the document is limited to the documentary correction of errors. IN NO EVENT SHALL Nokia Corporation HAVE ANY LIABILITY FOR ANY DAMAGES OF WHATEVER NATURE, WHETHER DIRECT, INDIRECT, SPECIAL, INCIDENTAL, ECONOMIC OR CONSEQUENTIAL, that might arise from the use of or inability to use this document or anything contained herein.Intellectual Property Rights. This document and the product it describes are protected by copyright according to applicable laws. No part of this document may be reproduced or transmitted in any form or by any means without the prior written permission of Nokia Corporation. Nokia and Nokia Connecting People are registered trademarks of Nokia Corporation.Product names mentioned in this document may be trademarks of their respective companies and are mentioned for identification purposes only.Copyright Nokia Corporation 2002. All rights reserved.Documentation TeamJeff Evangelista, Maria Muia, Peg Mulligan, Joe Paul, Daniel Shugrue, and Len Turmel.2Copyright Nokia Corporation 2002.

1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.1 About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5DN0254713 3

1.2 Audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.3 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.4 Typographic conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.5 TGW documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.6 Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.7 If you have documentation comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.8 Revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2 Overview of the Nokia Multimedia Messaging Solution . . . . . . . . . . . . . . 132.1 Multimedia messaging services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.2 The Nokia MMS solution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.2.1 Nokia Artuse MMS Center (MMS Center) . . . . . . . . . . . . . . . . . . . . 132.2.2 Nokia Multimedia Terminal Gateway (TGW). . . . . . . . . . . . . . . . . . . . 142.2.3 Nokia Multimedia E-mail Gateway (EGW) . . . . . . . . . . . . . . . . . . . . . 142.2.4 Nokia Artuse Messaging Platform (NAMP) . . . . . . . . . . . . . . . . . . . 14

3 Nokia Multimedia Terminal Gateway: Release 1. . . . . . . . . . . . . . . . . . . . . 173.1 Product overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.2 TGW audience terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3.2.1 TGW subscribers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.2.2 Non TGW subscribers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.2.3 TGW end users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

3.3 TGW product package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

4 Functional Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194.1 Multimedia service applications functional overview . . . . . . . . . . . . . . . . . . . . . 194.2 TGW traffic flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

5 TGW R1 Product Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215.1 Album services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

5.1.1 Personal album storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215.2 Legacy phone support services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225.3 TGW administration and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

5.3.1 Class of Service Plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235.3.2 Administrator interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235.3.3 Class of Service Plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235.3.4 Supervisor interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245.3.5 Subscriber provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245.3.6 Configuration management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

5.4 Additional TGW product features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255.4.1 Log management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255.4.2 Report management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Issue 0-1 Draft en Copyright Nokia Corporation 2002.

5.4.3 Billing and billing management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255.4.4 Resource management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

5.4.5 Fault management and SNMP alarms . . . . . . . . . . . . . . . . . . . . . . . . . . 275.4.6 Performance management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275.4.7 Database management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

6 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296.1 Transport protocols and bearers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296.2 Architecture illustration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306.3 Scalability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306.4 Software redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306.5 Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

6.5.1 HW configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316.5.2 System software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

7 Training, Delivery and Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337.1 Documentation materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337.2 TGW documentation audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337.3 TGW documentation set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

7.3.1 TGW release binder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347.3.2 Additional reference materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

7.4 Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347.4.1 TGW system training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347.4.2 TGW installation training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357.4.3 TGW operation and maintenance training . . . . . . . . . . . . . . . . . . . . . . . 357.4.4 Training duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

7.5 Delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367.6 Product support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367.7 Software support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367.8 Sun support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Copyright Nokia Corporation 2002.

Preface

1 PrefaceDN0254713 5

The preface provides the following introductory topics: About this document Audience Scope Typographic conventions TGW documentation Related documentation If you have documentation comments Revision history

1.1 About this document

This product description provides general information about the Nokia Multimedia Terminal Gateway (TGW).

1.2 Audience

This document is written for anyone who wants an introduction to TGW and for all personnel involved in the operations of TGW who need general knowledge of the capabilities of TGW.

1.3 Scope

The document provides information on: Functionality Features Architecture Customer documentation Customer training Technical supportIssue 1-0 en Copyright Nokia Corporation 2002.

1.4 Typographic conventions6

The following notes and table provide a list of the typographic conventions that appear in this document.

Warning: This information helps avoid damage to the phone, personal injury, orproperty damage.

Caution: This information helps avoid loss of data.

The task icon marks the beginning of a procedure or task sequence.

1.2.3.

Note: This information provides explanatory information.

Tip: This information provides helpful guidelines for easy operation.

Convention Description

Courier Font Used for file names, lines ofcode, names of processes, andcommands.

Heavy courier Used for command line user input.

Bold Used for textual parts of graphical user interface, including menu items, buttons, toolbar names and options, and tabs.

Italics Used for screen names and document titles.

Bold Italics Used for emphasis.

(Angle Brackets) With italics text, used for variable data.

Table 1 Typographic conventionsCopyright Nokia Corporation 2002.

Preface

Convention DescriptionDN0254713 7

1.5 TGW documentation

For more information on Nokia Multimedia Terminal Gateway Release 1 (TGW R1), refer to the complete TGW documentation set, as described in the following table.

[___] (Square Brackets) Used for optional data such as command line arguments and database fields.

\ Backslash at the end of lines indicates that there is insufficient space and the line is continued in the space below.

| Vertical bar used between choices, for example in variable data in configuration file arguments.

Used for section and chapter titles.

Table 1 Typographic conventions

Document Document Number Audience Description

Administrators Web-based Help

Not Applicable Intended for system administrators who work directly for the operators and who are responsible for configuring and troubleshooting airtime services for subscribers.

Subscribers Web-based Help

Not Applicable Intended for TGW subscribers who are accessing their messages via their multimedia-messaging terminal.

Subscribers WAP-based Help

Not Applicable Intended for TGW subscribers and non TGW subscribers who are accessing TGW with the Wireless Application Protocol (WAP).

Table 2 TGW documentation setIssue 1-0 en Copyright Nokia Corporation 2002.

Document Document Number Audience Description8

Guide to Documentation

DN01154073 Intended for anyone seeking guidelines on how to use the TGW documentation set. Describes each document in the set. Also includes information on receiving documentation updates and ordering documentation.

TGW Content: A Guide for Operators

DN0182164 Intended for operators as boilerplate content that the operators can customize for their TGW subscribers. Boilerplate content describes how TGW subscribers use the MMT as it references TGW.

TGW R1 Commissioning Guide

DN0182176 Intended for system experts who install TGW R1 at operator sites. In most cases, installers are Nokia employees, though they can also be installers from the operator or from a third-party system integrator.

Customizing the TGW Interfaces

DN0182188 Intended for system integrators and operators who are customizing field labels, screen colors, online help, and the remote log in procedure for the subscriber, non TGW subscriber, and WAP interfaces. Also intended for translators who are responsible for translating the subscriber, non TGW subscriber, and WAP interfaces.

Table 2 TGW documentation set (Continued)Copyright Nokia Corporation 2002.

Preface

Document Document Number Audience DescriptionDN0254713 9

Third Party Development Guide

DN01161124 Intended for software developers writing applications external to TGW but desiring to integrate with TGW-supplied functionality. Software developers writing external TGW applications can use this document to gain an understanding of the TGW functionality that has been made available. For each TGW interface exposed, this document presents conceptual information, description of the exposed interface, and example interacting code.

TGW Database Schema Guide

DN01161124 Intended for DBAs who need to know the schema employed for TGW to produce backups or queries. DBAs can use this document to understand the TGW schema and the relationship between the various tables.

Release Notes DN0182191 Intended for installers. Also intended for system administrators who work directly for the operators and who are responsible for configuring and troubleshooting airtime services for TGW subscribers.

Technical Notes Available online at http://www.online.nokia.com

Intended for installers, administrators, and operators.

Table 2 TGW documentation set (Continued)Issue 1-0 en Copyright Nokia Corporation 2002.

1.6 Related documentation10

For more information on the Nokia Artuse Multimedia Messaging Service Center (MMSC), refer to the following documents, available online at this location:http://www.online.nokia.com

For more information on Nokia Activ Server (NACS) 2.1, refer to the following docu-ments. You can find these documents in PDF format on the Nokia Activ Server 2.1 CD.

Nokia Activ Server Getting Started GuideNokia Activ Server Administration Guide

1.7 If you have documentation comments

The Application Gateways product line at Nokia is always interested in improving its documentation. We value your comments about this guide and other Nokia documentation.

Document Document # Description

Product Description DN00133559 Provides an introduction to the product with general information on hardware and software, general product architecture, the MMS Center basic package, optional features, and support information relating to customer training and support.

Operating MMS Center

DN00148786 Designed for users who need procedures for periodic operations.

Configuring EAIF and External Applications

DN0134707 Provides general information about configuring EAIF and the external applications shipped with MMS Center as well as a practical guide to configuring the inter-MMSC and legal interception applications.

Technical Manual DN00148747 Provides the following information: environment variables processes database tables events

External Applications Developers Guide

DN00148759 Provides technical guidance relating to the development of external applications.

Table 3 Documentation related to the MMSCCopyright Nokia Corporation 2002.

Preface

Simply e-mail your documentation comments to Application Gateways atag.documentation@nokia.comDN0254713 11

In all your correspondence, please include the title of the document, its document number, release version, and the specific section upon which you are commenting.

1.8 Revision history

Table 4 shows a list of all revisions for this document.

Date Issue Release version

March 22, 2002 1-0 en First draft.

Table 4 Revision historyIssue 1-0 en Copyright Nokia Corporation 2002.

12

Copyright Nokia Corporation 2002.

Overview of the Nokia Multimedia Messaging Solution

2 Overview of the Nokia Multimedia DN0254713 13

Messaging Solution

2.1 Multimedia messaging services

Mobile messaging today predominantly incorporates Short Message Service (SMS), picture and voice messaging. Over time, the nature and form of mobile messaging will become less text based and more multimedia based. Mobile messaging is evolving from SMS to Multimedia Messaging Service (MMS).MMS is a versatile messaging service that is a natural continuation of conventional messaging. In addition to traditional messaging services, MMS provides much richer content types such as images, voice clips, video clips and e-mail. New and exciting possibilities are evolving, especially for mobile person-to-person communication. MMS is a key application within the wireless messaging business and one of the enablers of the Mobile Information Society. The Mobile Information Society is a world in which technologies such as Bluetooth, SyncML, WAP, UMTS, GPRS, etc. all combine to move mobile communication from simple voice to rich media, where an experience is defined by multiple senses. An increasing part of all personal information transmission utilizes multimedia messaging.The multimedia messaging migration path adds new functions and new content types to SMS in steps that consumers will readily understand. This path encourages the adoption of MMS, and will lead to rapid assimilation and high penetration rates. MMS delivers a location-independent, total communication experience that is a simple, logical extension of SMS.

2.2 The Nokia MMS solution

To meet the high demands of the new messaging era, Nokia provides a complete end-to-end solution for multimedia messaging based on expertise in both mobile terminals and infrastructure. The Nokia MMS Solution is comprised of, yet not limited to, the following elements: Nokia Artuse MMS Center (MMS Center) Nokia Multimedia Terminal Gateway (TGW) Nokia Multimedia E-mail Gateway (EGW) Nokia Artuse Messaging Platform (NAMP)

2.2.1 Nokia Artuse MMS Center (MMS Center)

The Nokia Artuse MMS Center supports person-to-person multimedia messaging. The MMS Center is a reliable, scalable, high capacity platform based upon the SMS implementation of store and forward. The MMS Center features include messaging for the following scenarios:Issue 0-1 en Copyright Nokia Corporation 2002.

Terminal-to-terminal Terminal-to-application14

Application-to-terminal Application-to-application messagingThe MMS Center provides an External Application Interface (EAIF) for application integration. Through the EAIF, the MMS Center connects to a variety of applications that add value to basic multimedia messaging. This interface is available for 3rd party MMS application developers as well as Nokia development teams. Nokia utilizes the EAIF for the Multimedia Terminal Gateway (TGW).

2.2.2 Nokia Multimedia Terminal Gateway (TGW)

The combination of the MMS Center and application gateways provide a comprehensive solution for multimedia messaging. TGW is an application gateway that enhances basic MMS Center person-to-person messaging. TGW provides storage and views of multimedia messages, as well as support for users that have SMS-enabled phones which are not multimedia enabled. (For detailed information on TGW refer to Nokia Multimedia Terminal Gateway: Release 1 on page 17). TGW has the same open architecture as the MMS Centers, allowing for complementary applications to be developed.TGW utilizes the EAIF of the MMS Center, providing an integrated and comprehensive multimedia solution.

2.2.3 Nokia Multimedia E-mail Gateway (EGW)

Currently, there are two messaging worlds: the Internet/e-mail world and the SMS/MMS world. Both of these worlds have different characteristics; the client capabilities, frequency of usage, and the protocols used are different in each network. Consequently, the Internet/e-mail world and the SMS/MMS world have difficulties communicating with each other. The purpose of the Multimedia E-mail Gateway is to enable communication between the different messaging worlds by accounting for the differences in implementation of communication and technology. Providing a bridge between the Internet/e-mail world and the SMS/MMS world is especially important in the early development stages of the multimedia messaging market.EGW utilizes the EAIF of the MMS Center, providing an integrated and comprehensive multimedia solution.

2.2.4 Nokia Artuse Messaging Platform (NAMP)

NAMP connects wireless networks with the Internet and corporate intranets by enabling mobile users to access HTML, WML, Nokia Smart Messaging and multimedia messaging content via their mobile phones.NAMP is a service platform that acts as a content application gateway between the wireless network and applications residing in the Internet and corporate intranets. NAMP does not provide content itself; it provides gateway functionally for content applications. NAMP provides value-added services to HTML, WML, Nokia smart messaging and Copyright Nokia Corporation 2002.

Overview of the Nokia Multimedia Messaging Solution

multimedia messaging content in the Internet. The services provided by NAMP are accessible using SMS and/or MMS services.DN0254713 15

NAMP Release 4.0, which supports MMS, is based on earlier releases of NAMP Messaging Platform and supports the major mobile network technologies including GSM and TDMA. In addition, GPRS and 3G networks are supported.NAMP utilizes the EAIF of the MMS Center, providing an integrated and comprehensive multimedia solution.Issue 0-1 en Copyright Nokia Corporation 2002.

16

Copyright Nokia Corporation 2002.

Nokia Multimedia Terminal Gateway: Release 1

3 Nokia Multimedia Terminal Gateway: DN0254713 17

Release 1

3.1 Product overview

TGW is a companion application to the Nokia Artuse Multimedia Messaging Service Center (MMS Center).TGW extends the MMS Center by providing storage and views of multimedia messages. In addition, TGW provides multimedia support for legacy phone owners (legacy phone owners own SMS-enabled phones that do not have multimedia capabilities.) via SMS, allowing legacy phone owners to view their multimedia messages via the Web. For detailed information on TGW storage and views of multimedia messages, refer to Album services on page 21. For detailed information on TGW legacy phone support, refer to Legacy phone support services on page 22.

3.2 TGW audience terminology

TGW offers versatile, reliable, multimedia messaging options for anyone using a GSM or GPRS mobile phone. This includes multimedia terminal (MMT) owners as well as legacy phone owners. Via TGW, legacy phone owners can access multimedia messages using the Wireless Application Protocol (WAP) or the Web. The TGW audience is comprised of three groups: TGW subscribers Non TGW subscribers TGW end users

3.2.1 TGW subscribers

TGW subscribers are wireless subscribers whose operator offers TGW services, which they are using. TGW subscribers may include both multimedia terminal owners, as well as SMS-enabled phone owners (legacy phone owners). TGW subscribers have access to all TGW features including message creation, album storage and retrieval features, all of which are made available via the subscriber's operator. These features may be accessed via WAP or web. TGW subscribers have significantly more features available to them than non TGW subscribers.For detailed information on TGW features, including message creation, album storage and retrieval features, refer to TGW R1 Product Features on page 21.

3.2.2 Non TGW subscribers

Non TGW subscribers include multimedia terminal owners that are not subscribing to TGW services via their operator. Non TGW subscribers have no access to TGW generated personal albums.Issue 0-1 en Copyright Nokia Corporation 2002.

TGW supports non TGW subscribers that are legacy phone owners by providing message retrieval information to the non-subscriber via an SMS message. Non-Subscribers can 18

retrieve messages only via the Web. For additional information on TGW legacy phone support refer to Legacy phone support services on page 22.

3.2.3 TGW end users

TGW end users are described as anyone that utilizes multimedia in their messaging, including pictures, video, audio, etc. TGW end users can be TGW subscribers or non TGW subscribers; they can be multimedia device owners or legacy phone owners, or owners of both types of phones/devices. TGW end users include anyone that is using TGW on a subscription basis (via their operator), or anyone owning a legacy phone receiving notification from TGW.

3.3 TGW product package

The TGW product package includes five integral elements: Album services Legacy phone support services Documentation Training Product supportInstallation and product maintenance are also available to TGW customers.Copyright Nokia Corporation 2002.

Functional Overview

4 Functional OverviewDN0254713 19

The MMS Center provides person-to-person multimedia messaging. The Nokia multimedia application gateways play a significant role in the Nokia multimedia messaging solution by providing additional options for multimedia messaging to anyone who owns a mobile phone. TGW supports SMS-enabled phones via SMS notification and Web access; TGW supports owners of multimedia terminals via albums with Web and WAP interfaces. The Nokia Multimedia Terminal Gateway (TGW), Multimedia E-mail Gateway (EGW), and Nokia Artuse Messaging Platform (NAMP) seamlessly integrate the wired and wireless messaging worlds. The gateway applications are crucial for generating multimedia traffic and are complementary to direct person-to-person messaging.

4.1 Multimedia service applications functional overview

The follow diagram illustrates how the Nokia application gateway products interface with the MMS Center:Issue 0-1 en Copyright Nokia Corporation 2002.

4.2 TGW traffic flow20

The TGW application includes the following services: Album services Legacy phone support servicesThe following diagram illustrates potential traffic flow of the Nokia multimedia service solution:Copyright Nokia Corporation 2002.

TGW R1 Product Features

5 TGW R1 Product FeaturesDN0254713 21

There are three fundamental categories of TGW product features, including: Album services Legacy phone support services TGW administration

5.1 Album services

Album services are multimedia capabilities made available to TGW subscribers. TGW subscribers: Compose new multimedia messages Store, browse, retrieve multimedia messages Forward messages to MSISDN or e-mail address Receive notification of new messages when MMT unavailable Self-provision settings, such as: Password

E-mail addressTGW provides end-users with album services that are available via the Web or via a WAP interface.

5.1.1 Personal album storage

TGW subscribers have access to personal albums where their multimedia messages can be stored. The following personal album features are available for subscribers: Long term storage of messages Message retrieval via WAP and Web browsers Message composition Retrieval to multimedia terminal options Forwarding options to other MSISDNs or e-mail addresses Guaranteed delivery of messages to multimedia terminals that are off or out of the

coverage area When a subscriber is not available to receive multimedia messages, the message is

stored in their New Messages area of their album.Issue 0-1 en Copyright Nokia Corporation 2002.

5.2 Legacy phone support services22

TGW's legacy phone support facilitates the early adoption of multimedia terminals by enlarging the audience to which multimedia messages can be sent. In addition, TGW's legacy phone support provides message storage and management options to legacy phone owners for the multimedia messages they receive.TGW legacy phone support provides the following services: Legacy phone owners receive a Short Message Service (SMS) informing them of a

message and how to access it Legacy phone owners can be TGW subscribers or non subscribers

Legacy phone owners view message headers via WAP or messages via the Web The operator's administrator configures the general content of the SMS that legacy

phone owners receive The operator's administrator configures the amount of time to store multimedia

messages for legacy phone ownersWithout TGW, MMT owners can only send multimedia messages to other MMT owners. With TGW, MMT owners are able to send multimedia messages to anyone. TGW's support for legacy phone owners requires no knowledge of the receiving terminal's capability, encouraging subscribers to send multimedia messages.The Nokia MMS Center (in conjunction with the Nokia Artuse Profiler (NAP)) determines the potential delivery options for a multimedia message based upon the capabilities of the target recipient's phone. If the phone capabilities are identified as not being able to support multimedia message formats, the Nokia MMS Center sends the multimedia message to TGW. TGW then notifies the intended recipient that they have received a multimedia message via an SMS message, as follows: For non TGW subscribers: "You have received a MMS message. It may be retrieved

at , using message id and the password . This message will be automatically deleted after days."

For TGW subscribers: "You have received a new multimedia message from . You may view this message in your New Messages area of your Album.

TGW allows all legacy phone users to view multimedia messages via a Web interface. In addition, legacy phone owners that are TGW subscribers can view their multimedia message headers via a WAP interface.

5.3 TGW administration and configuration

TGW provides two levels of administrative interfaces, as well as subscriber and configuration management: Administrator interface Supervisor interfaceCopyright Nokia Corporation 2002.

TGW R1 Product Features

5.3.1 Class of Service PlansDN0254713 23

A class of service plan (COS) is a configuration mechanism that allows the administrator to group subscribers together by shared characteristics. Each subscriber that belongs to a COS will have the following shared characteristics: Personal Album size (in MB) Mew Message storage size (in MB) Message storage time (in days)A supervisor or administrator may assign groups of subscribers or a single subscriber to a COS. By using a COS, an operator may group subscribers according to characteristics that may map to their marketing plans. For example, they may charge 10 euros per month for an Album service that provides 2 MB of space in their New Messages area, 5 MB of space in their Personal Album, and stores messages for 60 days. Then, they may charge 25 euros per month for an Album service that provides 3 MB of space in their New Messages area, 10 MB of space in their Personal Album, and stores messages for 120 days.This type of configuration can be easily managed by using different COS. It simplifies the provisioning routine.The administrator interface provides access to subscriber, system configuration parameters, log files, etc. The supervisor interface provides access to subscriber configuration parameters.Encrypted passwords for both levels of the administrative interface ensure that non-authorized personnel do not have access the system.

5.3.2 Administrator interface

The TGW administrator interface, designed for the MMS Application Administrator, includes access to all parameters and settings of TGW. The TGW administrator manages the server that hosts multimedia messages. Tasks available from the TGW administrator interface include: Provisioning (creating and managing) subscribers Provisioning (creating and managing) class of service (COS) plans Assigning COS plans Configuring the system Changing the administrator and supervisor password Managing events that generate CDRs, SNMP alarms, and log entries Viewing the system log

5.3.3 Class of Service Plans

A class of service plan (COS) is a configuration mechanism that allows the administrator to group subscribers together by shared characteristics. Each subscriber that belongs to a COS will have the following shared characteristics: Personal Album size (in MB)Issue 0-1 en Copyright Nokia Corporation 2002.

New Message storage size (in MB) Message storage time (in days)24

A supervisor or administrator may assign groups of subscribers or a single subscriber to a COS. By using a COS, an operator may group subscribers according to characteristics that may map to their marketing plans. For example, they may charge 10 euros per month for an Album service that provides 2 MB of space in their New Messages area, 5 MB of space in their Personal Album, and stores messages for 60 days. Then, they may charge 25 euros per month for an Album service that provides 3 MB of space in their New Messages area, 10 MB of space in their Personal Album, and stores messages for 120 days.This type of configuration can be easily managed by using different COS. It simplifies the provisioning routine.

5.3.4 Supervisor interface

The TGW supervisor interface provides access to TGW subscriber creation and management. From the TGW supervisor interface, the TGW supervisor may provision TGW subscribers. Tasks available from the TGW supervisor interface include: Provisioning subscribers Subscriber configuration Assigning COS plans The supervisor interface does not provide access to the creation of COS or system configuration parameters .

5.3.5 Subscriber provisioning

Subscribers are provisioned from either the administrator interface or the supervisor interface. Subscriber provisioning includes creating, modifying and deactivating TGW subscribers. Subscriber provisioning differs between the administrator interface and the supervisor interface in that a COS can be created from the administrator interface, whereas the supervisor interface makes use of pre-existing COS features (already created by the administrator).All features that are available to the supervisor are also available to the administrator (including subscriber provisioning).At this point, there is no pre-packaged interface between the TGW subscriber provisioning mechanism and an operator's customer care and billing system. However, since the TGW database schema is open and published, a separate integration project can allow a customer care and/or billing system to automatically provision TGW subscribers.

5.3.6 Configuration management

TGW's administrator interface provides a separate and secure UI that is accessible from anywhere via a Web browser. The following configuration management features are available via the administrator interface: Access via secured administrator login with encrypted passwordCopyright Nokia Corporation 2002.

TGW R1 Product Features

Album management including: Configuration of album sizeDN0254713 25

Configuration of storage time for messages COS management including:

Create, modify, activate/deactivate classes of service Group subscribers by album features

Subscriber provisioning including: Create, deactivate, modify, activate users Subscriber parameters

Configuration of SMS for legacy phone notification including defining: Text message to be displayed as part of SMS sent Which pieces of information will be included: Message ID Password to access message via Web URL Sender's MSISDN

5.4 Additional TGW product features

5.4.1 Log management

The event logger receives events from all TGW subsystems creating log records. The administrator configures which events are included as log messages.The administrator can configure the location of the log files, the number of log files that will be stored, and the maximum size of each log file. The above parameters are configured via the administrative interface, using the "Configuration Parameter" section.

5.4.2 Report management

The TGW Oracle database schema is open and published. Reporting by any standard reporting package is enabled.

5.4.3 Billing and billing management

The TGW billing subsystem produces CDR (call detail record) files for billing purposes. The events that generate CDRs are configurable by the administrator. The CDRs generated by TGW events can be relayed to an external billing system. It is possible to define whether or not a CDR is generated for each event via the administration program. The TGW billing interface allows the operator to charge for album services on a Issue 0-1 en Copyright Nokia Corporation 2002.

transaction basis by enabling the operator to collect charging data directly from TGW's logging subsystem. 26

All configurable information about CDRs may be found in the Configuration Parameters section of the administration program. CDRs are generated in the following manner:

The CDRs are buffered by the system in a flat text file format. The number and maximum size of these buffers are configurable. If the buffer is full, the corresponding file is closed, and a new buffer is opened. The file name is the timestamp when the buffer was opened, plus an underscore, plus the buffer sequence number, plus a suffix ".cdr" (e.g. 1001022755661_3.cdr). CDRs are buffered in a round-robin fashion, if multiple buffers are required.

The format of these files is a simple, comma-separated, list, where each CDR entry starts with a new line:

application-type,version,operation-type,event-timestamp,logging-timestamp,originating-address,destination-address, subscriber-address,transaction-id,message-id,mmsc-host,agw-host,tariff-class,message-octet-size,message-content-type, error-cause

All fields are variable size, and the following fields are optional: subscriber-address, message-id, mmsc-host, tariff-class , message-octet-size , message-content-type , error-cause.

All the other fields are mandatory. Also, there could be multiple, whitespace-separated, destination-addresses. In the XML format, each destination-address will be a separate element.

Here is an example of a CDR:tgw,1.0,17001,1234,1234,+1234567898,+12354567788,+1234567898,1234,dfgt567,mmsc01,niaum00,44,10201,app,OK

These files are post-processed at configurable intervals during the day. Post-processing means that currently open buffers are closed, new buffers are opened, and the existing .cdr files are moved to a post-processed directory on the file system. This directory location is also configurableDuring post-processing, the XML content is also generated in a separate directory (the customer may switch XML generation off, however), using the format as specified in the DTD. The idea is to allow the customer to easily process and transform the XML CDRs. Each .cdr file is parsed, and a corresponding .xml file is created, with the same filename. After XML generation, the .cdr file is renamed to .old (to prevent the same XML CDR content being generated multiple times). The customer may also configure a host and URL, and the generated XML content then gets posted automatically to this host and URL, for further (customer-specific) post-processing. In this way, the CDRs can be automatically distributed to a billing center. The .xml, .old, and .cdr files can also be manually pulled from the system by the customer, using FTP or any other file copy utilities.Lastly, cleanup: the customer may specify (in hours) how long the post-processed flat and XML files should exist on the system. All .xml, .cdr and .old files older than this will automatically be deleted from the system.Copyright Nokia Corporation 2002.

TGW R1 Product Features

5.4.4 Resource managementDN0254713 27

The operator can monitor platform resources with Sun tools. Sun resources include processes, memory, and disk storage. TGW system parameters can be set and monitored from the MMS Application Administrator.

5.4.5 Fault management and SNMP alarms

The logging subsystem collects and processes all alarms that are generated by TGW modules. Alarm processing includes writing them in the system log and sending the information to the network management system via SNMP where they can be viewed in the NMS graphical user interface. The events that generate alarms are configurable by the operator's administrator.When an alarming event occurs, an alarm is sent, via SNMP, to the NMS. There is a configuration parameter within the administration program that the customer may set which determines how long before this alarm will be sent out again, if it occurs again. For example, if an alarm occurs at 8, and the timeout is set to 30 minutes, the alarm will not be sent out again until 8:30. This prevents the NMS from being flooded with the same alarm unnecessarily. The alarm interface of TGW utilizes the SNMP standard for connecting to network management systems (NMS). Any V2 SNMP compatible NMS can be used. The NMS interface acts as a watchdog for TGW performance. Depending on the NMS features, a variety of actions can occur, including alarm forwarding.

5.4.6 Performance management

The performance management subsystem collects values from key performance indicators about TGW and the amount of traffic. When your performance characteristics are approaching the licensed limits, an SNMP alarm is generated.

5.4.7 Database management

TGW's subscriber database architecture is open and can be integrated with an operator's existing subscriber database, provided all the TGW elements are available. The database is managed via standard Oracle tools. Maintenance operations include: Running cleanup routines Running backups of the database Restoring backups of the database configuration and possibly of some of the data

storageIssue 0-1 en Copyright Nokia Corporation 2002.

28

Copyright Nokia Corporation 2002.

Architecture

6 ArchitectureDN0254713 29

TGW is an application gateway that supports the needs of wireless subscribers. Multimedia devices allow users to capture images, video, voice, and text and send them to other users similar to the way SMS messages are handled today. The architecture of TGW is designed for the multimedia environment where the volume of multimedia messages will grow substantially over time, and users will want to store images for later viewing and sharing. Multimedia network traffic may often come in spikes (on major holidays for example), where the requirement is to move large amounts of data over the network. In addition, the number of multimedia users will increase dramatically as multimedia terminals make their way into the marketplace. TGW's architecture is designed with consideration for the expected increase in market demand.

6.1 Transport protocols and bearers

The data transmission capabilities of the mobile networks will be utilized by the MMS Center in the message delivery between the server and the mobile terminals. There are various other protocols in use during the interaction between TGW, the MMS Center and the network.WAP is used as a transport protocol allowing TGW subscribers to access their messages from their wireless terminals.

Various SMS protocols are used to send an SMS message notifying non-multimedia wireless subscribers when they have a multimedia message waiting to be viewed. These protocols are network independent. As a result, multimedia messages can be sent over a number of network types and between network types.Using Nokia Artuse Server (NACS), TGW sends notifications to SMSCs and supports the following protocols: CIMD2 UCP SMPPNACS is bundled with TGW and is dedicated for TGW use. The operator does not need to purchase a separate NACS server, because it is included with TGW. However, in order to deploy TGW in the network, the operator is expected to have an SMSC that can be utilized for delivering SMS notifications.Other protocols that are utilized are as follows: HTTP allows TGW subscribers Web access to their messages SMTP allows TGW subscribers to forward messages to e-mail addresses TCP/IP interfaces with billing systems and user profile databases SNMP interfaces with network management systemsIssue 0-1 en Copyright Nokia Corporation 2002.

6.2 Architecture illustration30

The following diagram illustrates TGW's architecture:

6.3 Scalability

The TGW architecture is highly scalable. Scalability is provided by: Supplementing existing capacity with additional software and license keys Support for software clustering Adding CPUs to individual servers Managing storage scalability through HW clusteringAdditionally, by using the Net Apps 820 filer as a core component of the HW solution, scalability up to 3 TB of raw storage is available. The Net Apps solution provides network storage of data that is always available to the TGW application, and due to the architecture of the filers, allows additional storage to be added to the TGW solution while maintaining the operator's original HW investment.

6.4 Software redundancy

TGW provides the ability to be managed in a "lights out" environment. In the event of a failure of a component, TGW automatically restarts, without intervention.Copyright Nokia Corporation 2002.

Architecture

6.5 PlatformDN0254713 31

TGW runs on Solaris 8 platforms containing Oracle 8i for the subscriber database, WebLogic for the runtime environment, Critical Path for storage, and TGW software. The hardware and system requirements are itemized in the following two sections.

6.5.1 HW configuration

TGW is based on: 1 Sun 220R server with:

2 CPUs 2 GB Memory 2 internal 36 GB disk drives Video card QFE Ethernet card GBit Ethernet card CDROM drive

1 Sun 420R server with: 2 CPUs 4 GB Memory 2 internal 36 GB disk drives Video card QFE Ethernet card GBit Ethernet card CDROM drive

Net Apps 820 filer with: 730 GB storage space

Cisco Catalyst GBit switch Optional DAT drive

6.5.2 System software

Solaris 8 Oracle Standard Edition 8.1.7 Critical Path 5.5 (with proxy authorization patch) BEA WebLogic 6.0 sp2 Apache Web Server 1.3.19 (with proxy support)Issue 0-1 en Copyright Nokia Corporation 2002.

Nokia Activ WAP Server 2.0, Enterprise Edition for Solaris 832

Note: Note: TGW requires MMS Center release 35d or higher (release MC1).Copyright Nokia Corporation 2002.

Training, Delivery and Support

7 Training, Delivery and SupportDN0254713 33

This chapter summarizes the training, delivery and support that are available for the TGW product.

7.1 Documentation materials

The documentation set includes the following categories: Introductory documents that contain general information about the product and

documentation Reference documents including technical specifications TGW subscriber guide containing task-oriented instructions for configuration,

maintenance, and operation Installation documents TGW administration guide for optional features with instructions for installation,

configuration and operation of each feature

7.2 TGW documentation audience

TGW requires customer documents for targeted audiences. This audience includes: Administrators Subscribers Installers

7.3 TGW documentation set

The documentation set for the Nokia Multimedia Terminal Gateway Release 1 (TGW R1) includes the following: Administration Guide (Print/PDF) Administrator Web based Help Subscriber Web based Help Context sensitive help for administrators Context sensitive help for subscribers Subscriber help (WAP) TGW Content: a guide for operators Commissioning Guide (Print/PDF)Issue 0-1 en Copyright Nokia Corporation 2002.

Customizing the TGW Interfaces (Print/PDF) Technical Notes (Print/PDF)34

Guide to Documentation (Print/PDF)

7.3.1 TGW release binder

The TGW release binder contains the following information: System Test Report Generic Failure Report Release Notes

7.3.2 Additional reference materials

In addition to the TGW documentation available, the following reference materials may be helpful during installation and maintenance of the TGW product: Nokia Artuse Glossary MMS Center technical and reference materials SNMP interface specifications

7.4 Training

Nokia implements training after TGW has reached the E5 milestone, through a worldwide network of local customer service centers. Prior to the E5 milestone, trainers from the Application Gateway product line will be available to offer training classes on TGW.The three training classes associated with TGW are as follows: TGW system training TGW installation training TGW operation and maintenance training

7.4.1 TGW system training

TGW system training describes how the system functions in a wireless network. The audience for this course is operator personnel or Nokia personnel (non-technical) requiring a basic knowledge of TGW. At the end of this training course, trainees will be able to meet these objectives: Understand how TGW is configured with the MMS Center Identify the components involved in TGW's environment Describe basic TGW functionsCopyright Nokia Corporation 2002.

Training, Delivery and Support

7.4.2 TGW installation trainingDN0254713 35

Installation training describes the hardware and software installation of TGW. The audience for this course is Nokia personnel who will be involved in the installation and commissioning of TGW.At the end of this training course, trainees will be able to: Describe the components of TGW Describe the hardware and software requirements of TGW Install all hardware and software associated with TGW

7.4.3 TGW operation and maintenance training

Operation and Maintenance training describes the configuration and maintenance of TGW. The audience for this course is administrative personnel who will be operating and maintaining TGW.At the end of this training course, trainees will be able to: Describe the components involved in TGW's environment Describe the hardware and software requirements of TGW's environment Connect to the MMS Application Administration interface Add, deactivate, reactivate, and modify TGW subscriber information within TGW

Describe the configurable parameters within TGW Describe COS Configure and view TGW's system log Troubleshoot TGW Demonstrate WAP Access to a TGW subscriber

7.4.4 Training duration

The duration of the TGW training classes is as follows: TGW System Training is .5 days TGW Installation training is 3 days TGW Operation and maintenance is 1 day

Note: A full description of TGW training service is available from your Nokia Customer Service Center.Issue 0-1 en Copyright Nokia Corporation 2002.

7.5 Delivery36

In cooperation with the operator, Nokia provides the installation, commissioning, and configuration of TGW.

Note: A full description of this support is available from your Nokia Customer Service Center.

7.6 Product support

Nokia provides comprehensive support and maintenance services for TGW, including support for all third-party components delivered with TGW. The following services are available to customers who have a maintenance or technical support agreement with Nokia: Support services entitle the customer to Help desk services through the local Nokia

Customer Service Center during local business hours. Maintenance services entitle the customer to new feature releases and corrective

maintenance. Emergency services (full 24-hour service, 7 days a week, year-round)Software and hardware products have Nokia-wide guarantee periods.

7.7 Software support

TGW includes ninety days of free software maintenance. This maintenance includes the correction of possible errors and access to software change notes. After the ninety-day maintenance period, continued service is available, subject to the software support agreement.

7.8 Sun support

The proposed Sun platform includes support for the first year starting from the installation approval date. This service offers a 4-hour response time during office hours, hardware repairs, and access to software updates as well as hot-line service.ReferencesIn addition to the Nokia TGW customer documentation, the following resources may be helpful: ETSI, for telecom standards RFCs, on relevant issues, i.e. HTTP, SNMP, MIB, etc. WAP Forum, for standardsCopyright Nokia Corporation 2002.

Training, Delivery and Support

3GPP for MMS R99 specificationsThe resources are available at the following URL: http://www.net.nokia.com/NET/DN0254713 37

NOKIA/COM/ebusines.nsf/document/ES14T4SMC82.Issue 0-1 en Copyright Nokia Corporation 2002.

38

Copyright Nokia Corporation 2002.

1 Preface1.1 About this document1.2 Audience1.3 Scope1.4 Typographic conventions1.5 TGW documentation1.6 Related documentation1.7 If you have documentation comments1.8 Revision history

2 Overview of the Nokia Multimedia Messaging Solution2.1 Multimedia messaging services2.2 The Nokia MMS solution2.2.1 Nokia Artuse MMS Center (MMS Center)2.2.2 Nokia Multimedia Terminal Gateway (TGW)2.2.3 Nokia Multimedia E-mail Gateway (EGW)2.2.4 Nokia Artuse Messaging Platform (NAMP)

3 Nokia Multimedia Terminal Gateway: Release 13.1 Product overview3.2 TGW audience terminology3.2.1 TGW subscribers3.2.2 Non TGW subscribers3.2.3 TGW end users

3.3 TGW product package

4 Functional Overview4.1 Multimedia service applications functional overview4.2 TGW traffic flow

5 TGW R1 Product Features5.1 Album services5.1.1 Personal album storage

5.2 Legacy phone support services5.3 TGW administration and configuration5.3.1 Class of Service Plans5.3.2 Administrator interface5.3.3 Class of Service Plans5.3.4 Supervisor interface5.3.5 Subscriber provisioning5.3.6 Configuration management

5.4 Additional TGW product features5.4.1 Log management5.4.2 Report management5.4.3 Billing and billing management5.4.4 Resource management5.4.5 Fault management and SNMP alarms5.4.6 Performance management5.4.7 Database management

6 Architecture6.1 Transport protocols and bearers6.2 Architecture illustration6.3 Scalability6.4 Software redundancy6.5 Platform6.5.1 HW configuration6.5.2 System software

7 Training, Delivery and Support7.1 Documentation materials7.2 TGW documentation audience7.3 TGW documentation set7.3.1 TGW release binder7.3.2 Additional reference materials

7.4 Training7.4.1 TGW system training7.4.2 TGW installation training7.4.3 TGW operation and maintenance training7.4.4 Training duration

7.5 Delivery7.6 Product support7.7 Software support7.8 Sun support