Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

Administration of the SS7 Network in

EWSD Powernode / hiQ9200

Contents
1 Introduction: SSNC as the Control of the SS7 Signaling Network 3
1.1 SSNC in EWSD 4
1.2 SS7 Functions within the SSNC 6
1.3 SS7 Message Flows through an EWSD Powernode 8
2 Administration of the MTP Level 1 in SSNC and EWSD: The Signaling
Data Link 13
2.1 Overview: Types of Singling Data Links 14
2.2 Creation of Narrow Band Signaling Links Connected via EWSD 16
2.3 Creation of Narrow Band Signaling Links Directly Connected to a LIC 30
3 Administration of MTP Level 3 Objects 33
3.1 Overview of MTP Level 3 Objects 34
3.2 Own Signaling Point Code 36
3.3 Signaling Destination Point 42
3.4 Signaling Link Set 46
3.5 Signaling Routes 50
3.6 Signaling Links 52
3.7 Comparison of the Tasks for MTP Level 3 Administration in SSNC and
CCNC 54
4 Administration of the User Parts in the CP / SSNC 57
4.1 Overview C7User 58
4.2 Administration of the Trunk Related UPs in the CP 60
4.3 Administration of the SCCP and its Application Parts in the SSNC 62
5 Exercise 73

SN2073EU01SN_0001
1
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

6 Solutions 91

2 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

1 Introduction: SSNC as the Control of the

SS7 Signaling Network

SN2073EU01SN_0001
3
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

1.1 SSNC in EWSD

To control the SS7 signaling system, the Signaling System Network Controller
(SSNC) is used in EWSD Powernode. It replaces the Common Channel Network
Controller (CCNC) used in the EWSD Classic.
The SSNC provides following functions:
l all protocol functions of the message transfer part (MTP)
l most parts of the signaling connection control part (SCCP)
l parts of the operation and maintenance application part (OMAP).
The open architecture of the SSNC is based on Solution O.N.E (optimized network
evolution) technology, i.e. message transfer within the SSNC is based on ATM.
Connection to the CP113C is via the CP processor AMP.
The signaling channels are supplied by means of PCM30/24 via LTGs or directly by
the network.
Communication with users in the LTGs is provided directly via high-speed interfaces
over the MBD.
The SSNC has its own OAM platform and is administered by the NetM. The NetM is
connected via an Ethernet interface to the SSNC, the OAM Tasks are based on the
Q3 protocol transmitted via TCP/IP. It is also possible to use the SSNC as an transfer
point for the MML communication between the NetM and the CP113.
Thanks to its own OAM platform, the SSNC can also be used as a standalone
network element. It is then called a hiS700 and works without any further EWSD
equipment as a stand alone Signaling Transfer Point SA-STP and may additionally
perform the so called Signaling Relay Point SRP functions (global title translation for
non user channel related SS7 SCCP messages).

TIP
The connection of high speed signaling links (2Mb/s), directly connected to the
SSNC, is also possible but will not be discussed in this course.

4 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

EWSD Powernode Configuration

PCM30 with LTG

Trunks and
SS7 Links
LTG

PCM30 with PCM30 SN B

SS7 Links only with SS7
Links only

NetM
SSNC
207Mb/s
MB D

207Mb/s

AMPC IOP:MB
CP

Fig. 1

SN2073EU01SN_0001
5
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

1.2 SS7 Functions within the SSNC

Signaling System SS7 is divided into two main parts so that it can be adapted
optimally to the diverse requirements of its various situations it is used: the message
transfer part MTP and the user parts UP. The SSNC implements the functions of the
message transfer part MTP and parts of the SCCP (SCCP global title translation and
SCCP management).
Message Transfer Part
The message transfer part (MTP) is used in SS7 by all user parts as a transport
system for message exchange. Messages to be transferred from one user part to
another are given to the message transfer part which ensures that the messages
reach the addressed user part in the correct order, without information loss,
duplication or sequence alteration and without any bit errors.
Functional levels of the MTP are:
l Level 1
defines the physical, electrical and functional characteristics of a signaling data link
and the access units. Level 1 represents the bearer for a signaling link.
In a digital network, 64-kbit/s circuit switched channels are normally used as signa-
ling data links.
l Level 2
defines the functions and procedures for a correct exchange of user messages via
a signaling link. The following tasks must be carried out in level 2:
a) delimitation of the signal units by flags
b) error detection by check bits and error correction by re-transmitting signal units
c) restoration of fault-free operation, e.g. after disruption of a signaling data link.
l Level 3
defines the interworking of the individual signaling links. A distinction is made
between the two following functional areas:
a) message handling (routing of outgoing messages as well as discrimination and
allocation/distribution of received messages)
b) signaling network management
In the SSNC these functional levels are mapped on the functional units LIC (line
interface card), MP:SLT (signaling link terminal) and MP:SM (signaling manager).
l The LIC performs the MTP-level1 functions.
l The MP:SLT performs the MTP-level 2 (error correction) and MTP-level 3
(message handling) functions.
These SLT functions are logically combined and are performed by one or more
MPs. Depending on system usage of the network node, the SSNC can be
provided with up to 47 MP:SLT. Per SLT up to 127 signaling channels (64kbit/s)
may be connected, but not more than 1500 links in total!

6 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

l The MP:SM functional unit supports the MTP-Level 3 network management

function and hosts the routing database for the signaling network.
Thus, each MP:SLT has an internal connection to the MP:SM so that its image of
the SS7 routing database can always be updated by the MP:SM
User Parts
The functions, structures, formats and codings of the messages as well as the
connection sequences and the procedures for cooperating with other signaling
systems (interworking) are stipulated in the user parts. The user parts therefore
control the setup and release of circuit connections, the handling of service features
as well as administration and maintenance functions for the signaling channels.
l The ISDN- and telephone user parts (ISUP/TUP) are located in the LTGs.
l The SCCP is located in the SSNC and is the only user part in case the SSNC is
operated as Signaling Relay Point (SRP).

ITU-T SS7 Protocol Stack

OMAP OMAP
USER Part USER Part
L4 INAP INAP L4
ISS ISS

ISUP TCAP TCAP ISUP

SCCP SCCP
GTT GTT

MTP L3 MTP L3

MTP L2 MTP L2

MTP L1

Fig. 2 MTP and user parts

TIP
It is also possible to transmit the SS7 User Part information via ATM or IP-networks.
In this case the MTP described above is substituted by other solutions (M3UA/SCTP
in case of IP or BBMTP3/SAAL in case of ATM).

SN2073EU01SN_0001
7
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

1.3 SS7 Message Flows through an EWSD

Powernode
1.3.1 Signaling End Point SEP - Traffic
SEP messages are either messages that are generated by a user- or application part
of an exchange and sent to the SS7 network, or that are received from the SS7
network and are evaluated by a user- or application part in the exchange.

Signaling end point traffic, outgoing

l An user / application part in either LTG or CP generates a signaling message
(ORDER) that is forwarded to an idle MP:SLT via an EWSD message channel
MCH and the MBD.
l There level 3 tasks are performed before the message is forwarded to another
MP:SLT doing level 2 tasks.
l From there the message is sent via a LIC to the 64kb/s signaling data link (timeslot
in a PCM system) transporting the message to it's destination (DPC in routing
label of MSU). Since the SSNC internal message flow is based on ATM
connections, a LIC converts the MSU format from ATM to STM (E1).
The PCM system used in the network for transporting the signaling link might be
connected directly to the SSNC or to a so called outward LTG of EWSD. In the
latter case the connection between LIC and PCM timeslot is established as a
nailed up connection through EWSD (LIC - inward LTG SN outward LTG).

Signaling end point traffic, incoming

l The message is coming in via signaling link (time slot of a PCM30 system either
connected directly to the LIC or through-connected via EWSD).
In the LIC it will be converted STM to ATM.
Then it is forwarded to the MP:SLT responsible for this signaling link.
l There, the level 2 tasks as well as the level 3 tasks (message discrimination,
allocation and distribution) are performed.
l In case the message is intended for one of the own user parts (SEP traffic), it will
be forwarded to the respective user / application part in an LTG or in the CP.

8 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

Signaling End Point Traffic Outgoing

SS7-ISUP
MSU
2Mbps with LTG
SS7-Links 64 kbit/s
and trunks
LTG

SSNC V13

LTG
LIC DLU
ASN
SS7-Links 64 kbit/s LTG
or ORDER
ORDER
LIC
HS-Links 2 Mbit/s from
fromISUP
ISUP
MP/SLT Trunk
Trunk
LTG
LTG
MB D
NetM MP/SLT

MP/STAT

MP/SM

MP/OAM SN

CP113C

Fig. 3

Signaling End Point Traffic Incomig

SS7- ISUP
MSU
2Mbps with LTG
SS7-Links 64 kbit/s
and trunks
LTG

SSNC V13
LTG
LIC ASN DLU
SS7-Links 64 kbit/s
LTG
or
HS-Links 2 Mbit/s LIC

MP/SLT

MB D ORDER
MP/SLT
NetM to ISUP
MP/STAT Trunk
LTG
MP/SM

MP/OAM SN
SN

CP113C
CP113C

Fig. 4

SN2073EU01SN_0001
9
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

1.3.2 Signaling Transfer Point Traffic

Signaling transfer points don’t use level 4 functions for processing SS7 messages.
l They may just forward a message (MSU) within the same signaling network
(routing according to the DPC of the received message).
l In case of a ‚signaling relay point‘, they do global title translation with the called
party address of the received message in order to determine the DPC of the
signaling end point (routing by global title).

Signaling Transfer Point Traffic without GTT

l An MSU, coming from node A is forwarded to a LIC where the conversion from
STM to ATM takes place. According to the created level 1 path, it will be
processed (level 2 and 3) by an MP:SLT (the one responsible for the signaling link
via which the MSU is coming in).
Message discrimination determines that the MSU has not to be distributed to a
user / application part in the own exchange. Message routing in that MP:SLT
determines the link, leading to the next/final DPC for that MSU.
l The MSU is forwarded to the MP:SLT responsible for the selected signaling link.
This MP:SLT will perform the level 2 tasks an will sent this MSU via a LIC to the
64kb/s signaling data link (timeslot in a PCM system) transporting the message to
it's destination.

Signaling Transfer Point Traffic with GTT

The message flow for an STP with GTT is very similar to the one described before.
The difference is, that another MP:SLT is required, which is especially created for
doing global title translation.
l After the message has been received by the first MP:SLT it performs level2 tasks
and detects, that global title translation GTT is needed (routing indicator = 0, i.e.,
routing not by DPC but by global title).
l The MSU is forwarded to a second MP, which performs the global title translation
GTT and thus determines the DPC the MSU has to be sent to.
Then this MP also performs the level3 routing function and selects a signaling link
which can be used as a signaling route to the determined DPC.
l The MSU is forwarded to the MP:SLT responsible for the selected signaling link.
This MP:SLT will perform the level 2 tasks an will sent this MSU via a LIC to the
64kb/s signaling data link (timeslot in a PCM system) transporting the message to
it's destination.

