Introduction

GN Nettest's aim in publishing this series of technical

notes is to provide clear and correct information on rel e-

vant technical subjects.

This technical note is the fourth issue. It has been

rewritten to give the reader basic information that is hard

to find in other documents. It also forms a part of the

material used in the training pro grams offered by GN

Nettest.

We also wish to inform the reader about GN Nettest's

credentials as one of the world's leading manufacturers

of advanced telecommunications test and measurement

instruments – credentials that result from our

commitment to an intensive research programme. This

research programme strives to bring our customers new

equipment that combines the latest technology with

cost-effectiveness and ease of operation.

When an instrument in our range has rele vance to

the topic discussed, we have included a brief description

of that instrument.

January 1999

Issue 4

GN Nettest A/S
Kirkebjerg Allé 90

DK-2605 Brøndby

Denmark

Tel: +45 72 11 22 00

Fax: +45 72 11 22 10

E-mail: com@nettest.dk

Web: www.gnnettest.dk
Contents
1. Signalling ....................................................................................... 3

2. The Signalling Network ................................................................ 4

3. Signalling System No. 7 Levels..................................................... 5

3.1 OSI Reference Model ........................................................................ 5

4. Signalling-data Link (Level 1) ....................................................... 7

5. Signalling-link Functions (Level 2) ............................................... 8

5.1 Basic Frame ...................................................................................... 8

5.2 Message Types ................................................................................. 8

5.3 Error Correction ............................................................................... 9

5.4 Preventive Cyclic Retransmission (PCR) ........................................... 10

5.5 Length Indicator ............................................................................. 10

5.6 Network Management (LSSU) ........................................................ 11

5.6.1 Alignment ............................................................................. 12

5.6.2 Error Monitoring (SUERM) ..................................................... 13

6. Signalling Network Level Functions (Level 3) ........................... 14

6.1 Service Information Octet (SIO) ....................................................... 14

6.2 Routing Label ................................................................................. 15

6.3 Heading Code ................................................................................ 16

6.4 Network Management (SNM) ......................................................... 16

6.5 Network Testing (SNT) .................................................................... 19

7. User and Application Parts (Level 4) .......................................... 20

7.1 Telephone User Part (TUP) .............................................................. 20

7.2 ISDN User Part (ISUP) ...................................................................... 22

7.3 Signalling Connection Control Part (SCCP) ..................................... 27

7.3.1 Connection-oriented Data Transfer ........................................ 28

7.3.2 Connectionless Data Transfer ................................................ 28

7.3.3 SCCP Format ......................................................................... 29

7.3.4 SCCP Management ............................................................... 33

7.4 Transaction Capabilities Application Part (TCAP) ............................. 34

7.4.1 TCAP Transaction Sub-layer ................................................... 35

7.4.2 TCAP Component Sub-layer .................................................. 36

7.5 Operations, Maintenance and Administration Part (OMAP) ............ 36

7.6 GSM Mobile Application Part (MAP) ............................................... 36

7.7 Intelligent Network (INAP) .............................................................. 36

7.8 MTP Tester ..................................................................................... 40

8. Test and Maintenance................................................................. 42

8.1 Multichannel Protocol Analyser MPA 7xxx ...................................... 42

8.2 LITE 3000 ....................................................................................... 45

8.2.1 Main Features of the LITE 3000: ............................................ 45

8.2.2 General Description ............................................................... 46

8.2.3 Testing Transmission Quality .................................................. 46

8.2.4 SS7 Signalling Analysis in the LITE 3000 ................................. 46

8.2.5 Signalling Statistics ................................................................ 48

8.2.6 Other Signalling Options ........................................................ 48

9. References.................................................................................... 49
 1. Signalling
In any network, the definition of signalling is the A number of features differentiate CCS signalling from

exchange of information. In a tele communication CAS signalling:

network, signalling is the exchange of information that • Signalling and speech can be sent on separate PCM

relates to the establishment and control of links. This gives network design ers the possibility to

connections, including management. design robust networks that can withstand the

Today most transmission between tele phone failure of one or more PCM links.

exchanges is digital, but in some cases signalling • It has built-in error detection in the signalling,

operates on specifications developed for analogue thereby enabling error correc tion. The CAS,

exchanges. The exchanges in these networks use however, only has the option, if there are errors, of

Channel Associated Signalling (CAS). The CAS restricts dropping the connection, leaving reestablishment

signalling to the PCM link in which the telephone to the user.

connections take place. • It can carry signalling for a large num ber of

This means that the number of connections that connections (> 1000) in a single time slot, thereby

the CAS signalling controls is equal to the capacity of freeing time slots for connections.

the PCM link (30 in 2 Mbit/s systems and 24 in • Using data network techniques, it can carry other

1.5 Mbit/s systems). The CAS signalling also service information – for example requests for

monopolises one time slot (channel) for signalling number information, either from an operator

purposes in 2 Mbit/s systems. (information) or through computers in the network

Signalling System No. 7 uses a dif ferent method. It (800 numbers, GSM location-register lookups or

uses the same communication techniques as modern updates).

data networks: Common Channel Signalling (CCS). Thus, the designers of Signalling System No. 7 have

If the data-network approach is used, the signalling given different user groups their sets of messages,

for a number of connections takes place in a single depending on the needs of these user groups. The

time slot (channel). The same time slot can also architecture of Signalling System No. 7 makes it easy to

transfer other required signalling information needed implement new messages for a new user group

for operation of the network. without affecting existing user groups in the system.

The basis for this description of Signalling System

No. 7 is the ITU-T Q-series Recommendation, Helsinki

Q3/93 (White Book).

3
 2. The Signalling Network
The signalling network consists of a number of nodes network can survive the loss of one signalling path

interconnected by signalling links, with each link without customers being seriously affected. It also

consisting of two PCM links (one for each direction). A ensures that the nodes can split the traffic between

number of links that interconnect two nodes directly the available signalling paths and thereby reduce the

are called a signalling link set. The topography of the damage if there is a failure. In this context, failures

network is such that there are at least two signalling include loss of signalling processors located at the

paths and a maximum of eight signalling paths be- nodes as well as loss of the physical link set.

tween any nodes in the network. This ensures that the

SS7 signalling SCP

Speech circuit

Access signalling STP STP

A B
SSP SSP

STP STP

Fig. 2.1 ITU-T System No. 7 signalling network.

An SSP (Service Switching Point) is the node directly nodes. An STP can be a stand-alone unit or include an

serving the subscribers − for example a telephone SSP.

exchange for control of speech connections. An SCP (Service Control Point) is used for control of
An STP (Signalling Transfer Point) is used for intelligent network (IN) services.

transfer of signalling messages between network An SP (Signalling Point) is the name of a network
node (SSPs, STPs and SCPs are all SPs).

4
 3. Signalling System No. 7 Levels
Signalling System No. 7 is not a large monolithic This data link transfers signals in both directions

system. It is a layered system, in which each layer (level) simultaneously.

contains a well-defined functionality, including the

interface (functions and procedures). 2. Signalling Link

Each level provides services to the level above and The signalling link defines the functions and

uses the services of the level below to obtain the procedures for transmitting information in one data

functionality. This means that an entire level can be link. The link level shares the task with the data link of

replaced without levels above or below having to be ensuring reliable transmission between two signalling

changed. More importantly, new functionality can be points.

added to the topmost level, thereby implementing

more functionality in the network. 3. Signalling Network

This is the most important aspect of the Signalling The signalling network level defines the functions for

System No. 7 levels, because the user can add new routing the signalling information in the signalling

services to the network without affecting existing network, depending on the network's condition. The

services, resulting in a dynamic network rather than a network level also defines functions for test and

static one. maintenance.

Levels 1-3 together are called the message transfer

The four levels of Signalling System No. 7 are: part (MTP).

1. Signalling Data Link 4. User and Application Parts

The data link defines the characteristics (physical, The user level defines functions and procedures for

electrical and functional) for the data transmission link. different user parts. A user part can, for example, be

the signalling set for telephone users.

TUP ISUP SCCP IN

User and Application Parts
TUP ISUP SCCP IN
Level 4

Level 3 Signalling Network Functions Level 3

Level 2 Signalling Link Functions Level 2

Signalling Data Link (Level 1)

Fig. 3.1 Signalling System No. 7 levels.

3.1 OSI Reference Model

Signalling System No. 7 was developed before the Signalling System No. 7 defines a four-level

creation of open-system architecture. The developers' architecture that corresponds with the four functional

aim was to define a signalling system, not a general- groupings. The signalling data link function provides

purpose communication system. the services expected of an OSI physical layer. The

Signalling System No. 7 is a layered architecture. signalling link maps onto the OSI layer 2 data link. The

The layers are not in exact alignment with OSI. signalling-network functions fall into the network layer

5
of OSI. The MTP does not offer the complete OSI System No. 7 combines the higher-layer OSI functions

network service; it only provides a sequenced into a formless block called the user part.

connectionless service to the user parts. Signalling

Application

Presentation
User and

Application Parts
Session

Transport

Network
Signalling Network

Message
Data Link Signalling Link Transfer

Part (MTP)

Physical Data Link

OSI Layers Signalling System No. 7 Levels

Fig. 3.2 Signalling System No. 7 and the ISO OSI model.

6
 4. Signalling-data Link (Level 1)
In summary, level 1 has the means of sending a stream Basically, any available channel can be used. A

of bits of information from one point to another over a minimum of 4.8 kbit/s is specified for telephone

physical connection. signalling purposes.

The requirements for the signalling-data link are Error-performance requirements are specified for

defined in ITU-T Rec. Q.702. The standard signalling the particular channel type. In general, the objective is
-6
rate is 64 kbit/s, but many exceptions are permitted. a BER (Bit Error Rate) of less than 10 .

7
 5. Signalling-link Functions (Level 2)
The signalling-link level provides a reliable transfer of • Initial alignment of data link.

signalling messages between two directly connected • Error monitoring and reporting.

signalling points over one individual signalling data link. • Link-flow control.
The link-level functions include: These functions are usually modelled as a state-driven

