Service Management Application System (SMAS)

Chapter 6

OBJECTIVES:
Upon completion of this chapter the student will be able to:

• Define the SCE and SME

• Describe the role and purpose of the SCE
• Describe the service creation process
• Identify and define Ericsson’s SCE tool, SMAS
• Describe basic TMOS concepts
• Describe how SMAS is used in service creation
• Describe the role and purpose of the SME
• Identify and define Ericsson’s SME tool, SMAS
• Describe how SMAS is used in service management
GSM Mobile IN Overview

t io
e n na
lly
t
In

Bl n
a
k

EN/LZT 123 3974 R3B

 6 Service Management Application System (SMAS)

6 Service Management Application

System (SMAS)
Table of Contents

Topic Page

INTRODUCTION ................................................................................115
SERVICE CREATION................................................................................................ 116
SERVICE DEPLOYMENT.......................................................................................... 117
SERVICE PROVISIONING ........................................................................................ 117
SERVICE MONITORING ........................................................................................... 117
SERVICE TROUBLE SHOOTING ............................................................................. 117
NETWORK TRAFFIC MANAGEMENT...................................................................... 118
GENERIC SERVICE ADAPTER ................................................................................ 118
CONTROL TYPE COLLECTIONS............................................................................. 119

SERVICE CREATION ........................................................................120

SERVICE SCRIPTS................................................................................................... 121
SMAS FUNCTIONS ................................................................................................... 122

A SERVICE EXAMPLE......................................................................130
CREATION OF SERVICE AND SUBSCRIPTION ..................................................... 130
EXECUTION OF SERVICE ....................................................................................... 132

EN/LZT 123 3974 R3B –i–

GSM Mobile IN Overview

t io
e n na
lly
t
In

Bl n
a
k

– ii – EN/LZT 123 3974 R3B

 6 Service Management Application System (SMAS)

INTRODUCTION
This document describes existing Service Management
Application System (SMAS) applications for service creation,
management (deployment, provisioning and monitoring), as well
as service network traffic management.

SMAS is an operation system in the Ericsson

Telecommunication Management and Operations Support
(TMOS ™) family, and is the key to a successful utilization of
the Intelligent Network (IN). SMAS is the tool for both Service
Creation (SCE) and Service Management (SMS).

It is a service independent support system for Intelligent

Networks (INs) and the Service Script Interpreter (SSI) located
in a Service Control Point (SCP) or a Service Switching Control
Point (SSCP).

SMAS

INM
TCP/IP
x25

MTP/x25
STOC

SS7
SDP
SCP

Figure 6-1 SMAS Node

SMAS also handles communication towards the Service Data

Point (SDP). The Ericsson SDP is a database storage and
retrieval system developed as an integral part of the Intelligent
Network (IN) product. This increases the overall capacity of an
IN network.

The purpose of SMAS is to provide a powerful, user friendly

and centralized interface to applications within the IN network.

EN/LZT 123 3974 R3B – 115 –

GSM Mobile IN Overview

By using the SMAS system it is possible for the operator to

create Service Scripts, that is, network services, and the
corresponding support as menus, forms, tailored reports, etc.

It is also possible to purchase Service Scripts and support in the

form of Service Packages from Ericsson.

Since SMAS is a product within the TMOS family, it has the

advantages and flexibility of the following characteristics:

• UNIX based
• Object oriented design and implementation (C++)
• Relational database
• Modern user interface (OpenLook, Java etc.)
• Client-server architecture
• Scaleable and extensible configuration
• Using TMOS platform software (TPF)

Generic
Service Adapter (GSA)

Service Network
Service Service Service Service
Trouble Traffic
Creation Deployment Provisioning Monitoring
Shooting Management

Service IMS SCE Monitoring

Library DB DB Data

TMOS Platform

Figure 6-2 SMAS

Within the SMAS system there are the following major

applications:

SERVICE CREATION
Service creation provides facilities to design services for the
Intelligent Network (IN). This includes design of the service
logic and definition of service data. The tools for this have a full

– 116 – EN/LZT 123 3974 R3B

 6 Service Management Application System (SMAS)

graphical user interface where the service logic is composed by