10 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

MSU

SS7-Links 64 kbit/s, LTG

MSU
trunks
LTG

SSNC
LTG
LIC ASN
SS7-Links 64 kbit/s
LTG
HS-Links 2 Mbit/s LIC
SN
SN
MP/SLT
MP/GTT
MB D
SC MP/SLT

MP/STAT

MP/SM

MP/OAM

CP113C
CP113C

Fig. 5 STP without GTT

MSU

SS7-Links 64 kbit/s, MSU LTG

trunks
LTG

SSNC
LTG
LIC ASN
SS7-Links 64 kbit/s
LTG
HS-Links 2 Mbit/s LIC
SN
SN
MP/SLT
MP/GTT
MB D
SC MP/SLT

MP/STAT

MP/SM

MP/OAM

CP113C
CP113C

Fig. 6 STP with GTT

SN2073EU01SN_0001
11
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

12 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

2 Administration of the MTP Level 1 in SSNC

and EWSD: The Signaling Data Link

SN2073EU01SN_0001
13
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

2.1 Overview: Types of Singling Data Links

Principally two types of signaling links can be used with SSNC:
l Narrow band signaling links transported in the SS7 network as 64kb/s timeslots
l High speed signaling links with 2 Mb/s per link
(not offered with CCNC)
In the following only the 64kb/s narrow band links are discussed. These links can be
connected to the SSNC in two ways:
l Direct connection of a 2Mb/s PCM carrier to a LIC module of the SSNC
(not offered by CCNC, with SSNC used in case of Stand Alone Signaling Transfer
Points)
This solution is used, if the PCM carrier contains only timeslots used as 64kb/s
signaling channels and not any timeslot used as a normal user channel (user
trunk). Here the EWSD units LTG and SN are not involved in the transport (layer1)
of the signaling link.
l Connection of individual 64kb/s timeslots to the SSNC
This solution is used, if the signaling links are carried via 2Mb/s PCM carriers
which also include normal user channels.
Here EWSD has to take over the transport (layer1) of the individual signaling
channels to the SSNC (like it has always to be done with CCNC:
a) The2Mb/s PCM system has always to be connected to a DIU of an EWSD –
LTG.
b) Each timeslot used as signaling channels has then to be forwarded through
EWSD to the SSNC

14 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

Types of Signaling Links at SSNC

2Mb/s PCM
2Mb/s PCM
carrier with 64kb/s
carrier with 64kb/s
signaling channels only
user and signaling EWSD SSNC
channels
L L LIC
TS
T SN T
Signaling STM
Channel G G MP:SLT

MP:SLT
STM
ASN/
AMX
2Mb/s PCM
carrier with 64kb/s
signaling channels only
MP:SLT
2Mb/s ATM

High Speed 2Mb/sLink

Fig. 7

SN2073EU01SN_0001
15
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

2.2 Creation of Narrow Band Signaling Links

Connected via EWSD
2.2.1 Structure of the Level1 Path (Signaling Data Link)
Narrow band links coming from different partner signaling points are normally
distributed over several PCM links connected to different LTGs of an EWSD switch.
l All LTGs of an EWSD Powernode to which 2Mb/s PCM carriers containing one or
several signaling channels are connected to, serve to the signaling channels as so
called "outward LTGs". From the point of view of an outward LTG a signaling
channel is a trunk port belonging to a trunk group of the type CCSLGRP.
l Inside EWSD an concentration is performed onto specific LTGs, so called "inward
LTGs". I.e., different signaling channels connected to different outward LTGs, are
semipermanently through-connected via the SN to one of the inward LTGs.
l From each inward LTG up to two 2 Mb/s lines are leading to a LIC, each carrying a
max. of 31 links. Each channel of all 2 Mb/s lines between the different inward
LTGs and the LICs is created as a so called "inward trunk", half of the inward
trunks belong to the IW-TGRP0, the other half to IW-TGRP1.
Therefore the transport layer of the signaling channels (so called MTP L1) between
PCM timeslot at the outward LTG of EWSD and the MP:SLT of the SSNC
(responsible for the MTP L2 functions) can be divided into three subsections:
l Connection through EWSD:
STM-NUC between signaling channel port at outward LTG and inward LTG
The external signaling channels are connected via PCM lines at the outward LTG
of the EWSD, where the internal MTP L1 starts. The first part of the system-
internal MTP L1 leads from the DIU of the outward LTG through the SN to the
inward LTG. It is a semipermanent 64kb/s through-connection, a so called STM –
NUC. Physically, LTG-inward and LTG-outward can be the same LTG.
l Connection from EWSD to SSNC:
Timeslot of a 2Mb/s line (PDC) between the DIU of an inward LTG and the LIC
of SSNC, so called inward trunk IWTRUNK
To avoid whole link sets falling out of service when a non-redundant HW unit fails
(LTG-inward, PDC to SSNC), two interworking trunk groups (IWTGR0 and
IWTGRP1) were created between EWSD and SSNC. Every IWTRUNK is assigned
to one of the two interworking trunk groups. All IWTRUNKs of an LTG always
belong to the same IWTGR, thus any inward LTG is allocated to exactly one
IWTGRP.
Now the transport layers of the signaling links of one link set are automatically
divided over the two IWTGRP, i.e., half of the signaling links of a link set are
carried via IWTRUNKs / inward LTGs of the IWTGRP0, the other half via
IWTRUNKs / inward LTGs of the IWTGRP1.

16 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

Additionally only two PDC may be used for IWTRUNKs per inward LTG. This
restriction guarantees that never more than 62 signaling links can get out of
service because of a failure of one inward LTG. Thus the SS7 Network
Management can initiate the so called changeover procedure for the faulty links
the requested period of time.
l Connection through SSNC: ATM-NUC between the LIC and an MP:SLT
On the SSNC-side, the MTP L1 leads
c) from the LIC, where STM signals are converted into ATM signals (PCM-HDLC
--> ATM AAL A1)
d) via the ASN (ATM switching network)
e) to the signaling link terminations (MP:SLT). Here, signals are re-converted
(ATM AAL A1 --> HDLC --> MSU) and stored in receive buffers.
The MP:SLT performs the MTP – level2 functions for up to 127 signaling links.

SN

IW-TGRP0
Outward
LTG
Inward
LTG ASN
Outward LIC
LTG
Inward MP/SLT
LIC
LTG
2Mb/s PCM lines
- with SN0 1+1 MP/SLT
-
individual 64kb/s Inward Red.
-
signaling channels LTG -
created as - -
- -
sign. trunks Inward -
LTG MP/SLT
Outward
LIC
LTG
IW-TGRP1

STM-NUC ATM-NUC
(PVC)
MTP Level1

Fig. 8

SN2073EU01SN_0001
17
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

2.2.2 Overview: Creation Sequence for a Signaling Data Link

A Signaling Data Link SIGDLLTG forms inside the node the connection between the
PCM timeslot used for a SS7 links inside the SS7 network and MP:SLT performing
the Level 2 functions for this link. It is a longtime (nailed up) connection which is
established the EWSD side as STM- NUC and on the SSNC side as ATM- NUC
(PVC).
l CR TGRP / CR TRUNK
Creating trunks (used as signaling links) on the ports of the outward LTGs used for
the signaling.
l CR TGRP / CR TRUNK
Creating the interworking trunks between the inward LTG and the LIC port.
l CR PDCLNK
Definition of the PCM line between the inward LTG and the LIC port.
l CR LIC
Creation of the hardware (not discussed in this chapter).
l CR LICPRTE1
Defining which ports of the LIC are used and to what kind of link will they get
connected?
l CR IWPSS7
Translating the STM connection parameters into ATM connection parameters.
l CRSIGDLLTG
Nailed up connection between a timeslot of an outward LTG and an MP:SLT.

18 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

MML and Q3 Tasks for Creation of a Low Speed Link (64kb/s)

CRSIGDLLTG (EQN - MP)

CRPDCLNK
LTG,LIC
LIC.Port
SIGN-TRUNK EWSD IW- TRUNK
SSNC
CR TRUNK CR TRUNK
CR TGRP CR TGRP

L L LIC
TS T SN T TS
STM MP:SLT
G G

MP:SLT
CRIWPSS7
LIC-ID
Port STM ASN/
Time slot AMX
IWP-ID

CRLICPRT
Lic
Port
TrafficType

MP:SLT
ATM

Fig. 9 L1 path for links, connected via LTG

SN2073EU01SN_0001
19
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

2.2.3 Creation of Trunks / Trunk Groups at Outward / Inward

LTGs
l Creation of the signaling trunk groups / trunks (MML – TASKs)
Creation of a TGRP used for all signaling trunks from/to one partner node:
CR TGRP with GCOS=CCSLGRP, OPMODE=IC
Creation of the signaling trunk(s) used for the signaling link(s) in the network and
connected to an "outward LTG":
CR TRUNK belonging a CCSLGRP - trunk group and identified by
LTG=<ltgset - ltg of outward LTG> and LC=<DIU - timeslot inside outward LTG>
l Creation of interworking trunk groups / trunks (MML – TASKs)
Creation of two interworking trunk groups:
CR TGRP with GCOS=IWTGRP, OPMODE=OG and TGNO=IWTG01/IWTG02
Creation of a pool of interworking trunks for IWTG01 and IWTG02:
CR TRUNK connected either to a LTG of the inward LTG pool for IWTG01 or to a
LTG of the inward LTG pool for IWTG02

20 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

CR TGRP: TGNO=IWTG01,GCOS=IWTGRP,
OPMODE=OG;
CR TGRP: TGNO=C7TG01,GCOS=CCSLGRP, CR TRUNK: TGNO=IWTG01, LTG=0-1 (0-2), LC=2-1,
OPMODE=IC; TRRANGE=31, LCOS=DIGSIG8;
CR TRUNK: TGNO=C7TG01, LTG=0-5, LC=1-16, CR TRUNK: TGNO=IWTG01, LTG=0-1 (0-2), LC=3-1,
LCOS=DIGSIG8; TRRANGE=31, LCOS=DIGSIG8;

CR PDCLNK (for each PCM line

to a LIC)
CR IWPSS7 (for each
interworking trunk)
IWTG01
SN 0
LTG 0-1 1
2
inward 3
LTG 0-5 1

outward MP
MP22
0 2 (SM)
LTG 0-2 1 (SM)
2
inward 3
3

4
L
0
5
I ASN/
ASN/
AMX
AMX
MP5
MP5
(SLT)
LTG 0-3
inward
1
2
6 C (SLT)

LTG 0-6 3
7
outward
0 8
MP6
MP6
LTG 0-4 1
(SLT)
2 (SLT)
inward 3

IWTG02

CR TGRP: TGNO=IWTG02,GCOS=IWTGRP,
OPMODE=OG;
CR TRUNK: TGNO=IWTG02, LTG=0-3 (0-4), LC=2-1,
TRRANGE=31, LCOS=DIGSIG8;
CR TRUNK: TGNO=IWTG02, LTG=0-3 (0-4), LC=3-1,
TRRANGE=31, LCOS=DIGSIG8;