• Delimiting of frames. protocol machine. The activities of this machine are

• Alignment of frames. coordinated by the link-state control.

• Error detection.

• Error correction by retransmission.

5.1 Basic Frame

The basic frame consists of an opening flag, opening flag on the following frame. The flag is the bit

information, checksum and a closing flag. In some sequence 01111110. The transferred information in
implementations the closing flag is also the the frame is binary.

F CK Information F

01111110 16 bit n x 8 bit 01111110

(8 bit) (8 bit)

F = Flag

CK = Checksum (CRC-16)

Fig. 5.1 Basic frame structure.

To prevent false flags in information and checksum, The 16-bit checksum is there to enable the receiver to

the transmitter performs bit stuffing on all bits detect changes in the frame during transmission. If

between the flags: Whenever the transmitter has sent that occurs, the receiver will disregard the frame.

five one-bits, it will insert one zero-bit. The receiver will

remove the zero-bit if it comes after five one-bits.

5.2 Message Types

Signalling System No. 7 transmits all frames (messages) 2. Message Signal Unit (MSU). The node uses the

as units. The system operates with the follow ing three MSU for carrying signal information for user parts

signal units (SUs): located at other nodes.

1. Link Status Signal Unit (LSSU). The node uses the 3. Fill-in Signal Unit (FISU).The node uses the FISU as

LSSU at link start-up or for handling severe errors an idle signal for error surveillance – for example

on the link. when there is no information to transfer.

8
 5.3 Error Correction
Error correction is only performed on MSUs. To enable sequence number (BSN), the backward indicator bit

the error correction between two nodes, four fields are (BIB), the forward sequence number (FSN), and the

present at the beginning of each frame: the backward forward indicator bit (FIB).

F B
F CK Information I FSN I BSN F
B B

8 16 1 7 1 7

F = Flag (01111110)

CK = Checksum (CRC-16)

FSN = Forward Sequence Number

BSN = Backward Sequence Number

FIB = Forward Indicator Bit

BIB = Backward Indicator Bit

Fig. 5.2 Format of BSN, BIB, FSN and FIB .

The BSN and FSN contain a 7-bit value which is a The receiver side of the node uses the BSN to

number in the range 0-127. The transmitter side of the acknowledge received MSUs. The node does this by

node increments the FSN for every MSU frame sent. setting the BSN equal to the FSN of the last correctly

When the transmitter increments the FSN beyond 127 received MSU. Because of the size of the FSN and BSN,

it changes to 0. The transmitter uses the FSN as a label there is no need to acknowledge every MSU.

on every frame. The receiver in the opposite node uses The transmitting side keeps copies of the MSUs

the FSN to detect lost MSUs. that have been transmitted. These copies are kept until

the receiving side has accepted them.

MSU FSN=01
BSN=01 MSU
MSU FSN=02
MSU FSN=03
MSU FSN=04
BSN=04 MSU
MSU FSN=05
MSU FSN=06

Fig. 5.3 Example of acknowledgement of correctly received MSUs.

When the receiver side detects a lost MSU, it inverts starting with the frame with an FSN value one higher

the BIB to request retransmission. The BSN assumes than the received BSN, inverting the FIB to indicate the

the value of the last accepted MSU. retransmission. When new frames are transmitted, no

Upon receipt of the request for retransmission, the inversion of the FIB takes place.

receiver side retransmits the signalling messages,

9
 SP SP
MSU FIB=0 FSN=80 BIB=0 BSN=27

MSU FIB=0 FSN=81 BIB=0 BSN=27

MSU FIB=0 FSN=82 BIB=0 BSN=27

MSU FIB=0 FSN=83 BIB=0 BSN=27

BSN=80 BIB= 1 FSN=28 FIB=0 MSU

MSU FIB=1 FSN=81 BIB=0 BSN=28

MSU FIB=1 FSN=82 BIB=0 BSN=28

MSU FIB=1 FSN=83 BIB=0 BSN=28

BSN=83 BIB=1 FSN=28 FIB=0 FISU

MSU FIB=1 FSN=84 BIB=0 BSN=28

MSU FIB=1 FSN=85 BIB=0 BSN=28

= Lost frame

Fig. 5.4 Example of request for retransmission due to lost MSU frames.

Fig. 5.4 shows a sequence of frames being sent. The frames that are not confirmed and informs the receiver

receiver detects the error and requests retransmission by inverting the FIB. Finally, the receiver confirms the

by inverting the BIB. The transmitter transmits the frames, and signalling continues normally.

5.4 Preventive Cyclic Retransmission (PCR)

In systems that have long propagation delays – for 2. If new signal units are available, the retransmission

example satellite systems – preventive cyclic cycle (if any) must be interrupted and the signalling

retransmission of unacknowledged MSUs is used in units transmitted with first priority.

order to reduce error-correction times: 3. Under normal conditions, when there are no me s-

sage-signal units to be transmitted or cyclically r e-

1. If no new signal units are available for transmission, transmitted, fill-in signal units are sent continuously.

message-signal units which are available for

retransmission are retransmitted cyclically.

5.5 Length Indicator

The final mandatory information in the frame is the how many bytes are contained in the information part

length indicator (LI). The LI contains information about of the frame and indicates the message type indirectly.

10
 F B
F CK Information LI I FSN I BSN F
B B

8 16 6 1 7 1 7
F = Flag (01111110) FIB = Forward Indicator Bit
CK = Checksum (CRC-16) BIB = Backward Indicator Bit
FSN = Forward Sequence Number LI = Length Indicator Bit
BSN = Backward Sequence Number

Fig. 5.5 Format of length indicator.

The LI is a 6-bit field. Using 6 bits gives a number in the • LI > 2 indicates an MSU.

Level 2 Level 4 Level 3 Level 2

F B
MSU F CK SIF
SIO/
LI > 2 I FSN I BSN F
Label B B

Level 2 Level 3 Level 2

F B
LSSU F CK SF LI = 1-2 I
B
FSN I
B
BSN F

Level 2

F B
FISU F CK LI = 0 I FSN I BSN F
B B

SF = Status Field
SIF = Signalling Information Field
SIO = Service Information Octet

range 0-63, where: If the information is longer than 62 bytes, the LI has

• LI = 0 indicates a FISU. the value 63. Otherwise the LI con tains the length of

• LI = 1 or 2 indicates an LSSU. the information in the frame.

Fig. 5.6 Format of signal-unit types.

5.6 Network Management (LSSU)

A vital component of the network management on the indicate the sender's view of the actual status of the

link level is the LSSU, which contains either a one-byte link. LSSUs have the highest priority of all signal units.

or two-byte information field. This field is used to

Level 2 Level 3 Level 2

F B
F CK SF LI I FSN I BSN F
B B
8 or 16
bits

Spare CBA

Fig. 5.7 Format of an LSSU.

11
Only the first three bits of the status field are used, with the remaining bits spare. The assigned values are:

Indication C B A
Status "O" – Out of alignment 0 0 0
Status "N" – Normal alignment 0 0 1
Status "E" – Emergency alignment 0 1 0
Status "OS" – Out of service 0 1 1
Status "PO" – Processor outage 1 0 0
Status "B" – Busy 1 0 1

The OS status is sent when the link can neither tran s- associated processor is out of service. Level 2 conge s-
mit nor receive MSUs. The PO status is sent when the tion is indicated by the B status.

5.6.1 Alignment
Link alignment is the process of synchronising the data restoration following a link failure. Alignment is based
link between two directly connected signalling points. on the compelled exchange of status information and
It is applied initially at power-on time and during a proving period to validate performance.

SP SP

Start LSSU SIO

Aligned LSSU SIO or SIN
LSSU SIN
Proving LSSU SIN

8.2 sec

LSSU SIN
Aligned and
ready LSSU SIN

Fig. 5.8 Successful alignment of a link.

The normal, successful alignment procedure is illu s-
trated in fig. 5.8. A signalling terminal begins by sen d-
ing LSSUs carrying the Status Indicator "O", which
means out of alignment. This continues until the st a-
tion receives an LSSU with either an "O" or an "N"
(normal alignment) status. This indicates that the link is
operational and that the station can achieve frame
alignment. The two stations enter the proving phase
where they repeatedly transfer LSSUs to each other
while monitoring the error rate. The proving period is
216 octet times for normal alignment and 2 12 octet
times for emergency alignment. This works out at 8.2
and 0.5 seconds at 64 kbit/s and 110 and 7 seconds at
4.8 kbit/s.

12
 5.6.2 Error Monitoring (SUERM)
To support the objective of a reliable, responsive, and
efficient data-link service, the Signalling System No. 7
link mechanism incorporates an error-monitoring
function. A responsive error-monitoring system is
obtained by using an up-down counter. Receipt of an
erroneous signal unit causes the counter to step up by
one count. Receipt of 256 error-free signal units causes
the counter to step down by one count. If the counter
reaches its maximum limit of 64, an alarm is triggered
and the network level is notified.

Alarm
Error Up

6-bit counter

Good /256 Down

Fig. 5.9 SUERM counter.

This is also called a "leaky bucket" because each error

event causes a large increase in the main counter that
can slowly leak away as good blocks are received.

13
 6. Signalling Network Level Functions (Level 3)
The third level of Signalling System No. 7 provides the
functions and procedures for controlling the transfer of
messages between the nodes of the signalling
network. The signalling network levels build their
routing and management functions on top of the
underlying signalling link. Using these links, the
network level ensures a reliable transfer of messages
even when there is a link or node failure.
The level 3 functions are divided into two basic
categories: signalling-message handling and signalling-
network management.
Signalling-message handling ensures that messages
originated by a user part at a signalling point are
delivered to the corresponding user part at the
specified destination. The message-handling function
includes discrimination, distribution and routing.
Signalling-network management includes the func-
tions necessary to reconfigure the network if there is a
failure and to execute traffic-flow control when nece s-
sary. Network management includes traffic manag e-
ment, link management and route management.

6.1 Service Information Octet (SIO)