selecting appropriate functionality, called Service Independent
building Blocks (SIBs) represented by an icon from a palette,
and combining these icons together with point and click
techniques. There is a library function where services with
different versions can be stored. Functionality is provided to
validate the logic by checking that there are no loops and no
loose ends.

The service transfer function allows complete services to be

created in one SMAS system, called the Service Creation
Environment (SCE), and to be transferred to and deployed by
another SMAS systems.

SERVICE DEPLOYMENT
Service deployment provides functionality for installation of the
services and for modification of already installed services in the
SCP either immediately or at a later occasion by scheduling. The
service transfer function enables importing services created in
another SMAS system. There is also service version handling
for upgrading of services with a minimum downtime.

SERVICE PROVISIONING
Service provisioning enables operators to provide services to
subscribers. It includes functions to administer the service
subscribers and their service subscriptions. Subscribers can
control their own service by means of the subscriber control
functionality. The Service Provisioning also supports
administration groups that make it possible for end users to
administrate their own subscriptions.

SERVICE MONITORING
Service monitoring provides functions for managing and
monitoring installed services and subscriptions. It includes
facilities for collecting information from the SCPs such as
statistics and call reports.

SERVICE TROUBLE SHOOTING

Service trouble shooting provides functions for managing and
testing installed services and subscriptions in the network. Tools
for comparing and checking information in the SMAS database
with the corresponding data in the SCP/SDP are also available.

EN/LZT 123 3974 R3B – 117 –

GSM Mobile IN Overview

This tool also handles external mated SDP audits, to compare

the data stored in the database located in the SDP node for a
mate pair.

NETWORK TRAFFIC MANAGEMENT

In order to protect SCPs against service traffic overload, SMAS
supports the administration and manual activation of congestion
control in the network. Facilities are provided to limit the
destination dependent call intensity towards a specific number or
range of numbers.

GENERIC SERVICE ADAPTER

The Generic Service Adapter (GSA) provides support for
developing user interfaces, batch handling interfaces, and
communication interfaces for IN Service Provisioning. Via these
interfaces, administration of the service subscribers and their
service subscriptions are possible. The GSA offers a generic
service view to the user that hides the IN specific details of a
service.

GSA Client
Parameter
View
GSA server
Configuration Files
Script
View

SMAS

SDP
SCF

Figure 6-3

– 118 – EN/LZT 123 3974 R3B

 6 Service Management Application System (SMAS)

Network
Network Corporate
Corporate Personal
Personal
Service
Service Service
Service Service
Service
Management
Management Management
Management Management
Management

External PC Web
System Windows Server

GSA server

Figure 6-4 GSA Client / Server structure

CONTROL TYPE COLLECTIONS

A control type is a function in the SSI. The SSI contains a
number of different control types that can be used to define
Logic Modules (LMs) which can be combined to realize the
logic function of a service. A combination of LMs form a
Service Script Logic (SSL). One or more SSLs form an SL.

Most of the control type functions involve processing of data,

e.g. number analysis. For these control types, Data Modules
(DMs) with service data are connected to the LMs in the SSL
when a service is defined.

SMAS provides graphical user interfaces for creating SSLs by

defining LMs and connecting these in the sequence in which
they will be activated. Graphical user interfaces are provided for
defining and handling DMs.

Certain control types allow specific data parameters to be

changed by customer control via Dual Tone MultiFrequency
(DTMF) telephones.

SMAS supports the Control Type Collection CS-1 which covers

all CS-1-compatible Control Types developed for mobile
intelligent networks for MIN Platform R7 (CAMEL).

EN/LZT 123 3974 R3B – 119 –

GSM Mobile IN Overview

SERVICE CREATION
The design and installation of IN services is a multi-step process
comprised of several building blocks. The smallest building
block in the process is the Control Type (CT). The CT is a
predefined function designed to perform one or more tasks.
Each CT is graphically represented via an icon. Some examples
are depicted in Figure 6-5.

INFO
TIME

S M T W T F S
D
D
D
D
D

DAYINW

RESPONS

Figure 6-5 Control Type Icons

As noted earlier, depending on the system you are working on

and what part of the world you are in, you may encounter
different collections of Control Types. These collections
provide the designer with a list of all the CTs available on their
system. New Control Types are always being developed based
on customer’s needs or standards.