Fig. 10 SS7- and interworking trunks (example)

Create SS7 trunk group at outward LTG

CRTGRP: TGNO=<name> ,OPMODE=IC, GCOS=CCSLGRP;

Create trunks in SS7 trunk group

CRTRUNK: TGNO=<name>, LTG=<ltgset-ltg>, LC=<ltu-ts>,
LCOS=DIGSIG8, [TRRANGE= ,]BLK=NONE;

Create interworking trunk group at inward LTG

CRTGRP: TGNO=<name> ,OPMODE=OG, GCOS=IWTGRP;

Create trunks in interworking trunk group

CRTRUNK: TGNO=<name> ,LTG=<ltgset-ltg, LC=<ltu-ts>,

LCOS=DIGSIG8, [TRRANGE= ,]BLK=NONE;

Fig. 11

SN2073EU01SN_0001
21
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

2.2.4 Assignment of DIUs of Inward LTGs (EWSD) to LIC Ports

(SSNC)
Up to 8 PDC from 4 inward LTGs (only 2 PDCs per inward LTG can be used for
interworking trunks) are physically connected to an internally duplicated LIC
module.
The assignment (which DIU of which LTG is connected with which LIC) is
administered by the Q3 - TASK called CRPDCLNK with the parameters
LIC/LICPORT (SSNC side) and LTG/PDCLNK (inward LTG, i.e. EWSD side)

22 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

Create PDC link

CRPDCLNK: LIC = ,
LICPORT = <1...8>,
LTG=<ltg-ltgset>, PDCLNK=<ltu>;

Fig. 12 PDC link between inward LTG and LIC

DISPPDCLNK:LIC=1;
DISPLAY PDCLNK DATA

LIC LICPORT LTG PDCLNK

-----+---------+-------+------

1 1 0-1 2
1 2 0-1 3
1 3 0-2 2
1 4 0-2 3
1 5 0-3 0
1 6 0-3 1
1 7 0-4 0
1 8 0-4 1

Fig. 13 Display PDC-link (example)

SN2073EU01SN_0001
23
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

2.2.5 Creation of LIC Ports (SSNC)

Each LIC has 8 connectable ports. Depending on the connection (high speed/narrow
band links, direct connection or connection via EWSD), the ports must be created
accordingly.
In the SSNC both, E1- (2Mb/s, PCM30) and DS1-connections (1.5 Mb/s, PCM24)
may be used. Following Q3-Tasks are available:
l CR LICPRTDS1 (for PCM 24 LIC ports)
l CR LICPRTE1 (for PCM 30 LIC ports)
The so called Traffic Type parameter defines, whether narrow band or high speed
signaling links are used :
l traffic type 'STM': the LIC port is created for connection of a primary digital carrier
PDC with 31 time slots of 64 kb/s each (i.e. up to 31 narrow band signaling links)
l traffic type 'ATM': the LIC port is created for connection of a primary digital carrier
PDC with only one 2MB/s object with (i.e. one high speed link)
The timing source for the transmitted line signal may be the SSNC internal system
clock ACCG ('System Time') or may be derived from the incoming line ('Loop').
The 'E1 frame format' describes the kind of error detection method of the PCM line:
'CRC' stands for 'cyclic redundancy check' (CRC4) and will be used as default value.
If a LIC port is not created with the 'Administrative State = Unlocked', it has to be
unlocked afterwards, using the task MODLICPRTE1.

TIP
Since the LICs are created as a pair of one active and one redundant LIC, one must
make sure, that the LIC-ports are created at the active LIC only (DISP LICREDG;).
Nevertheless, the redundant LIC has to be entered too.

24 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

Create LIC ports for 64kb/s links (PCM 30)

CRLICPRTE1: LIC = ,
LIC port = <1...8>,
Traffic type = <STM/ATM>,
Redundant LIC = ,
[Timing source= <System time/Loop>,]
[E1 frame format = CRC,]
[E-Bit = TRUE,]
[E-Bit polarity = TRUE,]
[National Bit = FALSE,]
[Admin. state= Locked/Unlocked,]
[Alarm profile MP= ];

Fig. 14 LIC port for PCM30 link

DISP LICPRTE1:LIC=1, LIC port=5;

LIC | 1
LIC port | 5
Redundant LIC | 2
Admin. state | Unlocked
Operational state | Enabled
Alarm status | Cleared
Current problem list |
Alarm profile MP | "MAJNOESC"
Traffic type | STM
Timing source | System time
E-bit | TRUE
E-bit polarity | TRUE
National bit | FALSE
E1 frame format | CRC

Fig. 15 DISP LICPRTE1 (example)

SN2073EU01SN_0001
25
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

2.2.6 Creation of Interworking Points IWP

For every narrow band 64kb/s signaling link, a permanent virtual connection (ATM-
NUC) must be established inside the SSNC between the LIC and the MP:SLT
responsible for the signaling link.
Therefore it is necessary to establish a linkage between the STM - side of the SS7
link (64kb/s timeslot on PDC at LIC) and the SSNC internal ATM - side of the SS7
link. This is done by the logical object 'interworking point' IWP, which is assigned to
each 64kb/s SS7 link using the Q3-Task CR IWPSS7:
l The operator specifies only the physical location of each time slot (LIC, LIC-port,
64time slot) for which a virtual connection should be created.
l The SSNC generates automatically all necessary data for the ATM connection
itself. (Most of the ATM description data are internally predefined and don't need to
be specified by the operator).
l The IWP is identified by an interworking point number (IWP ID), which can be
entered by the operator or is assigned automatically by the system.
The task CRIWPSS7 has to be entered once for each single timeslot on the
connection between inward LTG and LIC (or for each timeslot of a PDC directly
connected to a LIC and carrying signaling links only). A parameter similar to
"TRRANGE" in CRTRUNK does not exist.

TIP
The IWP-ID is used explicitly in the Q3-Task for creation of a Signaling Data Link
(CRSIGDLLTG) on a PDC directly connected to a LIC. Here it makes sense to assign
an IWP ID from which the relation between LIC-port and timeslot can be derived:
Example:
IWP ID: "a b c" 1304
LIC: a 1
LIC Port: b 3
Time Slot: c 04

26 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

Create interworking point for SS7

CRIWPSS7: LIC = ,
LIC Port =<1...8>,
Time Slot =<1...31>,
[IWP ID = ,]
[Admin State = <Locked/Unlocked>,]
[Alarm Profile MP = ];

Fig. 16 Virtual connections for 64kb/s links

DISP IWPSS7: IWP ID=1103;

IWP ID | 1103
LIC | 1
LIC port | 1
Time slot | 03
Admin. state | Unlocked
Operational state | Enabled
Alarm status | Cleared
Current problem list |
Alarm profile MP | "CRITICAL"

Fig. 17 Display interworking point SS7 (example)

SN2073EU01SN_0001
27
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

2.2.7 Creation of a Signaling Data Link (SIGDLLTG between

Timeslot at Outward LTG and MP:SLT)
Signaling Data Links form the connection between the SS7 links in the network (PCM
timeslot) and an MP:SLT. This involves nailed up connections which are established
l inside EWSD as STM-NUC (NUC between outward and inward LTG, not required
for signaling links on PDCs directly connected to a LIC)
l inside the SSNC as ATM-NUC (PVC between IWP at LIC and MP:SLT).
The Q3-Task CRSIGDLLTG is used to establish the semipermanent connection
between the two end points (time slot of the outward LTG and MP:SLT) of the level1
path of the signaling link in the EWSD Powernode:
l The end points are defined by the location of time slot used for the signaling link in
the network (Outward EQN = <ltgset>-<ltg>-<ltu>-<timeslot>) and the number of
the terminating MP:SLT.
l The time slot (interworking trunk) used between EWSD (inward LTG) and SSNC
(LIC) is selected by the system automatically.
You can display the selected inward trunk (Inward EQN=<ltgset>-<ltg>-<ltu>-
<timeslot>) with DISPSIGDLLTG .
l It is sufficient if the signaling network and the data link are identified by their given
names ('Data link name' and 'Net name'). The identification number (ID) is then
allocated automatically.
The 'Data link name' can be any string of up to 12 characters.
The used 'Net name' depends on the signaling network, the signaling link should
belong to ,i.e., the signaling network, the adjacent DPC belongs to (see chapter
about "Administration of MTP Level3 Objects").
l The parameter 'Bit inversion' indicates whether the level 1 bit stream is inverted for
a signaling data link or not.
l The bandwidth ('Transmission rate')of the internal through connection will always
be 64kb/s in case of narrow band links.

TIP
Depending on the kind of signaling connection (Narrow band/High Speed, connection
directly or via EWSD to the LIC port), different Q3-Ttasks with different parameters
have to be used.

28 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

Create signaling data link for 64kb/s links via LTG

CRSIGDLLTG: Data link name = ,

[Data link ID = ]
Net name = <name>
[Net ID = ]
Adjacent DPC = <DPC of partner exchange>
MP = <no. of MP:SLT>
Outward EQN = <ltgset> - <ltg> - <ltu> - <timeslot>
[Transmission rate = 64 kb/s]
[Bit inversion = No Inverse];
Fig. 18 Signaling data link for narrow band links via LTG

DISPSIGDLLTG:Net name=TRAINING,Data link ID=2; STARTED

1015:DISP SIGDLLTG executed
Net name | „TELECOM1"
Net ID | 1
Data link name | „DL1T-Munich"
Data link ID | 2
Adjacent DPC | 2-2-2-2
MP | 5
LIC Port | licId = 1
| licPhysicalInterfaceId = 1
Inward EQN | LTG SET | 0
| LTG ID | 1
| DIU ID | 2
| STM channel | 7
SN Info | .
Outward EQN | LTG SET | 0
| LTG ID | 5
| DIU ID | 1
| STM channel | 16
Assoc.interworking point | Pointer : { IWP ID = 1105 }
Operational state | Enabled
Transmission rate | 64 kBit
Bit inversion | No inversion
Used | TRUE
ENDJOB

Fig. 19 Display of a signaling data link LTG (example)

SN2073EU01SN_0001
29
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

2.3 Creation of Narrow Band Signaling Links Directly