In message signal units (MSUs), the service information further divided into a two-bit network-indicator code
octet (SIO) is used to perform message distribution. and two bits that are spare if the indicator code is 00
This octet is divided into a four-bit service indicator (SI) or 01, or are available for national use if the indicator
and a four-bit subservice field. This subservice field is code is 10 or 11.

Level 2 Level 4 Level 3 Level 2

F B
F CK SIF Label SIO LI I FSN I BSN F
B B

8 bits

D C B AD C B A
Sub-service Service
Field Indicator

Fig. 6.1 SIO format.

Bit assignment for the Service Indicator (SI) is:

Indication DCBA Hex

Signalling-network management messages (SNM) 0 0 0 0 0

Signalling-network testing and maintenance messages (SNT) 0 0 0 1 1

Spare 0 0 1 0 2

Signalling connection control part (SCCP) 0 0 1 1 3

Telephone user part (TUP) 0 1 0 0 4

ISDN user part (ISUP) 0 1 0 1 5

Data user part (call and circuit-related messages) 0 1 1 0 6

Data user part (facility registration and cancellation messages) 0 1 1 1 7

MTP testing user part 1 0 0 0 8

1 0 0 1 9

Spare to

1 1 1 1 F

The data user part is not implemented and the related ITU-T recommendations have been deleted.

14
Bit assignment for the sub-service field is:

Meaning DCBA
International network 0 0 X X

Spare 0 1 X X

National network 1 0 X X

Reserved for national use 1 1 X X

The network indicator (bits D, C) provides for example, between functionality in two national
discrimination between international and national signalling networks with differing routing-label
messages. They can also be used for discrimination, for structures.

6.2 Routing Label

The "label" contains the routing information for messages. One of four different label types can be
delivery of MSUs from source to destination. It is used used, depending on the user part.
by both user messages and network-management

Level 2 Level 4 Level 3 Level 2

F B
F CK SIF Label SIO LI I FSN I BSN F
B B

TYPE A
Originating Destination
MTP Management Management Information SLC
Point Code Point Code
Messages

TYPE B Signalling Information

Circuit ID Code Originating Destination

TUP Messages SLS Point Code Point Code

TYPE C Signalling Information

Circuit
SLS
Originating Destination

ISUP Messages ID Code Point Code Point Code

TYPE C SCCP User Data SLS

Originating Destination

SCCP Messages Point Code Point Code

Fig. 6.2 Label types.

The destination point code (DPC) indicates the
signalling point for which the message is intended. The
originating point code (OPC) indicates the signalling
point that is the source of the message.
For call-related or circuit-related messages, the
circuit identification code (CIC) indicates the call or
circuit to which the message is related. The four most
significant bits of the CIC field are used to indicate the
signal link selection (SLS). SLS indicates the signal link
to be used if more than one link is used for signalling
(load sharing).
For message transfer part management
information, the signalling link code (SLC) is used to
indicate the signalling route.

15
 6.3 Heading Code
The heading code appears after the label in the
signalling-information field. This "message header" is a
Message Heading
Code
8 bits
H1 H0
D C B AD C B A
Type
Indicator
Fig. 6.3 Heading-code format.
Groups and types are unique only within the message
category. It is therefore necessary to process this field
in conjunction with the SI field in order to determine
the signalling-message format. For example, if the SI
6.4 Network Management (SNM)
Network management on the MTP level contains
procedures for handling changeover and rerouting of
messages.
A changeover from one link set to another is
initiated when a signalling link is recognised as
unavailable. This may be due to an excessive signal
unit-error rate or other errors on the line. The limit of
the error rate is decided by the SUERM counter (see
16
single octet field that identifies the message group and
then the message type within the group.
Label
Group
Indicator
indicates a network-management message (SI code
0000), the group indicator 0001 indicates a change-
over message and the type indicator 0010 indicates a
changeover acknowledgement signal.
the section "Error Monitoring (SUERM)"). The message
group, signalling network management (SI = 0000), is
used to transmit changeover messages.
The first field in a message indicates the message
type with the heading codes H0 and H1. Fig. 6.4
shows the heading codes for signalling-network
management messages.
 Level 2 Level 4 Level 3 Level 2
F B
F CK SIF SIO LI I FSN I BSN F
Label B B

Heading Heading
Code H1 Code H0

Abbr. Message H1 H0

COO Changeover order signal 1

COA Changeover acknowledgement signal 2
1
CBD Changeback declaration signal 5
CBA Changeback acknowledgement signal 6
ECO Emergency changeover order signal 1
2
ECA Emergency changeover acknowledgement signal 2
TFP Transfer prohibited signal 1
TFR Transfer restricted signal 3 3
TFA Transfer allowed signal 5
RST Signalling route set test signal for prohibited destination 1
5
RSR Signalling route set test signal for restricted destination 2
LIN Link inhibited signal 1
LUN Link uninhibited signal 2
LIA Link inhibited acknowledgement signal 3
LUA Link uninhibited acknowledgement signal 4
6
LID Link inhibited denied signal 5
LFU Link forced uninhibited signal 6
LLT Link local inhibit test signal 7
LRT Link remote inhibit test signal 8
TRA Transfer restart allow signal 1 7
DLS Signalling data link connector order signal 1
CSS Connection successful signal 2
8
CNS Connection not successful signal 3
CNP Connection not possible signal 4
UPU User part unavailable 1 A

Fig. 6.4 Heading codes for signalling-network management messages.

The changeover procedure must ensure that signalling
traffic carried by the unavailable signalling link is
diverted to the alternative link as quickly as possible
while avoiding message loss, duplication or mis-
sequencing.
If a failure is detected, an MSU containing a
changeover message will be transmitted on the
alternative link.

17
 A B

Level 2
Level 2 Level 4 Level 3 Level 2
FSN of last H1=1 H0=1 SIO=0 F B
F CK accepted MSU Label LI I FSN I BSN F
COO SNM B B

Fig. 6.5 Example of changeover and an MSU containing the changeover message.

When the changeover message in fig. 6.5 has been
answered by a changeover acknowledgement, the
messages in the retransmission buffer for the
unavailable link are transferred to the alternative link
and transmitted. When the link is in order, the
signalling is transferred back to the original link set.
If the link set CB (in fig. 6.6) is unavailable, a forced
rerouting has to be done by using the signalling
transfer point D. In this case, messages may be lost
because terminal A does not know what has been lost
in link set CB (link-by-link signalling). When the
signalling has been transferred to the alternative link
set, a "transfer prohibited" message will be
transmitted from terminal C to terminal A, and
terminal A will start transmitting the link-status signal
"out-of-service". When the link set is available again, a
controlled rerouting back to the original link set will
occur.

A C B
SP SP
STP

D
STP

Fig. 6.6 Forced rerouting.

A failure in the signalling terminal may make it impos-
sible for the corresponding end of the faulty signalling
link to determine the forward-sequence number of the
last accepted message. If this occurs, the emergency-
changeover procedure is used. The procedure is the
same as for normal changeover, except that the s e-
quence number for the last accepted MSU is not in the
emergency-changeover message and the transmission
starts on the alternative link set without retransmission.

18
 6.5 Network Testing (SNT)
In order to test the network, a signalling link-test of the service information octet. The test message has
message is specified. The user part for network testing the structure shown in fig. 6.7.
is identified by 0001(1) in the service indicator part

Level 2 Level 4 Level 3 Level 2

Test Pattern H1 H0 F B
F CK Label SIO LI I FSN I BSN F
N x 8 bits 0001 0001 B B

Fig. 6.7 Format of signalling-link test message.

19
 7. User and Application Parts (Level 4)

7.1 Telephone User Part (TUP)

ITU-T has specified the international telephone user
part but most countries have their own national
versions. The messages are almost the same in the
different versions but some messages may not be
implemented, in particular national versions. The
parameter fields in the messages are coded differently
in the various versions and will therefore not be
described here. The messages and their formats and
codes described here are based on ITU-T
Recommendation Q.723.

Level 2 Level 4 Level 3 Level 2

F B
F CK SIF SIO LI I FSN I BSN F
Label B B

Heading Code Originating Destination Sub-service Service Indicator

TUP User Data CIC
H1 H0 Point Code Point Code Field 0100
N x 8 bits 8 bits 12 bits 14 bits 14 bits

Fig. 7.1 Basic format of MSU containing a TUP message.

The service information octet (SIO) indicates that the
message belongs to a telephone user part with the bit
pattern 0100 (4 Hex) in the service indicator.
The label contains destination point code,
originating point code and circuit identification code.
For 2 Mbit/s systems the circuit identification code is
coded as follows:
The five least significant bits are a binary
representation of the actual time slot assigned to the
speech circuit. The remaining bits are used, where
necessary, to identify one among several systems
interconnecting an originating point and a destination
point.
The label is followed by the heading codes H0 and
H1. H0 indicates to which message group the message
belongs, and H1 indicates the name of the message
inside the group.

Message H1 H0

Forward Address Messages 1

IAM Initial address message 1

IAI Initial address message with additional information 2

SAM Subsequent address message 3

SAO Subsequent address message with one signal 4

Forward Setup Messages 2

GSM General forward setup information message 1

COT Continuity signal 3

CCF Continuity failure signal 4

Backward Setup Request Messages 3

GRQ General request message 1

Successful Backward Setup Messages 4

ACM Address complete message 1

CHG Charging message 2

20
Message H1 H0

Unsuccessful Backward Setup Messages 5

SEC Switching equipment congestion signal 1

CGC Circuit group congestion signal 2

NNC National network congestion signal 3

ADI Address incomplete signal 4

CFL Call failure signal 5

SSB Subscriber busy signal 6

UNN Unallocated number signal 7

LOS Line out of service signal 8

SST Send special information tone signal 9

ACB Access barred signal A

DPN Digital path not provided signal B

MPR Misdialled trunk prefix C

EUM Extended unsuccessful backward setup-information message F

Call Supervision Messages 6

ANU Answer signal, unqualified 0

ANC Answer signal, charge 1

ANN Answer signal, no charge 2

CBK Clear back signal 3

CLF Clear forward signal 4

RAN Reanswer signal 5

FOT Forward transfer signal 6

