TGW 1.0.3 Product Description

8/11/2019 TGW 1.0.3 Product Description

http://slidepdf.com/reader/full/tgw-103-product-description 1/34

DN0254713 1

Issue 1-3 en Copyright © Nokia Corporation 2002.

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

Product Description

Introductory Document



2

Copyright © Nokia Corporation 2002.

PURPOSE. This document describes the product(s) defined in the introduction of thisdocument and is subject to change without notice. This document is intended for the use of

Nokia Corporation’s customers for the sole purposes of the agreement under which it issubmitted. 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 theinstructions contained in the document are adequate and free of material errors andomissions. This document is provided on an “AS IS” basis, with no warranty of any kind.

NOKIA CORPORATION SPECIFICALLY DISCLAIMS ANY AND ALL IMPLIEDWARRANTIES, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OFFITNESS, MERCHANTABILITY AND TITLE. Further, the information or statementscontained 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 NokiaCorporation in the agreement under which this document is submitted.

Limitation of Liability. Nokia Corporation’ liability for any errors in the document islimited 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, ECONOMICOR CONSEQUENTIAL, that might arise from the use of or inability to use this documentor anything contained herein.

Intellectual Property Rights. This document and the product it describes are protected bycopyright according to applicable laws. No part of this document may be reproduced ortransmitted in any form or by any means without the prior written permission of NokiaCorporation. Nokia and Nokia Connecting People are registered trademarks of NokiaCorporation.

Product names mentioned in this document may be trademarks of their respectivecompanies and are mentioned for identification purposes only.

Copyright © Nokia Corporation 2002. All rights reserved.



4


5.4.5 Fault management and SNMP alarms . . . . . . . . . . . . . . . . . . . . . . . . . . 23

5.4.6 Performance management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

5.4.7 Database management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

6 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256.1 Transport protocols and bearers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

6.2 Architecture illustration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

6.3 Scalability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

6.4 Software redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

6.5 Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

6.5.1 HW configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

6.5.2 System software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

7 Training, Delivery and Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

7.1 Documentation materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297.2 TGW documentation audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

7.3 TGW documentation set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

7.3.1 TGW release binder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

7.3.2 Additional reference materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

7.4 Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

7.4.1 TGW system training. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

7.4.2 TGW installation training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

7.4.3 TGW operation and maintenance training . . . . . . . . . . . . . . . . . . . . . . . 31

7.4.4 Training duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

7.5 Delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

7.6 Product support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327.7 Software support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

7.8 Sun™ support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32



Preface

DN0254713 5


1 Preface

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 MultimediaTerminal 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 thecapabilities of TGW.

1.3 Scope

The document provides information on:

• Functionality

• Features

• Architecture

• Customer documentation

• Customer training

• Technical support



6


1.4 Typographic conventions

The following notes and table provide a list of the typographic conventions that appear inthis 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 of

code, names of processes, and

commands.

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 I talics Used for emphasis.

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

Table 1 Typographic conventions



Preface

DN0254713 7


1.5 If you have documentation comments

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

Simply e-mail your documentation comments to Application Gateways at

[email protected]

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.6 Revision history

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

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

\ Backslash at the end of lines indicates thatthere is insufficient space and the line iscontinued in the space below.

| Vertical bar used between choices, forexample in variable data in configurationfile arguments.

“” Used for section and chapter titles.

Convention Description

Table 1 Typographic conventions

Date Issue Release version

March 2002 1-0 en TGW 1.0

June 2002 1-1 en TGW 1.0.1

July 2002 1-2 en TGW 1.0.2

August 2002 1-3 en TGW 1.0.3

Table 2 Revision history



8




Overview of the Nokia Multimedia Messaging Solution

DN0254713 9


2 Overview of the Nokia MultimediaMessaging 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 fromSMS to Multimedia Messaging Service (MMS).

MMS is a versatile messaging service that is a natural continuation of conventionalmessaging. In addition to traditional messaging services, MMS provides much richercontent 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 enablersof the Mobile Information Society. The Mobile Information Society is a world in whichtechnologies such as Bluetooth, SyncML, WAP, UMTS, GPRS, etc. all combine to movemobile communication from simple voice to rich media, where an experience is defined

by multiple senses. An increasing part of all personal information transmission utilizesmultimedia messaging.