Connected to a LIC
In opposite to the CCNC, a PCM line carrying signaling links only may also be
connected to the SSNC directly (instead of connection at an EWSD – LTG).
In that case, each timeslot of the PCM represents one 64kb/s signaling link. Since no
trunk groups and no trunks (neither TGRP/Trunks for timeslots at outward LTG nor
interworking TGRP/Trunks) are needed here, the necessary database is simpler than
in the case described before.
Creation sequence:
l CR LICPRTE1
Which ports of the LIC are used and to what kind of link will be connected?
Tip
The LIC ports have to be created in the same manner as for narrow band links,
connected via LTG, described before:
l CR IWPSS7
Linkage the STM timeslot with SSNC internal ATM connection parameters.
Tip
The interworking points have to be created in the same manner as for narrow band
links, connected via LTG, and described before.
l CRSIGDLLIC
This Q3-Task is used to create a signaling data link for a narrow band SS7 link
connected directly to a LIC.
I.e., it establishes in the SSNC an ATM - nailed up connection (permanent virtual
connection PVC) between a timeslot of the PCM system (carrying the SS7 link in
the network) and the terminating MP:SLT of the SSNC.
The endpoints of the are defined in the following way:
a) PCM time slot used for the STM – SS7 link:
identified by the interworking point IWP created for this timeslot, i.e., IWPID
assigned to the physical address LIC / LIC Port / Time slot by Q3-Task
CRIWPSS7
For all created IWPs the assignment IWPID - LIC / LIC Port / Time can be
displayed by DISPIWPSS7.
b) MP:SLT
The MP is identified by its number.
All other parameters are used in the same way like in the Q3-Task CRSIGDLLTG
(used for signaling links connected at an EWSD outward LTG).

30 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

Direct connected Narrow Band SS7 Link (64kb/s)

CRSIGDLLIC (IWP - MP)

SSNC

LIC
MP:SLT

MP:SLT
PDC TS STM ASN/
only carrying AMX
SS7 links CRIWPSS7
LIC-ID
(each link one TS) Port
Time slot
IWP-ID

MP:SLT

CRLICPRT
Lic
Port
TrafficType

Fig. 20 L1 path for links, directly connected to SSNC

Create signaling data link for 64kb/s links

CRSIGDLLIC: Data link name = ,

[Data link ID = ,]
Net name = <name>,
[Net ID = ,]
Adjacent DPC = <DPC of partner exchange>,
MP = <no. of MP:SLT>,
Interworking point ref. = ,
[Transmission rate = 64 kb/s,]
[Bit inversion = No Inverse];

Fig. 21 Signaling data link for narrow band links, directly connected to a LIC port

SN2073EU01SN_0001
31
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

32 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

3 Administration of MTP Level 3 Objects

SN2073EU01SN_0001
33
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

3.1 Overview of MTP Level 3 Objects

A signaling network consisting of
l signaling points
l signaling links
l signaling link sets
l signaling routes
must be created by operator via Q3 tasks in the SSNC.
With the aid of the appropriate database, the MTP is then able to carry out its tasks.

34 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

Originating Point
SIEMENS D 900 SIEMENS D 900
Signaling links
CRSIGPOINT CRSIGLINK

1 Signaling link set

.. . 16 CRSIGLSET
. ..
31
1
.. . 16 Signaling Point
. .. (STP or SRP)
Signaling 31
route
SIEMENS D 900 SIEMENS D 900
1
.. .

C ela
CRSIGROUTE

irc te
r
16

ui d s
t r ig
.. .

el n
at al
ed in
31

Signaling

or g in
links

no for
n ma
ci ti
rc o
ui n
t
SIEMENS D 900 SIEMENS D 900

Signaling
link set SIEMENS D 900 SIEMENS D 900

Signaling Point
(STP or SRP)
Destination Point
CRSIGDP CRSIGDP

Fig. 22 Signaling network

SN2073EU01SN_0001
35
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

3.2 Own Signaling Point Code

3.2.1 Creation of the Own Signaling Point: CRSIGPOINT
l Every signaling point must have an own signaling address, consisting of SPC and
network indicator. This address has to be unique in the signaling network this node
belongs to:
SPC
Depending on the project specific structure, this SPC has to be entered as a
decimal value or structured.
Net Indicator
This specifies the so called ITU-T network. Possible values are NAT0 / NAT1 /
INAT0 / INAT1
l Due to the feature 'Multiple SS7 Networks', up to 32 different internal signaling
networks can be handled by a single SSNC.
Each signaling point is SSNC internally not only defined by SPC and ITU-T
Network Indicator, but additionally the internal network it is belonging to. This has
to be specified under 'Net Name'. It is sufficient to specify their 'Net Name', the
'NetID' will be assigned automatically.
Because of the feature 'Multiple SS7 Networks' (explained on the next pages) one
SPC / Network Indicator combination may be created several times for different
internal networks.
l If a different MSU length than 272 octets is required, the parameter 'Supported
data length' has to be set accordingly.
l The 'Signaling point type' determines the usage of the own SP:
STP Signaling point functions purely as a signaling transfer point, i.e. level 4
of CCS7 will not be used to evaluate the message, not even SCCP for
GTT.
SEP Signaling point functions purely as signaling end point, i.e. it can
distribute a received message to its own users only. Should the routing
label of an MSU indicate that a transfer to another signaling point is
required, the message is discarded and the discarded-message
counter is incremented.
STEP Signaling point functions as signaling transfer point and signaling end
point.
In case the own node is a standalone signaling relay point with GTT, it
has to be set up as STEP
l Furthermore, it must be defined how the SP shall handle signaling- and status
messages (TFA, TFP and TFR). I.e., here aspects of the signaling network
management function are defined.
Parameters: 'TFP TFA broadcast', 'TFR compatibility' and 'TFP for unknown DP'

36 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

Create own signaling point

CRSIGPOINT: Net Name = <name>,
[Net ID = <1...32>,]
Net Indicator = <Nat0/1 Inat0/1>,
SPC = ,
Signal. point type = <SEP/STP/STEP>,
TFP TFA broadcast=<YES/NO/Restricted> ,
TFR compatibility= ,
TFP for unkown DP= ,
[Supported data length= length272,]
[Alarm profile MP = ,]
.... ;

Fig. 23 Own signaling point

Signaling Network Management: Handling of TFP / TFA / TFR

A STP receives a MSU which cannot be transferred because of unknown DPC:

• If TFP for unkown DP is set to TRUE: TFP is sent back, MSU is discarded
• If TFP for unkown DP is set to FALSE: MSU is discarded, no TFP is sent back

A STP detects the unavailability of the direct signaling route to a destination (DPC=X)
Independent from TFP TFA broadcast (YES/Restricted/No) :
a so called preliminary TFP is sent to all adjacent nodes which this node uses as STPs to DPC X
(i.e., linksets to these nodes are used as alternative signaling routes to DPCX)

A STP detects the unavailability of a destination (DPC=X), i.e., all signaling routes to DPC X are lost:
• Only if TFP TFA broadcast is set to YES/Restricted:
- TFP messages are sent to all partner (adjacent) nodes:
„no transfer to DPC X is possible“
- After minimum one signaling route to DPC X is available again:
TFA to all adjacent nodes: „transfer to DPC X is possible again“
• If TFP TFA broadcast is set to NO: No TFP / TFA are sent in case of unavailability of a destination

Receiving of a TFR (transfer restricted to a destination Y) from a partner node,

whichn has before sent a TFP:
• If TFR compatibility is set to TRUE:
Interprete TFR as a TFA (i.e., use partner node again as STP to destination Y)
• If TFR compatibility is set to FALSE:
Ignore TFR (i.e., still do not use partner node as STP to destination Y)

Fig. 24 TFP/TFA/TFR

SN2073EU01SN_0001
37
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

3.2.2 Multiple SS7 Networks

The feature 'Multiple SS7 Networks' expands the range of network planning options
in deregulated markets with many operating companies. With this feature, up to 32
SS7 routing domains (internal networks) can be administered in one signaling
network node with SSNC.
SSNC internally a signaling network is identified by the parameters 'Network Name'
or 'Network ID' in addition to the 'Net Indicator' (which specifies the ITU standard
network).
This means that a node can be connected to up to 32 separate signaling networks,
each allocated to one of the so called ITU standard networks (NAT0/1, INAT0/1).
Each of these SS7 networks can be individually administered; in this way up to 32
own signaling addresses can be set up in one node. Signaling point allocation is
completely flexible.
The maximum SSNC capacity of the signaling network elements (1500 signaling
links, 1024 signaling link sets, 4096 DPC) remains unchanged. They can flexibly be
distributed over all internal networks.
The 'Multiple SS7 Networks' feature is fully compatible with ITU-T SS7 standards, i.e.
it is transparent to all SS7 protocols. The SS7 message format of the signaling units
exchanged between the nodes within the SS7 network remains unchanged.

Operator benefits
l Different operators can share one network node with SSNC
l Support of multiple point codes in one network node (e.g. for network
consolidation)
l Incoming linkset-specific routing domains
l Enhanced interworking with other operators
l Internal separation of SS7 traffic belonging to different operators
l Separation of traffic for different applications (e.g. MTP user parts)
l Free assignment of the network indicator (NI) per internal MTP network
l Addressing of up to 4 million trunks between two nodes (if both nodes use the
feature)

38 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

ITU: SSNC
4 standardized up to 32 internal SS7 networks
networks on top of the four ITU standardized neworks

NAT0/1, INAT0/1

INAT1
OP1

INAT0
OP32 OP5
SSNC
NAT1

NAT0 OP18
NAT0
OP25

Fig. 25 Multiple SS7 networks

SN2073EU01SN_0001
39
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

3.2.3 Example for Data of a SIGPOINT

The opposite page shows typical signaling point data. Apart from the parameters
mentioned, many others are shown, mainly timer values and parameters, indicating
how to handle transfer allowed- and transfer prohibited messages.

TIP
The SPC structure can be determined per internal signaling network. It is predefined
in the NetM and is fixed in the SSNC with the Q3-Task CRSIGPOINT.
Inside the system and in signaling messages the structured code is always
transferred as an unstructured binary value.
In some projects (China) SPCs with 24 bit are used in national networks.

Signaling Point Codes (14 bit)

national use:
• 14bit
• 5bit-9bit
• 3bit-4bit-7bit
• 4bit-3bit-4bit-3bit

international use (ITU-T Q 708):

3bit-8bit-3bit
meaning:
Zone - Area- sign. point
e.g. 3-20-n

Fig. 26

40 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

DISP SIGPOINT

Net name | "TELECOM1"

Net ID | 1
Net indicator | National network 0
SPC | 1-1-1-1
SPC structure | No. of bit | Component | Component
| s | minimum | maximum
| ======================================
| 4 | 0 | 15
| --------------------------------------
| 3 | 0 | 7
| --------------------------------------
| 4 | 0 | 15
| --------------------------------------
| 3 | 0 | 7
Operational state | Enabled
Alarm status | Cleared
Alarm Profile MP | "CRITICAL"
RST after conf DP | FALSE
TFP for unknown DP | TRUE
MTP restart | Off
TFR compatibility | TRUE
Ni screening | Activated
TFP TFA broadcast | Yes
Signaling point type | STEP
TFC sampling rate | 8
Number of TFA | 100
Number of TFP | 100
TFA interval | 600
TFP interval | 600
Supported data length | Length 272
TUP | -
Send UCIC indicator | FALSE
LPO control bit | TRUE
ITU-Timers
Q704 timer T1 | 1000
Q704 timer T2 | 2000
. . .
. . .