CCL Calling party clear signal 7

Circuit Supervision Messages 7

RLG Release guard signal 1

BLO Blocking signal 2

BLA Blocking acknowledgement signal 3

UBL Unblocking signal 4

UBA Unblocking acknowledgement signal 5

CCR Continuity check request signal 6

RSC Reset circuit signal 7

Circuit Group Supervision Messages 8

MGB Maintenance-oriented group blocking message 1

MBA Maintenance-oriented group blocking acknowledgement message 2

MGU Maintenance-oriented group unblocking message 3

MUA Maintenance-oriented group unblocking acknowledgement message 4

HGB Hardware-failure-oriented group blocking message 5

HBA Hardware-failure-oriented group blocking acknowledgement message 6

HGU Hardware-failure-oriented group unblocking message 7

HUA Hardware-failure-oriented group unblocking acknowledgement message 8

GRS Circuit group reset message 9

GRA Circuit group reset acknowledgement message A

SGB Software-generated group blocking message B

SBA Software-generated group blocking acknowledgement message C

SGU Software-generated group unblocking message D

SUA Software-generated group unblocking acknowledgement message E

Circuit Network Management Messages 9

ACC Automatic congestion control information message 1

21
Fig. 7.2 shows how the different messages in the telephone user part can be used during a normal call.

SP SP

IAM Initial address

SAO

Subsequent address
SAO

Address complete ACM

Answer setup, charge ANC

Conversation

CLF
Clear forward signal

RLG
Release guard

Fig. 7.2 Example of a TUP call.

7.2 ISDN User Part (ISUP)

The ISDN user part (ISUP) is the Signalling System No. 7 The ISUP is described in ITU-T Recommendations

protocol which provides the signalling functions Q.761 to Q.764. In addition, the ITU-T Rec. Q.767

required to support basic bearer services and describes an ISUP to be used for international

supplementary services for voice and non-voice signalling.

applications in an Integrated Services Digital Network

(ISDN).

Level 2 Level 4 Level 3 Level 2

F B
F CK SIF SIO LI I FSN I BSN F
Label B B

Message Originating Destination Sub-service Service Indicator

ISDN User Data CIC SLS
Type Point Code Point Code field 0101
N x 8 bits 8 bits 12 bits 4 bits 14 bits 14 bits

Mandatory Fixed Part

Mandatory Variable Part
Optional Part

Fig. 7.3 MSU containing an ISDN message.

22
An ISUP message contains the following information: For 2 Mbit/s systems, the circuit identification code is

• Routing label. coded as follows:

• Message type. The five least significant bits are a binary

• Mandatory fixed part. representation of the actual number of the time slot

• Mandatory variable part. which is assigned to the speech circuit. The remaining

• Optional part. bits are used where necessary to identify one among

several systems interconnecting an originating point

The service information octet indicates that the and a destination point.

message belongs to an ISDN user part with the bit The label is followed by an octet indicating the

pattern 0101 (5 Hex) in the service indicator. message type. The message-type code gives a unique

The label contains destination point code, definition of the function and format of each ISUP

originating point code and circuit identification code. message.

Abbr. Message Code

ACM Address complete 06

ANM Answer 09

BLA Blocking acknowledgement 15

BLO Blocking 13

CCR Continuity check request 11

CFN Confusion 2F

CGB Circuit group blocking 18

CGBA Circuit group blocking acknowledgement 1A

CGU Circuit group unblocking 19

CGUA Circuit group unblocking acknowledgement 1B

CON Connect 07

COT Continuity 05

CPG Call progress 2C

CQM Circuit group query 2A

CQR Circuit group query response 2B

DRS Delayed release 27

FAA Facility accepted 20

FAC Facility 33

FAR Facility request 1F

FOT Forward transfer 08

FRJ Facility rejected 21

GRA Circuit group reset acknowledgement 29

GRS Circuit group reset 17

IAM Initial address 01

IDR Identification request 36

INF Information 04

INR Information request 03

IRS Identification response 37

LPA Loop-back acknowledgement 24

NRM Network resource management 32

OLM Overload 30

PAM Pass along 28

REL Release 0C

RES Resume 0E

RLC Release complete 10

RSC Reset circuit 12

SAM Subsequent address 02

SGM Segmentation 38

SUS Suspend 0D

UBA Unblocking acknowledgement 16

UBL Unblocking 14

UCIC Unequipped CIC 2E

UPA User part available 35

UPT User part test 34

USR User-to-user information 2D

23
Below are short descriptions of each message type: Charge Information Message (CIM). Sent for
accounting and/or charging purposes.

Address Complete Message (ACM). Sent in the

backward direction to indicate that all the required Confusion Message (CFN). Sent in response to any
address signals have been received. message the exchange does not recognise.

Answer Message (ANM). Sent in the backward Connect Message (CON). Sent in the backward
direction to indicate that the call has been answered direction to indicate that the required address signals

and that metering or measurement of call duration can have been received and the call has been answered.

start.

Continuity Message (COT). Sent to request

Blocking Message (BLO). Only for maintenance. Sent continuity checking equipment to be attached.

in order to cause an engaged condition of a circuit for

subsequent outgoing calls. Continuity Check Request Message (CCR). Sent in

the forward direction to indicate whether or not there

Blocking Acknowledgement Message (BLA). Sent is continuity on the preceding circuit(s).

in response to a blocking message to indicate that the

circuit has been blocked. Delayed Release Message (DRS). Sent to indicate
that the calling or called party has been disconnected.

Call Progress Message (CPG). Sent in either direction

during the setup or active phase of the call, indicating Facility Accepted Message (FAA). Sent in response
that an event has occurred which is of significance and to a facility request message to indicate that the

which should be relayed to the originating or requested facility has been invoked.

terminating access.

Facility Reject Message (FRJ). Sent in response to a

Circuit Group Blocking Message (CGB). Sent to facility request message to indicate that the request for

cause an engaged condition for a group of circuits for the facility has been rejected.

subsequent outgoing calls.

Facility Request Message (FAR). Sent to request

Circuit Group Blocking Acknowledgement activation of a facility.

Message (CGBA). Sent in response to a circuit group

blocking message to indicate that the requested group Forward Transfer Message (FOT). Sent in the
of circuits has been blocked. forward direction when the outgoing international

exchange operator requires help from an operator at

Circuit Group Query Message (CQM). Sent to the incoming international exchange.

request the far end to give information about the state

of all circuits in a particular range. Identification Request Message (IDR). Sent to

request an action regarding the malicious call

Circuit Group Query Response Message (CQR). identification supplementary service.

Sent in response to a circuit group query message to

indicate the state of the circuits. Information Message (INF). Sent to convey
information in association with the call.

Circuit Group Reset Message (GRS). Sent to release

an identified group of circuits. Information Request Message (INR). Sent to
request information in association with a call.

Circuit Group Reset Acknowledgement Message

(GRA). Sent is response to a circuit group reset Initial Address Message (IAM). Sent in the forward
message to indicate that the requested group of direction to initiate seizure of an outgoing circuit and

circuits has been reset. to transmit the number and other information related

to the routing and handling of the call.

Circuit Group Unblocking Message (CGU). Sent to

cancel the engaged condition for a group of circuits. Loop Back Acknowledgement Message (LPA).
Sent in the backward direction in response to a

Circuit Group Unblocking Acknowledgement continuity check request message to indicate that a

Message (CGUA). Sent in response to a circuit group loop has been connected.

unblocking message to indicate that the requested

group of circuits has been unblocked. Network Resource Management Message (NRM).
Sent in order to modify network resources associated

with a certain call. The message is sent along an

24
established path in any direction in any phase of the Subsequent Address Message (SAM). Sent in the
call. forward direction to convey additional called-party

number information.

Overload Message (OLM). Sent in the backward

direction in response to an initial address message on Suspend Message (SUS). Sent to indicate that the
non-priority calls to invoke a temporary trunk blocking. called or calling party has been temporarily

disconnected.

Pass Along Message (PAM). Sent to transfer

information between two signalling points. Unblocking Message (UBL). Sent to indicate that the
engaged condition of a circuit is to be released.

Release Message (REL). Sent to indicate that the

circuit is being released. Unblocking Acknowledgement Message (UBA).
Sent in response to an unblocking message to indicate

Release Complete Message (RLC). Sent in response that the circuit has been unblocked.

to a release message to indicate that the circuit has

been released and brought into the idle condition. Unequipped CIC Message (UCIC). Sent when an
unequipped circuit identification code is received.

Reset Circuit Message (RSC). Sent to release a

circuit. User Part Available Message (UPA). Sent in either
direction as a response to a user part test message, to

Resume Message (RES). Sent to indicate that the indicate that the user part is available.

called or calling party, having been suspended, is

reconnected. User Part Test Message (UPT). Sent in either

direction to test the status of a user part marked as

Segmentation Message (SGM). Sent in either unavailable for a signalling point.

direction to convey an additional segment of an

overlength message. User to User Information Message (USR). A

message used to transfer user to user signalling

independently of call control messages.

Calling Party SP SP Called Party

Setup (Initial Address)

IAM
Setup
(Address Complete)

ACM
Alerting
CPG
Alerting (Call Progress) Connect
ANM
Connect (Answer)

Conversation

Fig. 7.4 Example of an ISUP call from an ISDN subscriber.

25
Each message contains one or several parameter fields. The names and codes of the parameters are given in the

following table.

Abbr. Parameter Name Hex Code