The multimedia messaging migration path adds new functions and new content types toSMS in steps that consumers will readily understand. This path encourages the adoptionof MMS, and will lead to rapid assimilation and high penetration rates. MMS delivers alocation-independent, total communication experience that is a simple, logical extensionof 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 andinfrastructure. The Nokia MMS Solution is comprised of, yet not limited to, the followingelements:

• 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. TheMMS Center is a reliable, scalable, high capacity platform based upon the SMSimplementation of store and forward. The MMS Center features include messaging for thefollowing scenarios:



10


• Terminal-to-terminal

• Terminal-to-application

• Application-to-terminal

• Application-to-application messaging

The MMS Center provides an External Application Interface (EAIF) for applicationintegration. Through the EAIF, the MMS Center connects to a variety of applications thatadd value to basic multimedia messaging. This interface is available for 3rd party MMSapplication developers as well as Nokia development teams. Nokia utilizes the EAIF forthe Multimedia Terminal Gateway (TGW).

2.2.2 Nokia Multimedia Terminal Gateway (TGW)

The combination of the MMS Center and application gateways provide a comprehensivesolution for multimedia messaging. TGW is an application gateway that enhances basic

MMS Center person-to-person messaging. TGW provides storage and views ofmultimedia messages, as well as support for users that have SMS-enabled phones whichare not multimedia enabled. (For detailed information on TGW refer to “NokiaMultimedia Terminal Gateway: Release 1” on page 13). TGW has the same openarchitecture as the MMS Centers, allowing for complementary applications to bedeveloped.

TGW utilizes the EAIF of the MMS Center, providing an integrated and comprehensivemultimedia solution.

2.2.3 Nokia Multimedia E-mail Gateway (EGW)

Currently, there are two messaging worlds: the Internet/e-mail world and the SMS/MMSworld. 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 witheach other. The purpose of the Multimedia E-mail Gateway is to enable communication

between the different messaging worlds by accounting for the differences inimplementation of communication and technology. Providing a bridge between theInternet/e-mail world and the SMS/MMS world is especially important in the earlydevelopment stages of the multimedia messaging market.

EGW utilizes the EAIF of the MMS Center, providing an integrated and comprehensivemultimedia solution.

2.2.4 Nokia Artuse™ Messaging Platform (NAMP)

NAMP connects wireless networks with the Internet and corporate intranets by enablingmobile users to access HTML, WML, Nokia Smart Messaging and multimedia messagingcontent via their mobile phones.

NAMP is a service platform that acts as a content application gateway between thewireless network and applications residing in the Internet and corporate intranets. NAMPdoes not provide content itself; it provides gateway functionally for content applications.

NAMP provides value-added services to HTML, WML, Nokia smart messaging and



Overview of the Nokia Multimedia Messaging Solution

DN0254713 11


multimedia messaging content in the Internet. The services provided by NAMP areaccessible using SMS and/or MMS services.

NAMP Release 4.0, which supports MMS, is based on earlier releases of NAMPMessaging 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 comprehensivemultimedia solution.



12




Nokia Multimedia Terminal Gateway: Release 1

DN0254713 13


3 Nokia Multimedia Terminal Gateway:Release 1

3.1 Product overview

TGW is a companion application to the Nokia Artuse™ Multimedia Messaging ServiceCenter (MMS Center).TGW extends the MMS Center by providing storage and views ofmultimedia messages. In addition, TGW provides multimedia support for legacy phoneowners (legacy phone owners own SMS-enabled phones that do not have multimediacapabilities.) via SMS, allowing legacy phone owners to view their multimedia messagesvia the Web. For detailed information on TGW storage and views of multimediamessages, refer to “Album services” on page 17. For detailed information on TGW legacy

phone support, refer to “Legacy phone support services” on page 18.

3.2 TGW audience terminology

TGW offers versatile, reliable, multimedia messaging options for anyone using a GSM orGPRS mobile phone. This includes multimedia terminal (MMT) owners as well as legacy

phone owners. Via TGW, legacy phone owners can access multimedia messages using theWireless Application Protocol (WAP) or the Web. The TGW audience is comprised ofthree groups:

• TGW subscribers

• Non TGW subscribers

• TGW end users

3.2.1 TGW subscribers

TGW subscribers are wireless subscribers whose operator offers TGW services, whichthey are using. TGW subscribers may include both multimedia terminal owners, as well asSMS-enabled phone owners (legacy phone owners). TGW subscribers have access to allTGW features including message creation, album storage and retrieval features, all ofwhich are made available via the subscriber's operator. These features may be accessedvia WAP or web. TGW subscribers have significantly more features available to themthan non TGW subscribers.