Q707 timer T1 | 12000

Q707 timer T2 | 90000

Fig. 27

SN2073EU01SN_0001
41
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

3.3 Signaling Destination Point

In every signaling point of a network, all other signaling points of the same signaling
network, to which messages can be sent and received respectively, must be created
as destination points.
l Destination points are uniquely identified by a signaling network 'Net Name/ID' and
an SPC. This has to be unambiguous in that signaling network.
The SPC structure of the DPC has to be the one defined (by CRSIGPOINT) for the
signaling network this DPC belongs to.
l The destination points can be reached from the own signaling point either via a
direct signaling link set (i.e. destination point is adjacent) or via one or more
intermediate signaling points, so called signaling transfer points.
a) A linkset, which can be used for transmitting messages to one destination
point in the own network is created as a signaling routes to this destination
(described later).
A maximum of eight signaling routes can be created for one destination,
different priorities can be given to these up to eight routes.
b) If 2 or more signaling routes are created for one destination with the same
priority, the so called loadsharing can be activated. I.e., the messages sent out
to this destination are distributed over these routes.
c) Loadsharing can normally be set for the first two active signaling routes at
most.
A 'Loadsharing key' defines, how the signaling messages towards that
destination point are offered to the possible linksets:
Loadsharing is carried out by evaluation of one of the SLS-bits (Signaling Link
Selection), found in the routing label of each MSU. The operator determines
the bit by entering a 'Loadsharing key' between 0 and 4:
Loadsharing Loadsharing algorithm
key =
none 0 No loadsharing. All MSUs are offered to the linkset with the
highest priority
SLS1...SLS4 Loadsharing between the first two linksets having the same
highest priority.
LSK = SLS1...SLS4 defines a bit position within the SLS field
of an MSU. A binary '0' at this position routes the MSU to the
first linkset, a binary '1' routes it to the second linkset.

TIP
The SSNC offers also the possibility to distribute the signaling traffic to one
destination over up to 4 signaling routes. This feature is optional, if it is activated, not
1 but 2 bits of the SLS are evaluated. the values SLS5 … SLS10 are then used for
the parameter 'Loadsharing key'.

42 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

Create signaling destination point

CRSIGDP: DPC = ,
DPC Name = ,
Net Name = ,
[Net ID = ,]
[Loadsharing key = ,]
[Alarm profile MP = ,]
[Alarm smoothing time = ];

Fig. 28 Signaling destination point

LSK = Bitposition in Selected linkset from

SLS field signaling route
none 0 XXXX first LS with highest priority

SLS1 XXX0 first LS with highest priority

XXX1 second LS with highest priority

SLS2 XX0X first LS with highest priority

XX1X second LS with highest priority

SLS3 X0XX first LS with highest priority

X1XX second LS with highest priority

SLS4 0XXX first LS with highest priority

1XXX second LS with highest priority

Fig. 29 Loadsharing between linksets towards a destination point

SN2073EU01SN_0001
43
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

Administrative and Operational State of a SIGDP

By means of the task MOD SIGDP, the administrative state of a destination point
has to be set to 'UNLOCKED' before it can be reached.
l As a prerequisite at least one signaling linkset must be created as a signaling
route leading to that destination point.
l The administrative state attribute describes whether it is administratively permitted
to route SS7 MSUs towards the respective destination point. The possible values
supported in the NE are ’LOCKED' and ’UNLOCKED’.
The operational state attribute describes whether the respective destination
signaling point is accessible (ENABLED) or not (DISABLED).
l If the operational states of all signaling linksets leading to the signaling destination
point are ’DISABLED’, then the operational state of the signaling destination point
is ’DISABLED’, in any other case it remains ’ENABLED’.
l If the administrative state is 'LOCKED', the operational state is 'DISABLED'.

44 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

Modify signaling destination point

MODSIGDP: DPC = ,
[Net Name = ,]
[Net ID = ,]
Administrative state = <Locked / Unlocked>,
Loadsharing key = ,
[Alarm smoothing time = ];

Fig. 30 Administrative state change

DISP SIGDP:Net ID =1;

Net name |Net|DPC name | DPC | Admin. | Opera | Load | Alarm | Alarm |Alarm | Extended|Con |Con |US
| | | | | state | key | | MP |thing | problem |gested |gested|routing
| | | | | | | time | list | | |state |level |
==============================================================================================================================
"TELECOM1" |1 |“Munich" |2-2-2-2| Unlocked| Enabled | "sls 0" |Cleared |"MAJNOESC"| 0 | { } |Not | - |
| | | | | | | | | | |Congested| |
----------------------------------------------------------------------------------------------------------------------------
"TELECOM1" |1 |“Berlin" |4-4-4-4| Unlocked| Enabled | "sls 0" |Cleared |"MAJNOESC | 0 | { } |Not | - |
| | | | | | | | | | |Congested| |
------------------------------------------------------------------------------------------------------------------------------
"TELECOM1" |1 |“Hamburg"|3-3-3-3| Unlocked| Enabled | "sls 3" |Cleared |"MAJNOESC | 0 | { } |Not | - |
| | | | | | | | | | |Congested| |

Fig. 31 Signaling destination point

SN2073EU01SN_0001
45
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

3.4 Signaling Link Set

A signaling link set, consisting of up to 16 links, connects the own signaling point to a
neighbor signaling point ('adjacent DPC') which can either be a signaling end point or
a signaling transfer point.
l Only one link set can be created for each adjacent signaling point inside one
signaling network.
The adjacent signaling point it is leading to is specified via its SPC (parameter
'DPC') and its 'Net name' / 'Net ID'.
l Regardless of this, the same neighbor signaling point may also be reached via
other, not directly running linksets, grouped together in a signaling route (see
below).
The 'max MSU length' defines the maximum length for message signal units. At
creation of a signaling link set the maximum MSU length can be given as part of the
linkset specific data. The maximum MSU length can be modified to a different value
up to the default value of 272 octets.
'Congestion method' reflects the control method within a signaling network, i.e. it
defines the reaction upon a signaling network congestion. In networks with 14 or 24
bit SPCs 'International' is the only allowed value.
Loadsharing between the links of one linkset is hard coded (SR9) and can't be
modified. The MSUs are offered equally to all links in the linkset.

46 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

SP Signaling link set X:

100 Group of up to 16 signaling links

to one adjacent signaling point
Signaling link set Y

SP
300

STP
200 All signaling points belong
to the same signaling network
(ITU-T and internal sign. Network)

SP
400
Fig. 32 Signaling link sets

Create signaling link set

CRSIGLSET: Link set name = ,

[Link set ID = ,]
Adjacent DPC = ,
Net name = ,
[Net ID = <1...32>,]
[Periodic link set test = ,]
[Alarm Profile MP = ,]
[Congestion method = International,]
[Alarm smoothing time = ,]
[max.MSU length = ];

Fig. 33 Creation of a signaling link set

SN2073EU01SN_0001
47
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

Periodic Link Set Test

If the 'Periodic link set test' parameter is set to ON, a link test of the links allocated to
the link set is carried out every 90 seconds. The test checks the L2 functions between
two adjacent SPs.
Testing and maintenance sends a Signaling Link Test Message (SLTM) to the
adjacent MTP which includes a test pattern. The partner responds with a Signaling
Link Test Acknowledgement (SLTA) containing the reflected test pattern.
The following data are checked during the test:
1. the Signaling Link Code (SLC, must be the same at both sides of a link)
2. the OPC (SLTM-DPC = SLTA-OPC)
3. the test pattern (which is merely looped back in the acknowledgement)
The test is positive only if the link status is "enabled".

General principles on linkset state information:

l The states of a signaling link set can only be displayed.
(Activation and deactivation of a linkset may be done indirectly via administration
of the signaling links)
l operational state:
- It is ’ENABLED’ when at least one link of the signaling link set is enabled.
- Otherwise it is ’DISABLED’.

48 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

SP A SLTM

SLTA 1
SP B
SLTM

2 SLTA

1) Testing of A-side
2) Testing of B-side

SLTM: Signaling Link Test Message

SLTA: Signaling Link Test Acknowledge

Fig. 34 Periodic link test

DISPSIGLSET:Link set name=C7LSRNC1;

Net name | "NAT0"
Net ID | 3
Link set name | "C7LSRNC1"
Link set ID | 50
Adjacent DPC | bit14 : 769
Operational state | Disabled
Periodic link set test | Off
Alarm status | Major
Alarm profile MP | "MAJNOESC"
Alarm smoothing time | 60
Max.MSU length | 272
VMS | Off
Congestion method | International

Fig. 35 Signaling link set

SN2073EU01SN_0001
49
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

3.5 Signaling Routes

Every signaling destination point may be reached by a maximum of eight signaling
linksets. These linksets are called signaling routes and have to be defined with the
task CR SIGROUTE.
The application of the signaling routes, leading to the same signaling destination
point is determined by the 'Priority', assigned to the single routes (1=highest and
8=lowest priority):
l Always the currently available signaling route with the highest priority is used for
sending out messages.
l If more than one signaling route with the currently highest priority is available,
loadsharing can take place (normally) between two linksets. This happens, if the
Loadsharing key if the concerned SIGDP is not set to 'none0'.
l If one of several linksets, having the same priority, fails and there is still an
additional linkset with the same priority existing, loadsharing will continue.
l Only if all linkset of one priority fail a switch over will take place to a linkset with the
next lower priority.
In the example on the opposite page, three cases are shown from point of view of 'A':
l towards DPC = B, loadsharing takes place between linksets LS_B and LS_C.
l towards DPC = C, loadsharing takes place between the linksets LS_B and LS_D
only, if linkset LS_C fails.
l towards DPC = D, no loadsharing is possible.

50 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

CR SIGROUTE

DPC = B: Prio1: LS_B

Prio1: LS_C
Prio2: LS_D
DPC = C: Prio1: LS_C
Prio2: LS_B
Prio2: LS_D
DPC = D: Prio1: LS_D
SPC
Prio2: LS_C
B
B
LS_

LS_C
SPC SPC
A C

LS_
D

CR SIGLSET

SPC
D

Fig. 36 Signaling routes

Create signaling routes

CRSIGROUTE: Net name = ,

[Net ID = ,]
DPC = ,
[DPC name = ,]
Link set name = ,
Priority = ,
[Route ID = ,]
[Priority mode = Equal];

Fig. 37 Creation of signaling routes

SN2073EU01SN_0001
51
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

3.6 Signaling Links

A signaling link is part of a link set.
l The 'Data link name' sets up the relation between:
a) the administrative object 'SIGLINK'

