Vous êtes sur la page 1sur 62

Telepath SMSC Release 2700

Feature Description

DRAFT

Telepath SMSC Feature Description


October, 1999
First Published 1999.
1999 Aldiscon Limited.
All rights reserved. No part of this publication may be reproduced, transmitted, transcribed,
stored in a retrieval system, or translated into any language, in any form or by any means,
electronic, mechanical, xerographic, optical, magnetic, or otherwise, without prior written
permission from Aldiscon.
Printed in Dublin, Ireland.
The information furnished herein is believed to be accurate and reliable. However, no
responsibility is assumed by Aldiscon for its use by any means whatsoever, nor for any
infringements of patents or any other rights of third parties whatsoever resulting from its use.
The information contained in this document is subject to change without notice.
All rights conferred by the law in relation to trademarks and copyrights and by the virtue of
international trademarks and copyright conventions are secured to the owners of the trademarks
used within this publication. Reproduction requires the prior written consent of the trademark
owners.

DRAFT

Feature Description

Table of Contents

Table of Contents
References .................................................................................................................................6
Preface .......................................................................................................................................9
1.

General (for all Network Operators).......................................................................12


1.1
Message Management....................................................................................12
1.1.1
Message Routing...........................................................................12
1.1.2
Access Control..............................................................................12
1.1.2.1
Address Translation................................................13
1.2
Platform Management....................................................................................14
1.2.1
Distributed Management Statistics Module..................................14
1.2.1.1
Business Features....................................................14
1.2.1.2
Business Benefits....................................................15
1.2.2
Distributed Administration and Provisioning Module..................16
1.2.2.1
DAP Module...........................................................16
1.2.2.2
Message Management Facilities.............................17
1.2.2.3
Provision Subscriber Facilities ...............................17
1.2.2.4
Benefits...................................................................17
1.2.3
Remote Administration and Provisioning.....................................18
1.2.3.1
Message Management Module...............................18
1.2.3.2
SME Management Module.....................................19
1.2.3.3
Subscriber Management Module............................19
1.2.3.4
Default Module.......................................................19
1.2.3.5
Query Module.........................................................19
1.2.3.6
Configuration Module.............................................20
1.2.3.7
Benefits of RAP......................................................20
1.2.4
Overload Control...........................................................................20
1.3
Network Management....................................................................................21
1.3.1
SNMP Agent.................................................................................21
1.3.1.1
Multiple SNMP Manager support...........................21
1.3.1.2
Support of SNMPv2 requests .................................22
1.4
Billing.............................................................................................................23
1.4.1
Prepaid SMS .................................................................................24
1.4.2
CDR File Improvements...............................................................24
1.4.3
Per-Interface Billing Configuration ..............................................25
1.5
Capacity and Performance .............................................................................26
1.5.1
Premium Messaging Mode ...........................................................26
1.5.2
Performance ..................................................................................27
1.5.3
Sizing ............................................................................................27
1.5.4
Classic Messaging (ORACLE).....................................................27
1.6
General Mobile Network Product Enhancements.........................................28
1.6.1
Message Delivery to Dual-Mode Phones......................................28
1.6.2
Co-resident Mobile Network Products .........................................28

2.

Wireless Application Protocol (WAP).....................................................................30


2.1
Telepath SMSC and WAP .............................................................................30
2.1.1
Express Messaging Mode .............................................................31
2.1.2
Premium Messaging Mode ...........................................................31

SMS-2700-FD-xxxx-UD2

DRAFT

Table of Contents

2.1.3
2.1.4
2.1.5
2.1.6
2.1.7
2.1.8
2.1.9
2.1.10
2.1.11
2.1.12
2.1.13

Feature Description

Extended Message Length ............................................................31


Alert Notification..........................................................................31
User Data Header Encoding (UDH) .............................................31
WAP in ANSI-136 (CMT and GUTS support) ............................32
Subaddress (End to End Security) ................................................32
WDP/WCMP Gateway Adaption .................................................32
Message Segmentation..................................................................32
Message Reassembly ....................................................................32
Application Port Addressing.........................................................32
HLR Delivery Pending Flag handling ..........................................33
Telepath SMSC and Internet IP Address Routing ........................33

3.

GSM Network Operators .........................................................................................34


3.1
GSM Mobile Network Product Architecture.................................................34
3.2
GSM 03.40 Phase 2+ Compliance.................................................................35
3.3
GSM 09.02 Phase 2+ Compliance.................................................................35
3.3.1
GPRS Interface .............................................................................36
3.3.2
Support of IMSI in MO-FSM .......................................................38
3.4
SIM Toolkit....................................................................................................38
3.5
Mobile Number Portability............................................................................38
3.6
Virtual Service Centres..................................................................................38

4.

ANSI-41 Network Operators ...................................................................................40


4.1
ANSI-41 Mobile Network Product Architecture...........................................40
4.1.1
ANSI-41 Teleservice Router.........................................................42
4.1.2
ANSI-41 Transmitter/Receiver Structure .....................................42
4.2
General ANSI-41 Features.............................................................................43
4.2.1
Removal of MO screening............................................................43
4.2.2
IMSI-based Addressing.................................................................43
4.2.3
International Callback Number Format ........................................43
4.2.4
# and * in Callback Number .........................................................44
4.3
ANSI-136 Features ........................................................................................45
4.3.1
ANSI-136 GUTS Mobile Network Product..................................45
4.3.1.1
ANSI-136 TSAR.....................................................45
4.3.1.2
Suppression of Orig Address for MT Messages.....46

5.

PDC Network Operators ..........................................................................................47


5.1
Intra-SMSC Alerting......................................................................................47
5.2
PDC Mobile Network Product Alarms..........................................................47
5.2.1
MTP indication ............................................................................47
5.2.2
MTP congestion indication..........................................................47
5.2.3
Control state indication................................................................47

6.

SMPP Interworking Product ...................................................................................48


6.1
Increased SMPP Connectivity .......................................................................48
6.2
SMPP Multiplexor Interworking Product......................................................49
6.2.1
Multiple SMPP Multiplexor Interworking Products.....................49
6.2.2
SMPP Protocol v3.4......................................................................49
6.2.3
SMPP Extended Message Length.................................................49

7.

Interworking Products..............................................................................................50
7.1
TAP Interworking Product.............................................................................50
7.1.1
Support for latest Version of Protocol Definition.........................50

DRAFT

SMS-2700-FD-xxxx-UD2

Feature Description

7.2

7.3

Table of Contents

7.1.2
Minimizing TAP TCP session startup times.................................50
Sierra Interworking Product...........................................................................51
7.2.1
Support for Latest OCL Version...................................................51
7.2.2
Sierra Configurable text additions .............................................51
TNPP Interworking Prooduct.........................................................................52
7.3.1
Application Support for TCP........................................................52

Appendix A: User Documentation...................................................................................... 53


Appendix B: Release 2700 Product Matrix........................................................................ 55
Appendix C: Platforms Supported ...................................................................................... 57
Glossary...................................................................................................................................59

SMS-2700-FD-xxxx-UD2

DRAFT

References

Feature Description

References
[1]

TIA/EIA-136-720 General UDP Transport Service (GUTS), October 7, 1998

[2]
1998

TIA/EIA-136-620 Teleservice Segmentation and Reassembly (TSAR), October 7,

[3]
Telocator Alphanumeric Protocol (TAP), Version 1.8, 4th Feb. 1997, Telocator Personal Communications Industry Association.
[4]
Distributed Management Metrics Module, version 1.0, Feature Description, FLDDMMM1.0-0001

DRAFT

SMS-2700-FD-xxxx-UD2

Feature Description

List of Tables

List of Tables
Message Management module commands ..............................................................................15
SME Management module commands ...................................................................................15
Subscriber Management module commands ...........................................................................15
Default module commands ......................................................................................................16
Query module commands ........................................................................................................17
Configuration module commands ...........................................................................................17
Multiple Mobile Networks ......................................................................................................27
GSM Mobile Network Product Components ..........................................................................32
Transfer Layer PDUs in Telepath SMSC Release 2700 .........................................................33
New Telepath SNMP alarms ...................................................................................................45
Table A-1: Telepath SMSC Release 2700 User Documentation............................................ 52
Table B-1: Product Matrix ...................................................................................................... 54
Table C-1: Hewlett Packard Configurations........................................................................... 56
Table C-2: Lucent DNCP Configurations............................................................................... 56
Table C-3: Sun Netra Configurations...................................................................................... 56
Table C-4: Estimated Disk and RAM Sizing.......................................................................... 57

SMS-2700-FD-xxxx-UD2

DRAFT

List of Figures

Feature Description

List of Figures

Figure 1-1: Distributed Administration and Provisioning Module......................................... 16


Figure 1-2: Multiple SNMP Managers.................................................................................... 21
Figure 1-3: Billing Components.............................................................................................. 23

DRAFT

SMS-2700-FD-xxxx-UD2

Feature Description

Preface

Preface
This document provides an overview of Release 2700 of Telepath SMSC. Release 2700 is a
major system release and includes extensive new functionality.
It is important to read the following sections of the Preface before you proceed:

Brief summary of each chapter

Intended audience

How to use this document

About this Document


This is a draft of the Telepath SMSC Release 2700 Feature Description. It contains the
following chapters:

Preface
This chapter provides a brief introduction to Release 2700 of the Telepath SMSC product.

Chapter 1: General ( for all Network Operators)


This chapter details the enhancements added to Telepath SMSC that apply to all network
operators, irrespective of type of network protocol. It covers areas such as message
management, platform management, billing, sizing and performance.

Chapter 2: Wireless Application Protocol


This chapter outlines the functionality that has been added to Release 2700 specifically to
enable applications and services that are based on WAP. This functionality is distributed
across various elements of the product family.

Chapter 3: GSM Network Operators


This chapter outlines the functionality that has been added specifically for GSM networks
for Release 2700, either to the GSM mobile network product, or to the core modules of
Telepath SMSC.

Chapter 4: ANSI-41 Network Operators


This chapter outlines the functionality that has been added specifically for ANSI-136
(TDMA) and ANSI-95/91 (CDMA) networks for Release 2700, either to the TDMA
mobile network product, or to the CDMA mobile network product, or to the core modules
of Telepath SMSC.