For detailed information on TGW features, including message creation, album storageand retrieval features, refer to “TGW R1 Product Features” on page 17.

3.2.2 Non TGW subscribers

Non TGW subscribers include multimedia terminal owners that are not subscribing toTGW services via their operator. Non TGW subscribers have no access to TGW generated

personal albums.



14


TGW supports non TGW subscribers that are legacy phone owners by providing messageretrieval information to the non-subscriber via an SMS message. Non-Subscribers canretrieve messages only via the Web. For additional information on TGW legacy phonesupport refer to “Legacy phone support services” on page 18.

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 nonTGW subscribers; they can be multimedia device owners or legacy phone owners, orowners of both types of phones/devices. TGW end users include anyone that is usingTGW on a subscription basis (via their operator), or anyone owning a legacy phonereceiving 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 support

Installation and product maintenance are also available to TGW customers.



16


4.2 TGW traffic flow

The TGW application includes the following services:

• Album services• Legacy phone support services

The following diagram illustrates potential traffic flow of the Nokia multimedia servicesolution:



TGW R1 Product Features

DN0254713 17


5 TGW R1 Product Features

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. TGWsubscribers:

• 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 address

TGW provides end-users with album services that are available via the Web or via a WAPinterface.

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 thecoverage area

• When a subscriber is not available to receive multimedia messages, the message isstored in their New Messages area of their album.



18


5.2 Legacy phone support services

TGW's legacy phone support facilitates the early adoption of multimedia terminals byenlarging the audience to which multimedia messages can be sent. In addition, TGW'slegacy phone support provides message storage and management options to legacy phoneowners 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 amessage 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 multimediamessages for legacy phone owners

Without 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'ssupport for legacy phone owners requires no knowledge of the receiving terminal'scapability, 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 thecapabilities 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 themultimedia 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 <URL>, using message id <msgid> and the password <password>. This messagewill be automatically deleted after <#> days."

• For TGW subscribers: "You have received a new multimedia message from<MSISDN>. 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. Inaddition, legacy phone owners that are TGW subscribers can view their multimediamessage headers via a WAP interface.

5.3 TGW administration and configuration

TGW provides two levels of administrative interfaces, as well as subscriber andconfiguration management:

• Administrator interface

• Supervisor interface




DN0254713 19


5.3.1 Class of Service Plans

A class of service plan (COS) is a configuration mechanism that allows the administratorto 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 aCOS. By using a COS, an operator may group subscribers according to characteristics thatmay map to their marketing plans. For example, they may charge 10 euros per month foran Album service that provides 2 MB of space in their New Messages area, 5 MB of spacein 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 subscriberconfiguration 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 managesthe server that hosts multimedia messages. Tasks available from the TGW administratorinterface 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 administratorto group subscribers together by shared characteristics. Each subscriber that belongs to aCOS will have the following shared characteristics:

• Personal Album size (in MB)



20


• New 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 thatmay map to their marketing plans. For example, they may charge 10 euros per month foran Album service that provides 2 MB of space in their New Messages area, 5 MB of spacein 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 provisionTGW 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 systemconfiguration parameters .

5.3.5 Subscriber provisioning

Subscribers are provisioned from either the administrator interface or the supervisorinterface. Subscriber provisioning includes creating, modifying and deactivating TGWsubscribers. Subscriber provisioning differs between the administrator interface and thesupervisor 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 fromanywhere via a Web browser. The following configuration management features areavailable via the administrator interface:

• Access via secured administrator login with encrypted password




DN0254713 21


• Album management including:

• Configuration of album size

• 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. Theadministrator configures which events are included as log messages.

The administrator can configure the location of the log files, the number of log files thatwill 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 standardreporting 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 CDRsgenerated by TGW events can be relayed to an external billing system. It is possible todefine 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



22


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

All configurable information about CDRs may be found in the Configuration Parameterssection 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 andmaximum size of these buffers are configurable. If the buffer is full, the correspondingfile 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, ifmultiple buffers are required.

The format of these files is a simple, comma-separated, list, where each CDR entry startswith 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 separateelement.

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-processingmeans that currently open buffers are closed, new buffers are opened, and the existing .cdrfiles are moved to a post-processed directory on the file system. This directory location isalso configurable