ACCDELINF Access delivery information 2E
ACCTR Access transport 03
ACL_ Circuit state indicator 26
BCLIN_ Backward call indicators 11
CALNO Called party number 04
CAUSE Cause indicators 12
CDIVINF Call diversion information 36
CGSM_ Circuit group supervision message indicators 15
CHISINF Call history information 2D
CLGNO Calling party number 0A
CLGPC_ Calling party category 09
CNTIN_ Continuity indicators 10
COMPINF Message compatibility information 38
CONNO Connected number 21
CR Connection request 0D
CREF Call reference 01
CSI_ Circuit state indicator 26
CUGIC Closed user group interlock code 1A
ECHO_INF Echo control information 37
EOP End of optional parameters 00
FACIN_ Facility indicators 18
FOCIN_ Forward call indicators 07
GE Generic notification 2C
GENDI Generic digit C1
GENNO Generic number C0
HLC High layer compatibility 34
INFIN_ Information indicators 0F
IRQIN_ Information request indicators 0E
LOCNUM Location number 3F
MCIDREQ MCID request indicators 3B
MCIDRES MCID response indicators 3C
MLPPPRE MLPP precedence 3A
NATCI_ Nature of connection indicators 06
NSFAC Network specific facilities 2F
OBCIN_ Optional backward call indicators 29
OFCIN_ Optional forward call indicators 08
ORC Original called number 28
PC_ Signalling point code 1E
PCOMINF Parameter compatibility information 39
PDELCOUN Propagation delay counter 31
RDGNO Redirecting number 0B
REDIN_ Redirection information 13
REDNO Redirection number 0C
Remoteop Remote operations 40
RG&ST Range & status 16
RNUMRP Redirection number restriction 40
SERVACT Service activation 33
SIGNPC Signalling point code 1F
SIGNPC Signalling point code 2B
SUBNO Subsequent number 05
TNS Transit network selection 23
TRMRQ_ Transmission medium requirement 02
TRMRQP Transmission medium requirement prime 3E
TRMUSED Transmission medium used 35
USRIN User-to-user information 20
USRSI User service information 1D
USRSIP User service information prime 30
UUIN_ User-to-user indicators 2A

26
 7.3 Signalling Connection Control Part (SCCP)
SCCP supplements the message transfer part by signalling data across the network, with or without use

providing both connectionless and connection-oriented of logical connections.

network services for the transfer of circuit-related and The combination of MTP and SCCP is called

non-circuit-related information. SCCP can control Network Service Part (NSP). NSP meets the

logical signalling connections. It can also transfer requirements for layer 3 services as defined in the OSI

reference model.

Network service Part (NSP)

SCCP SCCP
User Parts User Parts

Type A Type A

Common Common
Type B Signalling Link Type B
Transfer Transfer

Message transfer Part (MTP)

Type C Type C

Other Other

Fig. 7.5 Functional diagram for SCCP.

SCCP services are divided into two groups: Class 1: Sequenced Connectionless Class.
• Connection-oriented services. In protocol class 1 the features of class 0 are

• Connectionless services. complemented by a sequence control. By use of the

signalling link selection field, the same link is selected

For connection-oriented services, two types of for all messages in one call. This secures sequence

connections can be used: control and is identical to the standard service provided

1. Temporary signalling connections, with the by the MTP to the user parts.

connection initiated and controlled by the service The connectionless protocol classes 0 and 1 provide

user. This can be compared with dialled telephone functions necessary to transfer one network service

calls. data unit (NSDU). The maximum length of an NSDU is

2. Permanent signalling connections, established and restricted to 32 octets in the international network and

controlled by the local operation and maintenance 256 octets in the national network.

centre. These connections can be compared with

leased lines. Class 2: Basic Connection-oriented Class.

In protocol class 2, bi-directional transfer of NSDUs is

For transferring the data, four different protocol classes done by setting up a temporary or permanent

are defined: Two for connectionless services and two signalling connection. This corresponds to a simple

for connection-oriented services. The four classes are connection-oriented network service.

as follows:

Class 3: Flow Control Connection-oriented Class.

Class 0: Basic Connectionless Class. In protocol class 3, the features of protocol class 2

Data are transported independently of each other and are complemented by the inclusion of flow control,

may therefore be delivered out of sequence. This with its associated capability of expedited data

corresponds to a pure connectionless network service. transfer. Moreover, an additional capability of

detecting message loss and mis-sequencing is

included. In such circumstances, the signalling

connection is reset and a corresponding notification

is given by the SCCP to the higher layers.

27
 7.3.1 Connection-oriented Data Transfer
Setup of logic connections is based on the exchange of
references between two ends of the connection. These
references are used in all later data transfers.
The calling SCCP (A) starts transmitting a
connection request (CR) message. This CR contains
data about protocol class, the called SCCP address (B)
and a reference chosen by A. The CR can also contain
A's address and user data.
B answers with a connection confirm (CC)
containing the reference number from A, a reference
SP STP
A C
CR
CC
Data transfer
RLSD
RLC
Reserve Resource
Fig. 7.6 Establishment and release of logical connection.
7.3.2 Connectionless Data Transfer
In this kind of data transfer, no reference numbers are
exchanged or stored. The SCCP message, unit data
(UDT), contains destination point code and originating
point code. The destination point code is used for
routing the message to the user, and the originating
point code is used to return a message to the
originating user. This returned message could either be
28
number chosen by B and the selected protocol class.
The CC can also contain user data. When exchange A
receives the CC the data connection is established. In
the following data-transfer period, SCCP A uses the
reference number chosen by B and SCCP B uses the
reference number chosen by A.
The disconnection of the logic connection is done
when A transmits a released (RLSD) message which is
answered with a release complete (RLC) message.
SP
B
CR
CC
Data transfer
RLSD
RLC
Release Resource
an answer to the received UDT or a message from an
SCCP in the selected route indicating that the message
cannot be transferred. UDT also contains an indication
as to whether the message has to be returned or not if
it proves impossible to transfer the message to its
destination point.
 SP STP SP
A C B

UDT
UDT
UDT
UDT

Fig. 7.7 Connectionless data transfer.

7.3.3 SCCP Format

An SCCP message contains the following information: • Mandatory variable part.
• Routing label. • Optional part which may contain fixed length and
• Message type. variable length fields.
• Mandatory fixed part.

Level 2 Level 4 Level 3 Level 2

F B
F CK SIF
Label SIO LI I FSN I BSN F
B B

Originating Destination Sub-service Service Indicator

ISDN User Data Message Type SLS
Point Code Point Code Field 0011
N x 8 bits 8 bits 4 bits 14 bits 14 bits

Mandatory Fixed Part

Mandatory Variable Part
Optional Part

Fig. 7.8 Format of SCCP message.

The routing label has been discussed in the section

"Routing Level".

29
Message Type. function and format of each SCCP message. Each

The type code consists of a one-octet field. The message type can be used in different protocol classes,

message-type code gives a unique definition of the as shown in the following table.

Protocol class
Message type Code
0 1 2 3
X X CR Connection request 01
X X CC Connection confirm 02
X X CREF Connection refused 03
X X RLSD Released 04
X X RLC Release complete 05
X DT1 Data form 1 06
X DT2 Data form 2 07
X AK Data acknowledgement 08
X X UDT Unitdata 09
X X UDTS Unitdata service 0A
X ED Expedited data 0B
X EA Expedited data acknowledgement 0C
X RSR Reset request 0D
X RSC Reset confirm 0E
X X ERR Protocol data unit error 0F
X X IT Inactivity test 10
X X XUDT Extended unitdata 11
X X XUDTS Extended unitdata service 12

Connection Confirm. Is sent by the called SCCP to Extended Unitdata Service. Is used to indicate to the

indicate that the setup of the signalling connection has origination SCCP that an XUDT with optional

been carried out. parameters cannot be delivered to its destination.

Connection Request. Is sent by the calling SCCP to Inactivity Test. May be sent periodically to check if

request the setup of a signalling connection. the signalling connection is active at both ends.

Connection Refused. Is sent by the called SCCP to Protocol Data Unit Error. Is sent on detection of any

indicate that the setup of a signalling connection has protocol error.

been refused.

Released. Is sent to indicate that the transmitting

Data Acknowledgement. Is used to acknowledge SCCP wants to release the signalling connection.

the receipt of data in protocol class 3 with flow

control. Release Complete. Is sent in response to the released

message to indicate that a released message has been

Data Form 1. Is used to pass SCCP user data between received and that the signalling connection has been

two SCCP nodes transparently. released.

Data Form 2. Is used to pass SCCP user data between Reset Confirm. Is sent to indicate that a release

two SCCP nodes transparently and to acknowledge request has been received and that the reset

received messages. procedure has been completed.

Expedited Data. Has the same function as data form Reset Request. Is sent to indicate that the

2 messages but can also bypass the flow-control transmitting SCCP wants to initiate a reset procedure.

mechanism that has been selected.

Unitdata. Is used by the SCCP to send data in

Expedited Data Acknowledgement. Is used to connectionless mode.

acknowledge an expedited data messa ge.

Unitdata Service. Is used to indicate to the originating

Extended Unitdata. Is used by the SCCP that wants SCCP that a UDT cannot be delivered to its destination.

to send data along with optional parameters in

connectionless mode.

30
Parameter Fields. parameters. Fig. 7.9 shows which parameters are

Each SCCP message type has its own set of contained in each message.

Destination local reference

End of optional parameter

Receive sequence number
Segmenting/reassembling

Sequencing/segmenting
Source local reference

Calling party address

Called party address
Parameter Field

Message type code

Segmentation
Release cause

Refusal cause
Protocol class

Return cause

Hop counter
Reset cause

Error cause
Message

Credit

Data
CR Connection request M M M O M O O O

CC Connection confirm M M O M O O O

CREF Connection Refused M M O M O O

RLSD Released M M M M O O

RLC Release Complete M M M

DT1 Data Form 1 M M M M

DT2 Data Form 2 M M M M

AK Data Acknowledgement M M M M

UDT Unitdata M M M M M

UDTS Unitdata Service M M M M M

ED Expedited Data M M M

EA Expedited Data Ack. M M

RSR Reset Request M M M M

RSC Reset Confirm M M M

ERR Protected Data Unit Error M M M

IT Inactivity Test M M M M M M

XUDT Extended Unitdata M M M M M O M O

XUDTS Extended Unitdata Service M M M M M O M O

M = Mandatory field O = Optional field

Fig. 7.9 SCCP message types and parameters.

A brief description of the parameter fields is given in Called Party Address. This parameter field contains

the following. one octet for indicating the address type and a variable

number of octets containing the actual address (see

End of Optional Parameters. A one-octet field fig. 7.10). The address type indicates the type of