Chapter 5: PDC Network Operators


This chapter outlines the functionality that has been added specifically for PDC networks
for Release 2700, either to the PDC mobile network product, or to the core modules of
Telepath SMSC.

Chapter 6: SMPP Interworking Product

SMS-2700-FD-xxxx-UD2

DRAFT

Preface

Feature Description

This chapter outlines the SMPP functionality that has been added for Release 2700.

Chapter 7: Interworking Products


This chapter provides details of the enhancements added to the Telepath SMSC
Application Interworking Products for Release 2700.

Appendix A: User Documentation


This appendix details the user documentation that is available as part of Release 2700.

Appendix B: Release 2700 Product Matrix


This appendix provides a product matrix for Release 2700.

Appendix C: Platforms Supported


This appendix outlines the software and hardware platforms supported for Release 2700.

Glossary
The glossary includes a list of definitions, common acronyms, and terms used in this
document and in related documents.

10

DRAFT

SMS-2700-FD-xxxx-UD2

Feature Description

Preface

Intended Audience
The intended audience for this document is resellers and customers. It gives sufficient detail for
network planning and marketing functions to be able to understand the content of Release 2700
and make decisions as to its appropriateness for their network.
It is not the goal of this document to give enough detail to implement the various features and
functions described. The User Guides (as listed in Appendix A) give the level of detail required
for implementation and operation.

How to Use this Document


This document provides a draft feature description for Release 2700. It is subject to change.
It is recommended that you first acquaint yourself with the terms and acronyms defined in the
Glossary.

SMS-2700-FD-xxxx-UD2

DRAFT

11

General (for all Network Operators)

1.

Feature Description

General (for all Network Operators)

Release 2700 adds enhancements to the Telepath SMSC product family in the following areas:

Message Management (incl. Routing and Access Control)

Platform Management

Network Management

Billing

Sizing and Performance

1.1

Message Management

1.1.1

Message Routing

Release 2700 is removing support for routing based on regular expressions in favour of routing
based on the following attributes:

Protocol Identifier (PID)

Terminal Type

Service-Centre Address
This provides the basis for the feature known as virtual service centres, detailed below in
chapter 3.5.

Destination Address

Teleservice ID
This provides the ability to support multiple teleservices within the one Message Center,
as detailed below in chapter 4.1.

1.1.2

Access Control

Release 2700 has enhanced the access control functionality as follows:

Expansion of number of supported classes of service to 32


Releases of Telepath SMSC prior to Release 2700 restricted the number of services that
could be defined by an operator to 16 per Service Centre, each of which was assigned a
unique number. This in turn meant that any subscriber was limited to 16 Classes of Service
(COS), defined within a subscriber record as Originating COS and Terminating COS. With
Release 2700, this limit has been extended to 32.

12

Configurability of address length for customer validation

DRAFT

SMS-2700-FD-xxxx-UD2

Feature Description

General (for all Network Operators)

In certain networks e.g. Japan, it is possible for a phone to be connected to extended


devices, such as fax machine, PDA, etc. These devices are usually addressed by giving
them a device identifier, which is appended to the phone number. Telepath SMSC has been
enhanced with Release 2700 to provide support for such devices by allowing the operator
to specify, on a per-interface basis, whether customer validation should be performed in
the knowledge that the address contains a device identifier.
Benefit:
This has the effect of eliminating the requirement to provision the SMSC with all of the
extended devices as well as the phone, and thus speeding up the validation time.

1.1.2.1

Address Translation

The address translation feature in Telepath SMSC has been enhanced in Release 2700 with the
following functionality:

Full Address Translation


This provides the ability to specify that the translation will only take place when the exact
MIN or MSISDN is matched.

Wildcard Matching
This enhancement allows the operator to specify wildcards in an entry in the Address
Translation file.

PID Translation
This allows translation or setting of the Protocol Idenifier (PID) for any message going to
a particular subscriber.

Benefit:
All of the above feature enhancements provide additional flexibility in responding rapidly to
market and competitive pressures, whether it be for number portability reasons or because ofthe
introduction of new services.

SMS-2700-FD-xxxx-UD2

DRAFT

13

General (for all Network Operators)

1.2

Feature Description

Platform Management

1.2.1

Distributed Management Statistics Module

A new offering from Logica, the Distributed Management Metrics (DMM) Module forms the
cornerstone of an integrated and distributed graphical Operations, Administration and
Management environment.
At the heart of the DMM Module is a client server architecture. The client, which we call the
Distributed Management Metrics Portal, is implemented in Java. It can run anywhere there is a
web browser. The DMM Module server is built as a Common Object Request Broker
Architecture (CORBA) server. The DMM Portal and server communicate over a TCP/IP
network using the standardised Internet InterORB Protocol (IIOP).
Timely, accurate and focused information is the key to optimising the operation of an SMS
network. The DMM Module is the means to obtain this information. Used in conjunction with
Telepath SMSC the DMM Module facilitates day-to-day operational decision making.
Optimum configuration and management of the entire system is substantially enhanced with
metrics available on overall SMS usage, peak message time, message transmission success
rates, network and computing resource utilisation.
Focusing on the customer, business depends on the ability to provide the services a customer
wants in a way that optimises the return on investment. The DMM module is designed to
provide data needed for strategic business decisions focused on the customer. The module
provides metrics to compare specific service utilisation, customer usage profiles and user group
usage profiles.

1.2.1.1

Business Features

The main business features of the DMM Module, used in conjunction with Telepath SMSC
Release 2700, can be summarised as follows:

Distributed Management Metrics Portal implemented in Java to run anywhere

Designed from the ground up for maximum Ease of Use

Near real time monitoring of both platform and Telepath SMSC operation

Architected to scale and perform with growing systems

Near real time access to business critical and operational data

Integrated database dedicated to maintaining critical statistics on your SMS business

Server side deployment flexibility with the choice of on or off Telepath SMSC platform
operation

Standardised DMM Portal - server - Portal communication through the use of IIOP

Fully configurable operation

Secure DMM Portal operation

Reporting support through both graphical and text export facilities

A full list of the management metrics available from the DMM Portal can be found in
Distributed Management Metrics Module, Feature Description document [4].

14

DRAFT

SMS-2700-FD-xxxx-UD2

Feature Description

1.2.1.2

General (for all Network Operators)

Business Benefits

The overall rational of the Distributed Management Metrics Module is to provide network
operators with the most comprehensive package of information about the operation of their
Telepath SMSC and the services running on that system. The information is firmly focused on
providing the raw material to drive business decisions. In short a DMM Module will:

enable policy decisions to maximise the utilisation of network and computing resources

illustrate customer behaviour

produce valuable feedback on the relative value of individual SMS service offerings

From an operational perspective, the choice of architecture and technology ensures:

DMM Module deployment flexibility

cost effectiveness through the use of off the shelf software and hardware

with the Ease of Use, training time and costs are low

SMS-2700-FD-xxxx-UD2

DRAFT

15

General (for all Network Operators)

1.2.2

Feature Description

Distributed Administration and Provisioning Module

Continuing to deliver on Logicas commitment to make Telepath SMSC the easiest and most
flexible short message service centre, Release 2700 will come with a new Distributed
Administration and Provisioning (DAP) Module.
The DAP Module is designed and implemented to be easy to use. Targeted at customer care
operations, it provides access to all the basic call centre functionality through a Java based web
portal, the DAP Portal.
As SMS grows and develops, more and more new customers are using premium value services.
These customers demand a high level of customer care. The challange for service providers is
to realise effective, efficient and available customer support required. The New Distributed
Administration and Provisioning Module is specificially designed by Logica to provide all the
infrastructure needed to meet these demands.

1.2.2.1

DAP Module

The Distributed Administration and Provisioning Module is made up of a number of


components. The module has been designed with a client server architecture, see the figure
below. The package has been developed by making use of the latest state of the art software
technology. The client, called the DAP Portal, is a JAVA programme executing from a browser
window. To distribution the costomer care and provisioning functionality many clients will
communicating with each multi threaded DAP server. In this release the DAP server is coresident with the core functionality of Telepath SMSC.

..........
DAP Portal

DAP Portal

DAP Portal

DAP Server

tpevent

SMS Data
Store

Telepath SMSC

Figure 1-1: Distributed Administration and Provisioning Module

16

DRAFT

SMS-2700-FD-xxxx-UD2

Feature Description

1.2.2.2

General (for all Network Operators)

Message Management Facilities

With this functionality the operator is offered the possibility to remotely send and manage
messages. The following functions are provided:

Send a Message

View a Message

Browse Address

Accept/Delete a Message

Retrieve Message details

Display filtered list of Messages

1.2.2.3

Provision Subscriber Facilities

With this functionality the operator is offered the possibility to remotely manage the
Subscribers information. The following functions are provided:

Create a new Subscriber

View Subscriber information

Modify Subscriber information

Delete a Subscriber from the SMSC system

List Subscribers using the subscriber ID as a criteria

List the Subscribers registered page by page

1.2.2.4

Benefits

The Distributed Administration and Provisioning Module shipped as part of Telepath SMSC
Release 2700 provides:

distributed customer care and provisioning maximising the use of local skilled resources

cost effectiveness through the support for off-the-shelf computing resource

access to state of the art functions with a minimum skills barrier

SMS-2700-FD-xxxx-UD2

DRAFT

17

General (for all Network Operators)

1.2.3

Feature Description

Remote Administration and Provisioning

In a further effort to enhance the administration and provisioning features of Telepath SMSC,
Release 2700 will incorporate a new ASCII based Remote Administration and Provisioning
(RAP) protocol. The RAP protocol will facilitate:

application integration with Telepath SMSC administration and provisioning functionality

This might be done, for example, to automatically export provisioned data in Telepath SMSC
to other applications or to allow administration and provisioning of Telepath SMSC via a
custom interface (which may also administer other applications).

the support of non-GUI applications, for example applications used by support personnel,
customer care or billing systems via Telnet

