Intelligent Network Management Interface

Appendix D
GSM Mobile IN Overview

t io
e n na
lly
t
In

Bl n
a
k

EN/LZT 123 3974 R3B

 D Intelligent Network Management Interface

D Intelligent Network Management

Interface
Table of Contents

Topic Page

INTRODUCTION ................................................................................173

INM CONCEPTS ................................................................................174

DEFINITIONS ............................................................................................................ 174
FUNCTION................................................................................................................. 175

HARDWARE IN THE IOG ..................................................................178

DESCRIPTION OF THE OPERATIONS.................................................................... 178
COMMANDS.............................................................................................................. 181

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

 D Intelligent Network Management Interface

INTRODUCTION
The Intelligent Networks Management Interface function gives a
fast interface between the SCF and Service Management
Application System (SMAS) for the purpose of handling
Intelligent Network (IN) service scripts. It also supports transfer
of reports from the SCF to SMAS. SMAS designs service logic,
controls logic implementation through the network, and
manages the network operation. It also acts as an interface for
subscriber service management.

EN/LZT 123 3974 R3B – 173 –

GSM Mobile IN Overview

INM CONCEPTS

DEFINITIONS
• CRC : Cyclic Redundancy Check code

• IP : Internet Protocol : the IP provides a connectionless

datagram network layer and allows an application to
communicate transparently across several connected
networks
• MML : Man Machine Language

• TCP : Transmission Control Protocol : provides a

connection-oriented way to move data across the network.
The protocol supports byte oriented transfer of data between
applications and is a reliable end-to-end transport protocol
between processes.
• Change Number : a change number is a reference assigned to
a Data Module (DM) to indicate that Customer Control is
allowed for this DM.
• Operation : an operation is a named task. An operation can
be generated in the SCF or in SMAS. An example of an
operation is: INSTALL DMSEC-list.
• Message : message consists of one or more operations.
Example:
message
INSTALL DMSEC-list
MODIFY SC-list
:
end message

– 174 – EN/LZT 123 3974 R3B

 D Intelligent Network Management Interface

• DM - Data Module : a DM in the SCF consists of one main

part and zero or more subsections (SUB).

Main part

SUB 1

SUB n

The main part and the subsections of a DM contains integers,

strings, numbers, etc. The following MML commands can be
used to affect Data Modules (DMs):

• SSDTI : create a Data Module and assign values to its

main part.
• SSDTC : change values in the main part.
• SSDTC task=ADD : add a new subsection and assign
value(s) to it.
• SSDTC task=CHANGE : change values in a subsection.
• SSDTC task=DELETE : delete a subsection.
• SSDTE : remove the Data Module.

FUNCTION

Intelligent Networks Management Interface

The function Intelligent Networks Management provides a fast
interface between the SCF and SMAS. The interface will use
TCP/IP to transport the data between the SCF and SMAS.

Active Connection between SCF and SMAS

To transfer messages from the SCF to SMAS a so called active
connection needs to be established between the SCF and SMAS.
Commands are used for the connection on the SCF side. Once
the connection is set-up, it will stay open until it is closed by

EN/LZT 123 3974 R3B – 175 –

GSM Mobile IN Overview

command or until SMAS sends an order to close down. When

the close down is completed by SMAS, the SCF will start to
buffer all messages that no longer can be sent to SMAS. The
buffering will continue until the connection is established again.
IOG is used for buffering. The INM interface will support the
transfer of customer control changes, statistical reports and call
reports over the active connection. Up to three active
connections can be initiated. Which connection to use is
specified for the affected Control Type when building the
service script.

Passive Connection between SMAS and SCF

To transfer messages from SMAS to the SCF a so called passive
connection needs to be established. The set-up of the connection
on the SCF side is done by command. Once the connection is
set-up, it will stay open until it is closed by command or until
SMAS sends an order to close down the connection. The INM
interface will support installation, change and removal of
subscriber and service data over the passive connection. Up to
64 passive connections can be initiated.

Error Handling
In case of link failure the connection will be automatically re-
established.

Logging
All INM messages that are received in the SCF can be logged on
the INM log. The INM log function will be turned on/off
automatically when the MML command log is turned on/off.
Customer control changes may also be logged on the INM log if
decided so by the service script.