When a Control Type is selected and activated, it is then called a

Logic Module (LM). All LMs have one input and one or more
outputs. By stringing one or more LMs in a logical succession,
subroutines, also known as SSLs, are designed to perform
specified tasks (see Figure 6-6).

– 120 – EN/LZT 123 3974 R3B

 6 Service Management Application System (SMAS)

LM

LM

LM LM

LM LM

Figure 6-6 A Script

One or several of these subroutines are then strung in succession

to complete a service. Almost all the Logic Modules (LMs)
within a service require some sort of data definition for their
operation; therefore, they must be connected to their
corresponding Data Modules (DMs). The data determines the
performance of the Logic Module (LM) in the script.

SERVICE SCRIPTS
The same kind of service scripts as in the SCF are in the SMAS:
System Scripts, Group Scripts and Subscriber Scripts.

System Scripts
These scripts are shared by everyone that queries the IN. When
a query is initiated in the Intelligent Network (IN), the first script
that is encountered is the Access Script. This script may analyze
the A-number, to ensure it is a valid customer, or the B-number,
to ensure the number being called in fact has an IN service that
must be used before routing the call, etc.

The key to the Access Script is to understand that it performs

some kind of initial analysis to identify the validity of the query
and, if valid, routes the query accordingly.

The Error Script is another System Script that is shared by

everyone. This script is automatically activated when a fault
occurs during service execution or it may be accessed on
purpose by any script during execution to indicate an error.

EN/LZT 123 3974 R3B – 121 –

GSM Mobile IN Overview

Group Scripts
A Group Script is one that may be attached to many customers.
The idea behind this is that once a service is created and
installed in the NE, this service is then sold to as many
customers as possible. Most of the scripts we deal with in the
Intelligent Network (IN) are Group Scripts.

Subscriber Scripts
This kind of script is a service created for one and only one
customer. This service may be attached to only one phone
number. A unique script is created for each subscriber. In this
subscriber script it is possible to specify the data modules
according to the subscriber’s requests.

A limitation of this type of script should be apparent to you: if

more than one customer wants the same service, an identical
copy of the service must be created for each customer. With a
Group Script many customers may share the same service.

SMAS FUNCTIONS
The SMAS interfaces and the design and administration
procedures are described next. A sample of how the menu
options may look is given in Figure 6-7. Please note, however,
that the order of the menu options may change from one site to
another and between SMAS versions.

– 122 – EN/LZT 123 3974 R3B

 6 Service Management Application System (SMAS)

Figure 6-7 SMAS Menu

Service Logic Definition

The Service Logic Definition can be divided into the three main
functions discussed as follows.

Service Script Logic Design

A Service Script Logic is designed according to the following
procedures:

1. The Control Types (CTs), that is, the icons for the Logic
Modules (LMs), are selected and copied from the CT palette
into the design window.
2. The parameters, such as the number of outlets or the starting
Control Type, are defined for each of the CTs and the CTs
are then connected to each other.
3. The validated SSL is finally stored in a library in SMAS.

EN/LZT 123 3974 R3B – 123 –

GSM Mobile IN Overview

Service Logic Design

The Service Logic is created by selecting one or more
appropriate SSLs from the library. The designer must mark the
SSL as either a group or a subscriber specific script. If the
customer is to be able to update the service data, the SSLs must
be marked as customer controlled scripts. In the Service Logic
Design it is also possible to edit, view, or delete existing Service
Logic’s.

Service Logic Transfer

By means of the Service Logic Transfer function, it is possible
to store any part of, or an entire service on tape or load it from
tape to the SMAS database. The required information is
retrieved from the relational database, placed in a UNIX file and
the file then copied to magnetic media.

– 124 – EN/LZT 123 3974 R3B

 6 Service Management Application System (SMAS)

Red Line Tool

Red Line Tool is a graphical user interface to debug the Service
Logic.

Figure 6-8

Service Administration
The Service Administration (SA) is divided into three main
functions as described below.

Service Definition and Installation

A service consists of two parts: the logic part (Service Logic)
and the data part (Service Data).

A service is defined in SMAS by selecting a Service Logic from

the Service Logic library and then adding data to all the LMs in
the scripts. The data can be local to the SSL, local to the service
(that is, non-customer-specific), or global.