The RAP protocol consists of two parts. The first part, called ASCII-Transport System (ATS),
is a framework for the transfer of ASCII commands and responses, where the commands and
responses can be single-line or multi-line. The second part, called RAP Application Services,
are the operations which are layered on top of ATS to support the SMS Administration and
Provisioning functionality.
Administration and provisioning business needs of Telepath SMSC users are abstracted by the
RAP Application Services into three independent modules; Message Management, SME
Management and Sudscriber Management. There are also three RAP support modules: Default,
Query and Configuration modules.

1.2.3.1

Message Management Module

This module is responsible for sending and managing messages. Its commands are:

Command

Description

submit

Submits a message

list_msg

Lists messages

view

Displays information for a specific message

modify

Changes the details of a particular message

accept

Changes the status of an undelivered message to Accepted

delete

Changes the status of an undelivered message to Deleted

Table 1-1: Message Management module commands

18

DRAFT

SMS-2700-FD-xxxx-UD2

Feature Description

1.2.3.2

General (for all Network Operators)

SME Management Module

This module is responsible for managing SMEs. Its commands are:


Command

Description

get_dstate

Retrieves the SME state

retry

Initiates a retry delivery attempt on an SME

Table 1-2: SME Management module commands

1.2.3.3

Subscriber Management Module

The subscriber Management module allows an operator to perform different actions regarding
the provisioning of subscribers and distribution lists The functionalityof this module is still
under review.

1.2.3.4

Default Module

This module provides the initial commands necessary for the use of the RAP. These commands
are:

Command

Description

login

Handles the connection with the JSAT Server

logout

Closes the connection with the JSAT Server

exit

Closes the connection with the RAP Server

help

Provides information on the commands available

Table 1-3: Default module commands

1.2.3.5

Query Module

The query module provides an interface to manage the queries generated by the other modules.
It enables the following actions:
Command

Description

get_info

Retrieves summary information about a query

list

Lists the result of the query

refresh

Refreshes the information of the query

close

Closes the query

Table 1-4: Query module commands

SMS-2700-FD-xxxx-UD2

DRAFT

19

General (for all Network Operators)

1.2.3.6

Feature Description

Configuration Module

This module is to be used for configuring parameters. The following commands are available
in this module:

Command

Description

view

Displays the current settings

update

Updates the RAP protocol settings

save_param

Save the current settings into the systems file

Table 1-5: Configuration module commands

1.2.3.7

Benefits of RAP

The Remote Administration and Provisioning protocol has significant benefits for Telepath
SMSC users:

facilitates a holistic view of system administration, billing and customer care through
enhanced integration with existing systems without requiring re-implementation or
wrapping

provides a single interface for data retrieval, rationalising the automation of critical
business indicators

1.2.4

Overload Control

A facility is provided within Release 2700 for detection of platform overload on MO interfaces,
and subsequent rejection of messages until the situation is rectified.
Benefit:
This feature allows an operator to ensure that the SMSC does not continue to accept messages
for delivery if the platform is temporarily overloaded. This ensures that, if there is a problem
with delivery on any one interface, it does not degrade the response time to an unacceptable
level on all other interfaces.

20

DRAFT

SMS-2700-FD-xxxx-UD2

Feature Description

1.3

General (for all Network Operators)

Network Management

Release 2700 provides additional alarm information in an SNMP-based network managment


environment. Again, it is not expected that this additional functionality provides an opportunity
for an operator to generate additional revenue, but rather to save on the cost of maintaining the
platform.

1.3.1

SNMP Agent

Continuing to enhance the support for SNMP management of Telepath SMSC, for Release
2700 there are two significant new features; support for multiple SNMP Managers and support
for SNMP v2 requests.

1.3.1.1

Multiple SNMP Manager support

In Release 2700 of Telepath SMSC, it will be possible to send Telepath SMSC traps to multiple
SNMP managers. Traps will be sent using a user defined snmpd.conf file. This file is used by
the master agent to assign the destination SNMP manager to a given trap.

SNMP Subagent
(tpsa)
GET/SET
Requests

Requests to
raise TRAPs

TRAPs

Telepath SMSC
Platform

tpevent

HP-UX master agent

snmpd.conf

TRAPs to multiple SNMP Manager platforms

Figure 1-2: Multiple SNMP Managers


Benefits:

Configuration of the SNMP Trap destination allows for a focussed response to specific
system management events.

SMS-2700-FD-xxxx-UD2

DRAFT

21

General (for all Network Operators)

Feature Description

Support for multiple SNMP managers facilitates the distribution of critical management
information.

In a geographical context, the distribution of SNMP Management information enhances


the flexibility for recovery processes.

1.3.1.2

Support of SNMPv2 requests

Support for SNMPv2 requests will be introduced as part of Release 2700. Combining the
support for SNMPv1 traps in earlier Telepath SMSC releases, the system can be configured to
send either SNMPv1 or SNMPv2 traps.

22

DRAFT

SMS-2700-FD-xxxx-UD2

Feature Description

1.4

General (for all Network Operators)

Billing

Release 2700 introduces an improved billing architecture replacing what is currently in use with
Releases 2600 and 2650. The following diagram provides a simple illustration of the main
components responsible for billing in Release 2700.

Core Product

CDR Files
(TLV format)

Billing Spooler

CDR Post-Processor

Figure 1-3: Billing Components


The billing spooler is a Telepath SMSC component that takes a stream of short messages from
the core product in real-time and writes each entire short message to a CDR billing file in TLV
format. These files are subsequently post-processed by a separate component know as the CDR
post-processor. This latter component was introduced in Release 2600.
Benefits:
This new architecture improves the overall on-platform billing capabilities of Telepath SMSC
in two ways:

it enables real-time billing for applications such as prepaid SMS, due to its high
performance

as a result of the above, it enables billing for Express Messages

it removes the requirement for regular collection of billing information from the message
store (ORACLE or OpenIngres in previous releases), and the associated performance
impact.

SMS-2700-FD-xxxx-UD2

DRAFT

23

General (for all Network Operators)

1.4.1

Feature Description

Prepaid SMS

As mentioned previously, Release 2700 allows a real-time stream of billing information to be


generated. Traditionally this stream is written to a CDR file, and may subsequently be used to
reconcile billing information for either prepaid or postpaid subscribers. The frequency at
which this reconciliation is done can vary according to whether the messages are to be prepaid
or postpaid.
Release 2700 provides additional functionality to allow this real-time stream of billing
information to be written to a device other than a file e.g. a TCP port. This in turn can be used
by an external system, such as Logicas Aethos prepaid products, to provide real-time debiting
upon delivery of short messages.
Benefit:
This feature provides the ability to limit the window for fraud that is given to prepaid
subscribers who are charged for short messages on delivery only, by either debiting preallocated short message credits, or performing a debit immediately after delivery of the
message.

1.4.2

CDR File Improvements

The following additional fields are being added to the CDR files in Release 2700:

Mobile Subscriber Identity


This equates to MSISDN for GSM networks, and IMSI or MIN for IS-41 networks.

Destination Electronic Serial Number (ESN)


This is a unique identifier for a mobile entity, and corresponds to the internationally
recognized format of 8 bits for the Manufacturer Code and 24 bits for the Serial Number.

Message Class
This indicates the originators designated classification of the service, and is unique to
PDC networks.

Charging Indicator
This indicates whether the Originator or the Destination should be charged for this
message, and whether the Originator should be charged for the reply.

Message Mode
This field indicates whether this message was stored or not, that is, an Express message or
a Classic/Premium message.

Manual Delivery
This indicates whether an ACK was required for the message and whether it was a Manual
Ack or a Delivery Ack. This field is unique to IS-41 networks.

Distribution List
This indicates whether the message was part of a distribution list.

24

Reply Path

DRAFT

SMS-2700-FD-xxxx-UD2

Feature Description

General (for all Network Operators)

This indicates whether the Reply Path field was set on GSM MO and MT terminated
messages.

1.4.3

Per-Interface Billing Configuration

In addition to the Charging Indicator CDR field mentioned above, it is also possible in Release
2700, on a per-interface basis, to control whether there are any CDRs produced at all. This is
achieved through a configurable setting for each interface. It should be noted that the perinterface setting overrides any per-message Charging Indicator settings.
Benefit:
Operators may now turn off generation of CDR records where services are either not billed at
all, not billed on a per-message basis, or billed by subscription. This in turn results in a n SMSC
that is more finely tuned to the services it is providing, and more performant overall.

SMS-2700-FD-xxxx-UD2

DRAFT

25

General (for all Network Operators)

1.5

Feature Description

Capacity and Performance

A key consideration when planning SMS-based services is the capacity requirement, both in
terms of the traffic throughput and also the available storage. Recent years have seen impressive
growth in the usage of Short Message Services, and this is reflected in steadily rising capacity
requirements.
Logica have made system capacity and performance a key factor in the development of the
Telepath SMSC product, and each recent release has seen marked advances in this area, both in
terms of raising the basic limits and also with the introduction of innovative new features to
support the diversifying SMS application environment.
Highlights of previous releases have included:

RAM-caching of message queues (2510)

Introduction of Messaging Mode concept with Express Messaging (2600)

Solid-State disk and RAID support (2650)

NuKernel with optimised message completion algorithm (2650)

These feature innovations have been complemented by the continued evolution of our
supported hardware platforms, and combine to consistently reduce the cost factor per delivered
message.
Release 2700 is a major milestone in this advance, and sees the launch of a number of new
features which radically lift the capacity ceiling of a single Telepath SMSC node. Support for
multiple nodes in N+1 clusters ensures that Telepath SMSC is now ideally placed to meet even
the most ambitious capacity requirements for today - with capacity to spare for the future.

1.5.1

Premium Messaging Mode

The most notable single performance enhancement in Release 2700, Premium Messaging
Mode, joins Express and Classic Messaging in enabling the operator to choose the best possible
messaging mode for messaging service.
Premium Messaging offers store-and-forward capability similar to Classic Messaging, but
draws upon a journalled-file store to deliver much higher throughput levels than were
previously attainable on a single node. While still offering core messaging operations such as
insert, update, replace, query, cancel and purge, Premium Messaging dispenses with the
complex and maintenance-intensive relational SQL database to focus on delivering a high
performance messaging engine.
Premium Messaging is intended to replace Classic Messaging as the default choice for the
majority of messaging applications. Classic Messaging however will remain as an option for
specialised applications, where the advanced SQL capabilities of this mode remain an essential
requirement. Just as Express Messaging will continue to be applied for datagram type
applications, including support for WAP.
Messaging throughput has not just risen in recent years, but also expanded beyond traditional
business hours into the evening and night-time periods. Premium Messaging also eliminates the
need for an extended off-peak time in the daily profile by removing the need for the following
maintance activities:

26

DRAFT

SMS-2700-FD-xxxx-UD2

Feature Description

General (for all Network Operators)

No purging required - messages deleted in-flight when completed

No optimisation required - database is self-optimising

Minimal billing impact - CDRs are streamed in-flight as messages are completed

(This last feature is separate from Premium Messaging and also available in Release 2650).
As well as ensuring sustainable performance throughout the day, these enhancements also
considerably reduce the manual overhead of carrying out these maintenance activities.

1.5.2

Performance

As a truly global product installed in networks and working with diverse network technologies
around the world, Telepath SMSC is exposed to many different service environments and traffic
profiles.
Underlining our desire to make our platform reflect actual commercial traffic profiles, we have
reviewed the basis of our capacity benchmarking environment for Release 2700. Drawing on
our experience at over 100 operator sites, we have decided to switch our standard benchmarking
environment from the traditional one based strongly on Mobile-Terminated traffic, with 70%
Absent Subscriber, to one with 100% submission success.
This change has been carefully made to reflect the dramatic shift in traffic patterns both in the
GSM market (driven by prepaid subscribers) and the PDC market (driven by messaging
services). Furthermore, this recognises that in any market, this profile represents the most
demanding environment for an SMSC, and therefore is the appropriate choice for a generic
benchmark.
In comparing these figures with previously published BHSM figures, it is important to be aware
that BHSM figures measured in the 70% Absent Subscriber environment - currently a de-facto
industry standard - need to be twice to three times the nominal value of our quoted figures to
achieve the same traffic capacity for a given traffic profile.

1.5.3

Sizing

For Release 2700, we have made explicit our support for storage capacity:

Storage for 5 million messages per day

1 million messages may be in-flight (undelivered) at any instant

An indicative summary of the hardware requirements for different capacity sizing points from
50,000 to 5,000,000 messages per day is provided in Appendix C.

1.5.4

Classic Messaging (ORACLE)

SMS-2700-FD-xxxx-UD2

DRAFT

27

General (for all Network Operators)

1.6

Feature Description

General Mobile Network Product Enhancements

1.6.1

Message Delivery to Dual-Mode Phones

With the advent and increasing use of dual-mode wireless handsets, short messaging support
for the two network types has become very important. In Release 2700 a subscriber can be
provisioned with a terminal type, reflecting which network technologies the subscribers handset supports. The terminal type will also indicate which technology is primary (or home, i.e.
routed first) or secondary. If the customer is not provisioned in the database the terminal type
can be derived as part of the user validation process.
A terminal type is mapped to a configurable combination of two network technologies (known
as the primary and secondary channels), by means of the new message routing mechanism
(also introduced in Release 2700). The primary and secondary channels are defined by the
names of the Mobile Network Products (CDMA, TDMA, AMPS, DCS1900).
When a message is received for a subscriber, their terminal type is checked, either via the provisioned record or another user validation process. This terminal type is then looked up in the
routing table and the primary and secondary channels are retrieved. Delivery is then attempted
on the primary/home channel first. If this fails with a configurable error /cause code then the
message is immediately attempted on the secondary channel. If this also fails the message
goes into normal retry.
Note: All combinations of technologies depend on both network and handset support
being available.

1.6.2

Co-resident Mobile Network Products

Previous releases of Telepath SMSC have been deployed supporting a single air interface,
known as the Mobile Network Product. Within the Mobile Network Product, the protocol layer
used to transfer the message between the SMSC and the wireless phone is known as the Teleservice or Transfer Layer. In summary the Teleservices supported are:
-

TDMA. All ANSI-136 teleservices (CMT, OATS, OPTS, GUTS)

IS-95A CDMA. All Teleservices (CMT, CPT, VMN)

IS-91A AMPS. All messages are delivered as CMT-91. Message Type used is SMS.

GSM 03.40 Point-to-Point Messaging

With Release 2700 a single Telepath SMSC node can support the following combinations of
CDMA, TDMA, AMPS and GSM concurrently, including all of their teleservices and without
any loss of functionality on any of the Mobile Network Products. This is achieved through the
use of the ANSI-41 Teleservice Router (see Section 4.1.1) and new flexible routing (see Section 1.1.1), both of which are being introduced in Release 2700.

28

DRAFT

SMS-2700-FD-xxxx-UD2

Feature Description

General (for all Network Operators)

Table 1-1: Multiple Mobile Networks


Network Technologiesa

Dual-Mode Phonesb

Message Handoverc

CDMA/TDMAd

Not Applicable

Supported

TDMA/GSMe

Not Applicable

Unsupported

CDMA/AMPS

MT support only

Not Applicable

TDMA/AMPS

MT support only

Not Applicable

a. These are the combinations of mobile network product that may run simultaneously on one
SMSC.
b. This column indicates the types of dual-mode phones that are supported.
c. This indicates whether it is possible to hand MO-MT short messages off from one technology to the other.
d. Note that only one version of the CDMA mobile network product can be supported simultaneously, that is, either full ANSI or Korean CDMA.
e. Note that, while all other combinations require one SS7 stack only, this requires the use of
two different SS7 stacks.

SMS-2700-FD-xxxx-UD2

DRAFT

29

Wireless Application Protocol (WAP)

2.

Feature Description

Wireless Application Protocol (WAP)

Wireless Application Protocol (WAP) is an open global standard for delivery and presentation
of wireless information and telephony services on mobile phones and other wireless devices.
The objective of WAP is to provide an open interoperable framework for delivery of internet
based content and advanced data services to mobile subscribers - independently of mobile
network technologies, bearer technologies and wireless device technology.
WAP has been endorsed by all of the major participants in the Mobile Telecommunications
arena. Through the WAP Forum, an open, industry-led initiative has been established with the
goal of providing efficient information services to mobile device users via limited bandwidth
bearers such as SMS and Circuit Switched Data.
WAP services will be delivered to mobile users through an optimized information format
enabling interactive information exchange with wireless devices equipped with a micro
browser. Existing standards such as XML and IP are adopted wherever possible to maintain
compatibility with the internet model.

2.1

Telepath SMSC and WAP

SMS has been defined as one of the primary bearers for WAP services and will be used
extensively for applications requiring low bandwidth and/or for which interactive user response
may not be required. SMS will be particularly attractive for 'push' WAP applications in that it
offers an intuitive and inexpensive bearer for WAP data whilst the mobile device can still be
available for other services - such as voice calls.
Telepath SMSC Release 2700 may be connected to one or more WAP Gateways simultaneously
and supports the transport of both mobile originated (MO) and mobile terminated (MT) WAP
message data through the mobile network. It includes enhanced features to facilitate support for
WAP services, such as:-

30

Express and Premium message modes

Extended message length

Message fragmentation and re-assembly

Alert Notification

Support for User Data Header encoding (GSM specific, introduced in Release 2600)

Support for ANSI-136-750 GUTS (General UDP Transport Service)

More messages to send (GSM specific)

Application Port addressing (introduced in Release 2600)

DRAFT

SMS-2700-FD-xxxx-UD2

Feature Description

2.1.1

Wireless Application Protocol (WAP)

Express Messaging Mode

This message mode enables messages to be rapidly switched between the Internet IP network
and the mobile network, which is ideally suited for some WAP applications which require a
faster response to the user than can be offered using the traditional store and forward
mechanism.
Express WAP messages are not securely stored in a database and the associated functions of
"long-term" retry and guaranteed message delivery are therefore not supported.
Express messaging mode also supports a transaction capability which enables a delivery receipt
to be returned, thus confirming that the message was received at the destination mobile station.
Although the storage of WAP messages is not necessarily required in a WAP context, it should
be noted that the Telepath SMSC Release 2700 also the supports store and forward message
mode for use in WAP applications which require secure delivery.

2.1.2

Premium Messaging Mode

Telepath SMSC Release 2700 has been enhanced to include a Premium Message mode which
offers high performance, secure message delivery based on a journalled file store rather than a
database. Premium messaging offers the security of store and forward functionality whilst
greatly increasing message throughput. This offers significant advantages in a WAP context
where secure delivery is required but where it is also crucial to minimize any latency in
delivering messages to the handset.

2.1.3

Extended Message Length

Using Express Messaging, Telepath SMSC Release 2700 includes support for messages of up
to 1500 bytes in length. Since the maximum MSC message length limit may vary on different
networks, the message length is configurable on a per-MSC basis.
Extended Message length offers great advantages in WAP applications, which require increased
bandwidth.

2.1.4

Alert Notification

Telepath SMSC Release 2700 broadcasts an alert notification to connected ESMEs which is
used as an indication to the message originator than the destination mobile station has reentered the network.
Alert notification is a key feature for WAP applications as it can be used to trigger a WAP push
when a subscribes becomes available, after having been absent from the network.

2.1.5

User Data Header Encoding (UDH)

Telepath SMSC Release 2700 supports User Data Header Encoded data. Thus, the WAP
gateway may submit a UDH encoded message for delivery to a mobile station.

SMS-2700-FD-xxxx-UD2

DRAFT

31

Wireless Application Protocol (WAP)

2.1.6

Feature Description

WAP in ANSI-136 (CMT and GUTS support)

Telepath SMSC Release 2700 supports the GUTS Teleservice defined by TIA TR45-3.6 [1].
GUTS is designed for use specifically in WAP applications. It includes support for Application
Port addressing which allows routing of messages to a specific WAP application.
GUTS is supported for both MO and MT messages which may be delivered in store and forward
or express messaging modes.

2.1.7

Subaddress (End to End Security)