and
b) the 'SIGDLLTG / SIGDLLIC (signaling data link, i.e., level one path between
the timeslot the signaling link is received in the node and the MP:SLT by which
it will be terminated)
(The corresponding signaling data link must have been created before with CR
SIGDLLTG/LIC.)
When allocating SIGLINK- SIGDL(LTG,LIC,HS), care should be taken that the
signal channels of one linkset are distributed to two MP. In this way it is ensured,
that if one MP (both MPU) fails, this does not result in the failure of a complete
signaling relation.
l A maximum of 16 links may be created in one signaling linkset.
A signaling link can be uniquely identified by a link code (0...15), which must be
the same value at both ends of a link.
l The signaling link is assigned certain characteristics such as transmission rate, the
communications protocol, necessary timer and correction procedure by means of a
'Profile name'. If the standard profiles are not sufficient (they will be sufficient in
99,9% of all cases), additional profiles may be created by CRMTPL2PRF.
The most commonly used profiles are
a) ITU BASIC64
transmission rate: 64 kb/s, basic error correction, PCM30, world market
version
b) ANSI BASIC64
transmission rate: 64 kb/s, basic error correction, PCM24, US version

Administrative State of a SIGLINK

Before a signaling link can be seized, the administrative state must be set to
'UNLOCKED' by the task MODSIGLINK.

52 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

Create signaling link

CRSIGLINK: Net name = ,

[Net ID = ,]
Link set name = ,
[Link set ID = ,]
Link code = ,
Data link name = ,
Protocol Profile name = ,
.... ;

Fig. 38 Creation of a signaling link

DISPSIGLINK:Display names=Yes,Link set name=C7LSRNC1;

Nr. | Net name | Net ID | Link set name | Link set | Link code | Admin. sta | Operational |
| | | | ID | | te | state |
| | | | | | | |
======================================================================================================
1 | "NAT0" | 3 | "C7LSRNC1" | 50 | 0 | Unlocked | Disabled |

Data link | Data link name | Protocol profi | Bandwidth | VMS

ID | | le name | identifier |
| | | |
==================================================================
50 | "C7LSRNC1" | "ITU64" | Broadband | Off

DISP MTPL2PF:L2 Profile name=ITU BASIC64;

L2 profile name | "ITU BASIC64"
L2 profile ID | 1
Transmission rate | 64 kBit
Correction Method | Basic
L2 timer T1 [ms] | 45000
L2 timer T2 [ms] | 25000
L2 timer T3 [ms] | 1500
L2 timer T4E [ms] | 500
L2 timer T4N [ms] | 8200
L2 timer T5 [ms] | 100
L2 timer T6 [ms] | 4500
L2 timer T7 [ms] | 1000
Trm.cong.onset L1 | {
| messages 100,
| octets 2000
| }
Trm.cong.abatement L1 | {
| messages 15,
| octets 300
| }
Max.MSU for retrm. | 127
Max.oct.for retrm. | 300

Fig. 39 DISP of SIGLINK and MTP layer 2 profile "ITU BASIC 64"

SN2073EU01SN_0001
53
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

3.7 Comparison of the Tasks for MTP Level 3

Administration in SSNC and CCNC
For those, who are familiar with the creation of a MTP database in the CCNC, the
following table compares MML- and Q3-commands for same tasks.

54 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

MML (CCNC) Q3 (SSNC) Description

CR C7OP CR SIGPOINT Defines the own signaling address.

CR C7DP CR SIGDP Defines the signaling addresses of all other

CR SIGROUTE signaling points with which signaling
messages are exchanged (SEP, STP and
SRP) and the link sets, leading there.

CR C7LSET CR SIGLSET Creates a group of signaling links, leading to

the same neighbor-signaling node.

CR C7LINK CR SIGLINK Creates a signaling channel in a linkset.

CR NUC CR SIGDLLTG Semipermanent connection between the

CRSIGDLLIC PCM - port at which a signaling message is
received (or leaves the node) and that part of
the node, where level 2 tasks are performed.

Fig. 40

SN2073EU01SN_0001
55
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

56 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

4 Administration of the User Parts in the CP /

SSNC

SN2073EU01SN_0001
57
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

4.1 Overview C7User

The permitted user parts per destination point must be made known in order to
enable distribution of the message signal units (MSU) among the corresponding user
parts, or to send user part MSUs to the corresponding destination points.
The users currently being used are:
l for user channel (trunk) related signaling: ISDN user part (ISUP), TUP and TUP+
l for non traffic channel orientated signaling: SCCP/TCAP for signaling with the IN-
SCP (INAP) or for handling of ISDN supplementary services ISS (e.g.
CCBS/CCNR)
In an EWSD Powernode the trunk related user parts are administered in the CP, the
non trunk related user part SSCP is administered in the SSNC.

58 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

TCAP User
e.g. INAP, ISS

TCAP
ISUP TUP

SCCP

MTP

Fig. 41 CCS7 protocol stack

SN2073EU01SN_0001
59
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

4.2 Administration of the Trunk Related UPs in the CP

Creation of C7 USER
With the help of the CR C7USER MML command, the relevant user name (e.g. ISDN
user part ISUP) is allocated to a destination point code and a network name. The
C7USER of all known DPCs of the own network must be set up here.
As well as setting up, it is also possible to display and cancel the C7USER.

Creation of C7 TGREL
After the trunk related UPs are created, the so called C7TGREL can be entered for
each TRGP.
The C7 trunk group relation (C7TGREL) represents the link between the traffic
orientated user parts e.g. ISDN user part (ISUP) and level 3. Here the linkage of a
trunk group and a DPC is determined, this linkage is required for the "allocation
function"

60 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

Administration of C7USER
CR C7USER: DPC= , NETNAME=, USNAME=ISUP,.... ;

DISP C7USER: DPC= , NETNAME= ,USNAME=ISUP,.... ;

CAN C7USER: DPC= , NETNAME= ,USNAME=ISUP,.... ;

TAC1/000TAC1MPS/NCGCBK1V1530/P00/113 02-03-08 11:53:16

3344 NetM IPATH4N2 2871/09116

DISPC7USER:DPC=0-0-3,NETNAME=TRAINING; EXEC'D

CCS7 -- USER RELATED DATA

DPC OSPC NETNAME USNAME PCMTYP CICSIZE

--------------+--------------+-------------+-------+-------+--------
0-0-3 0-0-1 TRAINING ISUP DIU30 CIC12

END JOB 3344

Fig. 42 C7 user administration

SN2073EU01SN_0001
61
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

4.3 Administration of the SCCP and its Application

Parts in the SSNC
4.3.1 Overview: SCCP and its Users
The signaling connection control part (SCCP) is used as a supplement to the
message transfer part. It provides additional functions for the transfer of messages
between switching centers and other signaling points, such as data banks. From the
point of view of the message transfer part the SCCP is a user with its own service
indicator. The combination of the SCCP and the message transfer part is called the
network service part (NSP).

Types of Message Transfer with SCCP

The SCCP provides two types of message transfer:
l without logical signaling connection (connectionless)
l with logical signaling connection (connection-oriented)
Without logical signaling connection an SCCP user can send single messages to
other SCCP users. With logical signaling connection an exchange of messages
between two SCCP users is possible. A logical signaling connection arises through
the mutual exchange of the originating point codes between the SCCPs in the sig-
naling points of the signaling relation. The messages to the other SCCP user can
thus be directly addressed.

SCCP Users
The SCCP offers an interface to
l to the TCAP (Transaction Capabilities Application Part) with its users (called
subsystems or application parts)
The application parts like the INAP (Intelligent Network Application Part) or the ISS
(ISDN Supplementary (so-called application parts or subsystems) use the TCAP
for message control, i.e. the SCCP is used here "without logical signaling
connections" (connectionless). In this case the SCCP is mainly used for address
logic and address conversion towards other signaling points and for internal
addressing of the corresponding SCCP subsystems.
l the BSSAP (Base Station Application Part of mobile network D900)
The BSSAP uses the SCCP "with logical signaling connections" (connection
oriented) and can therefore do without the TCAP.

SCCPAddressing, Routing and Global Title Translation Functions

The SCCP possesses its own routing function. The SCCP can use the following as
address parameters:
l destination point code
The SCCP can address the destination of a message directly by the destination

62 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

point code. I.e., the SCCP delivers an address, which can be used directly by the
MTP of the SS7 network.
l global title
It is also possible to address the destination of a message by a so called global
title. The global title, however, contains digits or other forms of address information
that are not customary in the MTP of the SS7 network.
For this reason, the SCCP must first determine the destination point code for the
transfer of the message to the destination, i.e., it has to translate the global title
into an DPC (global title translation GTT). This address is entered in the MTP
message header of the messages, which the SCCP transfers to the MTP for
routing.
l subsystem number
The subsystem number identifies a user function; for example, in an incoming
message it identifies the SCCP user (e.g. ISS or INAP) for which the message is
intended.
The SCCP also provides the option for routing to replicated subsystems/nodes. If
there are two different subsystems/nodes performing the same functions (e.g.
translation service group) the SCCP routes traffic to the primary subsystem/node,
unless this is not accessible. In that case, the SCCP will divert traffic to the backup
subsystem/node. When the primary subsystem/node is accessible again, traffic is
shifted back (i.e. the dominant mode). Alternatively, the two subsystems/nodes can
operate in load-sharing mode, i.e. the SCCP shares the traffic equally between the
two subsystems/nodes.

ISS
MAP
TUP
INAP BSSAP ISUP
OMAP

Transaction ID Local
Reference
CIC

TCAP

Global
Signaling Connection Control Part
Title
(SCCP)
Translation

Message Transfer Part

(MTP)

Fig. 43

SN2073EU01SN_0001
63
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

4.3.2 Distribution of the SCCP Functions in the SSNC

The SCCP functions are mainly located in the SSNC. Only user specific parts still in
EWSD located. With SSNC configuration the entire SCCP administration runs via the
Q3 interface. The corresponding MML commands of the CP are blocked.
The following SCCP function are implemented in the SSNC:
l a SCCP maintenance function
l a SCCP broadcast function
l a SCCP sub-management function on the SM and
l a SCCP routing function including GTT on the SLTs.

64 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

ASN MP:SLT

LTG LTG L2/L3MH

LIC AMX SCCP-All.

SCOC MP:SLT/GTT
SCLC SN
L3MH
SCCP-GTT
SCCP-Acc.

MP:SM

SCMT
CP113 SCMG

SCRC
MP:OAM
SCLC
SCRC
SCOC
SCMG

SCLC: SCCP Connectionless Control SCOC: SCCP Connection Oriented Control

SCMG: SCCP Management SCRC: SCCP Routing Control
GTT: Global Title Translation SCMT: SCCP Maintenance

Fig. 44

SN2073EU01SN_0001
65
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

4.3.3 Overview: Administration of the SCCP General Data

SCCP as User of MTP

From the point of view of the MTP, the SCCP is one of the maximum 16 possible
users (0..15) that can be distinguished from the service information SI. As shown in
the diagram, NM has SI=0, SI=1 addresses testing and maintenance, and SI=3
addresses the SCCP.
While the MML-Task "CR C7USER" is required for announcing the trunk related user
parts (ISUP, TUP..) in the CP, the Q3-Tasks CRSPLNKLOC / CRSPLNKREM are
used to announce the non trunk related user part SCCP in the SSNC:
l CRSPLNKLOC creates the own SCCP (SCCP linkage local)
l CRSPLNKREM announces the partner SCCP (s), i.e., the users in the other nodes
with which SCCP messages are exchanged (SCCP linkage remote)

Local and Remote Subsystems of the SCCP

The function of the SCCP is divided into user-specific parts that are activated by
creating so-called subsystems. A distinction must be made here between:
l Local subsystems (SCCP users in the own signaling point)
A local subsystem must be created for each local user in each network node.
l Remote subsystems (users in remote signaling points)
For every destination point to which an SCCP message is signaled directly, the
remote subsystem must be created in the own node in accordance with the
function of the respective network node.
Each subsystem identifies itself by an SCCP calling party address, which may be
included in the SCCP part of a signaling message for rerouting of the answer.
The subsystems are addressed by means of subsystem numbers; the subsystem
numbers are, as a rule, standardized. National applications with national subsystem
numbers may also exist, though.

Creation sequence in SSNC:

l CR SPLNKLOC stores data about the SCCP in the own node.
l CR SPLNKREM creates a link to an SCCP in a remote signaling node, with which
SCCP messages are exchanged.
l CR SPSSN links a subsystem name with a subsystem number
l CR SPAPLOC announces the local SCCP subsystems.
l CR SPAPREM announces the SCCP subsystems in the other signaling nodes,
with which MAP-messages are exchanged.
l CR SPCLGPA creates a global title address for a local SCCP subsystem.

66 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

SCCP Access Point Local

(CRSPAPLOC)
OM
BSSAP INAP ISS
SCCP Access Point Remote AP
(CRSPAPREM)

SCCP Calling Party Address

(CRSPCLGPA)

TCAP

SCCP Subsystem Number

(CRSPSSN)

254 ............ 241 ........11........... 4 ............. 1

SCCP

SCCP Linkage Local

(CRSPLNKLOC)
SCCP Linkage Remote
(CRSPLNKREM)

15 ................. 5 4 3 2 1 0

MTP

Fig. 45 Creation sequence for SCCP and its subsystems

SN2073EU01SN_0001
67
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

4.3.4 Overview: Global Title Translation Database

Structure of a Global Title

The GTT function makes it unnecessary for SCCP-users to store knowledge of
SCCP signaling routing information (network and signaling point code).
This addressing information is contained in a global title which
l might be derived from an "access" address to a telecommunications network (e.g.
subscriber number, IMSI)
l might represent, in combination with the subsystem number SSN (in case it is not
implicitly embedded as address information in the global title itself) either:
a) an unambiguous identification of an SCCP-user in a signaling network (e.g. IN
services in a single SCP), or
b) a logical service address of any SCCP-user that is capable of providing a
requested service (e.g. IN services in a single - or pair of SCPs).
A Global Title GT consists of:
l a sequence of GT digits or other information elements (GTAI)
l a numbering plan (NP), e.g. E.164, E.214,....
l a nature of address indicator (NA) identifying the scope (network, geographical
region) in which a number is valid
l a translation type (TT) to distinguish different application of the same GTAI,NP and
NA combinations

