Information

Signaling
Signaling System Network Control
(SSNC)
A50016-D1109-K401-1-7618

Signaling System Network Control (SSNC)

Information
Signaling

Important Notice on Product Safety

Elevated voltages are inevitably present at specific points in this electrical equipment. Some of the
parts may also have elevated operating temperatures.
Non-observance of these conditions and the safety instructions can result in personal injury or in property damage.
Therefore, only trained and qualified personnel may install and maintain the system.
The system complies with the standard EN 60950 / IEC 60950. All equipment connected has to comply
with the applicable safety standards.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit
In elektrischen Anlagen stehen zwangslufig bestimmte Teile der Gerte unter Spannung. Einige Teile
knnen auch eine hohe Betriebstemperatur aufweisen.
Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Krperverletzungen und
Sachschden fhren.
Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die Anlagen installiert und
wartet.
Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene Gerte
mssen die zutreffenden Sicherheitsbestimmungen erfllen.

Trademarks:
All designations used in this document can be trademarks, the use of which by third parties for their
own purposes could violate the rights of their owners.

Copyright (C) Siemens AG 2000.

Issued by Information and Communication Mobile
Hofmannstrae 51
D-81359 Mnchen
Technical modifications possible.
Technical specifications and features are binding only insofar as
they are specifically and expressly agreed upon in a written contract.

A50016-D1109-K401-1-7618

Information
Signaling

Signaling System Network Control (SSNC)

This document consists of a total of 46 pages. All pages are issue 1.

Contents
1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2
2.1
2.1.1
2.1.2
2.1.3
2.2
2.3

SSNC Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MTP Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Message transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Message safeguarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Message handling and network management . . . . . . . . . . . . . . . . . . . . . .
SCCP Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Standalone STP functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10
10
10
11
13
15
15

3
3.1
3.2
3.3
3.4
3.5
3.6