Telepath SMSC Release 2700 includes support for WAP end to end security requirements,
through use of a sub-address field which is passed as a key by the mobile station for the
destination WAP Proxy Server IP address.
This eliminates the need for encryption of addresses end-to-end which would probably not be
possible with intermediate bearers which require the addresses for routing.

2.1.8

WDP/WCMP Gateway Adaption

Telepath SMSC Release 2700 also includes support for the WDP/WCMP Gateway Adaption
document which defines the tunnel protocol to be used when interfacing between a message
centre and a WAP Gateway.
This Tunnel protocol is defined by the WAP Forum as part of the WAP architecture and is based
on a subset of the SMPP v3.4 Protocol Specification.

2.1.9

Message Segmentation

Telepath SMSC Release 2700 includes support for message segmentation either at the service
centre or at the WAP Gateway (though not both).
Telepath SMSC supports the Segmentation and reassembly parameters defined in SMPP v3.4
for message concatenation.
Telepath SMSC supports message segmentation on both GSM and TDMA networks.
Segmentation on CDMA IS-95 will be supported on a future Telepath SMSC release.

2.1.10

Message Reassembly

Telepath SMSC Release 2700 will include support for message re-assembly either at the service
centre or at the WAP Gateway (though not both). Reassembly at the Service Centre will be
performed by the mobile network product for MO messages which must reassemble all
segments before forwarding the complete packet to the WAP Gateway.
If the length of the re-assembled message exceeds 1500 bytes the message will be discarded.

2.1.11

Application Port Addressing

Telepath SMSC Release 2600 included support for source and destination port addressing
which allows addressing and routing of messages to a specific WAP application.

32

DRAFT

SMS-2700-FD-xxxx-UD2

Feature Description

2.1.12

Wireless Application Protocol (WAP)

HLR Delivery Pending Flag handling

Telepath SMSC Release 2700 supports a request by an external entity (e.g. WAP Gateway) to
set (or not set) the Delivery Pending Flag (DPF) in the HLR for failed delivery attempts. This
can be used by Telepath SMSC to trigger an alert to the originating entity when the destination
becomes available.

2.1.13

Telepath SMSC and Internet IP Address Routing

Telepath SMSC Release 2700 supports end-to-end routing for IP Source and Destination
Addresses. IP addresses in IP V4 format are supported.

SMS-2700-FD-xxxx-UD2

DRAFT

33

GSM Network Operators

3.

Feature Description

GSM Network Operators

Telepath SMSC supports all GSM technology-based networks (1800, 900 and 1900 MHz) and
implements the SMS Gateway/Interworking MSC element of the GSM 03.40 and 09.02
standards. All products (1800, 900 and 1900 MHz) have been enhanced with the following
functionality for Release 2700.

3.1

GSM Mobile Network Product Architecture

GSM Mobile Network Products in Release 2700 consist of the following components:
Component

Description

GSM 03.40

Implements GSM 03.40 Gateway SMSC and Interworking SMSC


functionality and serves as the interface to the core product

MAP Provider and User

Implements Gateway MSC and Interworking MSC functionality as


defined in GSM 09.02

SS7 Stack

HP OpenCall

Table 3-1: GSM Mobile Network Product Components

The following block diagram depicts the interaction of these components:

SMSC
Core Product

Gateway Mediation

Interworking Mediation

GSM 03.40

GW-SMSC

IW-SMSC

MAP User
MAP Provider
GSM 09.02

HP OpenCall

PLMN

Figure 3-1: GSM Mobile Network Product Component Diagram

34

DRAFT

SMS-2700-FD-xxxx-UD2

Feature Description

3.2

GSM Network Operators

GSM 03.40 Phase 2+ Compliance

Telepath SMSC Release 2700 provides support for GSM 03.40 version 6.1.0. This version is
essential to enable deployment of WAP-based value-added services using SMS as a bearer.
The Service Centre capabilities include extended support for applications submitting short
messages and short message management through availability of various report and submitted
message handling options.
In addition to SMS-DELIVER, SMS-SUBMIT and SMS-STATUS-REPORT, which are
supported from Release 2600 onwards, the short message transfer layer PDUs available in
Release 2700 are:
PDU

Purpose

SMS-DELIVER-REPORT

used to convey a failure cause as well as a positive or a


negative acknowledgement to an SMS-DELIVER or SMSSTATUS REPORT

SMS-SUBMIT-REPORT

used to convey a failure cause as well as a positive or a


negative acknowledgement to an SMS-SUBMIT or SMSCOMMAND

SMS-COMMAND

used by an MS to request operations on short messages


previously submitted: enquiry to obtain status report(s),
status report request cancellation, message deletion, status
report request

Table 3-2: Transfer Layer PDUs in Telepath SMSC Release 2700


Support of User Data Header and Information Elements has already been offered from Release
2600 onwards, e.g. for Concatenated short messages. In Release 2700, it is complemented by
segmentation feature within Telepath SMSC. Mobile terminated Express short messages of up
to 1500 octets can be accepted for delivery to subscribers, with Telepath SMSC taking care of
segmentation. The segmented information can be delivered within one TCAP dialog, using the
appropriate MAP protocol capabilities available in Release 2700. Please refer to the next
section for further details on supported GSM 09.02 Phase 2+ features.
Benefit:
Support for GSM 03.30 Phase 2+ contributes to a greater message delivery efficiency and offers
improved Short Message management facilities both for subscribers and operators.
Furthermore, it is considered essential for deployment of WAP services.

3.3

GSM 09.02 Phase 2+ Compliance

Telepath SMSC Release 2700 implements MAP as specified in the GSM 09.02 version 6.2.0
(MAP Release 97), including a MAP Release 98 feature for support of IMSI in MO-FSM as
detailed below.
Implementation of the aforementioned MAP release assures an alignment between protocol
capability set and functionality offered to operators by GSM 03.40, furnishing an SMS-based
platform for development and deployment of innovative, sophisticated services.

SMS-2700-FD-xxxx-UD2

DRAFT

35

GSM Network Operators

Feature Description

The growing importance of GPRS is also addressed by Release 2700s ability to deliver
messages via SGSN. The relevant functionality is described in more details in section 3.3.1.
Telepath SMSC can be deployed in a heterogeneous network. The interworking with entities
supporting earlier MAP releases only is assured by the standardised mechanism for Application
Context Version negotiation.
The protocol enhancements offered include the option to send several messages within one
dialogue (More-Messages-To-Send Flag), thus reducing the signalling overhead and radio
resource usage. Once the network has completed paging, authentication and ciphering
procedures for a subscriber, any short messages waiting for delivery or carrying a larger block
of information can be sent without the need to terminate and re-establish the radio connection.
Furthermore, improved short message delivery reporting with more precise failure causes allow
optimisation of the associated network procedures and refinement of retry algorithms. The
SMSC functionality required for the implementation of SM Filtering by the HPLMN,
consisting of an indication to the HLR of RP-Message Type Indicator and RP-Originating
SMSC Address, is also available.
Benefit:
GSM 09.02 Phase 2+ compliance complements the functionality offered by GSM 03.40 Phase
2+ implementation in terms of WAP support, message delivery and network resource usage
efficiency. The associated signalling procedures create a platform for creation of sophisticated,
SMS-based services, and provide operators with additional information helping to monitor and
improve their networks.

3.3.1

GPRS Interface

Telepath SMSC Release 2700 offers full GPRS support, including the implementation of the
Gd interface between the SMSC and the SGSN.
The interface to the HLR has been modified to:

indicate that GPRS is supported (Send Routing Info For SM invoke)

accept both a MSC number and a SGSN number for SM delivery (Send Routing Info For
SM response)

report delivery failure or success specifying to which network node, MSC or SGSN, the
information being reported applies (Report SM Delivery Status)

accept and appropriately use the information provided by an HLR in an Alert Service
Centre request and the following routing data enquiry.

The SMSC can use the SGSN route or the MSC route for the short message delivery, based on
a combination of the information returned by the HLR and on SMSC configuration. This
information reflects the operators preference as to which path should be prioritised, the
subscription data and MS availability via any of the network nodes. If dual delivery path has
been indicated by the HLR, the secondary route will be used upon delivery failure via the
primary one.
This enhanced delivery route selection mechanism offers the option of a more efficient resource
usage, simultaneously providing for an increased likelihood of successful delivery.

36

DRAFT

SMS-2700-FD-xxxx-UD2

Feature Description

GSM Network Operators

An example of a failed short message delivery attempt via SGSN, followed by a successful
delivery via VMSC, is depicted below.
-

The SMSC first interrogates the HLR to obtain routing information, indicating that it
supports GPRS. Assuming a subscriber has access to both GPRS and circuit-switched
services, HLR may return two network entities, the current SGSN and VMSC addresses.
The MAP service used is Send Routing Info For SM.

The SMSC forwards the short message to the SGSN. The delivery fails, e.g. because the
subscriber is not GPRS attached. The SGSN informs the SMSC, returning an appropriate
error cause. The MAP service used is MT-ForwardSM.

A successful delivery attempt via the VMSC follows. The MAP service used is MTForwardSM.

The SMSC informs the HLR about the delivery outcome, indicating the failure cause for
GPRS, and that the MSC path succeeded. This is registered by the HLR. The MAP service
used is Report SM Delivery Status.

VMSC
SMSC

3. Delivery via MSC

2. Delivery Attempt
via SGSN
(MS not attached)
1. Routing Data
Enquiry
4. Delivery Report

HLR

SGSN

Figure 3-2: Example of Short Message Delivery Scenario


Benefit:
With an SMSC supporting SM delivery via GPRS, a more efficient resource usage and
increased successful delivery rate are offered. Furthermore, a bearer service is available to
support services which may be deployed in both GPRS and non-GPRS networks or coverage
areas. The service infrastructure requirements can be greatly reduced by the functionality
already offered by SMS, e.g. with regards to support by Mobile Stations or sophisticated
delivery mechanisms.

SMS-2700-FD-xxxx-UD2

DRAFT

37

GSM Network Operators

3.3.2

Feature Description

Support of IMSI in MO-FSM

In addition to implementing MAP Release 97, a change request approved by ETSI for MAP
Release 98 has been taken into account: an IMSI possibly supplied in a Mobile-Originated
Forward Short Message request is accepted and processed.
This feature is essential to unambiguously identify and validate a subscriber. Please note that it
may also be required for Mobile Number Portability solution.