Application of GTT
A point code for a signaling destination is only unique within an SS7 network. In a
network each operator may assign point codes for its own network. Therefore, in
order to address network nodes in another network, global titles have to be used.
These global titles are translated into the point code of the foreign network in the
gateways (nodes supporting more than one network).
When the result of the global title translation is a point code in another network than
the network in which the message is received, the calling party address (if provided
as a national global title) has to be translated into an international significant number.
When specific services provided in signaling points are addressed via a global title,
they can easily be relocated to other signaling points within the network. To do this, it
is only necessary to update a (few) centralized global title database(s). On the other
hand, if the services were addressed via their destination point code (DPC) the
routing tables would have to be updated in every single network node that addresses
the services.

68 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

GTT
Translation Type
(CRSPTT)
GT Translator
(CRSPGTTRL)
GT Rule
CRSPGTRUL)
GT Conv. Rule
(CRSPGTCRUL)
Relay Entity Set
(CRSPRNS)
End Node Entity Set
(with/without SSN)
(CRSPENS/SSN)
Calling Party Addr. Conv
(CRSPCLGCON)

Fig. 46

SN2073EU01SN_0001
69
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

Structure of a SCCP-Global Title Message

To facilitate better understanding, the format of an SCCP GT message is described
below. It contains, for example, the routing label, the called party address and the
calling party address.
The service indicator of a global title message in the MTP routing label has the
value 3 for SCCP users.
The called party address can consist of signaling point code, global title, subsystem
number or a combination of these elements.
It can therefore contain:
l Address indicator
consisting of routing indicator, global title indicator, SSN indicator and point code
indicator.
Þ Routing indicator
“0” routing is performed on the basis of the global title in the address “1”
routing is based on the DPC in the MTP routing label and the subsystem
number in the called party address
Þ Global title indicator
contains the global title indicator which can be coded as follows, e.g.:
0000 no global title included
0100 global title includes translation type, numbering plan, encoding
scheme and nature of address indicator
Þ SSN indicator
“1” indicates that the address contains a subsystem number.
Þ Point code indicator
“1” indicates that the address contains a signaling point code.
l Signaling point code
l Subsystem number
l Global title
a global title, e.g. the international ISDN number of a mobile subscriber, consists of
the following format parameters in addition to the global title address information:
Þ Translation type identification >TTID<: for example, TTID is used to transfer
the message to a corresponding GTT function, or it identifies a service
provided e.g. screening the number, freephone service...
Þ Numbering plan >NP<
Þ Nature of address indicator >NA<

70 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

The global title is translated by the SCCP into the corresponding signaling point code.
This signaling point code can be derived:
l by analyzing the global title parameter (GTDIGTR) and
l by translating the global title digits (GTRULE)

8 . B it 7 . B it 6 . B it 5 . B it 4 . B it 3 . B it 2 . B it 1 . B it

network indicator XX service information service information oktett

destination point code

MTP Routing Label

orgination point code

signaling link selection field

message type code
protokoll class
X Routing-ind. Global Title indicator SSN-ind. Point Code-ind. address indicator

signaling point code

called party
subsystem number
address
translation type
numbering plan encoding scheme
nature of address indicator Global Title

address information

X Routing-ind. Global Title indicator SSN-ind. Point Code-ind. address indicator

signaling point code

callin g party
subsystem number add ress
translation type

numbering plan encoding scheme

nature of address indicator Global Title

address information

Data

Called Party Address (Adresse des gerufenen Teilnehmers)

Calling Party Address (Adresse des rufenden Teilnehmers)

Fig. 47

SN2073EU01SN_0001
71
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

72 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

5 Exercise

SN2073EU01SN_0001
73
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

74 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

Exercise 1
Title: SS7 administration
Objectives: The participant will be able to administrate SS7 signaling
connections
Prerequisite: SS7 knowledge

Task
Find the answers to the following questions, by entering the right commands at the
SSNC!
Query
Question Q3 Task Answer
Find out all own signaling
addresses of the node you're
working on!
Which signaling networks are
handled in the SSNC you're
working on?
Find out all signaling destination
points, created in your switch!
Which MPs are used for
processing signaling links?
Which LIC ports are used for
connecting CCS7 links directly?
Which LTG ports are used for
connecting CCS7 links?
What are the names of the inward
TGRPs?
Find out the names of the TGRPs
that carry signaling information
only!
Which local SCCP subsystems
are created in your switch?
Which remote SCCP subsystems
are created in your switch?

SN2073EU01SN_0001
75
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

76 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

Exercise 2
Title: Level1 for SS7
Objectives: The participant is able to create the SS7 level one connection
Pre-requisite: SS7 knowledge

SN2073EU01SN_0001
77
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

Task
Create the SS7 level one connection via EWSD for the destination Nürnberg and
Stuttgart according the figure.

Outward Inward

0 0

16 MP
Nürnberg 1 1
LTG LTG 4
16
1
2 0-5 0-2 2

2
3 3

SN 4 MP
LIC AMX
16
ASN
5
0 0
5 1

1 1
LTG LTG 6

Stuttgart 2
0-6 0-3 2 7

16 17
3 3
8
MP
6

78 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

Query
Name the steps necessary for creation the SS7 level one connections via EWSD.
1. SS7 Trunk groups and Trunks

Command:

2. Interworking Trunk groups and Trunks

Command:

3. LIC Ports

Command:

4. PDC LINKS

Command:

5. Interworking Points

Command

6. Data link creation after SIGPOINT and SIGDP creation

Command:

SN2073EU01SN_0001
79
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

80 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

Exercise 3
Title: SS7 net creation
Objectives: The participant is able to create the SS7 net.
Pre-requisite: SS7 knowledge

Task
Create the SS7 net for the SPC 1-1-1-1 die SS7 according the figure below.

2-2-2-2
Nürnberg 3-3-3-3
Stuttgart

NAT0
TELECOM
ID=1

LS33
LS22

1-1-1-1
München

SN2073EU01SN_0001
81
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

82 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

Query
1. Creation of the signaling points
a) Creation of the own signaling point
Command Parameter Value
CR SIGPOINT Net name
Net ID
Signaling point type
Net indicator
SPC
TFP TFA broadcast
TFR compatibility
Alarm Profile Mp

b) Creation of the other signaling points

I) For DPC Nürnberg
Command Parameter Value
CR SIGDP Net ID
DPC
DPC name
Loadsharing key

c) For DPC Stuttgart

Command Parameter Value
CR SIGDP Net ID
DPC
DPC name
Loadsharing key

SN2073EU01SN_0001
83
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

2. Creation of the Link Sets

a) To DPC Nürnberg
Command Parameter Value
CR SIGLSET Net ID
Link set name
Adjacent DPC
Congestion method
Alarm profile MP

b) To DPC Stuttgart
Command Parameter Value
CR SIGLSET Net ID
Link set name
Adjacent DPC
Congestion method
Alarm profile MP

84 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

3. Creation of the Routes

a) Route to Nürnberg
Command Parameter Value
CR SIGROUTE Net ID
DPC
Linkset name
Priority

Command Parameter Value

CR SIGROUTE Net ID
DPC
Linkset name
Priority

b) Route to Stuttgart
Command Parameter Value
CR SIGROUTE Net ID
DPC
Linkset name
Priority

Command Parameter Value

CR SIGROUTE Net ID
DPC
Linkset name
Priority

SN2073EU01SN_0001
85
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

4. Creation of the signaling data link (nailed up connection)

a) To DPC Nürnberg
Command Parameter Value
CR SIGDLLIC Net Id
Data link name
Adjacent DPC
MP
IWP

Command Parameter Value

CR SIGDLLIC Net ID
Data link name
Adjacent DPC
MP
IWP

86 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

b) To DPC Stuttgart
Command Parameter Value
CR SIGDLLIC Net ID
Data link name
Adjacent DPC
MP
IWP

Command Parameter Value

CR SIGDLLIC Net ID
Data link name
Adjacent DPC
MP
IWP

