View
253
Download
3
Category
Preview:
Citation preview
7/25/2019 logica smsc
1/62
DRAFT
Telepath SMSC Release 2700
Feature Description
7/25/2019 logica smsc
2/62
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.
7/25/2019 logica smsc
3/62
Feature Description Table of Contents
SMS-2700-FD-xxxx-UD2 DRAFT 3
Table of Contents
References .................................................................................................................................6Preface .......................................................................................................................................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.............................................201.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 .............................................................................261.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
7/25/2019 logica smsc
4/62
4 DRAFT SMS-2700-FD-xxxx-UD2
Table of Contents Feature Description
2.1.3 Extended Message Length ............................................................31
2.1.4 Alert Notification..........................................................................31
2.1.5 User Data Header Encoding (UDH) .............................................31
2.1.6 WAP in ANSI-136 (CMT and GUTS support) ............................32
2.1.7 Subaddress (End to End Security) ................................................322.1.8 WDP/WCMP Gateway Adaption .................................................32
2.1.9 Message Segmentation..................................................................32
2.1.10 Message Reassembly ....................................................................32
2.1.11 Application Port Addressing.........................................................32
2.1.12 HLR Delivery Pending Flag handling ..........................................33
2.1.13 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 .............................................................................363.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.................................................................434.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
7/25/2019 logica smsc
5/62
Feature Description Table of Contents
SMS-2700-FD-xxxx-UD2 DRAFT 5
7.1.2 Minimizing TAP TCP session startup times.................................50
7.2 Sierra Interworking Product...........................................................................51
7.2.1 Support for Latest OCL Version...................................................51
7.2.2 Sierra Configurable text additions .............................................51
7.3 TNPP Interworking Prooduct.........................................................................527.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
7/25/2019 logica smsc
6/62
6 DRAFT SMS-2700-FD-xxxx-UD2
References Feature Description
References
[1] TIA/EIA-136-720 General UDP Transport Service (GUTS), October 7, 1998
[2] TIA/EIA-136-620 Teleservice Segmentation and Reassembly (TSAR), October 7,1998
[3] Telocator Alphanumeric Protocol (TAP), Version 1.8, 4th Feb. 1997, Telocator Per-
sonal Communications Industry Association.
[4] Distributed Management Metrics Module, version 1.0, Feature Description, FLD-
DMMM1.0-0001
7/25/2019 logica smsc
7/62
Feature Description List of Tables
SMS-2700-FD-xxxx-UD2 DRAFT 7
List of Tables
Message Management module commands ..............................................................................15SME 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........................................................................... 56Table C-2: Lucent DNCP Configurations............................................................................... 56
Table C-3: Sun Netra Configurations...................................................................................... 56
Table C-4: Estimated Disk and RAM Sizing.......................................................................... 57
7/25/2019 logica smsc
8/62
8 DRAFT SMS-2700-FD-xxxx-UD2
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
7/25/2019 logica smsc
9/62
Feature Description Preface
SMS-2700-FD-xxxx-UD2 DRAFT 9
Preface
This document provides an overview of Release 2700 of Telepath SMSC. Release 2700 is amajor 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 OperatorsThis 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
7/25/2019 logica smsc
10/62
10 DRAFT SMS-2700-FD-xxxx-UD2
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.
GlossaryThe glossary includes a list of definitions, common acronyms, and terms used in this
document and in related documents.
7/25/2019 logica smsc
11/62
Feature Description Preface
SMS-2700-FD-xxxx-UD2 DRAFT 11
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 draftfeature description for Release 2700. It is subject to change.
It is recommended that you first acquaint yourself with the terms and acronyms defined in theGlossary.
7/25/2019 logica smsc
12/62
12 DRAFT SMS-2700-FD-xxxx-UD2
General (for all Network Operators) Feature Description
1. 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.
Configurability of address length for customer validation
7/25/2019 logica smsc
13/62
Feature Description General (for all Network Operators)
SMS-2700-FD-xxxx-UD2 DRAFT 13
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 inthe 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.
7/25/2019 logica smsc
14/62
14 DRAFT SMS-2700-FD-xxxx-UD2
General (for all Network Operators) Feature Description
1.2 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 onor offTelepath 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].
7/25/2019 logica smsc
15/62
Feature Description General (for all Network Operators)
SMS-2700-FD-xxxx-UD2 DRAFT 15
1.2.1.2 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 onproviding 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
7/25/2019 logica smsc
16/62
16 DRAFT SMS-2700-FD-xxxx-UD2
General (for all Network Operators) Feature Description
1.2.2 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 co-
resident with the core functionality of Telepath SMSC.
Figure 1-1: Distributed Administration and Provisioning Module
DAP Portal
SMS Data
Store
DAP Server
Telepath SMSC
tpevent
DAP PortalDAP Portal
..........
7/25/2019 logica smsc
17/62
Feature Description General (for all Network Operators)
SMS-2700-FD-xxxx-UD2 DRAFT 17
1.2.2.2 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
7/25/2019 logica smsc
18/62
18 DRAFT SMS-2700-FD-xxxx-UD2
General (for all Network Operators) Feature Description
1.2.3 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
7/25/2019 logica smsc
19/62
7/25/2019 logica smsc
20/62
7/25/2019 logica smsc
21/62
Feature Description General (for all Network Operators)
SMS-2700-FD-xxxx-UD2 DRAFT 21
1.3 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 theplatform.
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.
Figure 1-2: Multiple SNMP Managers
Benefits:
Configuration of the SNMP Trap destination allows for a focussed response to specific
system management events.
Telepath SMSC
(tpsa)Requests to
raise TRAPs
HP-UX master agent
TRAPs to multiple SNMP Manager platforms
tpevent
GET/SETRequests TRAPs
snmpd.conf
PlatformSNMP Subagent
7/25/2019 logica smsc
22/62
7/25/2019 logica smsc
23/62
7/25/2019 logica smsc
24/62
24 DRAFT SMS-2700-FD-xxxx-UD2
General (for all Network Operators) Feature Description
1.4.1 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 atwhich 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 pre-
allocated 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.
Reply Path
7/25/2019 logica smsc
25/62
Feature Description General (for all Network Operators)
SMS-2700-FD-xxxx-UD2 DRAFT 25
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 per-
interface 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.
7/25/2019 logica smsc
26/62
7/25/2019 logica smsc
27/62
7/25/2019 logica smsc
28/62
7/25/2019 logica smsc
29/62
7/25/2019 logica smsc
30/62
7/25/2019 logica smsc
31/62
Feature Description Wireless Application Protocol (WAP)
SMS-2700-FD-xxxx-UD2 DRAFT 31
2.1.1 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 forwardmechanism.
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 re-
entered 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.
7/25/2019 logica smsc
32/62
32 DRAFT SMS-2700-FD-xxxx-UD2
Wireless Application Protocol (WAP) Feature Description
2.1.6 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.
7/25/2019 logica smsc
33/62
7/25/2019 logica smsc
34/62
7/25/2019 logica smsc
35/62
Feature Description GSM Network Operators
SMS-2700-FD-xxxx-UD2 DRAFT 35
3.2 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:
Table 3-2: Transfer Layer PDUs in Telepath SMSC Release 2700
Support of User Data Header and Information Elements has already been offered from Release2600 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.
PDU Purpose
SMS-DELIVER-REPORT used to convey a failure cause as well as a positive or anegative acknowledgement to an SMS-DELIVER or SMS-STATUS REPORT
SMS-SUBMIT-REPORT used to convey a failure cause as well as a positive or anegative acknowledgement to an SMS-SUBMIT or SMS-COMMAND
SMS-COMMAND used by an MS to request operations on short messagespreviously submitted: enquiry to obtain status report(s),status report request cancellation, message deletion, statusreport request
7/25/2019 logica smsc
36/62
7/25/2019 logica smsc
37/62
7/25/2019 logica smsc
38/62
38 DRAFT SMS-2700-FD-xxxx-UD2
GSM Network Operators Feature Description
3.3.2 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 networkidentity 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.
7/25/2019 logica smsc
39/62
7/25/2019 logica smsc
40/62
7/25/2019 logica smsc
41/62
7/25/2019 logica smsc
42/62
7/25/2019 logica smsc
43/62
Feature Description ANSI-41 Network Operators
SMS-2700-FD-xxxx-UD2 DRAFT 43
4.2 General ANSI-41 Features
4.2.1 Removal of MO screening
In Release 2600 the TDMA and CDMA Mobile Network Products screened the DestinationAddress 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 thatthe relevant Mobile Network Product has bound with.
In Release 2700 the following elements are now accepted in the SMDPP Invoke parametersSMS_OriginalDestinationAddress, SMS_OrigAddress and SMS_OrigOrigAddress for aMobile Originated Message:
4.2.2 IMSI-based Addressing
Release 2700 provides support for IMSI based addressing of ANSI-41 MAP Message Opera-tions through the introduction of the MSID (Mobile Station Identity). The MSID can either bean 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 than10 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.
Element Value Value Meaning
Type of Digits IgnoredNature of Number 0
1NationalInternational
Numbering Plan 023714
UnknownTelephony Numbering (E.164)Data Numbering (X.121)Private Numbering PlanInternet Protocol (IP)
Encoding 13
BCDOctet String
7/25/2019 logica smsc
44/62
7/25/2019 logica smsc
45/62
7/25/2019 logica smsc
46/62
7/25/2019 logica smsc
47/62
7/25/2019 logica smsc
48/62
7/25/2019 logica smsc
49/62
7/25/2019 logica smsc
50/62
7/25/2019 logica smsc
51/62
Feature Description Interworking Products
SMS-2700-FD-xxxx-UD2 DRAFT 51
7.2 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 CommandLanguage (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. Thecurrently 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 notificationwill 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.
7/25/2019 logica smsc
52/62
7/25/2019 logica smsc
53/62
7/25/2019 logica smsc
54/62
7/25/2019 logica smsc
55/62
7/25/2019 logica smsc
56/62
7/25/2019 logica smsc
57/62
7/25/2019 logica smsc
58/62
SMS-2700-FD-xxxx-UD2 DRAFT 58
Feature Description Appendix
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.
Premium Messaging Classic Messaging
No. ofMessages
(Million)
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
1 3129MB 29GB 1467MB 21GB
2 n/a 29GB n/a 21GB
3 n/a 34GB n/a 26GB
4 n/a 39GB n/a 26GB
5 n/a 39GB n/a 26GB
7/25/2019 logica smsc
59/62
7/25/2019 logica smsc
60/62
7/25/2019 logica smsc
61/62
7/25/2019 logica smsc
62/62
Recommended