EN/LZT 123 3974 R3B – 125 –

GSM Mobile IN Overview

Once the service is designed and validated it must be installed in

the Network Element (NE). It can either be installed
immediately or scheduled for a future installation.

Global Data Definition

A Global Data Module (GDM) is a data file that can be used by
many services. A GDM contains data associated with a
particular Control Type, and can thus be connected to the
particular Control Type in different scripts.

As an example, a GDM for the Control Type DATE can be

defined to contain all national holidays in a year. The GDM can
then be connected to a DATE Control Type used in any service,
as long as the service trying to use the GDM and the GDM itself
are both installed in the same SCP.

Installed Service Modification

This function enables the operator to change data directly in the
SCP. The function makes data structures visible that are
normally hidden by other applications in the SCP, such as the
Service Administrators (SAs), the Service Customer, and
OP/NOP areas.

With this function, it is possible to modify data in an installed

service/subscription, reinstall a service, or activate/deactivate a
service. The function also enables installation or removal of an
SSL independent of a service or subscription. Access and Error
scripts are installed in this way.

Subscriber Data Administration

The Subscriber Data Administration application concerns all
subscriber and subscription information. It is divided in two
parts:

• Subscriber Administration handles subscriber identification

data.
• Subscription Administration handles subscription
identification data, the definition of customer-specific data,
and the installation of the subscription.

– 126 – EN/LZT 123 3974 R3B

 6 Service Management Application System (SMAS)

Subscriber Administration
In Subscriber Administration, the operator can define new
subscribers, delete subscribers, and modify the data of existing
subscribers. The parameters that can be defined for a subscriber
are:

• The subscriber’s name.

• UNIX ID (if the subscriber has access to customer control
data)
• The terminal type (if the subscriber has access to customer
control data)
• Information text concerning the subscriber (address, phone
number, etc.)

Subscription Administration
With the Subscription Administration function (see Figure 6-9),
an operator can create new subscriptions by connecting the
subscriber identification data defined in Subscriber
Administration with a service.

The operator can enter customer-specific data. Finally, the

subscription can be installed in the SCP. When the subscription
is installed, the access script is updated with the new valid
customer.

Service Monitoring
Service Monitoring provides a number of functions for
managing and monitoring services and subscriptions installed in
the SCP. It also includes functions for collecting information
such as statistics and call report information from the SCPs.

Statistics
The statistics function provides the operator with a tool for
generating statistics on the usage of a service or subscription.
The activity has two parts: collecting statistics and reporting
statistics. Statistics are collected on call attempts and
termination results, e.g. on congestion, B-answer, B-busy, etc.
Once statistics are collected, they may be viewed using a
spreadsheet application provided with the system.

EN/LZT 123 3974 R3B – 127 –

GSM Mobile IN Overview

Call Reports
The Call Report function is used to generate reports of IN call
results, such as set-up, query, conversation, response, and
terminating data in the SCP. Like statistics, the activity can be
divided into a collecting and a reporting phase.

Audits
The Audit function is used to compare information within given
databases, e.g. the information in the SMAS database may be
compared with the information in the SCP database for
consistency. The function can also be used to compare
information in mated pairs of SCPs.

The audit function should be used any time a discrepancy

between SMAS and SCP data is suspected, as in the case of
some kind of failure. It may also be used in normal
maintenance. An audit process is executed as a background
process. Each audit produces a discrepancy report.

Troubleshooting
Troubleshooting includes three functions: sending test queries,
blocking/deblocking services or subscriptions, and manually
setting outlets in Logic Modules (LMs).

Test query is a tool to simulate the SSF-SCF interface. It is used

for testing services after they are installed and for
troubleshooting. Blocking/deblocking is a tool to manually
block/deblock a service or subscription. Blocking a service or a
subscription means taking it out of traffic. When a service is
blocked, all subscriptions to that service are automatically
blocked.

Manual outlet setting is a tool that allows the operator to

determine the outlet of the Logic Module (LM), regardless of
any attached Data Module (DM).

Running Counters
The Running Counter function allows the operator to view or
resets a running counter in an SCP. A running counter is a
counter specific to some of the Control Types that are updated in
real time in the SCP during service interpretation. The value of
these counters is not sent to SMAS and the SMAS database is
not updated with this information. This function provides the