Command Parameter Value

CR SIGDLLIC Net ID
Data link name
Adjacent DPC
MP
IWP

SN2073EU01SN_0001
87
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

5. Creation of the signaling links

a) For LS22 to Nürnberg
Command Parameter Value
CR SIGLINK Net ID
Link set name
Link code
Data link name
Profile name

Command Parameter Value

CR SIGLINK Net ID
Link set name
Link code
Data link name
Profile name

88 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

b) For LS33 to Stuttgart

Command Parameter Value
CR SIGLINK Net ID
Link set name
Link code
Data link name
Profile name

Command Parameter Value

CR SIGLINK Net ID
Link set name
Link code
Data link name
Profile name

Command Parameter Value

CR SIGLINK Net ID
Link set name
Link code
Data link name
Profile name

SN2073EU01SN_0001
89
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

6. Release the signaling links and destination

a) Unlock the signaling links
Command Parameter Value
MOD SIGLINK Net Id
Linkset name
Link code
Admin. state

b) Unlock the destination

Command Parameter Value
MOD SIGDP Net ID
DPC
Admin. state

90 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

6 Solutions

SN2073EU01SN_0001
91
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

92 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

Solution 1
Title: CCS7 administration
Objectives: The participant will be able to administrate CCS7 signaling
connections
Pre-requisite: SS7 knowledge

Task
Find the answers to the following questions, by entering the right commands at the
SSNC!
Query
Question Q3 Task Answer
Find out all own signaling DISPSIGPOINT;
addresses of the node you're
working on!
Which signaling networks are DISPSIGPOINT;
handled in the SSNC you're
working on?
Find out all signaling destination DISPSIGDP;
points, created in your switch!
Which MPs are used for DISPMP;
processing signaling links? -> load model = SLT
Which LIC ports are used for DISPLICPRTE1;
connecting CCS7 links directly?
Which LTG ports are used for DISPTRUNK:TGNO=X,
connecting CCS7 links? LCOS=DIGSIG8;
What are the names of the inward DISPTGRP: TGNO=X,
TGRPs? GCOS=IWTGRP;
Find out the names of the TGRPs DISPTGRP: TGNO=X,
that carry signaling information GCOS=CCSLGRP;
only!
Which local SCCP subsystems DISPSPAPLOC;
are created in your switch?
Which remote SCCP subsystems DISPSPAPREM;
are created in your switch?

SN2073EU01SN_0001
93
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

94 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

Solution 2
Title: Level1 for SS7
Objectives: The participant is able to create the SS7 level one connection
Pre-requisite: SS7 knowledge

SN2073EU01SN_0001
95
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

Task
Create the SS7 level one connection via EWSD for the destination Nürnberg and
Stuttgart according the figure.

Outward Inward

0 0
16 MP
Nürnberg 1 LTG LTG 1
4
16 2 0-5 0-2 2

3 3 1

3
SN MP
4 LIC
16
AMX
ASN 5
5 1
0 0
6
1 LTG LTG 1
7
Stuttgart 2 0-6 0-3 2
8
16 17 3 3

MP
6

96 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

Query
Name the steps necessary for creation the SS7 level one connections via EWSD.
1. SS7 Trunk groups and Trunks
Command:
CR TGRP:TGNO=STUTTG,OPMODE=IC,GCOS=CCSLGRP;
CR TGRP:TGNO=NUERNB,OPMODE=IC,GCOS=CCSLGRP;
CR TRUNK:TGNO=STUTTG,LTG=0-5,LC=2-16,LCOS=DIGSIG8;
CR TRUNK:TGNO=STUTTG,LTG=0-6,LC=3-16,LCOS=DIGSIG8,TRRANGE=2;
CR TRUNK:TGNO=NUERNB,LTG=0-5,LC=1-16,LCOS=DIGSIG8;
CR TRUNK:TGNO=NUERNB,LTG=0-6,LC=0-16,LCOS=DIGSIG8;

2. Interworking Trunk groups and Trunks

Command:
CR TGRP:TGNO=IWTG01,OPMODE=OG,GCOS=IWTGRP;
CR TGRP:TGNO=IWTG02,OPMODE=OG,GCOS=IWTGRP;
CR TRUNK:TGNO=IWTG01,LTG=0-2,LC=0-1,LCOS=DIGSIG8.TRRANGE=31;
CR TRUNK:TGNO=IWTG01,LTG=0-2,LC=1-1,LCOS=DIGSIG8,TRRANGE=31;
CR TRUNK:TGNO=IWTG02,LTG=0-3,LC=0-1,LCOS=DIGSIG8,TRRANGE=31;
CR TRUNK:TGNO=IWTG02,LTG=0-3,LC=1-1,LCOS=DIGSIG8,TRRANGE=31;

3. LIC Ports
Command:
CRLICPRTE1:LIC=2,LICport=1(2,3,4),Red.LIC=1,Traff.type=STM,

4. PDC LINKS
Command:
CRPDCLNK:LIC=1,LICPORT=1(2,3,4...),LTG=0-2,PDCLNK=0(1,2,3);

5. Interworking Points
Command
CRIWPSS7:IWP ID=1101,LIC=1,LIC port=1(2,3,4),Time slot=1(2-31);
6. Create signaling data link (after SIGPOINT and SIGDP creation)
Command:
CRSIGDLLTG:NetID=1,DPC=3-3-3-3, DL-Name=DL1-Stuttg, EQN=0-5-2-16,
MP=4;
CRSIGDLLTG:NetID=1,DPC=3-3-3-3, DL-Name=DL2-Stuttg, EQN=0-6-3-16,
MP=5;
CRSIGDLLTG:NetID=1,DPC=3-3-3-3, DL-Name=DL1-Stuttg, EQN=0-6-3-16,
MP=6;
CRSIGDLLTG:NetID=1,DPC=2-2-2-2, DL-Name=DL1-Nürnb, EQN=0-5-1-16,
MP=4;
CRSIGDLLTG:NetID=1,DPC=2-2-2-2, DL-Name=DL2-Nürnb, EQN=0-6-0-16,
MP=5;

SN2073EU01SN_0001
97
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

98 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

Solution 3
Title: SS7 net creation
Objectives: The participant is able to create the SS7 net.
Pre-requisite: SS7 knowledge

Task
Create the SS7 net for the SPC 1-1-1-1 die SS7 according the figure below.

2-2-2-2
Nürnberg 3-3-3-3
Stuttgart

NAT0
TELECOM
ID=1

LS33
LS22

1-1-1-1
München

SN2073EU01SN_0001
99
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

100 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

Query
1. Creation of the signaling points
a) Creation of the own signaling point
Command Parameter Value
CR SIGPOINT Net name TELECOM
Net ID 1
Signaling point type STEP
Net indicator Nat0
SPC 1-1-1-1
TFP TFA broadcast NO
TFR compatibility TRUE
Alarm Profile Mp MAJNOESC

b) Creation of the other signaling points

I) For DPC Nürnberg
Command Parameter Value
CR SIGDP Net ID 1
DPC 2-2-2-2
DPC name Nürnberg
Loadsharing key 0

c) For DPC Stuttgart

Command Parameter Value
CR SIGDP Net ID 1
DPC 3-3-3-3
DPC name Stuttgart
Loadsharing key 0

SN2073EU01SN_0001
101
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

2. Creation of the Link Sets

a) To DPC Nürnberg
Command Parameter Value
CR SIGLSET Net ID 1
Link set name LS22
Adjacent DPC 2-2-2-2
Congestion method international
Alarm profile MP MAJNOESC

b) To DPC Stuttgart
Command Parameter Value
CR SIGLSET Net ID 1
Link set name LS33
Adjacent DPC 3-3-3-3
Congestion method international
Alarm profile MP MAJNOESC

102 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

3. Creation of the Routes

a) Route to Nürnberg
Command Parameter Value
CR SIGROUTE Net ID 1
DPC 2-2-2-2
Linkset name LS22
Priority 1

Command Parameter Value

CR SIGROUTE Net ID 1
DPC 2-2-2-2
Linkset name LS33
Priority 2

b) Route to Stuttgart
Command Parameter Value
CR SIGROUTE Net ID 1
DPC 3-3-3-3
Linkset name LS33
Priority 1

Command Parameter Value

CR SIGROUTE Net ID 1
DPC 3-3-3-3
Linkset name LS22
Priority 2

SN2073EU01SN_0001
103
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

4. Creation of the signaling data link (nailed up connection)

a) To DPC Nürnberg
Command Parameter Value
CR SIGDLLIC Net Id 1
Data link name Nürnb1
Adjacent DPC 2-2-2-2
MP 4
IWP 1201

Command Parameter Value

CR SIGDLLIC Net ID 1
Data link name Nürnb2
Adjacent DPC 2-2-2-2
MP 5
IWP 1202

104 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

b) To DPC Stuttgart
Command Parameter Value
CR SIGDLLIC Net ID 1
Data link name Stuttg1
Adjacent DPC 3-3-3-3
MP 4
IWP 1101

Command Parameter Value

CR SIGDLLIC Net ID 1
Data link name Stuttg2
Adjacent DPC 3-3-3-3
MP 5
IWP 1102

Command Parameter Value

CR SIGDLLIC Net ID 1
Data link name Stuttg3
Adjacent DPC 3-3-3-3
MP 5
IWP 1103

SN2073EU01SN_0001
105
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

5. Creation of the signaling links

a) For LS22 to Nürnberg
Command Parameter Value
CR SIGLINK Net ID 1
Link set name LS22
Link code 0
Data link name Nürnb1
Profile name ITU BASIC64

Command Parameter Value

CR SIGLINK Net ID 1
Link set name LS22
Link code 1
Data link name Nürnb2
Profile name ITU BASIC64

106 SN2073EU01SN_0001
© 2002 Siemens AG
Administration of the SS7 Network in EWSD Powernode / hiQ9200 Siemens

b) For LS33 to Stuttgart

Command Parameter Value
CR SIGLINK Net ID 1
Link set name LS33
Link code 0
Data link name Stuttg1
Profile name ITU BASIC64

Command Parameter Value

CR SIGLINK Net ID 1
Link set name LS33
Link code 1
Data link name Stuttg2
Profile name ITU BASIC64

Command Parameter Value

CR SIGLINK Net ID 1
Linkset name LS33
Link code 2
Data link name Stuttg3
Profile name ITU BASIC64

SN2073EU01SN_0001
107
© 2002 Siemens AG
Siemens Administration of the SS7 Network in EWSD Powernode / hiQ9200

6. Release the signaling links and destination

a) Unlock the signaling links
Command Parameter Value
MOD SIGLINK Net Id 1
Linkset name LS33 (LS22)
Link code 0/1/2 (0/1)
Admin. state Unlocked

b) Unlock the destination

Command Parameter Value
MOD SIGDP Net ID 1
DPC 2-2-2-2 (3-3-3-3)
Admin. state Unlocked

108 SN2073EU01SN_0001
© 2002 Siemens AG