containing only zeros. address information contained in the address field. The

actual address consists of any combination of the

Destination Local Reference. A three-octet field following elements:

containing a reference number used to identify the • Signalling point code, represented by two octets.

connection section for outgoing messages. • Subsystem number that identifies an SCCP user

function, for example OMAP or ISDN-UP.

Source Local Reference. A three-octet field • Global title, for example dialled digits.
containing a reference number used to identify

incoming messages.

31
 Sub-system Signalling Address
Global Title Number (SSN) Point Code Indication
87654321
Point-code indicator
SSN indicator
SSN not known/not used 00 Global title indicator
SSCP management 01 Routing indicator
ITU-T Reserved for ITU-T allocation 02 Reserved for national use
ISUP 03
OMAP 04
MAP (for future use) 05
HLR 06
VLR 07
ETSI GSM MSC 08
EIR 09
AUC (possible future use) 0A
BSSAP 0E
O&M (A interface) 0D

Fig. 7.10 Format of SCCP address field.

Calling Party Address. A variable length parameter Sequencing/Segmenting. The first octet contains the

with the same structure as the called party address. send-sequence number in bits 2-8. Bit 1 is spare. The

second octet contains the receive-sequence number in

Protocol Class. A one-octet field used to indicate the bits 2-8 and bit 1 indicates more data as follows:

selected protocol class. Bits 1-4 are coded as follows: • Bit 1 = 0 – No more data.

Bit 4-1 = 0000 – Class 0. • Bit 1 = 1 – More data.

Bit 4-1 = 0001 – Class 1.

Bit 4-1 = 0010 – Class 2. Credit. A one-octet field used in protocol classes that

Bit 4-1 = 0011 – Class 3. include flow-control functions (allowed window size).

When bits 1-4 indicate a connection-oriented protocol

class (classes 2 and 3), bits 5-8 are spare. Release Cause. The release cause field contains the

When bits 1-4 indicate a connectionless protocol class reason for the release of the connection.

(classes 0 and 1), bits 5-8 are used to specify message

handling as follows: Return Cause. For unit data service messages, the

Bits 8-5 = 0000 – No special options. return cause field is a one-octet field containing the

Bits 8-5 = 1000 – Return message on error. reason for the message return.

Segmenting/Reassembling. More data is indicated Reset Cause. A one-octet field containing the reason

by bit 1 as follows: for resetting the connection.

• Bit 1 = 0 – No more data.

• Bit 1 = 1 – More data. Error Cause. A one-octet field indicating the exact

Bit 1 is spare. protocol error.

Receive Sequence Number. The receive number of

the next expected message is contained in bits 2-8. Bits

2-8 are spare.

32
 Release cause Code
End-user originated 00
End-user congestion 01
End-user failure 02
SCCP-user originated 03
Remote procedure error 04
Inconsistent connection data 05
Access failure 06
Access congestion 07
Subsystem failure 08
Subsystem congestion 09
Network failure 0A
Network congestion 0B
Expiration of reset timer 0C
Expiration of receive inactivity timer 0D
Not obtainable 0E
Unqualified 0F
10
Spare to
FF

Refusal Cause. A one-octet field indicating the reason Hop Counter. Used in the XUDT and XUDTS
for the refusal on the connection. messages to detect loops in the SCCP layer.

Data. The data field is of variable length and contains Segmentation. Used in the XUDT and XUDTS
the SCCP user data. messages to indicate that an SCCP message has been

segmented.

7.3.4 SCCP Management

The SCCP provides functions for managing the status ordinated change of status of SCCP subsystems. A

of the SCCP subsystems. These functions are, for brief description of the SCCP management messages is

example, used to inform other subsystems of the given below:

status of an SCCP subsystem and to allow a co-

Message Code
SSA Subsystem allowed 01
SSP Subsystem prohibited 02
SST Subsystem status test 03
SOR Subsystem out-of-service request 04
SOG Subsystem out-of-service grant 05

Subsystem Allowed (SSA). Sent to involved Subsystem Out-of-service Request (SOR). Is used to
destinations to inform them that a subsystem which allow subsystems to go out of service without

was formerly prohibited is now allowed. degrading the performance of the network.

Subsystem Out-of-service Grant (SOG). Sent in Subsystem Prohibited (SSP). Is sent to involved
response to a subsystem out-of-service request destinations to inform SCCP management at these

message to give information that the request has been destinations of the failure of a subsystem.

accepted.

Subsystem Status Test (SST). Is sent to verify the

status of a subsystem that was marked prohibited.

33
 7.4 Transaction Capabilities Application Part (TCAP)
The overall objective of the ITU-T specified transaction while being independent of any of these. The currently

capabilities application part (TCAP) is to provide means specified applications using TCAP are OMAP, GSM

for the transfer of information between nodes MAP and INAP, which are described in more detail

(exchanges and/or service centres), and to provide later.

generic services to applications (distributed over the The relation between TCAP, applications (TC users)

exchanges and service centres), and the ISO OSI model is shown in fig. 7.11.

OMAP GSM MAP INAP

LAYER 7 Application
Component Sub-layer
TCAP
Transaction Sub-layer

LAYER 6 Presentation

LAYER 5 Session ISP = 0 Intermediate Service Part

LAYER 4 Transport

SCCP Only class 0 and 1

LAYER 3 Network

MTP
LAYER 2 Data Link

LAYER 1 Physical

Fig. 7.11 Relation between INAP, OMAP, GSM, MAP, TCAP and the ISO OSI model.

ITU-T has only specified the use of SCCP class 0 and 1 TCAP is divided into two sub-layers:

(connectionless transfer) for the TCAP. This means that

the Intermediate Service Part (ISP) is empty/not needed • Component sub-layer deals with components
because no layer 4-6 functions are required for control that are the application protocol data units (APDU)

of SCCP connections. which convey remote operations and their

responses.

• Transaction sub-layer deals with the exchange of

messages containing components and, optionally, a

dialogue portion between two TC users.

34
 Originating Trancaction Identifier
Destination Transaction Identifier
P-Abort Cause
Dialogue Portion
Message-type Tag Component Portion
Message Types:
Total Message Length

- Unidirectional
Transaction Portion-information Element Tag
- Begin
- End Length

- Continue Contents
- Abort
Component-portion Tag

Tag
Component-type Tag
Length
Component Types: Component Length
Contents

- Invoke Component-portion Information Element

- Return Result
(Last)
- Return Result Invoke ID

(Not Last) Linked ID

- Return Error Operation Code

- Reject Sequence/Set
Component Error Code
Problem Code

Fig. 7.12 TCAP message structure.

7.4.1 TCAP Transaction Sub-layer

Message-type tag Code

- Unidirectional (Used when there is no need to establish a transaction) 61

- Begin (Initiate transaction) 62

- End (Terminate transaction) 64

- Continue (Continue transaction) 65

- Abort (Terminate transaction in abnormal situation) 67

Transaction portion information-element tag Code

- Originating transaction ID (Transaction identity at originating end) 48

- Destination transaction ID (Transaction identity at destination end) 49

- P-Abort cause (Reason for abort by transaction sub-layer) 4A

- Dialogue portion (Application context and user information that are not components, e.g. application

protocol/subset/options to be used, passwords and identification of sub-processes) 6B

- Component portion (Contains component portion, see component sub-layer) 6C

35
 7.4.2 TCAP Component Sub-layer
Component-type tag Code

- Invoke (Request operation to be performed at remote end) A1

- Return result (last) (Successful completion of operation, contains last/only result) A2

- Return error (Reports unsuccessful completion of operation) A3

- Reject (Incorrect component received at remote end) A4

- Return result (not last) (Contains part of result of operation) A7

Component portion information-element tag Code

- Invoke ID (Operation-reference number) 02

- Linked ID (Reference number for an operation linked to another operation) 80

- Local operation (Indicates the local operation to be invoked) 02

- Global operation (Indicates the global operation to be invoked) 06

- Sequence (Sequence of parame ters accompanying a component) 30

- Set (Set of parameters accompanying a component) 31

- Local err code (Reason for unsuccessful completion of operation contained in the return 02

- Global err code error component) 06

- Problem code (Cause contained in the reject component) 80-83

The operation to be performed at the remote end depends on the TC user.

7.5 Operations, Maintenance and Administration

Part (OMAP)
OMAP specifies procedures and protocols related to Three groups of procedures are specified:

operations, maintenance and administration • Operations, maintenance and administration

information. These procedures and protocols are procedures for the signalling network.

associated with the application layer of the OSI • Operations, maintenance and administration

reference model (layer 7). procedures for exchanges.

• Operations, maintenance and administration

procedures that are associated with the signalling

network and exchanges.

7.6 GSM Mobile Application Part (MAP)

MAP (mobile application part) is specified by ETSI subscriber to be routed to the area in which the mobile

(European Telecommunications Standards Institute) for is presently located.

use in GSM networks (Global System for Mobile More details on GSM and MAP can be found in GN

Communication) for the transfer of location and Nettest Technical Note 6, GSM Global System for

service information of the mobile subscribers, for Mobile Communication.

example to allow an incoming call to a GSM mobile

7.7 Intelligent Network (INAP)

Intelligent network (IN) concentrates the intelligence to introduce new services faster and independently of

for controlling telecommunications services in a small the switch vendors. A typical example of an IN

number of IN switches instead of spreading it architecture is shown in fig. 7.13.

throughout the network (as today), making it possible

36
 SMP
SCEF SCP Signalling
SMF Physical
SDF
SMAF Management
SCF

Signalling System No. 7

IP IP

SRF
SRF
SSP SSP
CCF CCF

SSF SSF

Fig. 7.13 IN architecture.

The service switching point (SSP) allows the users The service management point (SMP) performs service
access to the IN capabilities. SSP contains a normal management control, service provision control and

switch call control function (CCF) and a service service deployment control via the service

switching function (SSF) that provides interaction to management function (SMF). Examples of functions
the SCP. are database administration, network surveillance and

The service control point (SCP) contains the service testing, network-traffic management and network-

logic programs via the service control function (SCF) data collection. The service creation environment