3.4

SIM Toolkit

SIM Toolkit necessitates several features, a part of which has already been available in Releases
2600 and later. These features include Message Class, Binary Encoding and Message
Concatenation. In Release 2700, the MAP message acknowledging a short message delivery
may carry a component containing User Information Information Element, RP-UI. This
Information Element may contain an RP-ACK, or even an entire short message.
Support of the protocol enhancements aforementioned is essential for SIM Toolkit.

3.5

Mobile Number Portability

The current ETSI Mobile Number Portability specification (GSM 03.66) does not require any
specific SMSC support for Number Portability.
However, if validation of subscribers submitting mobile-originated short messages to the
SMSC is required, MSISDN may no longer be suitable for this purpose. Telepath SMSC is
capable of using the IMSI supplied in a MO-FSM request as the unique subscriber and network
identity information.
Logica will co-operate with operators on an individual basis in order to fulfil further
requirements on specific number portability solutions.

3.6

Virtual Service Centres

Telepath SMSC Release 2700 offers the option to associate an onward route or address for each
of the virtual service centre addresses defined in the system. Any messages arriving at that
service centre are forwarded to this pre-defined destination.
Telepath SMSC Release 2650 already offered the following benefits to operators:

Alleviation of SMSC failure impacts: traffic to an SMSC can be re-routed to another one,
having one service centre address for its own traffic, and one for the re-routed short
messages. Hierarchical order of primary, secondary, tertiary, etc. addresses may be
defined.

Load sharing between two SMSC nodes appearing as a single service centre: identical
service centre address may be assigned to each node, handling the part of short message
traffic allocated through the alternate routing capability of SS7.

38

DRAFT

SMS-2700-FD-xxxx-UD2

Feature Description

GSM Network Operators

Splitting of one physical SMSC between several service providers: an SMSC address is
assigned to each service provider (or another user group, e.g. corporate users), permitting
a clear identification, management and charging of short message traffic relating to the
respective users.

Release 2700 enhancements provide for a simplification of short message handling through the
onward routing. Some specific services are conceivable, requiring regular sending of short
message to a defined destination address or address list. Having received SIM cards with a predefined service centre address from their service providers, subscribers may just compose a
message with any destination address. A fixed assignment of an onward destination to a service
centre address permits to forward all short messages with the particular service centre address
to the correct, pre-determined destination, which is responsible for further message distribution.
A basic form of destination address translation, which depends on service centre address rather
than destination address itself, is also available, consisting of the ability to replace the Type of
Number and Numbering Plan Indicator received in the message destination address by a predefined parameter combination.
Benefit:
Apart from offering a cost-efficient SMSC on a shared platform to multiple, independent users
(e.g. corporates), this feature facilitates the implementation of services utilizing an automated
message distribution.
As an example, the following service is conceivable:
1.

A short message is sent with the destination number indicating a menu option.

2.

Based on the SMSC address, the short message is routed to a defined application being
able to deal with the request and to return the information as appropriate.

SMS-2700-FD-xxxx-UD2

DRAFT

39

ANSI-41 Network Operators

Feature Description

4.

ANSI-41 Network Operators

4.1

ANSI-41 Mobile Network Product Architecture

In Release 2700 the ANSI-41 Mobile Network Product Architecture has three components,
namely Mobile Network Products, Router and Stack. The following table outlines the options
for the each component:

Component

Options

ANSI-41 Mobile
Network Products

One or more of :CDMA, TDMA, TDMA-OTA*, AMPS


Mandatory : Notification Handler
* Only one TDMA-OTA will be supported per platform.

ANSI-41 Router

One of : ANSI, ITU , Reverse Hybrid

SS7 Stack

One of : HP Opencall/SINAP (ANSI, ITU, Reverse Hybrid)

The main features of this new architecture are as follows:

Support for co-resident Mobile Network Products

Splitting of Mobile Network Products into Transmitter and Receivers (except for TDMAOTA)

Loadsharing of messages to Mobile Network Products of the same technologies, this is


done by configuration of multiple Receivers.

Routing of messages, both incoming and outgoing, based on teleservice ID.

40

DRAFT

SMS-2700-FD-xxxx-UD2

Feature Description

ANSI-41 Network Operators

Single Notification Handler to handle all SMSNOTs received from the router.

Core Product

Transm
itter

CDMA
Mobile
Network
Receiver

TDMA-OTA
Activation
HLR
TDMA
Transm Mobile
itter
Network
Receiver

ANSI-41

TDMA-OTA

Notification

Message

Handler

Handler

ANSI-41 Router
HP Opencall or Lucent SINAP

SMS-2700-FD-xxxx-UD2

DRAFT

41

ANSI-41 Network Operators

4.1.1

Feature Description

ANSI-41 Teleservice Router

Release 2700 provides the ability to route incoming ANSI-41 messages based on Teleservice
ID. This is possible due to the new architecture of the ANSI-41 Mobile Network Products.
When an ANSI-41 User (TDMA,CDMA, etc.) connects to the ANSI-41 Router it sends details
of what Teleservices and Operation codes (OpCode) it accepts or sends and on what sub system
number (the Users do not have connections to the stack an thus have no view of point codes or
any other stack configuration).
Benefit:
It is this feature that provides the unique benefit of being able to support multiple teleservices
on the one Telepath SMSC platform.

4.1.2

ANSI-41 Transmitter/Receiver Structure

In Release 2700 the ANSI-41 Mobile Network Products have been split into two processes,
namely a transmitter and a receiver. The Transmitter sends messages (Mobile Originated) to
the Telepath SMSC Core Product that it has received from the SS7 stack (via the router) and
the Receiver takes messages (Mobile Terminated) from the Telepath SMSC Core Product and
sends that to the SS7 stack for delivery (via the router).
Also, in Release 2700 a seperate process, known as the Notification Handler, receives SMSNOTS from the network via the router.

42

DRAFT

SMS-2700-FD-xxxx-UD2

Feature Description

4.2

ANSI-41 Network Operators

General ANSI-41 Features

4.2.1

Removal of MO screening

In Release 2600 the TDMA and CDMA Mobile Network Products screened the Destination
Address parameter attributes for mobile originated messages. In effect the message (SMDPP)
would have to be submitted with a destination TON and NPI equal to the TON and NPI that
the relevant Mobile Network Product has bound with.
In Release 2700 the following elements are now accepted in the SMDPP Invoke parameters
SMS_OriginalDestinationAddress, SMS_OrigAddress and SMS_OrigOrigAddress for a
Mobile Originated Message:

Element

Value

Value Meaning

Type of Digits

Ignored

Nature of Number

0
1

National
International

Numbering Plan

0
2
3
7
14

Unknown
Telephony Numbering (E.164)
Data Numbering (X.121)
Private Numbering Plan
Internet Protocol (IP)

Encoding

1
3

BCD
Octet String

4.2.2

IMSI-based Addressing

Release 2700 provides support for IMSI based addressing of ANSI-41 MAP Message Operations through the introduction of the MSID (Mobile Station Identity). The MSID can either be
an IMSI (International Mobile Station Identity) or a MIN (Mobile Identification Number).
MSID is optional in an SMDPP but mandatory in an SMSREQ and SMSNOT.

4.2.3

International Callback Number Format

In Release 2700 ANSI-41 Mobile Network Products can recognise callback numbers other than
10 digit North American numbers, which are embedded in the text of the message. It also
supports numbers with more than 10 digits.
As with previous releases, if the callback number is not explicitly supplied by the Telepath
SMSC Core Product, then the Mobile Network Product will extract it from the text of the
message. In Release 2700 an escape string can be prepended to a callback number. This will
ensure that only actual callback numbers will be sent as such and numbers such as monetary
amounts etc. are not interpreted as call numbers.

SMS-2700-FD-xxxx-UD2

DRAFT

43

ANSI-41 Network Operators

4.2.4

Feature Description

# and * in Callback Number

Previous releases of Telepath SMSC only supported the DTMF values of 0-9 in a callback
number. Release 2700 will also support the remaining two values of * and # in a callback
number.

44

DRAFT

SMS-2700-FD-xxxx-UD2

Feature Description

4.3

ANSI-41 Network Operators

ANSI-136 Features

TDMA technology based networks are supported with Mobile Network products which provide
the full feature set defined in ANSI-136 and ANSI-41C Interface Standards for the Message
Centre Element. For Release 2700, the ANSI-136 mobile network product has been enhanced
with improved compliance to these standards as well as some new functionality.

4.3.1

ANSI-136 GUTS Mobile Network Product

In Release 2700, the TDMA Mobile Network Product provides support for the General UDP
Transport Service (GUTS), as specified by reference [1], for both Mobile Originated and
Mobile Terminated traffic. The GUTS Teleservice is designed to be an efficient transport layer
for Internet/WAP applications. Therefore all WAP traffic on the TDMA Mobile Network Product is expected to be delivered or received using the GUTS Teleservice. GUTS messages are
encapsulated within the SMS_BearerData portion of the ANSI-41 SMDPP Invoke operation
for transport across the ANSI-41 network.
The TDMA Mobile Network Product provides support for the following GUTS message:
GUTS Data (MO/MT)

This message is used for the delivery of a datagram to/from the


MS. The user data in the datagram is binary data, which has
been encoded by the originating application. This encoding is
transparent to the GUTS Teleservice

The use of Teleservice Segmentation and Reassembly (TSAR) is optional for GUTS. It is
implemented as part of the TDMA Mobile Network Product whereby if a GUTS message
exceeds the network maximum message length, it is segmented by the Mobile Network Product using TSAR and reassembled using TSAR by the MS.

4.3.1.1

ANSI-136 TSAR

The TDMA Mobile Network Product provides support for ANSI-136 Teleservice Segmentation and Reassembly (TSAR), as specified by reference [2], for both Mobile Originated and
Mobile Terminated messages. Release 2700 supports TSAR for following ANSI-136 Teleservices :

OATS

OPTS

GUTS

CMT is currently under investigation.

