Information

Signaling

Common Channel Signaling Network

Control (CCNC)
A30828-X1130-K400-1-7618
Common Channel Signaling Network Information
Control (CCNC) Signaling

Copyright (C) Siemens AG 1999

Issued by the Information and Communication Networks Group

Hofmannstraße 51
D-81359 München

Technical modifications possible.

Technical specifications and features are binding only insofar as
they are specifically and expressly agreed upon in a written contract.

2 A30828-X1130-K400-1-7618
Information Common Channel Signaling Network
Signaling Control (CCNC)

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

Contents
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2 CCNC functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.1 Message transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.2 Message transfer safeguarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.3 Message handling and network management . . . . . . . . . . . . . . . . . . . . . . 12
2.4 Adaptation system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3 CCNC hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.1 Multiplex system (MUX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.1.1 Master multiplexer (MUXM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.1.2 Slave multiplexer (MUXS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.2 Signaling link terminal group (SILTG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.3 Common channel signaling network processor (CCNP). . . . . . . . . . . . . . . 21
3.3.1 Signaling periphery adapter (SIPA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.3.2 Signaling management processor (SIMP) . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.3.3 Coordination processor interface (CPI). . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

4 CCNC software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.1 Operating systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
4.2 Peripheral debugging facility (PDF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
4.3 Start Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.4 PMU:SIMP software/firmware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.5 MH:SIMP firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.6 PMU:CPI software/firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.7 SIPA firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.8 SILTC firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.9 SILTD firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4.10 MUXM firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
4.11 Common software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

5 CCNC maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
5.1 Error detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
5.2 Fault analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.3 System restoration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.4 Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.5 Data backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.6 Diagnosis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.7 CCNC redundancy (duplication) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

6 CCNC administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

7 CCNC overload control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

8 CCNC technical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

A30828-X1130-K400-1-7618 3
Common Channel Signaling Network Information
Control (CCNC) Signaling

4 A30828-X1130-K400-1-7618
Information Signaling Common Channel Signaling Network
Control (CCNC)

1 Introduction
EWSD can control traffic to and from other network nodes with all conventional signaling
methods. One method particularly well suited to processor-controlled digital network
nodes is the signaling system no. 7 (SS7). It transfers messages separately from the
user information (speech, data) along common channel signaling links.
The common signaling channels are routed via a separate signaling network whose
nodes are generally integrated in the network nodes of the communication network.
There are three functionally distinct nodes in a signaling network:
– node as signaling end point (SEP)
– node as signaling transfer point (STP)
– node as relay point (SPR)
A network node functioning as an SEP represents a point of origin or a destination for
signaling messages. A network node functioning as an STP receives signaling
messages from an SEP and passes them on to an SEP or STP. A network node func-
tioning as an SPR can additionally perform global title translation (GTT). A network node
may function simultaneously as an SEP, STP and SPR.
The Common Channel Signaling Network Control (CCNC) is responsible in EWSD
for control of signaling traffic via common channel signaling links. The CCNC provides
the protocol functions of the message transfer part (MTP) along with parts of the
signaling connection control part (SCCP).

Position in the system

The CCNC belongs to the signaling area of EWSD. The position in the system is shown
in Fig. 1.1.

A30828-X1130-K400-1-7618 5
Common Channel Signaling Network Information Signaling
Control (CCNC)

Access Switching

Analog,
ISDN, V5.1 DLU LTG SN

Trunks, V5.2, PBX

LTG

Signaling

SS7 links
CCNC

Control

MB

CT CP

CCG

Fig. 1.1 Subsystems in EWSD

Features
The principal features of the CCNC are:
– system configuration with 254 signaling links
– 4,580 message signal units (MSU)/s
– maximum signaling traffic load per link greater than 0.4 Erl
For detailed performance values, see CCNC technical data.

6 A30828-X1130-K400-1-7618
Information Signaling Common Channel Signaling Network
Control (CCNC)

Structure
The CCNC has a modular structure and is composed of large-scale integrated circuits.
Because of its modular structure and the clear separation of the other EWSD functions
from the CCNC function, the CCNC can be adapted to technological innovations and
can be retrofitted or expanded with new components and functional units.
The CCNC hardware comprises the following functional units (see Fig. 1.2):
• Multiplex system (MUX)
The purpose of the multiplex system (MUX) is to combine all outgoing signaling links
from the CCNC onto one secondary digital carrier (SDC) leading to the switching
network (SN). In the receive direction, the multiplex system distributes the links
incoming to this SDC to the SILTD in the CCNC.
The multiplex system consists of a duplicated master multiplexer (MUXM0/1) and 32
slave multiplexers (MUXS).
• Signaling link terminal group (SILTG)
A CCNC can serve up to 254 links, and these links can be assigned to up to 32
groups of signaling link terminals (SILTs). Each group (SILTG) consists of up to eight
digital signaling link terminals (SILTD) and one signaling link terminal control
(SILTC). One outgoing and one incoming signaling link is connected to each SILTD
in a CCNC.
The slave multiplexer is also considered to be part of the SILTG due to its interface
to the SILTG.
• Common channel signaling network processor (CCNP)
The common channel signaling network processor (CCNP) identifies and processes
the tasks derived from the layer-3 tasks of signaling system no.7. It is duplicated for
redundancy, each unit having links to all SILTGs installed in the system.
A CCNP consists of
– up to 8 signaling periphery adapters (SIPA)
– one signaling management processor (SIMP)
– one coordination processor interface (CPI)
Like other EWSD hardware, the CCNC consists of modules, frames and racks. Refer to
the Maintenance Manual Construction.

A30828-X1130-K400-1-7618 7
Common Channel Signaling Network Information Signaling
Control (CCNC)

LTG SN

GP

Digital
LTG
signaling links
Analog
signaling links

CCNC
1
Modem MUXM0

MUXS

SILTG0 SILTG31

SILTD0 SILTD7 SILTD0 SILTD7

SILTC0 SILTC31

CCNP1
CCNP0
SIPA0 SIPA7

SIMP

CPI

CP

Fig. 1.2 Hardware architecture of the CCNC

Interfaces
There are interfaces between CCNC and
– Switching network (SN), see description Switching Network (SN),
– Coordination processor (CP), see description Coordination Processor 113C/CR
(CP113C/CR).

8 A30828-X1130-K400-1-7618
Information Signaling Common Channel Signaling Network
Control (CCNC)

2 CCNC functions
The functions of the message transfer part (MTP) of the SS7 are divided into three levels
in accordance with ITU-T:
• Level 1 – Message transfer (Q.702)
• Level 2 – Message transfer safeguarding (Q.703)
• Level 3 – Message handling and network management (Q.704)
In the CCNC, these functional levels are mapped onto the hardware units multiplexer
system (MUX), signaling link terminal group (SILTG) and common channel signaling
network processor (CCNP). In addition there is the Adaptation system which acts as a
link between level 2 and level 3.

2.1 Message transfer

The level 1 function of the message transfer is the physical interface to the signaling
system no. 7. It implements the transport function of the signaling channels within the
network node. In EWSD this task is performed by the line/trunk groups (LTG) and the
multiplex system (MUX) of the CCNC.
The multiplex system performs the following tasks:
– Distribution of individual signaling channels outgoing from the SILTDs in the CCNC
onto the paths leading to the signaling network
– Distribution of signaling channels incoming from the network to the various SILTDs
in the CCNC

LTG

Reception/
transmission of
SS7 messages

Forwarding of SS7 messages to

the SN; reception of
SS7 messages from the SN

Level 1
functions MUX

Distribution of
SS7 messages
to the SILTDs

Concentration of
SS7 messages
to the SN

Fig. 2.1 Functions of message transfer (level 1)

A30828-X1130-K400-1-7618 9
Common Channel Signaling Network Information Signaling
Control (CCNC)

2.2 Message transfer safeguarding

The level 2 function message transfer safeguarding ensures reliable transfer of
messages. This task is implemented in the signaling link terminal, digital (SILTD).
The functionality of the MTP level 2 is divided into (see Fig. 2.2):
– Management
– Reception of signaling messages
– Transmission of signaling messages
The management function consists of:
– Link state control
This function supervises and controls the signaling link operating state and automat-
ically takes faulty links into operation again.
– Processor outage control
Processor outage is reported to the neighboring network node, which then reroutes
the message traffic to other links. If messages are still received in the same common
signaling channel, they are discarded.
– 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 synchroniza-
tion in order to be able to classify the links as usable.
– Error rate monitoring
This function monitors the number of message errors occurring on a signaling link
during a specified period. The level 2 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 two other buffers is reported to the own level 3.
– Reception control
This function contains parts of the SS7 protocol. Received acknowledgements are
monitored and verified.

10 A30828-X1130-K400-1-7618
Information Signaling Common Channel Signaling Network
Control (CCNC)

The transmission function consists of the transmission control (this function includes
parts of the SS7 protocol). The transmission function includes the procedures for
correcting transmission errors:
– Basic error correction method:
A transmitted message is stored in the retransmission buffer until a positive acknowl-
edgement is received.
– Preventive cyclic retransmission:
If no messages are to be sent, but some are still stored in the retransmission buffer,
cyclical retransmission is started.
– Forced retransmission:
Messages are retransmitted if the threshold value for the messages in the retrans-
mission buffer or for the bytes to be retransmitted is exceeded.
Refer to the description Signaling System No. 7 (SS7) (Q.703) for information regarding
the general procedure for sending and receiving signaling messages SS7.

SILTD

Link state control

Management Processor outage control

Initial alignment control

Alignment error rate

monitoring

Level 2 Reception
functions Error rate monitoring

Congestion control

Reception control

Transmission
Transmission control

Fig. 2.2 Functions of message transfer safeguarding (level 2)

A30828-X1130-K400-1-7618 11
Common Channel Signaling Network Information Signaling
Control (CCNC)

2.3 Message handling and network management

The level 3 function message handling and network management ensures that signaling
messages are transmitted correctly and reliably from a specific user part of an origi-
nating signaling point to the same user part in the destination signaling point.

CCNP
Message routing

Message
Message discrimination
handling

Message distribution

Signaling link
management
Signaling network Signaling traffic
management management

Signaling route
Level 3
management
functions

Testing and Signaling link testing

maintenance (on cutover)

Restart 1
(soft switchover)
Start up, Restart 2
restart (hard switchover)

Restart 3
(initial start)

Fig. 2.3 Functions of message handling and network control (level 3)

12 A30828-X1130-K400-1-7618
Information Signaling Common Channel Signaling Network
Control (CCNC)

The message handling function includes the following sub-functions:

– Message routing
This function is used to determine an outgoing signaling channel for a message
signal unit (MSU). Using the route description, an appropriate signaling link set, from
which the current 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 desti-
nations. If the messages are intended for the same network node, they are trans-
ferred via the message distribution function to the appropriate user part. If the
messages are meant for a different network node, they are transferred to the
message routing function.
– Message distribution
This function evaluates the message field known as the service indicator in order to
identify the desired user part. The messages are then transferred directly to the user
parts or to the user allocation functions.
The functions of the signaling network management include configuration of the
signaling network whenever errors occur and traffic control in overload cases. Signaling
network management comprises the following:
– Signaling link management
Its task is to activate/deactivate the link sets and their links in response to input
commands or link errors.
– Signaling traffic management
Its task is to reroute the signaling traffic to other links in the same route if a signaling
link has failed (change over) or to an alternative route if a route has failed (rerouting).
– Signaling route management
Its task is 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.

A30828-X1130-K400-1-7618 13
Common Channel Signaling Network Information Signaling
Control (CCNC)

The following functions are provided to perform the tasks listed above:
– Signaling link control
This function controls the activation, deactivation and blocking of signaling links.
When the link is taken into service, it is tested - i.e., test messages are exchanged
between the two signaling points.
– Changeover of signaling links
This function is started either by a changeover order from an adjacent signaling
points or a command from the own signaling point. Messages for a failed signaling
link are buffered during the changeover. Messages already present in the SLT with
the failed link are first switched to the SLT with the operable signaling link (retrieval)
before new, subsequent messages are processed.
– Message flow control
This function informs users in its own network node or in the adjacent nodes of over-
load situations, so that they can reduce the amount of messages generated for the
destinations affected by the overload.
– Blocking/unblocking message transfers
Whenever the accessibility of a destination changes (e.g., failure or restored avail-
ability of a signaling link set) this function informs adjacent signaling points that one
or more destinations are not available or are available again, as the case may be.
The function is only active if the CCNC is operating as an signaling transfer point.
– Switchover to a standby or previous route set (rerouting)
This function deactivates or activates a route set on reception of a “message transfer
prohibited/allowed” message.
The testing and maintenance function (ITU-T Q.707) tests the path from the func-
tion’s own level 3 to the adjacent level 3.
The test is performed:
– when a link is activated by a configuration request or restored after failure
– when a remote processor has returned to operation after an outage
– periodically for active links in the event of a configuration request
The function start/restart ensures the availability and operability of the MTP in a network
node after restarting it in the existing network. To do so, network status information is
exchanged between the restarting MTP and the adjacent network nodes.
Depending on the type of recovery, one of the following restarts is performed:
– Restart 1 (soft switchover)
In this switchover from the active CCNP to the standby CCNP, the transient and
semipermanent data in both CCNPs are up to date. This is checked by the newly
active CCNP. Furthermore the regular scheduled jobs of signaling traffic manage-
ment are started.
– Restart 2 (hard switchover)
In this switchover, the transient data in the newly active CCNP have to be updated.
– Restart 3 (initial start)
In this restart, the entire CCNC is reloaded. The semipermanent data are reloaded
from the CP. The transient data are no longer up to date and have to be re-estab-
lished.

14 A30828-X1130-K400-1-7618
Information Signaling Common Channel Signaling Network
Control (CCNC)

2.4 Adaptation system

The adaptation system consists of:
• Signaling link terminal control (SILTC)
• Signaling periphery adapter (SIPA)

Signaling link terminal control (SILTC)

The SILTC forms the link between the SILTG and the signaling periphery adapters
(SIPA) in the CCNP. A CCNC can contain up to 32 SILTCs, depending on its capacity.
The functions of the SILTC are as follows:
– serial receiving and sending, plus buffering, of messages from/to one of the two
connected SIPAs
– byte-by-byte receiving and sending of messages from/to whichever SILTD is being
addressed
– serial receiving of SILTD maintenance messages
– receiving test commands from the active and stand-by SIPA
– sending test command acknowledgments to the active and stand-by SIPA
– sending error messages to the SIPA
– detection of errors during sending/receiving SILTC <-> SIPA
– connecting the SILTG with a MUXS to the MUXM of the (SN)0/1 switching network
– testing at start up and during operation
SILTG and CCNP are connected via an HDLC link (data rate 1.63 Mbit/s). The interface
adaptation function is performed by the SIPA in the CCNP and by the SILTC in the
SILTG.
In order to handle the exchange of messages over this HDLC link, the following func-
tions are implemented both in the SILTC and in the SIPA:
– addition of flags before and after each message when sending, and suppressing
these flags when receiving
– insertion of a zero after five consecutive ones when sending, and removing these
zeros when receiving
– addition of two CRC bytes when sending, and removal of the check bytes when
receiving a message
– addition of a communication byte

Signaling periphery adapter (SIPA)

In addition to the functions needed to transfer messages between SILTC and SIPA, the
SIPA performs the following tasks:
– communication with the signaling management processor (SIMP)
– receiving, sending and processing maintenance tasks in standby mode
– monitoring:
for errors in the transmission sequence (SIPA -> SILTC)
for errors in the receive sequence (SILTC -> SIPA)
the supply voltage
runtimes
– test during recovery and during operation

A30828-X1130-K400-1-7618 15
Common Channel Signaling Network Information Signaling
Control (CCNC)

3 CCNC hardware
The CCNC comprises the following hardware functional units:
• Multiplex system (MUX)
• Signaling link terminal group (SILTG)
• Common channel signaling network processor (CCNP)

3.1 Multiplex system (MUX)

The purpose of the multiplex system (MUX) is to combine all signaling links outgoing
from the CCNC onto one secondary digital carrier (SDC) leading to the switching
network and to distribute the links incoming to this SDC to the SILTDs in the CCNC.
The two-stage multiplex system consists of:
• a duplicated Master multiplexer (MUXM)
• 32 Slave multiplexer (MUXS)

SN0 SN1 SN0 SN1

MUX
MUXM0 MUXM1

MUXMA MUXMB MUXMA MUXMB

0 6 7 15 0 6 7 15

MUXS MUXS

SILTG 0 SILTG 31

Fig. 3.1 Multiplex system (MUX)

16 A30828-X1130-K400-1-7618
Information Signaling Common Channel Signaling Network
Control (CCNC)

3.1.1 Master multiplexer (MUXM)

The master multiplexer MUXM0/1 consists of the MUXMA module and, depending on
the configuration, an expansion module, MUXMB module (see Fig. 3.1).
The MUXMA module is connected to a max. of 7 MUXS via 7 inputs/outputs. Up to eight
signaling channels can be carried on each of these highways (512 kbit/s). The signaling
channels are multiplexed and demultiplexed in the MUXS upstream from the SILTG.
The multiplexer is connected to the switching network (SN) through an input/output by
means of an 8-Mbit/s highway over which the 7 x 8 SILTG channels are routed.
For a configuration with more than 7 and up to 16 SILTGs, the expansion module
MUXMB is used; this can service a further 9 SILTGs. The MUXMB has 9 inputs/outputs
to the MUXSs and no connection to the SN. Transmission of the 9 x 8 channels from the
SILTGs to the SN is handled via the MUXMA, which feeds the channels into the 8 Mbit/s
secondary digital carrier to the SN.
This results in the following configurations:

MUXMA 0 1...55 signaling links

MUXMB 0 56...127 signaling links
MUXMA 1 129...183 signaling links
MUXMB 1 184...255 signaling links

MUXMA module
The hardware of the MUXMA comprises the following functional blocks:
– A clock generator which produces all the timing and synchronization signals
required in the multiplexer (MUX) unit
– A buffer which synchronizes all the data items arriving from the switching network
with the internal clock system of the MUX
– A channel demultiplexer which splits the datastream arriving from the switching
network into individual channel groups (1...8 channels) and supplies it to the output
registers of the MUXS interfaces
– A channel multiplexer which feeds the channels that are transferred to the input
registers by the MUXSs into a common 8 Mbit/s datastream to the switching network
– Output and input registers which convert the transmission rates between the inter-
faces to the SN and MUXS
– Monitoring circuits, for monitoring and routine testing of the internal clock system
– The message channel control unit (MCH), comprising a microcontroller and an
HDLC controller, processes messages from the message buffer unit for line/trunk
group (MBU:LTG), or generates messages for the MBU:LTG which are transmitted
over the MCH
– Extraction/insertion logic for the MCH
In order to monitor the internal functions of the MUXMA module, the control unit in
the module exchanges messages with the message buffer (MB) via the MCH. The
channel used as the MCH is channel 0 of the 128 channels of the secondary digital
carrier between SN and MUXMA. The extraction logic extracts an incoming channel
0 from the secondary digital carrier (SDC), and feeds it to the control section MCH.
The insertion logic inserts an outgoing channel from the control unit into the SDC.
– Changeover logic to transfer channel 0 alternately to the insertion logic elements for
MUXMA or MUXMB, if the configuration concerned includes an MUXMB expansion
module.

A30828-X1130-K400-1-7618 17
Common Channel Signaling Network Information Signaling
Control (CCNC)

MUXMB module
All the control signals required by the MUXMB are provided by MUXMA.
The hardware of the MUXMB comprises the following functional blocks:
– data synchronization
– channel demultiplexer (data flow SN -> SILTD)
– channel multiplexer (data flow SILTD -> SN)
– extraction/insertion logic circuit for message channel (MCH)
The data synchronization, channel demultiplexer and channel multiplexer are functional
blocks which are identical to those of module MUXMA.
In a configuration in which expansion module MUXMB is used, this module alternates
with MUXMA in performing the insertion and extraction of channel 0.

3.1.2 Slave multiplexer (MUXS)

The slave multiplexer constitutes the transfer stage to the SILTD in the SILTG. It has
one interface to the MUXM for each system side 0 and 1, and 8 interfaces to the SILTDs.
In the receive direction the MUXS demultiplexes the 8 channels carried by the MUXM
at a data rate of 512 kbit/s to 8 SILTD interfaces with a data rate of 64 kbit/s or 56 kbit/s.
In normal operation the available signaling channels are divided between the two
system halves, so that the MUXS receives signaling channels both from MUXM0 and
from MUXM1. In the transmit direction it distributes the 64 kbit/s or 56 kbit/s data
streams coming from the 8 SILTDs to MUXM0 and MUXM1. The SILTDs switch over
the transmission speed from 64 kbit/s to 56 kbit/s individually for each channel.

MUXS module
The hardware of the MUXS comprises the following functional blocks:
– Changeover logic for signaling network changeover
The MUXS receives the control signal indicating the destination MUXM via the
SILTC. The data from the SILTD are transmitted by the MUXS to the two MUXMs
alternately.
– Switchover logic between 64 kbit/s and 56 kbit/s
The MUXS receives a control signal from each SILTD for switchover of the transmis-
sion speed from 64 kbit/s to 56 kbit/s for the individual channels.
– Channel demultiplexer
This distributes the information on the channels transmitted by the MUXM to the
output registers of the SILTD interfaces. The SILTDs are also supplied with a data-
synchronous symmetrical 64 kHz clock or asymmetrical 56 kHz clock.
– Channel multiplexer
This combines the channels transmitted from the SILTDs to the input registers into
a common 512 kbit/s data stream to the MUXM. A synchronous 2.048 MHz clock is
transmitted with the data to the MUXM.
– Input and output registers
The different transmission rates between the interfaces to the MUXM and SILTD are
converted here.

18 A30828-X1130-K400-1-7618
Information Signaling Common Channel Signaling Network
Control (CCNC)

3.2 Signaling link terminal group (SILTG)

The 254 signaling links (max.) in a CCNC can be divided into a maximum of 32 groups
of signaling link terminals (SILTGs). Such a signaling link terminal SILTG consists of up
to 8 digital signaling link terminals SILTD and a signaling link terminal control SILTC.
The SILTG handles the tasks of level 2 (message safeguarding). An outgoing signaling
link and an incoming signaling link are connected to each SILTD of a CCNC.
An interface to the SILTG also assigns the slave multiplexer in part to the SILTG
(see Fig. 3.2).

SN0/ SN1/
MUXM0 MUXM1

SILTG31

SILTG0
MUXS0

SILTD0 SILTD7

B:SILT

SILTC0

CCNP0 CCNP1

Fig. 3.2 The signaling link terminal group (SILTG)

SILTD module
The hardware of the SILTD comprises the following functional blocks:
– In the SILTD a microprocessor unit (MPU) is used which has a 16-bit processing
unit (CPU) and several peripheral modules. These modules are responsible for
address decoding, for the control of program interrupts (interrupt controller), for
direct access to the RAM without CPU involvement (DMA controller) and for timing
supervision (timer).
– The signaling messages are transmitted in the signaling channels in the SS7 trans-
mission protocol format. The transmit messages are embedded in the transmission
format and the receive messages are extracted from the transmission format by an
HDLC protocol module.
– The memory unit consists of an EPROM and a RAM. The EPROM contains the
recovery and processing program of the SILTD. The RAM contains the variable data.
– The transfer memory (dual-port RAM) transfers the messages to be transmitted
between SILTD and SILTC. The dual-port RAM allows the CPU of the SILTDs and
the SILTCs time-independent access.

A30828-X1130-K400-1-7618 19
Common Channel Signaling Network Information Signaling
Control (CCNC)

SILTC module
The SILTC supervises and serves 8 SILTDs. The messages coming from the SIPA are
distributed to the corresponding SILTDs by the SILTC. Messages from the SILTDs are
picked up by the SILTC and passed on to the signaling periphery adapter (SIPA).
The hardware of the SILTC comprises the following functional blocks:
– The processing unit is the heart of the SILTC and operates in minimum mode
because of memory access via DMA modules, i.e. it generates all the control signals
itself.
– The interrupt controller receives an interrupt request from the SILTC and calls a
service routine.
– The programmable DMA controller fetches the data from the SILTCs’ RAMs and
distributes them to one of the two serial interfaces to the CCNP. In the opposite
direction it fetches data from the HDLC module and stores them in the RAM. Two
DMA controllers are used in the SILTC.
– The timer supplies a clock for calling the timing program. The frequency and type of
the output pulses are defined by the software. The timer also performs watchdog
functions in the SILTC.
– Each of the interfaces to the two CCNPs is processed by an HDLC module. They
are initialized by the CPU. The DMA controller controls the data exchange between
the HDLC module and the RAM.
– The memory unit consists of an EPROM and a RAM. The EPROM stores the
recovery and monitoring program and all the processing programs. The RAM
contains the variable data.
– The bus interface to the bus system for signaling link terminal (B:SILT) bus is used
to exchange messages between the SILTC and the connected SILTDs.

20 A30828-X1130-K400-1-7618
Information Signaling Common Channel Signaling Network
Control (CCNC)

3.3 Common channel signaling network processor (CCNP)

The common channel signaling network processor (CCNP) determines and processes
the jobs arising from the Level 3 tasks of signaling system No.7. It is duplicated and each
unit is connected to all the SILTG groups installed in the system. One of the two units is
switched to active. An update of the data is made from the active to the standby CCNP.
Only a communication check runs through the standby CCNP. This checks the opera-
bility of the CCNP and the connection to the SILTGs at intervals. As a result the standby
CCNP can take over the role of active CCNP at any time without loss of messages.
The CCNP functional unit consists of the following subunits (see Fig. 3.3):
• up to 8 Signaling periphery adapter (SIPA)
• one Signaling management processor (SIMP) with
the message handler for the signaling management processor (MH:SIMP module)
and the processor memory unit for the signaling management processor
(PMU:SIMP module)
• one Coordination processor interface (CPI) with
the processor memory unit for the coordination processor (PMU:CPI module) and
the connection units:
memory unit for the common channel signaling network processor (MU:CCNP),
memory unit for the coordination processor interface (MU:CPI) and
input/output control for the coordination processor interface (IOC:CPI)

SILTG CCNP SILTG

B:CCNP B:CCNP

SIPA0 SIPA7

SIMP
MH:SIMP
B:CCNP B:SIMP
PMU:SIMP

B:CPI CPI

MU:CCNP IOC:CPI PMU:CPI

or MU:CPI
B:CCNC

IOP:MB

Fig. 3.3 The common channel signaling network processor (CCNP)

A30828-X1130-K400-1-7618 21
Common Channel Signaling Network Information Signaling
Control (CCNC)

3.3.1 Signaling periphery adapter (SIPA)

SIPA module
The SIPA and the SILTC together constitute the adapter system between the CCNP and
the SILTG.
The hardware of the SIPA comprises the following functional blocks, whose structure
and tasks are identical to those of the SILTC:
– processing unit
– interrupt controller
– programmable direct memory access (DMA) controller
– programmable timer
– HDLC module
– memory unit
– bus interface (dual port) to the bus B:CCNP

3.3.2 Signaling management processor (SIMP)

MH:SIMP module
The task of the MH:SIMP is to control the exchange of messages between the modules
of the CCNP which are interconnected via the CCNP bus. Each device on the CCNP
bus contains a dual-port memory as its communication memory. Messages can be
exchanged between the SIPA and MH:SIMP, the CPI and MH:SIMP, the SIPA and
MU:CPI or MU:CCNP via this memory.
The hardware of the MH:SIMP consists of the following functional blocks:
– processing unit with clock system
– internal bus system
– memory unit with EPROM and RAM
– interface to the CCNP bus (bus master)
– interface to the SIMP bus (dual-port memory)
– timer
– reset circuit
– input ports/output ports

22 A30828-X1130-K400-1-7618
Information Signaling Common Channel Signaling Network
Control (CCNC)

PMU:SIMP module
The PMU:SIMP processes the Level 3 program complexes ‘routing’ and ‘network
management’.
In addition to this it implements the following hardware functions for maintenance and
administration purposes:
– supervision and detection of malfunctions in hardware and software
– monitoring of supply voltage
– activation of the CPU self-test after a reset
– initialization of the dynamic RAM (DRAM)
– test phase displays for hardware and software faults, ready for loading, loading
completed
– time supervision for program execution
– display of watchdog blocking during test
– fault detection and correction for DRAM
– setting and cancelling of write protection
– marking of individual fault sources for fault analysis (alarm register)
The hardware of the PMU:SIMP consists of the following functional blocks:
– processing unit with clock system
– internal bus system
– memory unit, divided into EPROM and RAM; the RAM comprises a high-speed
static RAM area (SRAM) and a dynamic RAM area
– address decoding
– DRAM control
– fault detection and correction
– timer and watchdog
– interrupt controller
– alarm register
– input ports/output ports
– bus interface (bus master) to the SIMP bus (B:SIMP)
– reset circuit

A30828-X1130-K400-1-7618 23
Common Channel Signaling Network Information Signaling
Control (CCNC)

3.3.3 Coordination processor interface (CPI)

The CPI consists of the modules PMU:CPI, MU:CPI or MU:CCNP, and IOC:CPI. The
CPI is connected to each of the two input/output processors for the message buffer
(IOP:MB) in CP by the bus system B:CCNC.

PMU:CPI module
Modules PMU:CPI and PMU:SIMP have the same layout; they differ only in the address
coding. The features and functional blocks of the two modules are also identical.

MU:CPI module or MU:CCNP module

The memory unit MU:CPI acts as a dual-port memory for the processor memory unit
PMU:CPI and as a buffer for the exchange of messages between PMU:CPI and
MH:SIMP.
As an alternative to module MU:CPI, the earlier memory module MU:CCNP can also be
used for system data.
The hardware of the MU:CPI or MU:CCNP consists of the following functional blocks:
– internal bus
– dual-port bus
– input ports/output ports
– dual-port memory and control

IOC:CPI module
Module IOC:CPI handles the exchange of data between the input/output processors of
the CP (IOP:MB) and the PMU:CPI.
The hardware of the IOC:CPI consists of the following functional blocks:
– The interface of the module to the CPI bus (connection to the CPU on module
PMU:CPI) is implemented using transceivers.
– Data transfer between the B:CPI of the PMU:CPI (16 bits wide) and the B:CCNC to
the IOP:MB of the CP (8 bits wide) is handled in the input and output directions by
two input/output FIFO memories. The IOP:MB controls input to and output from the
FIFOs byte by byte using a handshake procedure.
– One input port and one output port are available for communications between
IOP:MB and IOC:CP relating to the current state of a transmission procedure.
– The CP can reset the entire CCNP by means of a reset logic circuit on the IOC:CPI
(‘restart’ procedure).

24 A30828-X1130-K400-1-7618
Information Signaling Common Channel Signaling Network
Control (CCNC)

4 CCNC software
Each of the hardware functional units in the CCNC has its own software/firmware, which
is stored in an EPROM (see Fig. 4.1). The SIMP and CPI also contain reloadable soft-
ware that is downloaded from the CP. Common software for the control of CP-CCNC
tasks is contained in the CP. The CCNC software is divided into subsystems. These
subsystems are in turn made up of modules (procedures, processes and data)
containing the functions.

DLU CCNC SN CP

LTG CCNC OMDS

software

PMU:SIMP MH:SIMP PMU:CPI SIPA

software/ firmware software/ firmware
firmware firmware

SILTC SILTD MUXM Common

firmware firmware firmware software

Fig. 4.1 Structure of the CCNC software

All the functional units of the CCNC software contain certain functions which have a
similar or identical structure. The items concerned are:
– the operating system
– the peripheral debugging facility (PDF)
– the start software

A30828-X1130-K400-1-7618 25
Common Channel Signaling Network Information Signaling
Control (CCNC)

4.1 Operating systems

The operating systems of the CCNC processors coordinate and control the defined
functions of the CCNC. With the exception of the operation system of the multiplexer
(MUX), all the operating systems of the CCNC processors have a uniform structure. This
standard structure is necessary in order to ensure the smooth exchange of information
between the processors, using a standard message format.
The operating systems determine the jobs to be processed on the basis of internal and
external events and present them in a standard form at the central interface, from which
they are read for processing. The jobs are processed on two processing levels with
different priorities; an interrupt level with high priority, and the level of the executive
master program with low priority.
The operating systems have the following functions:
– bootstrapping and initializing the processors
– processing interrupts
– driving controllers
– supporting low-level protocols (hardware-specific input/output formats)
– transferring data within a unit and between the processors of different units
– controlling processes
– coordinating multiple-start (reentrant) programs (only possible in the PMU:SIMP)
– synchronizing processes
– administering timers
– administering and providing service routines and data structures
The operating systems consist of the following functional components:
– start and initialization program
– executive master program (task determination, task processing)
– interrupt programs
– timer administration
– interprocess communication
– message exchange

4.2 Peripheral debugging facility (PDF)

PDF is an online software tool which supports both the development and maintenance
of the CCNC system software. It can be used not only during the development stage but
also after the software system has been put into operation.
The PDF comprises the following functions:
– ‘Dump’ function, for reading out memory contents
– ‘Patch’ function, for changing memory contents
– ‘Trace’ function, for tracing the functional sequence of program-complex events
Each function is incorporated in the program system as a separate program complex. In
all processors, most of the PDF functions are implemented in the common modules, the
remainder in processor-specific modules.

26 A30828-X1130-K400-1-7618
Information Signaling Common Channel Signaling Network
Control (CCNC)

4.3 Start Software

The CCNP start process is initiated with a Reset command from the CP. The
subsystems created for this purpose in the PMU:SIMP and PMU:CPI first initialize and
check the hardware and the memory areas of the processors. Following a load request
to the CP, the software is loaded into the two CCNPs and started. The CP then places
one CCNP in the active state, the other in the inactive state (standby).
The other processors are also started with Reset; causing the processors to verify and
initialize their hardware and software. The load data are then transmitted by the CCNP.

4.4 PMU:SIMP software/firmware

PMU:SIMP contains level 3 functions as well as functions for maintenance and admin-
istration.

Level 3 functions
– Message routing
– Signaling link management
– Signaling traffic management
– Signaling route management
– Overload handling
– Testing and maintenance
– Start/restart
– Control of the message buffer in the SILT

Administration functions
– Administrative configuration
– Checking network elements for consistency, measurements
– Alarm signaling and reporting
– Congestion

Maintenance functions
– Fault analysis
– Configuration
– System recovery
– Reporting
– Routine testing
– Update
– Communication test
– Data transfer to partner CCNP

A30828-X1130-K400-1-7618 27
Common Channel Signaling Network Information Signaling
Control (CCNC)

4.5 MH:SIMP firmware

MH:SIMP contains only functions for message exchange and for maintenance. Func-
tions for administration are not implemented.

Message exchange functions

– Carrying out the exchange of messages between functional units PMU:SIMP,
PMU:CPI and SIPA 0...7.
– Level 3 function:
message buffering and distribution, i.e. deciding whether a received message is
intended for the home signaling point or for another signaling point (transfer
message), or whether the message is a signaling message or a signaling network
management message. In addition, the network indicator (NI) of an incoming
message is compared with the one entered in an allocation table (screening). This
function can be switched off by means of a patch.
– Notifying the fault analysis system of MH:SIMP and PMU:SIMP if a message was
discarded.

Maintenance functions
– Fault analysis
– Routine testing
– Start test

4.6 PMU:CPI software/firmware

The PMU:CPI forms the interface of the CCNC to the CP via the input/output processor
for the message buffer, IOP:MB. PMU:CPI contains functions for message handling as
well as functions for administration and maintenance.

Message handling functions

– Level 3 allocation function,
i.e. the PMU:CPI distributes incoming messages among users (e.g. integrated
services digital network, ISDN; signaling connection control parts, SCCP; in the CP
or line/trunk group, LTG).
– Conversion of the messages to be exchanged between the CP and the CCNC from
EWSD format to CCNC format and vice versa.

Administration functions
– Administrative configuration
– Overload control
– Measurements
– Parameter administration

Maintenance functions
– Fault analysis
– Configuration
– System recovery
– Reporting
– Routine testing
– Communication test
– Loading

28 A30828-X1130-K400-1-7618
Information Signaling Common Channel Signaling Network
Control (CCNC)

4.7 SIPA firmware

SIPA contains functions for message exchange as well as functions for administration
and maintenance.

Message exchange functions

– Detecting the destination address in the case of messages from the PMU:SIMP and
extracting messages for its own subsystems
– Assigning the serial hardware logic in the SILTC, with which communication is to
take place
– Transferring a message or an inquiry (if no message is present) to the connected
SILTC
– Accepting a message or a receive acknowledgment from the connected SILTC
– Detecting the destination address in the case of messages from a SILTC, forwarding
to the transfer store leading to the SIMP, or extracting messages for its own mainte-
nance subsystem

Administration functions
– Overload control
– System recovery

Maintenance functions
– Fault analysis
– Configuration
– System recovery
– Reporting
– Routine testing
– Communication test

4.8 SILTC firmware

The SILTC software contains only functions for message exchange and maintenance.
Administration tasks are not implemented.

Message exchange functions

– Receiving messages from the SIPA and distributing them to the connected SILTDs
according to their destination addresses
– Scanning the connected SILTDs and transmitting messages to the SIPA
– Transmitting messages to its own maintenance program system

Maintenance functions
This program complex is responsible for safeguarding hardware functions as well as
programs and data in the SILTC. In addition, it safeguards the interfaces to the SILT and
the SIPA. Maintenance also supports the PMU:SIMP by implementing safeguarding
measures for the SILTs. The following functions are available for these tasks:
– Fault analysis
– Configuration
– System recovery
– Reporting
– Routine testing
– Communication test

A30828-X1130-K400-1-7618 29
Common Channel Signaling Network Information Signaling
Control (CCNC)

4.9 SILTD firmware

The SILTD software contains level 2 functions as well as functions for administration
and maintenance.

Level 2 functions
The level 2 functions have the following two tasks:
– Receiving and transmitting
message signal unit (MSU), in which a message for a user is packaged
link status signal unit (LSSU), by means of which information about the state of the
signaling link is transmitted (e.g. backlog in receive memory),
dummy message which is sent if there is no user information
– Inserting and removing backup data (flags, zero bits, CRC). This is the task of the
HDLC device
These two tasks can make use of the following functions:
– Interrupt routines
– Event detection
– Service routines
– Receiving section
– Transmitting section
– Control of signaling link state
– MSU retrieval
– Overload control
– Message buffer control

Administration functions
– Measurements
– Overload

Maintenance functions
This program complex is responsible for safeguarding hardware functions as well as
programs and data in the SILT. In addition, it safeguards the level 1 within the own
signaling point and the level 1 clock. The following functions are available for these
tasks:
– Fault analysis
– System recovery
– Reporting
– Communication test
– Routine testing
– Error data collection

30 A30828-X1130-K400-1-7618
Information Signaling Common Channel Signaling Network
Control (CCNC)

4.10 MUXM firmware

The firmware is used for control and maintenance of the message channel MCH, a
communication line for maintenance functions between the MUXM and the message
buffer unit for line/trunk group (MBU:LTG). The operating system of the processor used
for this purpose differs in its structure from the operating systems of the other CCNC
processors, which are largely standardized.
The MUXM software contains only functions for maintenance.

Operating system for MUXM

The processes for controlling the user programs in the maintenance subsystem are split
between four levels with different priorities.
– Level 0
This contains the recovery program with the standard hardware tests
(EPROM, RAM etc.)
– Level 1
Interrupt level
– Level 2
Receiving and transmitting processes
– Level 3
Test and supervision programs and supplementary modules for the operating
system and modules with time processing programs

4.11 Common software

The subsystems combined in the common software are divided into three groups:
– Subsystems for common routines and macros to support the functions of 8068/8088
processors and peripheral debugging facilities in each of the CCNC software func-
tional units
– Subsystems with CCNC routines to support the operation, startup, maintenance and
operating system functions in each of the CCNC software functional units
– Subsystems with macros to support the functions of Levels 2 and 3 of SS7 and of
the operating system

A30828-X1130-K400-1-7618 31
Common Channel Signaling Network Information Signaling
Control (CCNC)

5 CCNC maintenance
The CCNC maintenance functions are split between the CCNC and the CP. The CCNC
handles those maintenance tasks that it is capable of executing unaided. The CP only
handles those tasks which the CCNC is unable to perform without assistance, for
instance because it does not have direct access to external memory.
CCNC maintenance covers all functions which serve to maintain the technical system
of the CCNC and the message paths within the EWSD system. The CCNC maintenance
system is divided into the hierarchical levels: SILT, SILTC and CCNP.
The interfaces between two levels are the responsibility of the unit at the higher of the
two levels.
Maintenance comprises the following functions:
• error detection
• fault analysis
• system restoration
– configuration
– recovery
• reporting
• updating
• diagnosis
• CCNC redundancy (duplication)

5.1 Error detection

The monitoring hardware detects the following errors in the CCNC functional units:
– memory errors
– endless loops (by watchdog)
– interface/communication errors (by watchdog)
– violations of memory write protection
– continuity check failures
Defensive checks are built into all SS7 software functions, i.e. every program has to
perform error detection routines such as plausibility checks or range checks when it is
called by another routine, when it accesses data or when it terminates and relinquishes
control to another program.
Routine tests are another error detection facility. They test the following units: CCNP
changeover to standby, the processors and memory on each module; plus the files
SY.PSW/SY.SIMP in the background memory. Data stored in memory is protected by
parity checks and partially or completely under write protection.
A continuity check monitors the operability of interfaces between functional units.

32 A30828-X1130-K400-1-7618
Information Signaling Common Channel Signaling Network
Control (CCNC)

5.2 Fault analysis

Fault analysis is performed at all levels, in some cases with the support of the CP. The
fault analysis functions in each unit report detected faults to the SIMP, which passes the
reports on to the CP if the CP is expected to perform countermeasures. Faults are
assigned to 7 categories by the fault analysis function in the SIMP or CP. The categories
are defined by the subsequent action to be taken as a consequence of the fault.
Examples of subsequent actions are:
– ignore
– record in statistics
– configure
– system new start
– error message/reporting
– diagnosis

5.3 System restoration

If a system unit fails, the maintenance complex has two ways of restoring the system to
service:
– configuration
– recovery

Configuration
Both the CP and the SIMP are able to start configuration actions. In each case, the
higher-ranking unit configures the units dependent on it, i.e. the CP configures the entire
CCNP, the SIMP configures SIPA, SILTC and SILTD.
Configuration commands transfer the functional unit in question to one of the following
operating states:

ACT active
STB stand-by
UNA unavailable
SEZ seized
NAC not accessible
PLA planned
SED seized for diagnosis
CBL conditionally blocked
MBL maintenance blocked
EAC emergency active
Any unit which is able to issue configuration commands stores the states of the units in
configuration tables.

A30828-X1130-K400-1-7618 33
Common Channel Signaling Network Information Signaling
Control (CCNC)

Recovery
Both the CP and the CCNC itself can execute recovery actions for the CCNC. The CP
has the task of supporting recovery measures in the CCNP that require the reloading of
programs and/or data, because the CCNP does not have direct access to background
memory.
There are three types of recovery:
– restart (no more than one message is lost)
– new start (processor initialized and messages lost)
– initial start (global recovery action, system initialization, loss of all messages)
SIPA, SILTC and SILT can send a request for new start to the SIMP. The CPI and SIMP
can send a request for a new start to the CP.

5.4 Reporting
The CP operating system provides the functions and interfaces needed to edit the
output data generated by the reporting function in the CCNC maintenance software.
Output data are:
– alarm printouts (error messages)
– alarm indications at the system panel
– safeguarding data for the history file (a file on the hard disk which records all errors
detected in the system)
– printouts of fault symptoms stored in a processor’s error notebook

5.5 Data backup

This task is handled by the update function in the maintenance software. It transfers new
or modified items of semipermanent data, entered via man-machine language (MML)
commands, to the CCNC and makes changes to transient CCNC data, for instance data
resulting from configuration actions, and updates the data memories of the standby
CCNP. The update function also saves the CCNC data to the background memory
(magnetic disk).

5.6 Diagnosis
Diagnosis is the means of identifying the cause of trouble and failures.
Diagnosis is started and controlled by MML commands entered at an operation & main-
tenance terminal and proceeds as follows:
– configuration of the unit under diagnosis to the state ‘seized for diagnosis’
– sending one or more diagnosis commands to the CCNC to start a diagnostic routine
– receiving one or more diagnosis responses
– evaluating the diagnosis responses
– formulating feedback messages to the system operator
– output in MML format.
The edited information contains details on the malfunctions in the unit.

34 A30828-X1130-K400-1-7618
Information Signaling Common Channel Signaling Network
Control (CCNC)

5.7 CCNC redundancy (duplication)

Fundamentally different failure strategies are employed in the two main functional units
of the CCNC (CCNP and SILTG)
The central unit, CCNP, is duplicated. Each CCNP forms a failure unit. One of the two
CCNPs is active and responsible for the level 3 functions and for monitoring and oper-
ational tasks. The second CCNP (system half) is on standby. All semipermanent and
transient data in the two system halves are kept up-to-date by the CP and the active
CCNP. In addition, the standby CCNP performs safeguarding tasks (routine tests) to
ensure a high level of availability in the event of a switchover. If switchover takes place
because the active CCNP fails, no messages are lost apart from those that are being
processed by the CCNP at that time. If the switchover is instigated by means of a config-
uration command (soft switchover), no messages are lost.
SILTD and SILTC are not duplicated because it is possible to switch to other signaling
links serving the same destination area.
Each of the two CCNPs processes interfaces to IOP:MB0/1 and to every SILTG. As a
result, every SILTG and every IOP:MB can interoperate with each of the two CCNPs.
Furthermore, every SILTD can interoperate with either of the two switching network (SN)
halves. If one SN half fails, the call processing traffic for all SILTDs is switched onto links
serving the other SN half.

LTG

SN0 SN1

CCNC
MUXM0 MUXM1

MUXS

SILTD

SILTC

CCNP0 CCNP1

CP
IOP:MB0 IOP:MB1

Fig. 5.1 Duplication of functional units in the CCNC

A30828-X1130-K400-1-7618 35
Common Channel Signaling Network Information Signaling
Control (CCNC)

6 CCNC administration
The administration software contains programs which implement the functions needed
to
– administer the CCNC
– administer the signaling network
– create, cancel and modify network and CCNC data
The administration programs are distributed among the CP, SIMP, CPI and SILTD. The
functional units SILTC and SIPA do not handle any administrative functions.
The operating personnel can use specific MML commands for administrative tasks
relating to the CCNC. Programs in the CP forward the corresponding jobs to the CCNC
and at the same time ensure that the administrative data in the CPs external memory is
updated. Thus, all data describing the configuration of the CCNC and the signaling
network can be entered, modified or canceled via the MML interface. The unit handling
the most central administrative tasks in the CCNC is the SIMP (collection of measure-
ment data). The SIMP records the administrative data collected in the CPI and in the
SILTDs and edits the data. Each SILTD obtains information on the load on the signaling
link. Measurements in the CPI provide information on the volume of messages gener-
ated by users in the own node. And lastly, the SIMP collects information on the volume
of forwarded message signal units.
The tasks are divided into the following areas:
• load observation
• grade-of-service observation
• administrative configuration
• administration of operating parameters
• recording

Load observation
The following traffic flows are measured:
– signaling point traffic
– signaling transfer point traffic
– total traffic (signaling point traffic and signaling transfer point traffic)
Measurement of these traffic flows is activated by means of MML command.

36 A30828-X1130-K400-1-7618
Information Signaling Common Channel Signaling Network
Control (CCNC)

Grade-of-service observation
Grade-of-service observation covers the following elements:
– Transmission quality
In order to determine the transmission quality on a signaling link, a count is made of
the numbers of receive and send transmission repeats. The counts are maintained
in the SILTD. The observation of transmission quality can be activated by MML
commands.
– Network performance
In order to determine the network performance, i.e. the actual availability of the
signaling elements, signaling network management observes and records state
changes in the following signaling network elements:
signaling link sets, signaling links, signaling route sets. These state changes are
output unsolicited.
– System performance
In order to determine the system performance, the behavior of the system compo-
nents during overload situations is observed. This involves the recording of the
beginning, end and location of such situations, and any measures to deal with them;
these details are forwarded unsolicited to the administration system in the CP.
The observation periods are specified by the operator.

Administrative configuration
Administrative configuration comprises the following activities:
– Creation/cancellation of units within the CCNC
Operating personnel use MML commands to create or delete data maps of the
installed hardware devices, thus these devices exist or are eliminated as far as the
software is concerned.
– Creation/cancellation of signaling network elements
This makes it possible to add or remove signaling network elements in the signaling
network within a plan period.
The signaling network elements concerned are
own signaling point/signaling transfer point, signaling data link, signaling link set,
signaling link, signaling route set.
– Administration of CPI allocation tables
The tables in the CPI which are to be maintained by the administrative programs are
used for converting the internal CCNC data formats into the EWSD data formats and
vice versa.
– Configuration of signaling network elements
This complex of programs activates/deactivates and blocks/unblocks the signaling
links/signaling link sets.
– Testing of signaling network elements.
– Putting the CCNC into service
Original start up of the CCNC:
Before signaling traffic is released by the administration system, the CCNC
elements and the signaling link elements must be tested, and the details of the
CCNC and signaling link elements written into the spaces provided in the application
program system (APS) table for this purpose.
Restarting the CCNC:
Each time the system is restarted, the administration system must reload the CPI.

A30828-X1130-K400-1-7618 37
Common Channel Signaling Network Information Signaling
Control (CCNC)

Administration of operating parameters

The administration system maintains the following types of operating parameters:
– Operating parameters to control signaling traffic, e.g. the ’load sharing key’ for
signaling link sets, which controls the selection of signaling links in a set.
– Smoothing parameters for setting guard periods; a guard period is a time period,
which must be specified, from the incidence of a fault until the message reporting it
is output (30 s up to 10 min).
– Threshold parameters for the number of discarded (misdirected) signaling
messages (message signaling units, MSUs), specifying the point at which an output
message must be generated, and for the number of discarded MSUs lying above the
threshold which must be appended to the output message.
– Threshold parameters for system messages about unsuccessful attempts to release
calls on a signaling link.
– Parameters for alarm and overload situations:
alarm priorities and overload conditions
Each of these parameters can be set and activated by means of an MML command.

Recording
The recording function incorporates the output of information about the CCNC and the
signaling network to the background memory in the CP, to a craft terminal or to a printer.
A distinction is made between:
– Indicators which are output as the reply to a query, e.g. about the magnitude of an
operating parameter.
– Outputs resulting from system activities; such activities could be
initiated by the operator (traffic volume recording for a signaling link)
controlled by the operator by means of threshold values (misdirected messages)
permanently embedded in the application program system, (APS) (alarm report)
Whereas indicators are always output to an operation & maintenance terminal or printer,
in the case of outputs the operator can specify the output medium.

38 A30828-X1130-K400-1-7618
Information Signaling Common Channel Signaling Network
Control (CCNC)

7 CCNC overload control

The CCNC is equipped with functions to detect and deal with overload, in order to
ensure trouble-free operation even under high traffic loads.
Overload in the various functional units is detected by counting the number of routine
tests: a low number of routine tests indicates a high processor load.
In addition, overload in transmitters and receivers (SILTD) is detected by measuring the
occupancy level of transmit and receive buffers and when the traffic volume counters
exceed defined thresholds. To counteract these situations, the processors send
messages to their users or to users in the adjacent signaling point (SP), instructing them
to reduce the message flow. Reduction is effected by a specified quantity per received
overload message. If no more overload messages are received within a certain period,
the recipients of the earlier overload messages resume their normal message transmis-
sion operation in stages.
The overload control actions are designed to have no effect whatsoever on the execu-
tion of maintenance functions (e.g. configuration of a signaling link, restart of the CCNC
or a functional unit).
Even overload control actions, such as non-acknowledgment of a message signal unit
(MSU) if the receive buffer overflows, do not cause signaling links to be taken out of
service.
The overload control actions do not lead to overload situations in other signaling points.

A30828-X1130-K400-1-7618 39
Common Channel Signaling Network Information Signaling
Control (CCNC)

8 CCNC technical data

Transmission speed with connection of an analog signaling
channel: 4.8 kbit/s
Transmission speed with connection of a digital signaling channel: 56 kbit/s or
64 kbit/s
Any pair of channels on a digital link that can be connected to
EWSD can be used as a signaling link.

Memory capacity of messages if there is a backlog due to overload: 8 kbyte

Maximal signaling traffic load per link: greater than 0.4 Erl
approx. 1000 voice circuits can be controlled with: 0.2 Erl

Each SILTD is capable of forwarding SP traffic and/or STP traffic to

the SIMP.

Number of possible signaling links in one signaling link set: 16

Number of possible digital signaling links: 254

Number of possible analog signaling links: 128

Full availability of all signaling points in the common channel

signaling network

Accessibility of at least 1000 destinations from any point in the

network via the adjacent STP

Number of signaling networks for SEP traffic and for STP traffic: 3 in each case

Number of destinations and destination areas in all networks: 2000

Number of destinations and destination areas in all signaling

net works: in each case
- national network 0 (NAT0), national network 1 (NAT1),
- international network (INAT0) 2000

Number of networks per signaling link set: 1

Number of possible routes via one link set: 2000

Users in the signaling networks in SEP traffic:
NAT0: TUP
ISDN/TF
ISUP/ETSI
INAT0: ITUP
ISUP/ETSI
(There are no restrictions in STP traffic)

Number of SS7 trunk groups per DPC/user: 6

40 A30828-X1130-K400-1-7618
Information Signaling Common Channel Signaling Network
Control (CCNC)

Number of SS7 trunks per trunk group and in total per DPC: 4095

Number of SS7 trunks with switching network for 252 LTGs: 30,000 *)
*) This is a statistical value; the number of SS7 trunks that can be
operated dynamically is calculated from the average trunk load, call
model and MSU throughput.

Max. message throughput of the CCNC, Version 3+, at an average

message length of 25 bytes, at 0.64 Erl processor load (ITU-T ref.
load A):
in pure SEP traffic: 2 x 1800 MSU/s
in pure STP traffic: 2 x 2800 MSU/s
in mixed SEP and STP traffic: 4580 MSU/s

A30828-X1130-K400-1-7618 41