– 128 – EN/LZT 123 3974 R3B

 6 Service Management Application System (SMAS)

possibility to directly access the SCP, to ask for the current

value of a counter, or to reset a counter.

Exception Reports
An Exception Report is a call report that includes a binary error
code. It is sent to SMAS in the same way as a call report, but
may be routed to a specific output device, i.e. to a printer.

Network Traffic Management

The Network Traffic Management application is used to protect
the SCP against service traffic overload. This congestion
control can be used to limit the destination-dependent call
intensity for a specific number or a range of numbers, e.g. all
Freephone numbers.

EN/LZT 123 3974 R3B – 129 –

GSM Mobile IN Overview

A SERVICE EXAMPLE
To understand the principles of how to design, implement, and
execute a service, a simple example is described next.

CREATION OF SERVICE AND SUBSCRIPTION

We want to create a service that, when a call is received Monday
through Friday between 8 AM and 5 PM, routes the call to a
work number, but otherwise routes the call to a home number.
The following flowchart is designed to perform such analysis.

B-Number

Analyze Sa - So
Mon-Fri
Day of C Number 2
Week

Analyze 1700-0800
Time of C Number 2
Day

0800-1700

C Number 1
2

Figure 6-9 Service to be created

Since this service is going to be offered to many customers, we

create it as a Group Script. The designed service is shown in
Figure 6-10 on the facing page.

The DAYINW LM compares the present day of the week to the

instructions in its data module table. For its data we will specify
to take outlet 0 if the call is received between Monday and
Friday or outlet 1 if received any other day.

The TIME LM compares the present time with the instructions

in its data module table. The instructions indicate to take outlet

– 130 – EN/LZT 123 3974 R3B

 6 Service Management Application System (SMAS)

0 if the call is received between 8 AM and 5 PM, otherwise to

take outlet 1.

S M T W T F S TIME INFO
D 0
D
D
D
1
RESPONS
D
DAYINW
INFO

Figure 6-10 Control Types for the Service

The INFO LM is used, among other things, to pass phone

numbers. On the top INFO icon in Figure 6-10, we specify the
work phone and on the bottom one the home phone. These
numbers, of course, are different for each customer so this is a
good example of Customer Data in action.

The RESPONS LM initiates the transfer of the selected phone

number to the SSF, which in turn handles the switching of the
call.

Once the service is created, it is installed in the SCP, we

advertise the service, and one of our customers subscribes to it.
The following information about the customer is used in
creating the subscription:

• Name = John Doe

• B# = 555-1111
• Work # = 0319983619 (C - Number 1)
• Home # = 0313016209 (C - Number 2)
• Mobile # = 0793345403 (C - Number 3)
With this in mind the subscription is created and installed.

EN/LZT 123 3974 R3B – 131 –

GSM Mobile IN Overview

EXECUTION OF SERVICE
We now have a new service defined, installed, and available.
And we have subscription information for our first service
subscriber in the database and activated.

Figure 6-11 and the following text describes what happens in

our network when the service is accessed.

Access Group Switch

3 4
MIN
B-Subscriber
SCF
HLR
2 5

SSF
6
VLR MSC C-Number GMSC

1 C-Subscriber

A-Subscriber

Figure 6-11 Service Execution

1. On Tuesday at 12:45 PM someone calls 555-1111, the

message is routed to the SSP.
2. The SSP recognizes this number as one that is attached to an
IN service; therefore, the message is routed to the SCP in the
network.
3. At the SCP, the first script that is encountered is the Access
Script. The Access Script checks to make sure that the B-
number is indeed a valid number, which it is, and then routes
the call to the Group Service in question.

– 132 – EN/LZT 123 3974 R3B

 6 Service Management Application System (SMAS)

4. The Group Service runs, using the customer’s specific data,

and the result of the analysis is passing the number 555-
1111.
5. This number is sent back to the SSP...
6. ...which in turn establishes the connection and the call goes
through.

EN/LZT 123 3974 R3B – 133 –

GSM Mobile IN Overview

t io
e n na
lly
t
In

Bl n
a
k

– 134 – EN/LZT 123 3974 R3B