TSAR allows for the delivery of SMs which cannot fit within a single ANSI-41 SMDPP
Invoke operation. Segmentation involves breaking the Teleservice message into smaller segments for transport across the network, while reassembly is the process of arranging the segments into their original format.
The ANSI-136 Mobile Network Product provides support for the following TSAR messages:

SMS-2700-FD-xxxx-UD2

DRAFT

45

ANSI-41 Network Operators

Feature Description

TSAR Begin (MO/MT)

This message contains the first of a number of TSAR segments. The Mobile Network Product does not provide support for the optional parameters of the TSAR Begin message
i.e. compression, encryption and CRC calculation.

TSAR Continue (MO/MT)

This message contains intermediate TSAR segments.

TSAR End (MO/MT)

This message contains the last of a number of TSAR segments.

4.3.1.2

Suppression of Originating Address for MT Messages

Release 2700 will allow an operator to suppress the Originating Address in Mobile Terminated
TDMA messages. This prevents a subscriber from knowing where a message has originated
from
Benefit:
This feature is ideal where the operator does not want the subscriber to reply to the message,
or wants to offer a trial service but does not want to supply the originating address to the subscriber.
Note:

46

This functionality is optional and when switched on will have the effect of not
displaying the originating address on the handset.

DRAFT

SMS-2700-FD-xxxx-UD2

Feature Description

PDC Network Operators

5.

PDC Network Operators

5.1

Intra-SMSC Alerting

Details of this feature will be added to a future draft of this document.

5.2

PDC Mobile Network Product Alarms

A list of new alarms generated by the Telepath SMSC Release 2700 SNMP sub-agent are shown
below.
Trap ID

Trap name

18

MNAIM MTP indication *

19

MNAIM MTP congestion indication *

20

MNAIM control state indication

Table 5-1: New Telepath SNMP alarms


* Traps 18 and 19 are supported on the Ulticom SignalWare SS7 stack only.
Each alarm is identified by a unique SNMP trap ID (as shown in the table above).

5.2.1

MTP indication

This trap is raised when an MTP_PAUSE signal originates from the Ulticom SignalWare SS7
stack and signifies that the MTP layer cannot accept any more ISUP messages for forwarding
to/from the network. It is cleared when an MTP_RESUME signal is received to indicate that
the previous MTP_PAUSE condition has abated.

5.2.2

MTP congestion indication

This trap indicates that the MTP layer of the Ulticom SignalWare SS7 Stack is congested. There
are four levels of congestion, 0-3, with 3 being the highest level of congestion and 0 indicating
that the congestion has cleared. The trap will be raised when an event with levels 3,2,1 is
received and will be cleared when a level 0 event is received.

5.2.3

Control state indication

This trap is raised when the mobile network product is unable to accept messages from or send
messages to the network. It is cleared when the mobile network product has re-bound to the
Telepath SMSC core as a transmitter/receiver and hence is able to continue to process
messages.

SMS-2700-FD-xxxx-UD2

DRAFT

47

SMPP Interworking Product

6.

Feature Description

SMPP Interworking Product

SMPP is an open protocol designed to provide a flexible data communications interface for
exchange of short message data between a Short Message Service centre and an SMS
application system, e.g. an SMS Gateway or a WAP Proxy Server. It offers a flexible and easyto-use message transaction interface between an SMSC and an external Short Message Entity
(ESME) and can be implemented over a TCP/IP or X.25 type network connection.
SMPP is Logica Aldiscons primary access protocol for interfacing between Telepath SMSC
and an external Short Message Entity (ESME). The SMPP protocol enables an ESME to submit
messages to the SMSC and to cancel, replace and query messages stored on the SMSC pending
delivery to the destination. SMPP provides return responses for each ESME initiated operation
and also facilitates delivery to the ESME, of short messages originating from the network, e.g.
delivery receipts, mobile originated messages, pager messages etc.
The main enhancements to SMPP for Telepath SMSC Release 2700 are the increase in SMPP
connectivity and those added to support WAP.

6.1

Increased SMPP Connectivity

Telepath SMSC Release 2700 offers increased SMPP connectivity over previous versions of
Telepath SMSC.
This connectivity increase enable to offer a far greater number of value-added service
applications on Telepath SMSC, thus enhancing their service offering.

48

DRAFT

SMS-2700-FD-xxxx-UD2

Feature Description

6.2

SMPP Interworking Product

SMPP Multiplexor Interworking Product

The SMPP Multiplexor Interworking Product is designed to offer an increased number of


concurrent SMPP connections to Telepath SMSC. This improvement in connectivity is gained
through optimisation of the Telepath SMSC base architecture and more efficient use of system
resources. It is intended for use in situations where many low bandwidth SMPP connections
require to connect with Telepath SMSC.
Note:

It is recommended that the simplex SMPP Interworking Product be used to interface


with high data throughput applications, e.g. a voice mail system.

Benefit:
The SMPP Multiplexor Interworking Product offers an increase in the number of simultaneous
SMPP connections that can be supported on Telepath SMSC thus enabling the Network
Operator to offer an increased number of new messaging applications and value added
messaging services.

6.2.1

Multiple SMPP Multiplexor Interworking Products

Multiple instances of the SMPP Multiplexor Interworking Product can be configured on


Telepath SMSC in order to further increase the maximum number of concurrent SMPP
sessions.

6.2.2

SMPP Protocol v3.4

Telepath SMSC Release 2700 includes full support for the SMPP v3.4 Protocol Specification,
including those SMPP PDUs which have been specifically added for WAP applications, i.e.
bind_transceiver, data_sm and alert_notification.

6.2.3

SMPP Extended Message Length

Telepath SMSC Release 2700 includes support for long message lengths up to 1500 bytes.
Since the maximum MSC message length limit may vary on different networks, the message
length is configurable on a per-MSC basis.
Extended Message length offers great advantages in WAP applications, which can be expected
to require increased bandwidth.

SMS-2700-FD-xxxx-UD2

DRAFT

49

Interworking Products

Feature Description

7.

Interworking Products

7.1

TAP Interworking Product

The TAP application product enables paging bureaus and general users of PCs to send
alphanumeric messages to subscribers of the Telepath SMSC. A standard protocol is used from
the paging industry so that existing bureaus and PC software owners can interact with the
Telepath SMSC exactly as they interact today with alphanumeric pager networks. The TAP
application is fully integrated with, and dependent on, the Telepath SMSC product.
The interface to the TAP application utilizes a LAN-based terminal server for modem
communication over PSTN facilities.
It should be noted that, while the TAP application product may be configured to support messages from 1 up to 255 characters in length, the TAP protocol limits messages to 140 characters and thus does not support messages of zero length.

7.1.1

Support for latest Version of Protocol Definition

Release 2700 will support version 1.8 of the Telocator Alphanumeric Protocol (TAP) as
defined by reference [3]. There are three major enhancements in version 1.8 of the TAP specification over the previously supported version 1.5 specification. These are:

The addition of response code numbers to the message sequences returned to the RED
from the TAP Interworking Product.

Implementation of the special response message on a successful logon which shows the
TAP specification supported.

The support for the transparency mechanism whereby non-printable characters can be
included within messages.

7.1.2

Minimizing TAP TCP session startup times

In Release 2700 a compressed logon sequence has been added to the TAP Interworking Product; which will allow for a faster initiation of a new TAP session following on from a previous
session. The existing logon sequence takes five steps, whereas the new logon sequence takes
only two steps.
As this shortened sequence is not formally defined in the TAP specification, Release 2700 will
retain the former 5-step sequence for full compliance and backward compatibility.

50

DRAFT

SMS-2700-FD-xxxx-UD2

Feature Description

7.2

Interworking Products

Sierra Interworking Product

The Sierra application accepts Voice Mail Alerts, Paging Alerts and OA&M Messages from the
Octel Sierra VMS and relays them through the SMSC to the relevant mobile stations. The
interface between the SMSC and the Octel VMS is based on extensions to the Octel Command
Language (OCL Ver.5 12-10-1993) running over X.25.

7.2.1

Support for Latest OCL Version

Release 2700 provides support for the latest version of the Octel Command Language. The
currently supported OCL will continue to be available in a backwards compatibility mode.
In addition the following support is under investigation:

Urgent messages: a notification will be urgent if there are one or more outstanding urgent
voicemail messages in the Octel Sierra system. On IS136/IS95 networks, the notification
will be tagged priority.Where no urgent voicemail messages are outstanding, the urgent
messages part of the short message text will be suppressed.

Replace capability: All voicemail alerts submitted to the SMSC will replace any existing
voicemail alerts so only the latest status is delivered to the handset.

7.2.2

Sierra Configurable text additions

Release 2700 will allow the addition of text before or after the raw callback number delivered
by the Octel Sierra system over the Sierra Interworking Product. The text and its disposition
(prefix or suffix) will be configurable per Sierra connection.

SMS-2700-FD-xxxx-UD2

DRAFT

51

Interworking Products

7.3

Feature Description

TNPP Interworking Prooduct

This short messaging application is used to originate/terminate short messages from the
Telepath SMSC to/from Paging Terminals in Paging Networks. Termination could be initiated
for several reasons, the most likely being the SMSC was unable to deliver the short message to
the subscribers handset within a pre-defined escalation timeframe. Subsequently, the Telepath
SMSC attempts to also deliver it to that same subscribers alternative device (i.e. pager) via a
link to a single Paging Network Operator.
Each instance of the TNPP application can be configured to be either a sender or a receiver or
both. When configured as a receiver, the application monitors the configured port for the
modem ring code. Once the modem connection completes, the application is ready to begin
receiving messages. If the application is configured to be both a receiver and a sender of TNPP
messages, the priority of receiving versus sending is indeterminate.
The interface between the two systems utilizes dial-up asynchronous modem communication
over PSTN facilities. A more permanent connection (such as a leased line) may also be used.
However, if both a direct and a modem connection are desired then two instances of the
application are required, one for each connection type.

7.3.1

Application Support for TCP

Previous releases of TNPP Interworking Product have only supported direct connect modem
or serial connections, in Release 2700 this has been replaced with TCP/IP support. This will be
achieved through the use of a LAN based terminal server, similar to the TAP Interworking
Product. The connectivity between the message center and the terminal server will be TCP/IP
and the connectivity to the paging network will be through modems connected to the terminal
server.