that handle the IN service processing and customer function (SCEF) is used to define, develop and test
concerned and/or network data via the service data new IN services. The service management access

function (SDF). function (SMAF) provides selected users – such as

The intelligent peripheral (IP) provides the special service managers or some customers – with access to

resources needed for supporting the IN services via the the SMP.

specialised resource function (SRF), for example voice ITU-T has standardised the first set of IN

announcements, DTMF digit collection, speech- capabilities: capability set 1 (CS-1). CS-1 makes
recognition devices, audio-conference bridge and possible the provision of the services listed in the

protocol converters. following table as well as other non-standardised

services using the same capabilities.

37
 ABD Abbreviated dialling

ACC Account card dialling

AAB Automatic alternative billing

CD Call distribution

CF Call forwarding

CRD Call rerouting distribution

CCBS Completion of call to busy subscriber

CON Conference calling

CCC Credit card calling

DCR Destination call routing

FMD Follow-me diversion

FPH Freephone

MCI Malicious call identification

MAS Mass calling

OCS Originating call screening

PRM Premium rate

SEC Security screening

SCF Selective call forward on busy / don't answer

SPL Split charging

VOT Televoting

TCS Terminating call screening

UAN Universal access number

UPT Universal personal telecommunication

UDR User-defined routing

VPN Virtual private network

IN will evolve in the future. The next capability set The intelligent network application protocol (INAP)
(CS-2) from ITU-T is, among others, expected to cover supports the communication between the functional

mobility services and broadband ISDN entities SCF, SSF, SRF and SDF (see fig. 7.13). INAP is a

(B-ISDN). user of TCAP.

Calling Party Called Party Protocol SCCP Unit Data

Data Pointers Type
Address Address Class (Connectionless)

Operation Operation Invoke Type + Component Transaction Type +

Parameters Code ID LI Portion Tag Identifiers LI

TCAP
INAP TCAP Transaction Sublayer
Component
Sublayer

Fig. 7.14 SCCP/TCAP message structure for INAP information.

38
INAP operations for ITU-T CS-1:

INAP operations
SCF - SSF operations:
- Activate service filtering - Activity test

- Activity test response - Analysed information

- Analyse information - Apply charging

- Apply charging report - Assist request instructions

- Call gap - Call information report

- Call information request - Cancel (call information request)

- Cancel status report request - Collected information

- Collect information - Connect

- Connect to resource - Continue

- Disconnect forward connection - Establish temporary connection

1)
- Event notification charging - Event report BCSM

- Furnish charging information - Hold call in network

2)
- Initial DP - Initial call attempt

- O_answer - O_called_party_busy

- O_disconnect - O_midcall

- O_no_answer - Origination attempt authorised

- Release call - Request notification charging event

- Request report BCSM event - Request status report (poll resource status, monitor for change

or continuous monitor)

- Reset timer

- Route select failure - Select facility

- Select route - Send charging information

- Service filtering response - Status report

- T_answer - T_called_party_busy

- T_disconnect - Term attempt authorised

- T_midcall - T_no_answer

SCF - SRF operations:

- Assist request instructions from srf - Cancel announcement

- Collected user information - Play announcement

- Prompt and collect user information - Specialised resource report

SCF - SDF operations:

- Query - Query result

- SDF response - Update confirmation

- Update data

1) BCSM = Basic call state model. 2) DP = Detection point (in SSP).

SSP (SSF) SCP (SCF)

TCAP begin (TCAP invoke

(INAP initial DP (freephone number)))

TCAP end (TCAP return result

(INAP apply charging (to B-party), connect (B-number)))

Fig. 7.15 Signalling example: Freephone.

39
 Combined
SSP (SSF)
and IP (SRF) SCP (SCF)

TCAP Begin (TCAP invoke

1.
(INAP initial DP ))

TCAP continue (TCAP return result (INAP connect to resource

2.
prompt and collect user information (disconnect from IP forbidden)))

TCAP continue (TCAP invoke (INAP specialized resource

3. report (credit card number, Pin code)))

TCAP continue (TCAP return result (INAP prompt and collect

4.
user information (disconnect from IP allowed)))

TCAP continue (TCAP invoke (INAP specialized resource

5. report (B number)))

6. TCAP end (TCAP return result (INAP connect (B number)))

Fig. 7.16 Signalling example: Credit-card calling.

1. SSP detects off-hook of a credit-card payphone. 4. SCP requests the IP to collect more information

2. SCP requests SSP to connect the payphone to a from the user after verification of credit-card

digit-collection device in IP and instructs the IP to number and pin code.

collect the information keyed in by the user. 5. IP returns the collected B number to SCP.

3. IP returns the collected credit-card number and pin 6. SCP instructs SSP to connect the call to the

code to SCP. collected B number.

7.8 MTP Tester

The MTP tester is connected to the MTP as a user part, criteria for that MTP. The MTP tester is controlled by

i.e. identified by a service indicator. It generates the OMAP.

message signal units (MSUs) containing a serial number The service indicator coding for the MTP tester is:

(and possible additional information) in the signalling 1000 (8 Hex).

information field (SIF). On receipt of these messages, a

check is performed to verify that the messages are The heading codes for the MTP tester messages are

delivered in accordance with the defined performance listed in the following table.

Message H1 H0

Test Control Messages 0

Test request message 0
Test acceptance message 1
Test refusal message 2
Test termination request message 3
Test termination acknowledge message 4

Test Traffic Messages 1

Test traffic message 0

40
The test-traffic message is formatted as indicated in fig. 7.17.

BA 0 1
Filler Serial
Spare GPC H1 H0 Label
Octets Number
m*8 32 2 14 4 4 32
0< m <262

GPC: The point code of the tester initiating the test and generating the traffic.
Serial number: The serial number assigned to the message.
Filler octets: Additional octets of information, i.e. a time stamp.

Fig. 7.17 Format of test-traffic message.

41
 8. Test and Maintenance
8.1 Multichannel Protocol Analyser MPA 7xxx
Fig. 8.1 GN Nettest Multichannel Protocol Analyser MPA 7100/7200/7300.
The MPA is designed for the installation testing, per-
formance analysis, maintenance and troubleshooting
of today's large, complex SS7 networks, with special
focus on advanced services/protocols such as IN and
GSM.
Typical applications:
Acceptance testing, detailed troubleshooting, daily
maintenance, performance analysis.
• Up to 24 full duplex links in one instrument.
• User interface based on MS Windows® 95.
• Large (and expandable) processing capacity.
• Predefined "click-and-go" triggers and filters in-
cluding complete call trace.
• Focus on GSM and IN protocols.
• Automatic recognition of signalling errors.
• User-defined result displays.
• Statistical counters.
• ODBC (Open Data Base Connectivity).
General description:
The Multichannel Protocol Analyser (MPA) is an easy-
to-use multi-link test instrument for the detailed analy-
42
sis of telecom digital signalling protocols, i.e. Signalling
System No. 7 (SS7), particularly complex protocols such
as IN (Intelligent Network) and GSM (Global System for
Mobile Communications). The MPA is available as
three different instrument types:
MPA 7100
Slimline portable unit able to handle four full duplex
signalling links and using an external PC for data pre-
sentation.
MPA 7200
19" subrack able to handle up to 24 full duplex signal-
ling links, also using an external PC for data present a-
tion.
MPA 7300
Portable stand-alone instrument able to handle up to
16 full duplex signalling links and with built-in PC for
data presentation. The instrument contains a 10.4"
colour LCD display, a 3.5" floppy-disk drive, a key-
board (PC notebook type) and a trackball. The ke y-
board can be flipped up during transportation, cover-
ing the display. Socket for external mouse.
The user interface is based on MS Windows® 95. Up
to 1 Gbyte of data can be stored. Five different line
interfaces are available:
• 2 Mbit/s Unbalanced Quad Link Unit (BNC or
1.6/5.6).
• 2 Mbit/s Balanced Quad Link Unit.
• DS1 Quad Link Unit.
• DS0(A) Triple Link Unit.
• V.35 Quad Link Unit.
The MPA provides three main measurement functions:
transmission alarm monitoring, protocol analysis, and
statistics. The instrument can be controlled from a
remote PC using standard communication interfaces
and PC remote control programs, for example
ReachOut.
Transmission alarm monitoring:
Transmission-link alarms are monitored on every line
input on the MPA:
• 2 Mbit/s: No Signal, AIS (Alarm Indication Signal),
No Frame, Distant Alarm.
• DS1: No Signal, AIS, Out of Frame, Yellow Alarm,
CRC6 Error.
• V.35/DS0(A): No Data, No Octet, No Timing.
Alarms are sent immediately as they are recognised
(the delay in the MPA is shorter than one second). An
indication is also sent when an alarm ceases. Alarms
can be time-stamped and stored in the memory.
Protocol analysis:
The basic function of the MPA is to record and dis-
play in real time the decoded signalling messages on
one or more of its link interfaces. Decoding takes
place using the protocol assigned to the link. Up to
10 different protocols may be in use simultaneously.
The MPA works on full-rate as well as sub-rates and
supports both split-rate and link load-sharing.
The MPA has two different modes of operation:
Event mode and Sequence mode. Sequence mode is
a sorted version of Event mode, with messages
grouped according to call. The Sequence mode al-
lows capture MAP, INAP, BSSAP and A-bis sequences
as well as TUP and ISUP.
Graphical user interface (GUI):
Based on the MS Windows® 95/NT platform, the
MPA’s GUI is much like that for other Windows®
applications. Its prime elements are the protocol,
alarm and statistical windows, providing the user
with a good overview of measurement status and
results. Extensive use of schematic diagrams, flow
charts and combo-boxes facilitates operation.
Storage:
Instrument configurations, measurement conditions,
individual filters and measured data can all be stored
for later use. The user’s own favourite filters can be
stored, for example. The Replay function permits a
virtual repetition of the measurement back home in
the office − even allowing decoding protocols and
filters to be changed and conversion of the recorded
measurement from simple Events into Sequences.
Filters:
The MPA contains several independent filters for
reducing the amount of data stored and/or displayed.
All filters are logically represented by hierarchical
layers, for example MTP, SNT, SNM, ISUP, SCCP etc.
to allow filter criteria to be specified at individual
layers. A special sequence filter allows the capture of
whole sequences, simply by specifying for example
Calling or Called, or IMSI number.
Remote operation:
The MPA can be controlled from a remote site using
the PC software package “Reach Out”. This can be
used to achieve remote control via RS 232, a sta n-
dard modem, LAN networks or the Internet.
For more advanced applications, the MPA also serves
as the measuring probe in a TMN-based QUEST7
surveillance system.
Statistics:
The MPA offers statistical counting in three different
areas: link activity, message types and alarms. The
statistical function allows real-time monitoring of
statistics and more advanced post-processing for the
preparation of pre-defined graphs and reports. Time
resolution can be set to any value between 1 minute
and 2 hours.
Application software:
Optional software packages are available for various
applications, for example the Call Data Recorder
package. This generates a record containing relevant
information for every call and stores it in an ODBC
database. Such records include a time stamp, call
duration, the called/calling numbers and other rele-
vant parameters.
43
 VLR