During post-processing, the XML content is also generated in a separate directory (thecustomer may switch XML generation off, however), using the format as specified in theDTD. 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 CDRcontent being generated multiple times).

The customer may also configure a host and URL, and the generated XML content thengets 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 andXML files should exist on the system. All .xml, .cdr and .old files older than this willautomatically be deleted from the system.




DN0254713 23


5.4.4 Resource management

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 ApplicationAdministrator.

5.4.5 Fault management and SNMP alarms

The logging subsystem collects and processes all alarms that are generated by TGWmodules. Alarm processing includes writing them in the system log and sending theinformation to the network management system via SNMP where they can be viewed inthe NMS graphical user interface. The events that generate alarms are configurable by theoperator'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 setwhich determines how long before this alarm will be sent out again, if it occurs again. Forexample, if an alarm occurs at 8, and the timeout is set to 30 minutes, the alarm will not besent out again until 8:30. This prevents the NMS from being flooded with the same alarmunnecessarily.

The alarm interface of TGW utilizes the SNMP standard for connecting to networkmanagement systems (NMS). Any V2 SNMP compatible NMS can be used. The NMSinterface acts as a watchdog for TGW performance. Depending on the NMS features, avariety of actions can occur, including alarm forwarding.

5.4.6 Performance management

The performance management subsystem collects values from key performanceindicators about TGW and the amount of traffic. When your performance characteristicsare 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'sexisting subscriber database, provided all the TGW elements are available. The databaseis 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

storage



24




Architecture

DN0254713 25


6 Architecture

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 toother users similar to the way SMS messages are handled today. The architecture of TGWis designed for the multimedia environment where the volume of multimedia messageswill grow substantially over time, and users will want to store images for later viewing andsharing. Multimedia network traffic may often come in spikes (on major holidays forexample), where the requirement is to move large amounts of data over the network. Inaddition, the number of multimedia users will increase dramatically as multimediaterminals make their way into the marketplace. TGW's architecture is designed withconsideration 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 MMSCenter in the message delivery between the server and the mobile terminals. There arevarious other protocols in use during the interaction between TGW, the MMS Center andthe network.

WAP is used as a transport protocol allowing TGW subscribers to access their messagesfrom their wireless terminals.

Various SMS protocols are used to send an SMS message notifying non-multimediawireless 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 anumber of network types and between network types.

Using Nokia Artuse™ Server (NACS), TGW sends notifications to SMSCs and supportsthe following protocols:

• CIMD2

• UCP

• SMPP

NACS 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 todeploy TGW in the network, the operator is expected to have an SMSC that can be utilizedfor 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 systems



26


6.2 Architecture illustration

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 clustering

Additionally, by using the Net App 820 filer or EMC SAN as a core component of the HWsolution, scalability up to 3 TB of raw storage is available. The Net App or EMC solution

provides network storage of data that is always available to the TGW application, and dueto the architecture of the filers, allows additional storage to be added to the TGW solutionwhile 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 afailure of a component, TGW automatically restarts, without intervention.



Architecture

DN0254713 27


6.5 Platform

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 App 820 filer or EMC SAN 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)



28


• Nokia Activ WAP Server 2.0, Enterprise Edition for Solaris 8

Note: Note: TGW requires MMS Center release 35d or higher (release MC1).



30


• Customizing the TGW Interfaces (Print/PDF)

• Technical Notes (Print/PDF)

• 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 theApplication 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 functions



Training, Delivery and Support

DN0254713 31


7.4.2 TGW installation training

Installation training describes the hardware and software installation of TGW. Theaudience 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 ofTGW. 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 NokiaCustomer Service Center.



32


7.5 Delivery

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

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

7.6 Product support

Nokia provides comprehensive support and maintenance services for TGW, includingsupport for all third-party components delivered with TGW. The following services areavailable 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 correctivemaintenance.

• 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 thecorrection of possible errors and access to software change notes. After the ninety-daymaintenance period, continued service is available, subject to the software supportagreement.

7.8 Sun™ support

The proposed Sun™ platform includes support for the first year starting from theinstallation 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.

References

In addition to the Nokia TGW customer documentation, the following resources may behelpful:

• ETSI, for telecom standards

• RFCs, on relevant issues, i.e. HTTP, SNMP, MIB, etc.

• WAP Forum, for standards



Training, Delivery and Support

DN0254713 33


• 3GPP for MMS R99 specifications



34

TGW 1.0.3 Product Description

Documents

Transcript of TGW 1.0.3 Product Description