Buffering
In the case of link failure or SMAS sending a close order on an
active connection, the SCF will buffer the messages to be sent
towards SMAS by writing them to the IOG. When the link is
working correctly again, the SCF will send all the buffered
messages towards SMAS. The buffer mechanism will take care
that SMAS will always receive the messages in the same order
as the SCF has sent them.

– 176 – EN/LZT 123 3974 R3B

 D Intelligent Network Management Interface

Security
It can be specified per passive connection which SMAS is
allowed to connect to it. A 32-bit checksum (CRC-32) is used
for every message to secure the data transfer between the SCF
and SMAS.

EN/LZT 123 3974 R3B – 177 –

GSM Mobile IN Overview

HARDWARE IN THE IOG

A Signaling Terminal Open Communication (STOC) magazine
is used in the AXE. The functions are implemented in the block
OCITS, and allows a CP or RPD application to send and receive
any type of data. The STOC magazine consists of the standard
RPD hardware with the RDEX operation system complemented
with an Ethernet communication board, ETHU.

CP USERS PEIP

APT_TRSP_IF

SADM

STCOM
OCITSU (CP)

OCITSR (RPD)
RPS
SCPCOM COMTEST

COMADM
TCP_API
STADM

TCP_IP/
ENET

DESCRIPTION OF THE OPERATIONS

Install SC-list
Installs one or more Service Customers with all the DM’s. Each
DM is installed completely with main part and subsections. A
change number can also be defined for each DM if needed.

Direction: SMAS-AXE

Error Handling: Executed/Partly executed/Not executed

Modify SC-list
Changes one or more Service Customers. The change can be an
increase of the number of allowed Data Modules (DMs) for the

– 178 – EN/LZT 123 3974 R3B

 D Intelligent Network Management Interface

Service Customer and/or installation of new Customer Data

Modules (DMs). Each DM is installed completely with main
part and subsections. A change number can also be defined for
each DM if needed.

Direction: SMAS-AXE

Error Handling: Executed/Partly executed/Not executed

Install DM-list
Installs one or more Data Modules (DMs). The DMs can be
global, local or customer data modules. Each DM is installed
completely with main part and subsections. A change number
can also be defined for each DM if needed.

Direction: SMAS-AXE, AXE-SMAS

Error Handling: Executed/Partly executed/Not executed

EN/LZT 123 3974 R3B – 179 –

GSM Mobile IN Overview

Remove DM
Removes a Data Module (DM) (including main part and
subsections).

Direction: SMAS-AXE, AXE-SMAS

Error Handling: Executed/Partly executed/Not executed

Install DMSEC-list
Installs one or more subsections in one or more existing DM’s.

Direction: SMAS-AXE, AXE-SMAS

Error Handling: Executed/Partly executed/Not executed

Modify DMSEC-list
Modify DMSEC-list will change values in main part(s) and/or in
subsection(s) of one or more existing DM’s.

Direction: SMAS-AXE, AXE-SMAS

Error Handling: Executed/Partly executed/Not executed

Remove DMSEC-list
Removes one or more subsections from one or more DM’s.

Direction: SMAS-AXE, AXE-SMAS

Error Handling: Executed/Partly executed/Not executed

Report Report-list
Sends a statistical report, call report or error report to SMAS.

Direction: AXE-SMAS

Error Handling: Executed/Not executed

– 180 – EN/LZT 123 3974 R3B

 D Intelligent Network Management Interface

Query
Ask the SCF about it’s current state. The answer will be sent in a
STATUS operation to SMAS with one of the indications: 1idle
2connection still used by the previous operation

Direction: SMAS-AXE

Error Handling: Not applicable

Status
Returns the result of the handled operation to the sender of the
operation. Possible results are:

• Executed
• Partly executed
• Not executed
• TCP/IP handling fault
Direction: SMAS-AXE, AXE-SMAS

Error Handling: Not applicable

COMMANDS
Three commands are available to handle the connection(s)
between the SCF and SMAS.

- A command to initiate a link between the SCF and SMAS.

- A command to end a link between the SCF and SMAS.
- A command to print the link status between the SCF and
SMAS.
Two commands are available to handle the INM logging
function.

- A command to read INM log-files from tape.

- A command to set INM log parameters.

EN/LZT 123 3974 R3B – 181 –

GSM Mobile IN Overview

t io
e n na
lly
t
In

Bl n
a
k

– 182 – EN/LZT 123 3974 R3B