52

DRAFT

SMS-2700-FD-xxxx-UD2

Feature Description

Appendix

Appendix A: User Documentation


Product Area

HP Version

Base Product User


Documentation

To be decided

Mobile Network Product


User Documentation

GSM Mobile Network AIM


Configuration Guide

Lucent Version
To be decided

IS41 TDMA Mobile Network AIM Configuration Guide


IS41 CDMA Mobile Network AIM Configuration Guide
PDC Mobile Network AIM Configuration Guide
Application Interworking
Product User
Documentation

SMPP AIM Configuration Guide

SMPP Multiplexer AIM Configuration Guide


TAP AIM Configuration Guide
TNPP AIM Configuration Guide
Sierra AIM Configuration Guide
UCP AIM Configuration Guide
Provisioning Product User
Documentation

TPPROCUS Users Guide


TPCAI Users Guide
SMPPP AIM Configuration Guide

Operational Management
Product User
Documentation

SNMP Sub-Agent Configuration Guide

TPCUST Users Guide


TPSMT Users Guide (IS41 and GSM)

Table A-1: Telepath SMSC Release 2700 User Documentation


There has been a major restructuring of the user documentation for Release 2700. Details will
be provided at a later date.

SMS-2700-FD-xxxx-UD2

DRAFT

53

Feature Description

Appendix

Appendix B: Release 2700 Product Matrix


Product Area

HP

Ascend

Base Product
Mobile Network Products

Application Interworking
Products

Provisioning Products

Operational Management
Products

Table B-1: Product Matrix

SMS-2700-FD-xxxx-UD2

DRAFT

55

Feature Description

Appendix

Appendix C: Platforms Supported


The following tables outline the hardware and operating system software supported by Release
2700. In all cases, it is recommended that Release 2700 be run with a minimum of 1GB of
memory and a disk array consisting of a minimum of four (4) 9GB disks in a mirrored
configuration (i.e. a total of 72GB of physical disk).
Details of all current medium availability, high availability and fault tolerant platforms can be
had on request from Logica Aldiscon.

HP 9000
HP 9000Series
HP-UX 11
OpenCall 2.0
ORACLE 8.1.5
X.25 ???
Table C-1: Hewlett Packard Configurations

Lucent DNCP
418/428 AC and CO
HP-UX 11
SINAP 8.4
ORACLE 8.1.5
Spider X.25 ???
Table C-2: Lucent DNCP Configurations

Sun Netra
Netra
Solaris 2.6
OMNI SignalWare 6.02.2
Table C-3: Sun Netra Configurations

The following table C-4 outlines the memory and disk requirements for systems supporting
different levels of daily message rates. Please keep in mind that this is indicative, and final disk
and memory requirements for any deployment of Release 2700 should be verified with Logica:

SMS-2700-FD-xxxx-UD2

DRAFT

57

Feature Description

Appendix

Premium Messaging
No. of
Messages
(Million)

Classic Messaging

RAM
(Inflight
Messages)

Disk Storage
(Messages/
Day)

RAM
(Inflight
Messages)

Disk Storage
(Messages/Day)

0.05

670MB

29GB

355MB

21GB

0.1

806MB

29GB

413MB

21GB

0.2

1064MB

29GB

530MB

21GB

0.5

1838MB

29GB

882MB

21GB

3129MB

29GB

1467MB

21GB

n/a

29GB

n/a

21GB

n/a

34GB

n/a

26GB

n/a

39GB

n/a

26GB

n/a

39GB

n/a

26GB

Table C-4: Estimated Disk and RAM Sizing

Note:

The number of In-flight Messages column represents the amount of memory required
to handle the specified number of messages pending delivery at any one time.

Note:

The number of Messages per Day column represents the amount of disk storage that
is required to store the specified number of messages in any one 24-hour period.

Note:

Thus, as an example, a deployment that is sized to use Classic Messaging to support 4


million messages per day with 100,000 in-flight at any time would require 413Mbytes
of memory and 26Gbytes of memory.

SMS-2700-FD-xxxx-UD2

DRAFT

58

Glossary

Feature Description

Glossary
A
ACK
API
C
CCITT

CDMA
CDR
CMT
CPT
CUG
Customer

D
DBMS
Destination Number
Display area
DL

DTMF
E
ESME
Event Display

F
FSM
FTAM
FTP
G
G/IW MSC
GTT
GSM

Acknowledgement - a positive Report from a SME.


Application Programming Interface

International Consultative Committee for Telephone and Telegraph. This is a


standards organisation affiliated with the International Telecommunication
Union.
Call Detail Record. A CDR contains necessary information to bill customers for
message transactions.
Cellular Messaging Teleservice
Cellular Paging Teleservice
Closed User Group. Members of a CUG can only send messages to other
subscribers within the group.
A Telepath SMSC subscriber who can view, send, accept, replace, and delete
Short Messages through TPCUST and TPSMT.

Database Management System


The MSISDN of the message recipient.
The middle area of a screen which displays the command forms and command
output.
Distribution List. An alias which can be used to send one message to a number
of customer names, rather than having to send the message to each customer
name individually. This is a List Id and not an MSISDN.
Dial Tone

External Short Message Entity


The Event Display is a user interface which provides an interactive view of the
latest events being generated.

Forward Short Message


File Transfer and Access Management
File Transfer Protocol. FTP is a program for transferring files on X.25 lines.

Gateway/Interworking Mobile Switching Centre


Global Title Translation. Used for routing of messages.
Group Special Mobile/Global System for Mobile Communications. A set of
standards for digital mobile communications developed by European
Telecommunications Standards Institute (ETSI).

SMS-2700-FD-xxxx-UD2

DRAFT

59

Feature Description

Guest

Glossary

A guest user who can access TPSMT and TPCUST to send messages to
Telepath SMSC customers.

H
HLR

Home Location Register

I
IVR

Integrated Voice Response

J
JSAT
M
MAP
Message status area

MT
MTP
MT-SM
MWD

Mobile Application Part.


The lower area of the screen which displays status messages pertaining to menu
selections, commands or processes.
Mobile Originated
Mobile Originated Short Message
Mobile Station. An MS can be a source or sink of Short Messages.
Mobile Switching Centre. This is the interface between the Base Station
Subsystem and the fixed network. It performs the necessary functions in order
to handle the calls to and from the Mobile Stations.
Mobile Station Integrated Services Digital Network. The Mobile Station
international ISDN number identifies an MS as ISDN terminal. It is used to
route calls from any international telecommunications network (PSTN, ISDN,
GSM-PLMN) to the MS.
Mobile Terminated
Message Transfer Part
Mobile Terminated Short Message
Message Waiting Data

N
Network Operator
NMS
NPI

A company which provides SMSC services.


Network Management System
Numbering Plan Indicator

MO
MO-SM
MS
MSC

MSISDN

O
OA&M
OCL
OATS
OPTS
P
PC
PDU
PLMN
PSTN

Operations, Administration & Maintenance


Octel Command Language
Over-The-Air Activation Teleservice
Over-The-Air Programming Teleservice
Point Code. Used for routing of messages.
Protocol Data Unit
Public Land Mobile Network
Public Switched Telephone Network

SMS-2700-FD-xxxx-UD2

DRAFT

60

Feature Description

RDBMS
S
SAR
SCCP
SGSN
SINAP
SM
SMS
Short Messaging
SME

SC
SMDPP
SMSC

SME
SMPPP
SMT
Source Number
SPC
SQL
SRI
SSN
SS7
State
Status
Submit
T
TAP
TCAP
TCP/IP
Text Box
TLV
TON/NPI
TNPP

Glossary

Relational Database Management System

Segmentation and Reassembly


Signalling Connection Control Part
Stratus Intelligent Network Applications Platform
Short Message
Short Message Service
A service defined within GSM for sending and receiving Short Messages to/
from a Mobile Station.
Short Messaging Entity. Any source or sink of Short Messages. The entity is
either inside or outside the Public Land Mobile Network (PLMN) and can send
and/or receive Short Messages, for example, Mobile Stations, Pagers, DTMF
telephones.
Service Centre.
Short Message Delivery Point to Point
Short Message Service Centre. Logica Aldiscons Telepath SMSC product. The
SMSC system encompasses all of the software and hardware required to send
Short Messages (SMs) from one Short Message Entity (SME) to another.
Short Messaging Entity. An entity that can send and/or receive short messages.
Short Message Peer-to-Peer Provisioning
System Manager Terminal
The MSISDN number of the message originator.
Signalling Point Code. Used as the destination address for the routing of
messages.
Structured Query Language. SQL is a comprehensive language for organising,
managing and retrieving data stored by a relational database.
Send Routing Information request.
Sub-System Number
Signalling System No.7. Transports the signalling information to carry out the
call establishment function on a public switched telephone network.
This indicates the state of the message. This can be one of 4 values: For
Delivery, Scheduled, For Redelivery, or Done.
This refers to the status of each message. Status can be one of five values: Sent,
Expired, Deleted, Undelivered, or Invalid.
Process whereby a message is submitted to the SMSC for delivery.

Telocator Alphanumeric Protocol


Transaction Capabilities
Transmission Control Protocol/Internet Protocol
The area in which the Short Message text is entered.
Tag-Length-Value. A term that defines the format of a parameter or field in a
record or PDU.
Type of Number/Numbering Plan Indicator. This makes up part of the MSISDN
number.
Telocator Network Peer-to-Peer

SMS-2700-FD-xxxx-UD2

DRAFT

61

Glossary

TPSMT
Type

U
UCP
UDP
V
VMA

VMS

62

Feature Description

Telepath SMSC System Manager Terminal. The application that supports


system administration and maintenance.
This indicates the message type. This can be one of three values: Normal,
Priority, or Scheduled.

Universal Computer Protocol


Universal Datagram Protocol

Voice Mail Alert. An indication that voice mail messages are present in voice
mailbox. Short Message may indicate voice mail present or may also give an
indication of how many messages.
Voice Mail System

DRAFT

SMS-2700-FD-xxxx-UD2

Vous aimerez peut-être aussi