SSNC Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Main processor (MP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ATM Switching network (ASN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Line interface card (LIC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ATM Bridge processor, type C (AMPC) . . . . . . . . . . . . . . . . . . . . . . . . . . .
ATM Interface module (ATM230) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Standalone STP Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

16
16
18
20
21
23
23

4
4.1
4.2
4.3

SSNC Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Software architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Software units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Load model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

24
24
26
29

5
5.1
5.2
5.3
5.4
5.5
5.6
5.7
5.8
5.9

Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SS7 Screening . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SS7 Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
High-Speed Signaling Links (HSL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multiple SS7 Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Global Title Translation (GTT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MTP Route Verification Test (MRVT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Extended load sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SS7 Traffic structure measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Additional features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

30
30
30
31
31
31
31
32
33
33

SSNC Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

7
7.1
7.2
7.3

SSNC Operation, administration and maintenance . . . . . . . . . . . . . . . . . .

Operations, maintenance and administration part (OMAP) . . . . . . . . . . . .
Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SSNC Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

A50016-D1109-K401-1-7618

36
36
39
41

Signaling System Network Control (SSNC)

Information
Signaling

A50016-D1109-K401-1-7618

Information
Signaling

Signaling System Network Control (SSNC)

1 Introduction
The most modern and most efficient methods to control traffic to and from other network
nodes is Signaling System No. 7 (SS7). It transfers messages separately from user information (speech, data) along common channel signaling links.
The common signaling channels form a (logically) separate signaling network. They interconnect the signaling points.
Signaling points can be one or more of the following:
signaling end point (SEP)
signaling transfer point (STP)
signaling relay point (SRP)
The signaling points are integrated in the nodes of the communication network. Signaling transfer points can also be installed as independent nodes in the network (standalone STP, SRP).
A network node functioning as a signaling end point represents a point of origin or point
of destination for signaling messages. A network node functioning as a signaling transfer point receives signaling messages from a signaling point and passes them to another
signaling point. A network node functioning as a signaling relay point can perform global
title translation (GTT). A network node may function simultaneously as a signaling end
point, signaling transfer point and signaling relay point.
The Signaling System Network Control (SSNC) is responsible for the control of SS7
signaling traffic. The SSNC provides the protocol functions of the message transfer part
(MTP) and the signaling connection control part (SCCP) and the operations, maintenance and administration part (OMAP).
The SSNC offers maximum efficiency for SS7 signaling. It can also be used as a gateway between different networks, network operators or network topologies, such as ITUT 14 bit, ITU-T 24 bit and ANSI 24 bit. For such applications SSNC offers special features for recording and verifying the amount of traffic with adjacent network nodes and
also for protecting the own network against misuse. It is also possible to administer up
to 32 internal, independent networks. SSNC is a future-proof system which also supports the connection of SS7 high-speed signaling links (HSL).
Position in the system
The SSNC belongs to the signaling area of the network node. Its position in the system
is shown in Fig. 1.1.

A50016-D1109-K401-1-7618

Signaling System Network Control (SSNC)

Information
Signaling

Access

Switching

Analog, ISDN-BA,
V5.1, xDSL, IP

DLU

SN

LTG

Trunks, PBX, ISDN-PA,

V5.2, SS7 (56/64 kbit/s), CAS

LTG

Signaling
high-speed SS7 links
SSNC

Management (OA&M)

Control
MB

Switch
Commander

CP

CCG

Fig. 1.1

Functional areas and subsystems

Features
The SSNC is characterized by the following features:
Asynchronous transfer mode (ATM) technology
Interworking between synchronous transfer mode (STM) and ATM
Maximum system configuration with 1500 signaling links and more than
100,000 message signal units per seconds (MSU/s)
Optional 1.5-Mbit/s or 2-Mbit/s ATM based high-speed signaling link interfaces
(see Fig. 1.2)
Reduction in CP loads by moving the OA&M functionality to the SSNC
Cost-effective standalone solution
For detailed performance values, see SSNC Performance.

A50016-D1109-K401-1-7618

Information
Signaling

Signaling System Network Control (SSNC)

Structure
The SSNC Functions are spread over several units. This results in a high degree of flexibility. Adaptation to future requirements regarding message throughput and new features is possible, due to the scalability of the main processor platform.
The SSNC Hardware comprises the following units (Fig. 1.2):
Line interface card (LIC)
The Line interface card (LIC) converts incoming message streams from the SS7 networks from synchronous transfer mode with 1.5 Mbit/s or 2 Mbit/s to internal ATM
cell streams with 207 Mbit/s and vice versa. The LIC is also the interface to highspeed links. Up to 248 signaling channels (8 E1/DS1) or 8 high-speed signaling
links can be connected to a LIC.
Main processor (MP)
The Main processor (MP) is the key component of the SSNC.
Up to 50 MP exist in the maximum SSNC configuration:
1 MP up to a maximum of 47 MPs for signaling link termination (MP:SLT)
1 MP for signaling manager (MP:SM)
1 MP for statistics (MP:STATS)
1 MP for operation, administration and maintenance (MP:OAM)
The maximum system configuration allows the connection of 1500 signaling links
and a message throughput of more than 100 000 MSU/s.
ATM Switching network (ASN)
The ATM switching network (ASN) interconnects the individual MPs and links the
LICs to the MP:SLTs.
ATM Bridge processor, type C (AMPC)
The ATM bridge processor, type C (AMPC) is the interface between the ATM equipment on the ASN and the coordination processor 113C (CP113C). It converts packet-oriented data flows from the ATM area to the CP communication mode and vice
versa. For functional purposes the AMPC belongs to the SSNC, but it is located in
the module frame of the CP.
The mechanical design of the SSNC hardware is described in the Construction manual.
Interfaces
Fig. 1.2 illustrates the interfaces between the SSNC and
AMPC
2 x 207 Mbit/s per AMPC pair (optical fiber cable)
(see description Coordination processor 113C/CR (CP113C/CR))
Message buffer D (MBD)
16 x 207 Mbit/s up to 32 x 207 Mbit/s
(see description Message buffer D (MBD))
LTG
4 x 1.5 Mbit/s or 4 x 2 Mbit/s
(see description Line/trunk group N (LTGN))
NetManager
TCP/IP via Ethernet

A50016-D1109-K401-1-7618

Signaling System Network Control (SSNC)

Information
Signaling

1,5 / 2 Mbit/s
STM
LTG

trunks and
SS7 links
(56/64 kbit/s)

SN

LTG

SSNC
1,5 / 2 Mbit/s
STM/ATM
LIC
conventional
SS7 links
(56/64 kbit/s)
SS7-high-speed
signaling links
(1,5 / 2 Mbit/s)

207 Mbit/s
ATM

ASN

LIC
MP:SLT

MP:SLT
MP:SM
MP:STATS
Switch
Commander

TCP / IP

MP:OAM
207 Mbit/s
ATM
CP

Fig. 1.2

AMPC

MBD

Hardware architecture of the SSNC with external/internal interfaces

In addition to the high-speed signaling links also 56/64 kbit/s signaling links can be directly connected to the SSNC.
Internally the SSNC uses 207 Mbit/s ATM interfaces.

A50016-D1109-K401-1-7618

Information
Signaling

Signaling System Network Control (SSNC)

Standalone STP
The SSNC has a separate platform MP:OAM. As a consequence, the SSNC operation,
administration and maintenance can be performed independently of the coordination
processor (CP). This means that the SSNC can be used as a cost-effective standalone
STP without any other functional units (i.e. CP, SN, LTG) (Fig. 1.3).
A standalone STP can be used to implement the highest SS7 network level. It can also
be used as SS7 gateway between different SS7 networks.

SSNC

LIC

SS7 links
(56/64 kbit/s)
SS7-high-speed signaling links
(1,5 / 2 Mbit/s)

207 Mbit/s
ATM

ASN

LIC

1,5 / 2 Mbit/s
STM/ATM

MP:SLT

MP:SLT
MP:SM
MP:STATS
Switch
Commander

Fig. 1.3

A50016-D1109-K401-1-7618

TCP / IP

MP:OAM

Standalone STP

Signaling System Network Control (SSNC)

Information
Signaling

2 SSNC Functions
The functions of Signaling System No. 7 (SS7) are specially suited for the requirements
of digital networks. The separation of the functions into a common message transfer part
(MTP) and several specific user parts (UP) results in a high degree of flexibility.

2.1

MTP Functions
The functions of the MTP are divided into three levels:
Level 1 Message transfer (Q.702)
Level 2 Message safeguarding (Q.703)
Level 3 Message handling and network management (Q.704).

2.1.1

Message transfer
The MTP level 1 function message transfer is the physical interface to the signaling system no. 7. It implements the transmission function of the signaling channels within the
network node. In the EWSD the line/trunk group (LTG) and the SSNC share this task.
The message transfer is handled in the SSNC by the line interface card (LIC), the ATM
switching network (ASN) and the MP:SLT.
The following functions are performed in the receiving direction (see Fig. 2.1):
Reception of incoming SS7 messages as an STM byte stream in the LTG
Transfer of this byte stream from the LTG via the switching network (SN) to the LIC
In the LIC, packaging the bits that are contained in the time slot belonging to a signaling channel into ATM cells (AAL1)
Transport of the ATM cells from the LIC through the ASN to the relevant MP:SLT responsible for the signaling link
Conversion of the ATM cells to MTP signaling units which are passed to message
safeguarding.
The procedure is reversed in the transmit direction.
High speed signaling links bypass LTG and SN and arrive directly at the LIC already in
ATM cell format.

10

A50016-D1109-K401-1-7618

Information
Signaling

Signaling System Network Control (SSNC)

LTG
Reception of
SS7 messages
Transfer
to the SN and LIC

LIC
Level 1
functions

Packaging the bits into

ATM cells

Transport
to the SLT

ASN

Conversion of
ATM cells to MTP
signaling units

Fig. 2.1

2.1.2

SLT

Functions of message transfer in the receiving direction (level 1)

Message safeguarding
The functionality of the MTP level 2 message safeguarding is divided into (see Fig. 2.2):
Management
Reception of signaling messages
Transmission of signaling messages
It is handled in the SSNC unit MP:SLT.
The management function consists of:
Link state control
This function supervises and controls the signaling link operating status and automatically takes faulty links into operation again.
Processor outage control
A processor outage in the adjacent network node is detected, and the message traffic is diverted to other signaling channels accordingly
Initial alignment control
This function activates the signaling channels and starts their initialization test.
The reception function consists of:
Alignment error rate monitoring
This function checks the number of errors that occur during the initial synchronization in order to be able to align the links.

A50016-D1109-K401-1-7618

11

Signaling System Network Control (SSNC)

Information
Signaling

Error rate monitoring

This function monitors the number of message errors occurring on a signaling link
during a specified period. The level 3 manager is informed whenever a permitted
threshold value is exceeded.
Congestion control
This function monitors the reception, retransmission and transmission buffers by
means of counters. Congestion in the receive buffer is reported to the remote sender. Congestion in the sending direction is reported to the own level 3.
Reception control
Received messages and acknowledgements are monitored and verified.

The transmission function includes transmission control. It contains parts of the SS7
protocol and is divided into:
Basic error correction method
A transmitted message is stored in the retransmission buffer until a positive acknowledgement is received. The message is retransmitted on request.
Preventive cyclic retransmission
At times when no new messages are being transmitted but unacknowledged messages are still present in the retransmission buffer, these messages are retransmitted cyclically. Messages are also retransmitted if either a threshold for the number
of messages in the retransmission buffer or a threshold for the number of bytes to
be retransmitted is exceeded (forced retransmission).
Refer to the description Signaling System No. 7 (SS7) (Q.703) for information regarding
the general procedure for sending and receiving SS7 signaling messages.
High speed signaling links utilize the signaling ATM adaptation layer (SAAL) as level 2
protocol.

12

A50016-D1109-K401-1-7618

Information
Signaling

Signaling System Network Control (SSNC)

SLT
Link state control
Management
function

Processor outage control

Initial alignment control

Alignment error rate

monitoring

Level 2
functions
Reception
function

Error rate monitoring

Congestion control
Reception control

Transmission
function

Fig. 2.2

2.1.3

Transmission control

Functions of message safeguarding (level 2)

Message handling and network management

These message transfer part (MTP) level 3 functions ensure the transfer of signaling
messages from a specific user part of an origination point to the same user part in the
destination point. These functions are handled in the SSNC by the function units
MP:SLT and MP:SM (see Fig. 2.3).
The MP:SLT is responsible for the message handling. It includes the following functions:
Message routing
This function is used to determine an outgoing signaling link for a message signal
unit (MSU). Using the route description, the current route (signaling link set), from
which the signaling link is taken, is selected. The message is then sent along this
link.
Message discrimination
This function distinguishes the signaling messages received according to their destinations. If the messages are intended for the own network node, they are transferred via the message distribution function to the appropriate user part. If the
messages are destined to a different network node, they are transferred to the message routing function.

A50016-D1109-K401-1-7618

13

Signaling System Network Control (SSNC)

Information
Signaling

Message distribution
This function identifies the user part for which the message is intended. The messages are then transferred directly to the user parts or to the user allocation functions.

The MP:SM is responsible for the signaling network management. This is subdivided
into:
Signaling traffic management
This function is responsible for diverting the signaling traffic in the event of an error:
to a different signaling link on the same route in the case of disturbances on a signaling link (changeover), or to an alternative route in the case of disturbances on a
route (rerouting).
Signaling link management
This function has to activate/deactivate the link sets and their links in response to
input commands or link errors.
Signaling route management
This function has to send status information regarding the signaling network and its
own MTP to adjacent MTPs in the event of errors occurring in the SS7 network or in
its own MTP.
The testing & maintenance function (ITU-T Q.707) tests the path from the functions
own level 3 to the adjacent level 3. The test is performed when a link is activated per
configuration request or restored after failure, after a remote processor outage situation
has ceased and periodical for active links on configuration demand.

14

A50016-D1109-K401-1-7618

Information
Signaling

Signaling System Network Control (SSNC)

SLT
Message routing

Message
handling

Message discrimination

Message distribution

Level 3
functions
SM
Signaling traffic management
Signaling network
management

Signaling link management

Signaling route management

Testing and
maintenance

Fig. 2.3

2.2

Test signaling links

(for cutover)

Message handling and network control functions (level 3)

SCCP Functions
The SCCP provides additional addressing and message transport functions for SS7. For
details on its realization in the SSNC see Signaling Connection Control Part (SCCP).

2.3

Standalone STP functions

The task of a standalone STP is to forward incoming signaling messages. There are no
trunk-related user part functions.
Because all required STP functions are already included and because of the SSNCs
own MP:OAM platform it is easy to deploy the SSNC as a stand-alone STP.

A50016-D1109-K401-1-7618

15

Signaling System Network Control (SSNC)

Information
Signaling

3 SSNC Hardware
The SSNC comprises the following hardware units:
Main processor (MP)
ATM Switching network (ASN)
Line interface card (LIC)
ATM Bridge processor, type C (AMPC)
The hardware units MP, LIC and AMPC are connected to the ASN via the ATM Interface
module (ATM230).
For a standalone STP configuration the AMPC is not required.

3.1

Main processor (MP)

The SS7-specific functions are implemented on the different main processors (MP).
Each MP comprises two Main processor units (MPU) and an Alarm indication module
(ALI).
The two main processor units operate microsynchronously - i.e., each MPU processes
the same sequence of commands on the same clock cycle. To guarantee this, both
MPUs are initialized with identical states and all data are transmitted synchronously to
the two MPUs. The state of each MPU is checked at regular periods. The result is transmitted to the other MPU via the cross link (XLink) and compared with the test data generated there.
If a hardware fault occurs in one of the two MPUs which leads to a loss of the microsynchronous parallel operation, both of them perform routine tests. The MPU that detects
that it is faulty switches itself off. Once the faulty unit has been replaced, the new MPU
must be synchronized. Each MPU is responsible for detecting its own faults and reporting them to the other MPU. This hardware self-fault detection function ensures that the
faulty MPU is taken out of operation.
The two MPUs are connected via the ATM interface (ATM230) with the ASN. Both
MPUs receive ATM cells but only one of the two (the active MPU) transmits ATM cells.
Main processor units (MPU)
The MPU consists of the following major functional units located on one hardware module (see Fig. 3.1):
Intel P54CS (PP150-VRT) Pentium Processor (CPU).
ATM interface chip (ATM230)
The internal system communication and the loading of the system software are performed via this chip. The ATM230 has a line capacity of 207 Mbit/s to the ASN.
Cross Link (XLink)
This unit is a master/checker interface for communication and synchronization of the
two MPUs. In addition, the synchronization between ATM230 and processor activities is performed here along with checks on the clock generation.
Boot flash EPROM (FEPROM)
Each of the three FEPROMs has a capacity of 2 Mbytes. The FEPROMs contain the
boot software and hardware test programs needed for startup of the MPU. The
FEPROMs are connected with the ATM230 bus.
Small Computer System Interface (SCSI)
Supports the connection of a magnetic disk device (MDD) and magneto-optical disk
device (MOD). The MDD is a device used as an off-board mass storage for the stan-

16

A50016-D1109-K401-1-7618

Information
Signaling

Signaling System Network Control (SSNC)

dalone STP with a capacity of 9 GByte. The MOD is used to enable loading of software and configuration data into the MP:OAM. The maximum data transfer rate on
a SCSI bus is asynchronously 7 Mbyte/s and synchronously 10 Mbyte/s.
Power supply unit (PSU)
Each MPU has its own power supply. Power failure in an MPU in a redundant system
does not cause an alarm if the other MPU is in order.
Ethernet interface
This interface is used for connection to a LAN.

Alarm indication module (ALI)

The main processor (MP) is additionally equipped with an alarm indication module (ALI).
Unlike the MPU, the ALI is not duplicated. The ALI indicates the alarm status of the system. It is connected via two serial ports with the two main processor units. Only the active MPU controls the ALI. Two power supply units, each with 12 V / 500 mA, provide
power.
The ALI has the following main interfaces:
16 inputs for external alarms
4 inputs for internal alarms, for example, to monitor temperature
3 LEDs for critical (red), major (red) and minor (yellow) alarms
4 relays for critical, major, minor and PCM alarms
2 LEDs (red, green) for the status of the ALI (controlled by a watchdog and MPU)
combined V.24 radio clock interface
monitoring of total MPU failure
LAN
MPU0

MOD

MDD

ACCG0
LAN

ATM230

ALI

AMXE1

Radio
Clock

XLink
Alarm
Inputs/
Outputs

AMXE1
ATM230
LAN
ACCG1
MPU1

Fig. 3.1

A50016-D1109-K401-1-7618

MOD

MDD

Structure of the MP hardware

17

Signaling System Network Control (SSNC)

3.2

Information
Signaling

ATM Switching network (ASN)

The ATM switching network (ASN) comprises 2 ATM multiplexers/demultiplexers and
the ATM switching core module for ASN40 (ASMG16/16) (see Fig. 3.2).
The ATM multiplexer (AMX) consists of an ATM Multiplexer, type E (AMXE) and ASN
Controller and clock generator (ACCG). The ACCG monitors the AMXE and provide the
clock for the AMXE.
The ATM Multiplexer for ATM switching network (GMX) has up to 8 GMX:E multiplexers.
In addition, the ATM Switching core module for ASN40 (ASMG16/16) is located in the
ATM switching network. A separate ACCG controller monitors the GMX and ASMG. The
power supply unit PSAG is used for supplying power to the ASMG.
The central parts of the ASN (AMX, GMX, ASMG) are duplicated.
ATM Multiplexer, type E (AMXE)
The ATM multiplexer, type E (AMXE) is used in the SSNC as a concentrator stage to
the ASN. Up to 32 peripheral ports are possible between the AMXE and the peripheral
units line interface card (LIC) or main processor unit (MPU). Each of the ports is connected with the AMXE via one or two STM1-equivalent ATM interfaces (each with
207 Mbit/s). The ATM traffic from these peripheral units is concentrated by the AMXE
into up to 16 high-speed ATM links to the ASMG. In the opposite direction, the AMXE
distributes the ATM traffic from the ASMG to the different ATM ports of the peripheral
units. The interfaces between the AMXE and the peripheral units are implemented by
means of electrical connections.
The AMXE itself is controlled via the ACCG.
ASN Controller and clock generator (ACCG)
The ACCG monitors and controls the ATM multiplexer, type E (AMXE). In addition, it
supports the clock pulse for the AMXE as well as for the peripheral units LIC and MPU.
The peripheral control platform (PCP) in the ACCG controls the configuration, testing,
OAM and communications with the MPU. The hardware of the PCP is based on the INTEL 80386EX controller.
Communication with the MPU is performed using the internal transport protocol (ITP).
ATM Multiplexer for ATM switching network (GMX)
The GMX has the function of multiplexing sixteen 207-Mbit/s signals incoming from the
periphery and transferring them in the form of a 3.3-Gbit/s bit stream to the switching
network (SN). In opposite direction the 3.3-Gbit/s signals have to be demultiplexed into
16 serial 207-Mbit/s signals. The switching function ensures that the ATM cells are correctly directed to the 16 outputs. A GMX:E chip is responsible for the multiplex function,
while the switching network chip SE32/16B with an external multicast RAM is used for
the switching function. The GMX has an internal clock distribution system.

18

A50016-D1109-K401-1-7618

Information
Signaling

Signaling System Network Control (SSNC)

ATM Switching core module for ASN40 (ASMG16/16)

The module ASMG16/16 has two parallel connected SE-G16/8 switching network chips.
The chips switch ATM cells at a data rate of 3.3 Gbit/s (an STM-16 equivalent) in a configuration with 16 inputs and 8 outputs. The data rate per port is 3.3 Gbit/s
physically connected in parallel on 4 lines, each with 828 Mbit/s. In addition to the
two SE-G16/8 chips, the ASMG16/16 module has bipolar input and output drivers and
a clock module.

ASN
GMX

AMX
LIC

AMXE

207 Mbit/s
(STM-1)

GMX:E
1

3,3 Gbit/s
(STM-16)

ASMG
16/16

LIC
207 Mbit/s
(STM-1)

MPU

GMX:E
8

MPU
ACCG

Fig. 3.2

A50016-D1109-K401-1-7618

ACCG

3,3 Gbit/s
(STM-16)

Power
supply
unit

Structure of the ASN hardware

19

Signaling System Network Control (SSNC)

3.3

Information
Signaling

Line interface card (LIC)

The line interface card (LIC) provides a E1/DS1 interface with 2 Mbit/s and 1.5 Mbit/s
respectively. It converts the byte-oriented data stream on the STM side into a packetoriented data stream on the ATM side, and vice versa.
The LIC operates 1:1 redundantly i.e., both LICs receive ATM cells but only one LIC
sends this ATM cells to the ATM switching network (ASN). Each LIC has a common and
a specific hardware part (see Fig. 3.3). The common part (which is identical for all LICs)
contains the ATM part, the peripheral control platform (PCP), the power supply unit
(PSU) and clock distribution. Specific to the LIC is the physical layer (PHY) for providing
the physical interfaces.
The individual functions of the different hardware parts are as follows:
The ATM part implements the ATM layer functions. It is logically divided into an upstream and a downstream part.
The peripheral control platform (PCP) is based on the INTEL 80386EX controller.
This controller is used for all LIC types and the ACCG. The internal communication
to the MPU is implemented with the aid of the ATM adaptation layer, type 5 (AAL5)
and internal transport protocol (ITP).
The power supply unit (PSU) generates the necessary voltages (3.3 and 5 V).
The clock generator monitors one of the two ASN clock inputs from the ACCGs and
supplies the clock generators for the physical layer and ATM parts.
The physical layer contains the physical layer functions and also the ATM adaptation
layer, type1 (AAL1).

LIC
physical layer

ATM part

upstream
external
links

ATM multiplexer
ASN
downstream

ASN
clock

Fig. 3.3

20

clock
generator

power
supply
unit

peripheral
control
platform

Cross
channel
V.24

Structure of the LIC hardware

A50016-D1109-K401-1-7618

Information
Signaling

Signaling System Network Control (SSNC)

3.4

ATM Bridge processor, type C (AMPC)

The ATM bridge processor, type C (AMPC) is the interface between the ATM equipment
on the AMXE and the coordination processor 113C (CP113C). It converts the ATM data
streams to the CP communication mode. For functional purposes the AMPC belongs to
the SSNC, but it is located in the module frame of the CP.
The AMPC is realized as one module.
Like the other CP processors (BAP, CAP, IOC) the AMPC is connected to the bus for
common memory (B:CMY), which provides it with access to common memory (CMY).
Pairs of AMPCs are operated in the CP in order to increase availability. An AMPC pair
works in working/spare mode - i.e., both AMPCs receive the same messages simultaneously; messages are only sent by the active AMPC however.
In addition, the components of one AMPC are duplicated. Both halves operate microsynchronously in order to detect hardware faults faster. One half operates as master
and generates data for the memory or external interfaces. The other half checks that
both halves are running synchronously.
The AMPC hardware consists of the following major functional blocks (see Fig. 3.4):
Fiber optic transceiver type X (FOTX)
Each AMPC is connected to both halves of the duplicated AMXE via FOTX. The
FOTX modules are duplicated for redundancy reasons. If a FOTX or AMXE fails, the
AMPC can still communicate with the ATM network via the other FOTX and AMXE.
In the direction of the ATM network, the FOTX converts the electrical signals from
the AMPC to optical signals, which it sends to the AMXE. The FOTX has a clock recovery circuit for extracting the 207-MHz synchronization clock from the optical data
stream.
ATM interface chip ATM230
Two ATM230 and the two FOTX modules implement the 207-Mbit/s interface to the
ATM network. The FOTX module generates a 207-MHz clock and sends it to the two
ATM230. One of these chips is implemented as master, the other as checker. Signals are exchanged between both ATM230 for synchronization purposes.
Clock generator
The clock generator is not duplicated. It is monitored by the interface controller to the
B:CMY (AMPIFC) for the case that the clock frequency is not within the permissible
range.
Control unit (with microprocessor MC68EC040, with 50 MHz clock)
Used for handling the programs and protocols to transfer messages across the ATM
network.
Access and cycle control (PROAMP)
These ASICs control bus and memory for the microprocessor and the interface chip
ATM230.
Local memory unit (LMY) and flash EPROM (FEPROM)
The size of the LMY is 32 Mbytes. The FEPROM memory has 4 Mbytes. Neither
memory unit is duplicated.
Duplicate interface controller to the B:CMY (AMPIFC)
This unit constitutes the interface to the bus for common memory (B:CMY). Its central function is the transmission of messages between local memory (LMY) and the
B:CMY (and vice versa). In addition, the dynamically critical parts of the internal
transport protocol are implemented by means of two integrated processors in the
AMPIFC.

A50016-D1109-K401-1-7618

21

Signaling System Network Control (SSNC)

Information
Signaling

AMXE0

AMXE1

FOTX0

FOTX1

AMPC

ATM230 0
(Master)

ATM230 1
(Checker)
Clock
Generator

Control 0
(MC68EC040)

Control 1
(MC68EC040)

PROAMP0
(Master)

PROAMP1
(Checker)

LMY
FEPROM

AMPIFC
(Master)

B:CMY1
Fig. 3.4

22

AMPIFC
(Checker)

B:CMY0

Structure of the AMPC hardware

A50016-D1109-K401-1-7618

Information
Signaling

Signaling System Network Control (SSNC)

3.5

ATM Interface module (ATM230)

For the main processor (MP), ATM bridge processor, type C (AMPC) and message buffer D (MBD) platforms, the ATM interface module (ATM230) is the functional unit which
permits communication with all other system units, and the outside world, on an ATM
basis.
It forms the interface to the redundant ATM multiplexers, type E (AMXE) of the ATM
switching network, and for this purpose it has a duplicated high-speed interface
(HSATM) for the internal ATM cell format with 207 Mbit/s.
All ATM cells are transmitted simultaneously by the module via both switching network
halves. Received ATM cells are processed using redundant path combining. In this
case, only the first valid cell with the expected sequence number is passed on, while the
second cell from the other switching network half with the same sequence number is rejected.
In order to ensure reliable processing of received cell bursts, the ATM230 has a buffer
for 100 cells.
The ATM230 is connected via a 32 bit bus architecture to the memory system of the relevant platform and operates as a coprocessor with intelligent DMA features parallel to,
and independently of, the main processor.
The ATM230 allows two modules to be interconnected for microsynchronous operation
(MP platform), and for use on the AMPC it also permits monitoring of the ATM interface
on the transmit side in master/checker mode.
An important function of the ATM230 is to support and take over the realtime tasks for
the following signaling protocols:
internal transport protocol (ITP) on the basis of AAL3 and AAL5 for point-to-point
connections
integrated ring structures that are formed with the aid of ITP point-to-point connections
MTP level 1 and 2
ATM Adaptation Layer No.5 (AAL5)
ATM Adaptation Layer for signaling (SAAL)

3.6

Standalone STP Architecture

The SSNC can be used as a cost-effective standalone transfer point (STP) as no other
EWSD functional units (i.e. CP, SN, LTG) are required. In this configuration the AMPC
is not deployed.

A50016-D1109-K401-1-7618

23

Signaling System Network Control (SSNC)

Information
Signaling

4 SSNC Software
4.1

Software architecture
The SSNC software is split up into different applications which may sometimes have to
share a main processor (MP). The software structure is as follows (see Fig. 4.1):
Virtual CPU (VCPU)
Service provision unit (SPU) inc. Service addressing
Recovery suite (RS)
Virtual CPU (VCPU)
A virtual CPU (VCPU) is a logical group of processes which have to fulfill a common
function on a main processor (MP), and which share a specific portion of the CPU time
for this purpose. This portion of the CPU time is specified via the VCPU budget, which
is defined in an MP-specific Load model.
This ensures that different functions which are executed on one MP always receive a
fair portion of the CPU time and that processes of one function cannot completely exclude processes of a different function.
Example: Maintenance and administration processes run under the VCPU OAM. MTP
network management processes are assigned to the VCPU Network Management,
while MTP Level 2 and Level 3 functions run under the VCPU Protocol Handler.
Service provision unit (SPU)
The service provision unit (SPU) is a unit comprising processes and data modules with
a strong relationship of functions. The unit enhances safety and communications because data are exchanged only at operating system level between SPUs. The SPU is
designed in such a manner that it can be used platform-transparently. It can even be
used simultaneously on several platforms if similar tasks need to be processed in parallel.
Recovery suite (RS)
Within an SPU processes can be compiled in a recovery suite, which can be started individually without impairing the operation of the other software. With the recovery suite
(RS) one can restrict the effects of software errors.
Service addressing
Since the SPU design units can be reproduced on different processing platforms for
loadbalancing reasons, a system function is required for assisting in communications
between two SPUs. This function is known as service addressing.
Services provided by an SPU are announced to the system. If an SPU wishes to communicate with another SPU it calls the operating system. The calling SPU is given a universal buffer ID with which the communication to the called SPU is performed. The
communication can take place by sending messages or by calling remote procedures.

24

A50016-D1109-K401-1-7618

Information
Signaling

Signaling System Network Control (SSNC)

Appropriate communication mechanisms enable the following

increased fault tolerance:
If a processing platform is taken out of operation, both messages and remote procedure calls can be forwarded to another platform by additionally calling the service
addressing function.
more equal distribution of the load in the system:
If the processing platform is overloaded, the load can be diverted to another platform
by regularly calling up the Service Addressing function.

Processing platform 1
SPU m
SPU 1
Data module

Process

RS 1
Process

Process

Communication only via

the operating system
Operating system

Communication with other

processing platforms
Processing platform n

Fig. 4.1

Arrangement of software structure elements on a processing platform

Application program system (APS)

An application program system (APS) is the combination of all sub-APSs. A sub-APSs
is the collection of all service provision units (SPU) belonging to a single processing platform (e.g. MP:OAM).

A50016-D1109-K401-1-7618

25

Signaling System Network Control (SSNC)

4.2

Information
Signaling

Software units
The following software units are distinguished in the SSNC (see Fig. 4.2):
Signaling link termination (SLT)
Signaling manager (SM)
Statistics support platform (STATS)
Operation, administration and maintenance platform (OAM)
In addition to its actual software functions, every main processor (MP) contains the operating system (OS), the internal transmission protocol (ITP) and the driver software for
the ATM interface module ATM230.
SSNC

SLT

SM

OAM

STATS

MTP level 1
MTP level 2
SAAL
MTP level 3 (MH)
SCCP GTT
MTP/SCCP MEAS
HPDB
DBMS

MTP level 3 (NM)

SCCP (SCMG)
MTP/SCCP MTC
HPDB
DBMS

MTP/SCCP ADMIN
MTP/SCCP MEAS
MTP/SCCP MONIT
MTP/SCCP MTC
DBMS
OMAP

ASN

OS

ITP

ATM
230

OS

ITP

ATM
230

OS

ITP

ATM
230

measurement
collection

207 Mbit/s

207 Mbit/s

207 Mbit/s

207 Mbit/s
to CP
to LIC
to MBD

Fig. 4.2

26

Software function units in the SSNC

A50016-D1109-K401-1-7618

Information
Signaling

Signaling System Network Control (SSNC)

The main processor (MP) can operate as a software function SLT, as Signaling management (SM), as Statistics support platform (STATS), or as MP:OAM platform. Depending on the application, an MP can be assigned a particular Load model from a
number of predefined load models. In accordance with the selected load model, the
available processor time is divided among the individual virtual CPUs in order to meet
the individual function-dependent run-time requirements.
Signaling link termination (SLT)
The SLT is a software package containing the following functions:
MTP level 1 functions (message transfer)
MTP level 2 functions (message safeguarding)
Signaling ATM adaptation layer (SAAL)
MTP level 3 functions (message handling, MH, user part allocation, and parts of the
network management)
SCCP routing for incoming SCCP messages (inc. global title translation, GTT)
MTP/SCCP measurements (MEAS)
Database functions (HPDB and DBMS)
Screening functions
Depending on the performance requirements for the network node, the SSNC can be
configured with up to 47 MP:SLTs. Depending on the link load up to 60 conventional signaling links (64 kbit/s / 56 kbit/s) or two high speed signaling links (2 Mbit/s / 1.5 Mbit/s)
can be connected to each MP:SLT.
Signaling manager (SM)
The SM is a software package that contains the following SSNC management functions:
MTP level 3 network management (NM)
SCCP management (SCMG)
MTP/SCCP maintenance (MTC)
Database functions (high performance database, HPDB and database management
system, DBMS)
There is exactly one MP:SM in an SSNC.
Statistics support platform (STATS)
In addition to the two platforms MP:SLT and MP:SM, the SSNC also contains the platform MP:STATS. The SSNC measurement data are collected by the MP:STATS, formatted and sent at intervals of 5 or 15 minutes to the MP:OAM, which in turn writes the
data to the local hard disk. From there the data records are transferred to the relevant
processing centers.

A50016-D1109-K401-1-7618

27

Signaling System Network Control (SSNC)

Information
Signaling

Operation, administration and maintenance platform (OAM)

The platform MP:OAM, which only exists once in the SSNC, only performs OA&M tasks.
It contains the following functions:
MTP/SCCP administration (ADMIN)
MTP/SCCP measurements (MEAS)
MTP/SCCP monitoring and alarming (MONIT)
MTP/SCCP maintenance (MTC)
MTP/SCCP database management system (DBMS)
Operations, maintenance and administration part (OMAP)
Due to this separate OAM platform and the fact that it performs the functions listed
above, the SSNC can be operated, administered and maintained independently of the
CP. The database management system (DBMS) is the MTP/SCCP master database.
From there, SS7 relevant semipermanent and transient data in the EWSD database of
the CP are updated when necessary.
The operations, maintenance and administration part (OMAP) is also located on the
OAM platform. The ITU-T Q.751.n series of recommendations defines object models
containing managed objects which allow to administer SS7 data - e.g. routing data,
availability of SS7 managed items, measurements results etc. - via the Q3 interface.
Such Q3 models are provided for the following functions:
MTP (Q.751.1)
(see description Signaling System No.7 (SS7))
SAAL signaling links (Q.751.1)
MTP monitoring and measurements (Q.751.1 main body and Annex E)
(s. chapter 7.1)
MTP accounting and verification (Q.751.3)
MTP screening (Q.751.1 and adaptation of Q.751.3)
MTP route verification test - MRVT (Q.751.1 main body and Annex F)
SCCP (Q.751.2)
(see description Signaling Connection Control Part (SCCP))
SCCP monitoring and measurements (Q.751.2 and proprietary improvements)
(see description Signaling Connection Control Part (SCCP))
SCCP accounting and verification (Q.751.4)

28

A50016-D1109-K401-1-7618

Information
Signaling

Signaling System Network Control (SSNC)

4.3

Load model
To support the concept of the virtual CPU (VCPU) every main processor (MP) needs a
load model which defines the budgets for the VCPUs on this MP. In order to be able to
make optimum use of the available processor capacity on an MP in accordance with the
functions that are being executed on it, several different load models are defined, from
which the load model management assigns to each MP the most suitable model for the
function of the MP.
In order to achieve the maximum possible performance of the various functions, the load
model management provides the following functionalities:
Easy integration of a load model for an MP platform into the system.
Automatic adjustments to the VCPU budgets due to time-limited events so as to retain the performance and delay time requirements for situations of this kind.
Changes to current load model data without the MP platform having to perform a recovery.
All load model data are centralized in a service provision unit (SPU), which exists once
on each MP platform.

A50016-D1109-K401-1-7618

29

Signaling System Network Control (SSNC)

Information
Signaling

5 Features
Network consolidation requires powerful and scalable signaling nodes. Deregulation of
national telecommunication markets results in a multitude of networks with frequent network interworking. Besides superior performance and flexibility the SSNC therefore offers a number of new and innovative features:
SS7 Screening
SS7 Accounting
High-Speed Signaling Links (HSL)
Multiple SS7 Networks
Global Title Translation (GTT)
MTP Route Verification Test (MRVT)
Extended load sharing
SS7 Traffic structure measurement

5.1

SS7 Screening
Supervision of the message flow, especially in deregulated networks, calls for the use
of screening (firewall/policing) in Signaling System No. 7 (SS7). The SS7 Screening feature ensures that only authorized signaling traffic is forwarded. Unauthorized traffic is rejected and can be registered. The screening function has no effect on the link throughput
capacity.
The signaling system network control (SSNC) supports the following SS7 screening
functions:
Screening in the message transfer part (MTP)
Screening in the signaling connection control part (SCCP)

5.2

SS7 Accounting
The SS7 Accounting feature (based on ITU-T Q.751) is used for usage metering regarding Signaling System No. 7 (SS7) traffic between different operators. Usage metering
data can be recorded for messages in the message transfer part (MTP) as well as for
messages in the signaling connection control part (SCCP).
MTP Accounting records the traffic volume of transferred SS7 messages (number of
messages and number of bytes). Sent SS7 messages are recorded by MTP Accounting
Verification.
SCCP Accounting enables operators to determine what traffic is using the SCCP global
title translation (GTT) function in the own signaling transfer point (STP).

30

A50016-D1109-K401-1-7618

Information
Signaling

Signaling System Network Control (SSNC)

5.3

High-Speed Signaling Links (HSL)

The High-Speed Signaling Links (HSL) feature increases the bandwidth between SS7
network nodes. High-speed signaling links can, for example, be used to set up a very
powerful SS7 overlay network consisting of (fully or partially meshed) standalone signaling transfer points (STP). The signaling end points (SEP) of the SS7 network are connected to the assigned mated pairs of standalone STPs via conventional signaling links.
High-Speed Signaling Links can also be used to connect the service control points
(SCP) of an intelligent network (IN) to the standalone signaling transfer points (STP).

5.4

Multiple SS7 Networks

The Multiple SS7 Networks feature expands the range of network planning options in
deregulated markets. With this feature, up to 32 Signaling System No. 7 (SS7) routing
domains (internal networks) can be administered in one network node. This means that
a node can be connected to up to 32 separate signaling networks.
The Multiple SS7 Networks feature is fully compatible with ITU-T SS7 standards, i.e. it
is transparent for all SS7 protocols.

5.5

Global Title Translation (GTT)

Global Title Translation (GTT) is a powerful function for translating the address data
contained in SS7 messages from users of the signaling connection control part (SCCP).
This function allows SCCP users to use a centrally administered address system that is
independent of the MTP network (e.g. special service numbers).
Global Title Translation is used, for example, in the mobile radio network in connection
with international roaming and in the intelligent network (IN) for addressing the service
control point (SCP).

5.6

MTP Route Verification Test (MRVT)

The MTP Route Verification Test (MRVT) feature is a management function of Signaling
System No. 7 (SS7). This feature is used to verify the routing of signaling traffic between
an originating point and a destination point in the SS7 network. The test covers all relevant routing tables of the message transfer part (MTP). The test function works in a decentralized manner. Test commands are distributed to the nodes in the SS7 network.
Each network node checks the routes that pass through it, leading to the destination
node. This check covers, among other things, compliance with maximum length and absence of loops.

A50016-D1109-K401-1-7618

31

Signaling System Network Control (SSNC)

5.7

Information
Signaling

Extended load sharing

A distinction is made between load sharing for the message transfer part and for the signaling connection control part (SCCP).
MTP load sharing
Load sharing ensures that the signaling traffic is distributed as evenly as possible over
all signaling links and signaling transfer points (STP) in the network. In the case of MTP
load sharing of the SSNC, up to eight possible routes can be created per destination,
and these are divided into load sharing groups, i.e. routes with equal priority.
The signaling traffic can be distributed over the first two signaling linksets of a load sharing group. If one route (linkset) fails, this traffic is diverted to the next signaling link set
of the same load sharing group. Only when all routes of one particular load sharing
group have failed is the traffic transferred to the next load sharing group.
In addition the SSNC optionally provides an extended loadsharing algorithm in order to
compensate for an uneven SLS distribution in incoming message streams. Depending
on network configuration and traffic characteristics it is thus possible to distribute outgoing traffic over all available links of a linkset even if the SLS addresses only a subset of
them. An additional advantage of this option is that it can eliminate the need for detailed
agreements between operators regarding traffic distribution in network interconnection.
SCCP Loadsharing
In the SCCP, load sharing between main and backup translators is possible, as well as
load sharing between subsystems. Remote SCCPs can be combined to form translator
groups consisting of two main nodes and two backup nodes in which the same translations are performed. If a main node fails, the backup node takes over its task at once.
Load sharing between the two main or backup translators is possible.
Remote subsystems can be combined to form subsystem service groups consisting either of a main subsystem and a backup subsystem or of two main subsystems on which
the same service is available.
If a main subsystem fails, switchover to the backup subsystem takes place at once. Load
sharing via the main subsystems is possible.

32

A50016-D1109-K401-1-7618

Information
Signaling

Signaling System Network Control (SSNC)

5.8

SS7 Traffic structure measurement

The feature SS7 traffic structure measurement evaluates the message flow in the
SSNC. The data of every nth message (n=trace rate) is traced. The data in this file can
then be evaluated by the operator, and this statistical evaluation can be used to verify
the network design. For example, the ratio of transit signaling traffic to terminating signaling traffic can be determined.

5.9

Additional features
A number of additional features extend the SSNC functionality:
MTP networks can support destination point codes (DPC) and originating point
codes (OPC) with a length of 14 bits (ITU-T) or 24 bits (ITU-T/ANSI, for national application).
Enforcement of message length compatibility according to ITU-T Q.701 7.2.5.
In the event of a lengthy route overload (this could be due to a routing loop) the MTP
checks whether the OPC of received messages and of messages that are to be sent
on the overloaded route corresponds to its own point code. In this case the message
is rejected and counted as a routing error (routing loop). This information allows
the operator to take appropriate counter-measures.
If a message is transmitted on the same signaling link set as the one on which it was
received (ping-pong loop), this message is rejected and a TFP concerning the destination is sent to the adjacent node, with the result that the loop is removed without
any intervention by the operator.

A50016-D1109-K401-1-7618

33

Signaling System Network Control (SSNC)

Information
Signaling

6 SSNC Performance
The SSNC uses the main processor (MP) as signaling manager (MP:SM), signaling link
termination (MP:SLT), STATS platform (MP:STATS) and OA&M platform (MP:OAM).
Technical Data
Number of signaling manager (SM) per node:

Max. number of signaling link termination (SLT) per node:

47

Transmission rate of a digital signaling link:

Number of different network indicators:

Number of SS7 networks:

64 kbit/s
56 kbit/s
1 920 kbit/s
1 536 kbit/s
4
32

Maximum possible number of signaling links per SLT:

60

Number of high speed signaling links per SLT:

Number of possible signaling links per node:

1 500

Number of possible link sets per node:

1 024

Number of possible signaling links in a signaling link set:

16

Number of possible routes in a route set:

Number of possible route sets per node:

4 096

Number of possible routes via a link set:

2 048

Number of trunk groups per node:

4 096

Number of trunk groups per destination point code (DPC):

64

Number of possible trunks per node:

120 000

Number of possible trunks per trunk group:

4 096

Number of configurable code points (SCCP GTT):

up to 16 384

Message throughput per node

(average MSU length: 33 byte):
SEP:
STP:
SEP/STP:

100 000
200 000
200 000

Transmission rate of a high speed signaling link:

34

A50016-D1109-K401-1-7618

Information
Signaling

Signaling System Network Control (SSNC)

GTT throughput per node

(average MSU length: 100 byte):

40 000

Signaling traffic load per signaling link:

normal load:
maximum load:
overload (max. for 3 sec):

0.4 Erl
0.8 Erl
1.0 Erl

MTP message length (including signaling information field, SIF, and

service information octet, SIO)
maximum (64 kbit/s):
maximum (broadband links, high speed signaling links):

273 Byte
4 096 Byte

Downtime:
of a signaling channel (only the hardware):
of a signaling channel (hardware, software, procedure error, O&M
activities):
total system downtime):

0.15 min/year
1.6 min/year
0.06 min/year

STP message transfer time (delay) fulfill the requirements of ITU-T

Q.706
GTT transfer time (delay) fulfill the requirements of ITU-T Q.706

A50016-D1109-K401-1-7618

35

Signaling System Network Control (SSNC)

Information
Signaling

7 SSNC Operation, administration and maintenance

SSNC operation, administration and maintenance can be performed via the separate
MP:OAM platform. A distinction is made between:
Operations, maintenance and administration part (OMAP)
Administration
Maintenance

7.1

Operations, maintenance and administration part (OMAP)

The main parts of the OMAP functions handled in the SSNC are located in the function
unit MP:OAM.
The operations, maintenance and administration part is divided into:
MTP Monitoring
SCCP Monitoring (for details see description Signaling Connection Control Part
(SCCP))
MTP Measurements
SCCP Measurements (for details see description Signaling Connection Control Part
(SCCP))
MTP Route Verification Test
MTP Monitoring
Monitoring delivers information (e.g. alarms) about specific events (e.g. link failures) in
SS7 networks after a configurable smoothing period (delay) to system alarming or the
NetManager. This smoothing period is used to prevent that the system is flooded by
short term alarms. In the event of failures of link sets, links or route sets the alarms are
held back for up to 10 minutes depending on the time set for the object.
SS7 events (e.g. link inhibiting) are analyzed by Monitoring and forwarded directly via
the Q3 interface to the NetManager. Events and alarms which are to be reported by
monitoring are defined in ITU-T Q.752.
E.g. a link failure will be recognized by the MTP level 2 and reported to network management. Network management informs MTP maintenance which updates the link state
in the database management system (DBMS) and informs monitoring about the state
change (see Fig. 7.1).
Monitoring updates the alarm state (attribute in the DBMS) for this link via the central
system alarming function. System alarming then forwards the corresponding alarm notification via the Q3 interface to the NetManager. The notification specifies the failure
reason as determined by MTP Maintenance.

36

A50016-D1109-K401-1-7618

Information
Signaling

Signaling System Network Control (SSNC)

MP:SLT
level 2,
signaling ATM
adaption layer

MP:SM
network management

MTP maintenance

MP:OAM
DBMS

MTP maintenance

MTP monitoring

system
alarming

Q3 platform

NetManager

Fig. 7.1

Position of MTP Monitoring in the OA&M

MTP Measurements
Measurements report the frequency of specific events in SS7 networks.
The MTP measurement functionality is distributed on MP:OAM, on MP:SM, all MP:SLT
and on coordination processor (CP). The functions for administrating the measurements
are located on the MP:OAM for the Q3 commands from the NetManager and on the CP
platform for MML-commands and Q3 Get commands for the traffic structure measurements.
The MTP measurements are based on ITU Q.751.1 / Q.752 and are defined in the MTP
object model. The MTP measurements Q3 commands originate from NetManager, are
administrated according to the Q.822 standard, and are processed at the MP:OAM.

A50016-D1109-K401-1-7618

37

Signaling System Network Control (SSNC)

Information
Signaling

On the MP:SLT platform and MP:SM platform measurements data are continuously collected by the MTP functions and recorded in the measurement tables of the high performance data base (HPDB). The measurement counters in these tables are incremented
by network management, message handling and signaling ATM adaptation layer(SAAL) applications. The measurement data from the HPDB measurement tables is delivered to STATS on the statistics support platform MP:STATS. Due to performance reasons there exists an own main processor (MP) handling exclusively this functionality.
STATS collects measurement data received from the providers, formats them and
sends them to the Q3 platform on the MP:OAM, which in turn writes the data to the local
hard disk. The files and data records are transferred from there to the relevant processing centers.
Fig. 7.2 below shows the Measurement interfaces within the main processor (MP) and
to the NetManager.

MP:SLT /
MP:SM
MTP-Measurements

MP:STATS
STATS

MP:OAM
DBMS

Q3-Platform

NetManager

Fig. 7.2

38

Messageflow of the MTP-Measurements

A50016-D1109-K401-1-7618

Information
Signaling

Signaling System Network Control (SSNC)

7.2

Administration
The Administration functions are implemented on the MP:OAM. The administration of
the MTP is in accordance with Q.751.1, Q.2751.1 and Q.822.
The MTP administration provides the Q3 interface for basic MTP object classes (i.e. the
MTP signaling network elements), object classes for measurements, for MTP screening,
for MTP accounting and for the MTP route verification test (MRVT).
The function of the SSNC administration is to accept user requests for all administrationspecific SSNC functions, to perform the maximum possible number of plausibility
checks on user inputs, to enter data in the master database as well as reading data out
of the database.
The software for the SSNC administration comprises the following (see Fig. 7.3):
MTP administration
SCCP administration:
(see description Signaling connection control part (SCCP))
Monitoring and alarm administration
Measurement administration

NetManager

MP:OAM
Q3 platform

MTP administration
SCCP administration
Monitoring and alarm administration
Measurement administration

database

Fig. 7.3

A50016-D1109-K401-1-7618

Software structure of the SSNC administration

39

Signaling System Network Control (SSNC)

Information
Signaling

MTP administration
The MTP administration in the SSNC controls the handling of the input and output commands entered by the operating personnel via the Q3 interface of the NetManager. Q3
requests enter the system from the OAM platform and are forwarded to the MTP administration.
All MTP administration functions run on the MP:OAM and affect the other MP platforms;
no administration is required in the other processors (line interface card, LIC, and ATM
bridge processor, type C, AMPC).
The following administration functions are available for objects that are defined in the
SSNC object model:
creation/modification/cancellation/display of the signaling network elements
These functions enable the signaling network to be modified. The signaling network
elements are the objects in the object model and represent, e.g., signaling links.
configuration of signaling network elements
Testing of signaling network elements
Monitoring and alarm administration
Monitoring and alarm administration configures the parameters for the individual handling of alarms and messages. This includes also the specification of the destination
(e.g. NetManager) where alarms and messages have to be routed to.
Measurement administration
The task of the measurement administration is to create and cancel measurement objects, etc. This means that the measurement objects are entered by the measurement
administration onto the database management system (DBMS) and the high performance database (HPDB).

40

A50016-D1109-K401-1-7618

Information
Signaling

Signaling System Network Control (SSNC)

7.3

Maintenance
The SSNC maintenance is responsible for evaluating the impact of hardware state
changes on SSNC functions and to trigger the appropriate handling. The maintenance
receives messages from network management about state changes of SSNC elements,
transforms the states according to Q.704 used by network management to those according to Q.751.1 to be stored in the database management system (DBMS) and informs monitoring about the state changes. Maintenance is responsible for providing the
permanent virtual channel addressing data for the ATM230 on the main processors after
a reset after recovery or on demand. Furthermore it is responsible for building, deleting
and verifying the level 1 paths (through the switching network (SN)) connected at a
line/trunk group (LTG).
All maintenance functions are divided into four levels:
4th level
3th level
2nd level
1st level

Maintenance managers
Maintenance
scheduler
Programs
Hardware/data

Global coordination and supervision of actions.

Handling of concurrent requests
Execution of specific actions according
to the object-specific tables
Execution of specific action

The levels 1 - 3 are processor-oriented. They mainly concern actions specific to individual functions (switchover, loading, activating, etc.).
In contrast, the level 4 (maintenance managers) effect a much larger area. It possess
little or no information as to which specific actions have to be carried out (this is the function of the maintenance scheduler). Instead, the maintenance managers know the relationships between the processors, evaluate their states in the database and perform the
communication between the maintenance software running on different processors.

A50016-D1109-K401-1-7618

41

Signaling System Network Control (SSNC)

Information
Signaling

The following maintenance functions are distinguished:

Configuration
Error handling
Diagnosis
Routine testing
Audits
Recovery
Configuration
The configuration processes the status changes of all hardware units. It is responsible
for maintenance of the statuses and for consistency of the device database. In addition,
it coordinates the various requests from other managers, such as the managers for diagnosis or routine testing. It is the control element for all alarm events and forwards
alarm information to the maintenance control interface.
Error handling
The error handling function is the first function activated for all spontaneous events in
the hardware. Using the diagnosis function, it verifies and locates errors and requests
status changes from the configuration function.
Diagnosis
Diagnosis is used to localize errors that occur in units that are not in operation. The diagnosis function is used both by operating personnel as well as by the error handling
function. It provides the operating personnel with access to the out of service units so
that the error information can be read.
Routine testing
Routine tests run in the background and check the operability of units that are running
and units that are not in operation. Units which are administratively blocked are not
checked.
Audits
An SSNC maintenance audit verifies the consistency of transient data in the high performance database (HPDB) on the signaling manager as master data and in the database management system (DBMS) on the MP:OAM. Inconsistencies result in triggering
repair actions and reports via the audit sequencer.

42

A50016-D1109-K401-1-7618

Information
Signaling

Signaling System Network Control (SSNC)

Recovery
After high level recoveries of the MP:OAM and the MP:SM a post recovery handling is
started on the MP:OAM to find and continue aborted SSNC maintenance jobs and to update the transient signaling managed object instance states in the DBMS:MTP. After recovery of the MP:SLT the channel data in the ATM230 for user node interface links and
AAL5 connections will be reestablished, if the ATM230 was reset during the recovery.
The SSNC has the following recovery levels:
PROREC
PROREC on MP:SLT
Recovery level PROREC is performed fast enough so that no timeout and consequently no route failure and no message loss occurs. Timers which may have been
active as the recovery occurred are restarted. Message handling is restarted without
external trigger and link supervision is executed as if no interruption had taken place.
Failed links are reported to network management. There are no specific measures
to compensate the effects of a PROREC of an MP:SLT.
PROREC on MP:SM
There are no specific measures to compensate the effects of this recovery level of
an MP:SM. The network management process, if affected, must ensure that any
task interrupted by the PROREC, is restarted. The SSNC maintenance function on
the signaling manager (SM) makes sure that no state changes have been lost.
PROREC on MP:OAM
The effected processes must ensure that tasks interrupted by this recovery level are
repeated. Messages without acknowledgement are repeated. The SSNC maintenance function on the OAM makes sure that no state changes of hardware elements, communication capabilities or network elements have been lost.
FULLREC
FULLREC on MP:SLT
The recovery level FULLREC of an signaling link termination (SLT) is handled as a
recovery level LOADREC.
FULLREC on MP:SM
Network management performs audit checks to ensure that distributed data are
compatible and that failed links are taken into restoration. The SSNC maintenance
function on the signaling manager (SM) makes sure that no state changes have
been lost.

A50016-D1109-K401-1-7618

FULLREC on MP:OAM
The recovery level FULLREC is performed locally without disturbing other processors. No external measures are necessary. Interrupted measures triggered by executed Q3 commands are reestablished.
LOADREC3
The recovery level LOADREC3 will format all memory areas and may be executed
only during manual activation of the unit.
LOADREC Scope platform (LOADREC2)
The recovery level LOADREC2 includes a selective memory formatting (without
symptom storage area) and may be executed due to recovery escalation.
LOADREC on MP:SLT
The recovery level LOADREC of the MP:SLT is supervised by hardware maintenance. The startup info service on MP:OAM informs SSNC maintenance on the
MP:OAM and network management on MP:SM about the beginning of the recovery.
The network management evaluates the affected links and performs the measures

43

Signaling System Network Control (SSNC)

Information
Signaling

on failure: changeover and report to SSNC maintenance. The network management

also reacts in the appropriate way if the SLT affected is the only one available. The
MTP routing tables are downloaded to new active SLT platform under network management control. After the end of recovery, the SLT reaches the active state again.
Startup info service informs SSNC maintenance. SSNC maintenance checks whether the affected SLT can communicate undisturbed with all other platforms, and if so,
it informs network management to restart restoration of the signaling links.
LOADREC on MP:SM
The recovery level LOADREC of the MP:SM is supervised by hardware maintenance on the MP:OAM. The startup info service informs SSNC maintenance on
MP:OAM about the beginning of the recovery. SSNC maintenance detects that the
MP is the SM. If the signaling manager (SM) is out of service for more than 10 minutes, all signaling links are deactivated. Whenever the SM is not available or not active, incoming Q3 commands are stored semipermanently and then executed when
the SM is available again. During the recovery level LOADREC, the network management performs an MTP restart for all networks which compensates any data
losses. All links will briefly go out of service.
LOADREC on MP:OAM
There is no LOADREC scope platform for the MP:OAM.
LOADREC System:
LOADREC system is the normal startup of the SSNC. The network management
performs an MTP restart.

Failure of LIC, ASN and AMXE

Reaction on state changes of hardware platforms:
LIC failure
When a line interface card (LIC) fails, all signaling links routed via this LIC fail as long
as the LIC is out of service. After reactivation of the LIC the affected links are reactivated automatically.
ASN failure
When the ATM switching network (ASN) fails, all main processors (MP) are isolated
and all links fail immediately. This situation is reported to and treated by SSNC maintenance as a total failure of SM and all SLT (and thus of all links) at the same time.
Monitoring is informed about the link failures. After reactivation of the ASN, reactivation of all MPs is reported to SSNC maintenance and handled accordingly.
AMXE failure
If MP:OAM and MP:SM are isolated from the rest of the system (e.g. as a result of
double failure (side 0 and side 1) of the ATM multiplexer to which they are connected), this does not initially have any effects on the other main processors (MP). These
processors can communicate as before, so no link fails immediately. This situation
however is reported to and treated by SSNC maintenance as a total failure of signaling manager (SM) and all signaling link terminations (SLT) (and thus of all links) at
the same time. Monitoring is informed. After reactivation of the AMXE, reactivation
of all main processors is reported to SSNC maintenance.

44

A50016-D1109-K401-1-7618

Information
Signaling

Signaling System Network Control (SSNC)

Operating states of the hardware

The operating state of the hardware components is defined by three attributes:
the administrative state
The operating personnel can change administrative states. The system may issue
warnings for certain changes in states in some cases but always permits changes.
Administrative states are stored semipermanently. The following administrative
states exist: not equipped (RSV), reserved (RES), maintenance blocked (MBL), upgrade (UPG), unblocked (UBL).
the error state
The error state indicates whether a hardware unit is faulty. Faults for which the hardware unit has completely failed are distinguished from faults for which the hardware
unit can still function. The following statuses exist: clear of faults (CLR), faulty (FLT),
unavailable (UNA).
the system state
The system state is administered by the configuration function according to internal
and external events. The operating personnel can only change a system state during
switchover if requested. The system state is critical transient data. The system state
can have the following values: not accessible (NAC), out of operation (OOP), in test
(TST), initialisation incomplete (INI), standby (STB), active maintenance (ACM), active (ACT).
Operating states are visible to the craft. The division into three states corresponds to the
different activities of the craft: administration tasks, hardware fault handling and configuration. The craft can configure a unit to a specific administrative state at any time. The
system automatically attempts to provide the operating state offering as much service
as possible. The administrative state is not changed by the system. Thus, after a repair
cycle, a unit is reconfigured to its original state.

A50016-D1109-K401-1-7618

45

Signaling System Network Control (SSNC)

Information
Signaling

8 SSNC Database
In the SSNC an object-oriented data model is used. The data are stored on different platforms.
Two databases are implemented:
Database management system (DBMS)
High performance database (HPDB)
Database management system (DBMS)
The database management system (DBMS) in the SSNC is the master database for the
message transfer part (MTP), the signaling connection control part (SCCP), etc. The
DBMS is located on the OAM platform, the signaling manager (SM) and the signaling
link terminations (SLT). All MTP data (level 1 - level 3) are administered and stored in
the master database of the OAM platform. As a result, the data are loaded exclusively
from this platform to the platforms SM and SLT.
High performance database (HPDB)
This database allows very fast access by applications to the required data.
The main reasons for designing a high performance database are the runtime critical requests of the MTP functions (e.g., routing, network management, user allocation).
Therefore the HPDB:MTP is closely connected to the MTP functions on SLT and SM.
In the following paragraphs only the MTP part of the HPDB is described. For more details on the SCCP part please refer to the description Signaling Connection Control Part
(SCCP).
The high performance database is located on software platforms SM and SLT. On the
SM the HPDB contains tables for network management. On the SLT the HPDB contains
tables for e.g. routing. The tables of the HPDB contain both, transient (e.g., link status,
counters) and semipermanent data. The semipermanent allocation data (trunkdata) is
loaded from the coordination processor (CP) to the signaling manager (SM). All other
semipermanent data of the HPDB is derived from the database management system on
each platform directly.
Access to HPDB data on SM is possible only via access procedures. On the signaling
link termination (SLT), direct access to HPDB data is possible for all applications under
the protocol handler (mainly message handling).
Changes of HPDB data are caused by events from the SS7 signaling network. The
HPDB is also updated in case of startup or configuration and in case of NetManager input via the DBMS.

46

A50016-D1109-K401-1-7618