Visitor
MSC Location

BTS BSC MAP Register

Base A-bis A-Interface

Base Mobile
Transceiver Station Switching
Home
HLR
System Controller Centre
Location
Register

ISUP/TUP
SS7 Network SSP
SCP
INAP
Service Service
Digital
Switching Control
Exchange
Point Point
(ISDN)

Primary Rate
Access

PABX
(ISDN)

Multichannel Protocol Analyser MPA 7300

Fig. 8.2 Typical applications for the MPA 7100/7200/7300.

Acceptance testing: Daily maintenance:

Detailed comparison of the signalling protocol with the
specification (message formats, message contents,
signalling sequences), performed during the initial
installation of the protocol and/or exchange type and
when there is a major software update/release.
Detailed troubleshooting:
Detailed signalling analysis during fault-finding in the
operation phase – for example tracing of specific calls,
looking for specific cause values, analysis of data just
before and after the occurrence of an error.
Checking of link loads (number/ratio of MSUs and
LSSUs) and quality (number/ratio of errored and re-
transmitted MSUs).
Performance analysis:
Counting of message types per link/direction, for ex-
ample number of error and blocking messages, or
number of call attempts (IAM/IAIs), number of success-
ful calls (ACMs) and number of unsuccessful call at-
tempts (unsuccessful backward setup messages).

44
 8.2 LITE 3000
The LITE 3000 is a multi-purpose, battery-powered problems. The addition of optional software modules

instrument for field technicians. The instrument is a expands the LITE 3000 from a full-featured

powerful tool for a wide range of applications, from transmission-line quality tester into an advanced

fast first-aid troubleshooting to comprehensive, in- signalling analyser.

depth analysis of transmission and signalling

8.2.1 Main Features of the LITE 3000:

• Fast troubleshooting. − CAS and MF signalling.

• Simultaneous monitoring of both sides of a 2 − Powerful signalling statistics.

Mbit/s PCM line. − MEASUREMENT_RESULT filter (A-bis).

• Powerful testing of framed Nx64 kbit/s and • Propagation-time measurements.

unframed 2 Mbit/s PCM systems. • Drop-and-insert testing.

• G.821, G.826 or M.2100 error-performance pa- • Immediate LED indications.

rameters. • Large colour display.

• Test of GSM A-bis interface (option). • Fast and easy access to results.

• Advanced all-layer signalling analysis options: • Easy intuitive operation.

− SS7 protocols incl. GSM A interface and MAP • Automatic configuration to monitored line.
protocols. • Cost-effective.
− GSM A-bis interface protocols. • More than 10 hours of battery operation.
− ISDN protocols.

Fig. 8.3 GN Nettest LITE 3000.

45
 8.2.2 General Description
The basic LITE 3000, with its two independent and statistics make signalling analysis and acquisition

receivers and one transmitter, supports framed and of information on the current state of the network

unframed testing and monitoring. This makes it ideal very straightforward tasks.

for both in-service and out-of-service transmission- Results are easy to read and interpret on the large

quality measurements. For fast troubleshooting, the LCD display, with its colour coding and graphical

LITE 3000 displays alarms and transmission-link status symbols. Data can be printed direct to an external

on LED indicators, as well as other relevant printer or exported to a PC via the remote interface.

information, such as the level of the 2 Mbit/s signal Presentation of transmission-error results as

and the frequency difference between the inputs. histograms facilitates error-tracing. The LITE 3000

The instrument’s two inputs permit immediate may be operated remotely through an optional MS

monitoring of the two sides of a PCM line and allow Windows® program.

comparison of simultaneously recorded results. With its auto-configuration feature, stored setups

With the SS7 signalling option added, the LITE and intuitive man-machine interface, the LITE 3000 is

3000 becomes a powerful signalling analyser for SS7. quick to set up and very user-friendly in operation.

An A-bis option tailors the LITE 3000 to test the A-bis The instrument’s portability and robust design allow

interface of GSM networks. Equipped with GSM- measurements to be taken at any suitable measuring

specific SS7 protocols (A-interface and MAP point. It is powered by rechargeable and replaceable

protocols), it is converted into a comprehensive intelligent high-capacity NiMH batteries. These

transmission tester and signalling analyser for GSM provide more than 10 hours of operation with

networks. With other options, it becomes a powerful PowerSave. T he LITE 3000 can also be powered via an

signalling analyser ISDN protocols and for CAS and external mains adapter in long-term measurement

MF signalling. Easy-to-interpret signalling decodes operations.

8.2.3 Testing Transmission Quality

The basic LITE 3000 includes a wide range of 2 Mbit/s • Framed 2 Mbit/s testing for stress testing a

network transmission-quality applications. For network element through variation of the test

example: signal.

• First-aid troubleshooting and in-service • In-service and out-of-service error-performance

monitoring, using the status monitoring facilities. measurements (G.821/G.826/M.2100).

• Identification of synchronisation problems through • Nx64 kbit/s drop-and-insert measurements for in-

slip measurements and input frequency deviation service measurements of transmission quality.

indication. • Propagation-time measurement for examination

• Traffic-channel monitoring and usage analysis. of delays in the network.

• Installation and conformance testing via • Advanced in-service troubleshooting, examining

comprehensive out-of-service BERT tests. errors and alarms with the event log.

• Audio Performance Test through generation of

analogue traffic-channel contents.

8.2.4 SS7 Signalling Analysis in the LITE 3000

With the SS7 signalling option added, the LITE 3000 All layers of the protocol are decoded completely into

facilitates analysis of the ITU-T defined Signalling mnemonics. The mnemonics can be translated to

System No. 7 (SS7) between public exchanges, plain language and the use and possible values of the

including high level TCAP-based protocols such as field are explained.

GSM. During installation or troubleshooting, the LITE The LITE 3000 can present the recorded

3000’s event log provides valuable, detailed information in different ways:

information on the signalling by collecting signalling The Overview presentation gives a one-line

messages from the connected SS7 signalling links. indication of each message. It is easy to see on which

46
of the two inputs the message was detected. Intuitive may be changed to contain a couple of lines per

colour indications highlight messages that could not message, stating the most important information in

be correctly decoded. A search facility makes it easy the message.

to find such messages. The overview presentation

Fig. 8.4 The overview presentation of signalling.

The High level presentation displays most parts of The Detailed presentation shows all parts of the

the message, making it easy to identify the message and its hexadecimal contents for detailed

information carried in each message. inspection and analysis.

8.5 The detailed presentation.

The SS7 messages are stored in the LITE 3000’s protocols the user can for example set a filter to see

memory and can be examined during or after the IAM messages only, giving a quick overview of calls

measurement. More than 20,000 messages can be on the line. Easy import of the OPC, DPC and CIC

stored. The instrument’s filter facilities permit parameter value to display filters makes it straight-

limitation of the information to be stored, minimising forward to extract messages that belong to the same

both the storage requirement and the time needed call. And a general 4 digit search facility allows

to retrieve data. extract of messages with containing the 4 digits. This

Filters can be applied to select the most essential may be used to identify messages with a particular

information for storage and display. For ISUP type called party or calling party number.

47
 Fig. 8.6 Extract of messages for a call.

8.2.5 Signalling Statistics

The LITE 3000’s signalling statistics provide data on possibilities for the user. Call completion in TUP

total traffic load and the quality of the signalling link. protocols can be examined by comparing count of

The instrument can inform the user on the IAMs or IAIs on one side of the line with answer

occurrence of and load from the different SS7 User messages (ANC/ANN/ANU) on the other side of the

Parts divided by the SIO value. line. Furthermore release cause statistics are available

For network optimisation the SS7 ISUP and TUP for ISUP type protocols.

message type statistics opens a vast range of

Fig. 8.7 Signalling link and message type statistics.

8.2.6 Other Signalling Options

Other signalling options available for the LITE 3000:

• ISDN signalling analysis.

• GSM A-bis interface protocol signalling analysis.

• Detailed CAS and MF signalling analysis.

48
 9. References
This Technical Note is based on the following ITU-T recommendations (dated Helsinki Q3/93):

Q.700 Introduction to ITU-T Signalling System No. 7.

Q.701-709 Message Transfer Part (MTP tester).

Q.710 Simplified message transfer p art

Q.711-716 Signalling Connection Control Part (SCCP).

Q.721-725 Telephone User Part (TUP).

Q.730 ISDN supplementary services

Q.741 Data user part DUP

Q.750-754 Operations, Maintenance and Administration Part (OMAP).

Q.755 Signalling System No. 7 Protocol Tests (MTP tester).

Q.761-767 Integrated Services Digital Network User Part (ISUP).

Q.771-775 Transaction Capabilities Application Part (TCAP).

Q.780-783 Test specification.

Q.791 Monitoring and measurements.

Q.795 Operation, Maintenance and Administrati on part (OMAP).

Q.12xx Intelligent Network Application Protocol (INAP).

In addition, the following ETSI specifications have been used:

GSM 09.02 Mobile Application Part (MAP).

49