You are on page 1of 64

2.

Call Set-up

2.1 Introduction
This module describes the software processes, blocks and signals involved
in the set-up of a typical outgoing PSTN call, using CCITT Signalling
System No7 (SS7) on the outgoing trunk. It is designed to give an
appreciation of the different functions involved and the place of software
signals in block interwork.

Module Objectives
After completing this module the student will be able to:
describe the traffic handling process in AXE 10 software
name the main blocks involved in traffic handling and briefly
describe their functions

Figure 2.1
Module Objectives.

2.2 General
When a function is designed in the AXE 10 system it is either assigned to
one function block, or distributed over a number of blocks, each of which
has a specific task. Very many functions are required to handle all the
different aspects of work that the AXE 10 switch is able to handle. This
work includes the operating system tasks, software handling and recovery,
traffic handling, operation and maintenance, automatic supervision and
maintenance. Thus a great number of function blocks are required: in the
dump presently used for an ISDN local exchange the APT and APZ
systems together contain about eight hundred function blocks.
During the operation of the exchange the individual blocks are called into
operation one by one - either by the operating system, or by another block
that passes on the next piece of work to be done. The blocks must
therefore be able communicate with each other. They do this by using
software signals. The signals are built into the programs - both central and
regional - by the block designers, using standard signals from a library
data base containing tens of thousands of signals.
Each separate piece of work that is done in a block is called a job. A job is
started by the reception of a signal into the program and ends at the
sending of a signal or the block exiting to the operating system, which will
send the next signal to continue the work.

038 02-EN/LZM 111 012 R1B 19


As the blocks cooperate using signals, these must contain information that
the executing block needs from the previous block, and even from blocks
that have been executing earlier and are still linked into the ongoing work.
This information - sent as data words in the signal - often includes linking
data such as the individual in the sending block or the addressed individual
in the receiving block.
As will be seen later, neither a signal or its data actually moves from one
block to another. Explained simply, a signal sent from block A to block
B simply causes the program to start at a certain address in block B. The
signal data words - having been prepared by block A in the Register
Memory of the CPU - remain in the RM, but can now only be manipulated
by block B, e.g. can be read from the RM into the data belonging to block
B in the Data Store.

2.3 Overview of CCITT Signalling System No7

2.3.1 Introduction
This section gives a brief outline of the main features of CCITT Signalling
System No7 (SS7). It is not intended to be a comprehensive description
and contains simplifications, but will cover the principles, terms and
signalling sequences encountered during a typical outgoing telephony call.
It is assumed that the reader is familiar with the general principles of
signalling systems.

2.3.2 Basic Principles and Structure


Exchanges in a telecommunications network are interconnected by many
traffic circuits used for telephony or other services like ISDN, Data calls
etc. When a call is to be set up, signalling information is sent from one
exchange to the other using a signalling system. This signalling
information (Seizing signal, B digits, Subscriber Category, Clearing
signals etc.) is traditionally sent as tones or electrical conditions directly
on the traffic circuit selected for the call. These methods are slow,
relatively unreliable and have limited capability to support the wide range
of functions required in a modern network.
CCITT Signalling System Number 7 (SS7) was designed to give high
speed, reliable digital signalling with the capability to be used for a wide
range of applications and services. It is also designed with the capacity to
be adapted to serve new applications in the future.
The exchanges in a network which have SS7 signalling implemented are
known as Signalling Points (SPs) and are interconnected by data links
called Signalling Links (SL), typically one or two between Signalling
Points. Signalling Links are typically 64kbit/s data links and are dedicated
to transmitting SS7 signalling data only. All signalling information is
sent on these Signalling Links in data packets, each packet containing
signalling information for a specific connection and circuit.
Figure 2.2 shows a simple SS7 network.

20 038 02-EN/LZM 111 012 R1B


Call Set-up

Signalling Link Signalling Link


SP
10 M
SU 10 0 SU
10 11
01
M 10 110 10 01
00
01
01
00 10
0 10 10
01 10
11 01
10 0

Traffic Circuits

SP SP
MSU
Signalling Link 10110101000101101010010

Figure 2.2
SS7 Signalling Network

There are two main parts to SS7 -


User Parts e.g Telephony User Part (TUP) and ISDN User Part (ISUP)
which are responsible for call set-up and supervision. It is the User Part
which selects a traffic circuit, sends seizure & clearing signals, digits,
subscriber categories, call set-up information etc.
The Message Transfer Part (MTP) which is responsible for ensuring
that the User Part signalling information is transferred accurately and
without loss to the correct receiving Signalling Point.

It does this by packaging the signalling data from the User Part,
together with its own control and addressing data, into a data packet,
known as a Message Signalling Unit (MSU) and sending it on the
appropriate Signalling Link to the receiving Signalling Point.

The receiving MTP checks the MSU control data to ensure the User
data has not been corrupted, checks the addressing data to see who the
message is for and delivers it.

If the address is for another Signalling Point, the MTP sends the MSU
out on an appropriate Signalling Link. If it is for its own Signalling
Point it delivers it to the correct User Part.

Signalling Point Codes


In order to uniquely identify a signalling point, each Signalling Point in a
national network has a unique number, called the Signalling Point Code
(SPC). International SPs will also have a second SPC for the International
network. The SPC consists of two numbers, the first is called the Network
Indicator (NI) and identifies to which network the SPC belongs (0 -

038 02-EN/LZM 111 012 R1B 21


International, 2- National) and the second number is the SP number. For
example 2-10 & 2-12345 are national SPCs, 0-99 is an international SPC.
NI can have values 0 to 3.
SPC can have values 0 to 16,383.
Figure 2.3 shows a simple network with SPCs.

SPC = 2-20
Signalling Link Signalling Link
SP
10 M
SU 1 00 SU
10 11
01
01
M 10 110 10 00
01
01
0 10
00 10
01 10
01 01
11 0
10

Traffic Circuits

SP SP
A Subscriber SPC = 2-10 SPC = 2-30 B Subscriber
123456 CIC = 42 456789
Area Code 01

Figure 2.3
SS7 network showing SPCs

Addressing and Routing of MSUs


MSUs for telephony and ISDN calls are sent from the originating SP to the
SP at the other end of the selected speech circuit. The MSU may be sent
via several intermediate SPs on the way. It must therefore contain the SPC
of the destination as an address. This is known as the Destination Point
Code (DPC). It also contains the Originating Point Code (OPC) to tell
where the message originated.
For example, in Figure 2.3, if subscriber A dials 01 45 67 89, they wish
to be connected to subscriber B. The dialled digits are analysed in SP 2-10
and a speech circuit to SP 2-30 is selected (Circuit Identification Code,
CIC = 42 above).
SP 2-10 must send an MSU to SP 2-30 to tell it of the call. There is no
direct SL between 2-10 and 2-30, so SP 2-10 sends the MSU to SP 2-20,
with the address of the final SP. This is the DPC, value 2-30 in the
example.
SP 2-20 receives the MSU and checks the DPC it contains and compares
this DPC with its own SPC (known as OWNSP*). Since this DPC is not
its OWNSP, it checks its routing tables and sends the unaltered MSU out
towards SP 2-30.

22 038 02-EN/LZM 111 012 R1B


Call Set-up

At 2-30, since the DPC in the MSU equals its OWNSP, it knows the
message is for itself. The MTP then sends the message to the correct User
Part (TUP, ISUP...) and the call progresses.

2.3.3 User Part


The User Parts are the traffic handling functions within SS7. They are
specific to the type of service, for example TUP for telephony, ISUP for
ISDN, DUP for data, MTUP for mobile. See Figure 2.4

User
Parts TUP TUP

User Signalling Data User Signalling Data


XXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXX

Message Signalling Link


Transfer MTP MTP
Part
1011101010 XXXXXXXXXXXXXXXX 0111010101

MSU
Signalling Point 1 Signalling Point 2

Figure 2.4
Basic Structure of SS7

The Telephony User Part (TUP) and ISDN User Part (ISUP) are part of the
Trunk and Signalling Sub-System, TSS. They perform the same functions
as other signalling system TSS blocks, such as circuit selection and
control, circuit blocking, call set-up signalling, digit sending & reception
and others. The main difference from other signalling systems is that when
the User Part has gathered all the signalling data, instead of sending it to
line itself, or via a code sending block, it sends the signalling data to the
MTP function to send as a data packet or MSU on a Signalling Link.
The User Signalling Data sent from User Part to MTP (and from MTP to
User Part at the receiving Signalling Point) contains a message asking the
User Part in the receiving Signalling Point to do something, or passing
information to this User Part. So this signalling data contains several
different pieces of information. For example -

038 02-EN/LZM 111 012 R1B 23


User Part Identity
Tells the receiving MTP which User Part the MSU message is to be
delivered to.

Signal Type
This tells the receiving User Part what to do with the data. In telephony
terms, this could be a seizing signal, a clear forward, a clear back, release
guard, circuit blocking signal etc.

Circuit Number
To tell the receiving Signalling Point which circuit this particular message
refers to. One Signalling Link can handle up to 4096 traffic circuits so it is
important to identify the circuit. This is known as the Circuit Identification
Code or CIC.

Destination Signalling Point Code (DPC)


The sending User Part must tell the MTP where to send the message i.e.
which destination Signalling Point the message is for.

Originating Signalling Point Code


Which SP the message is from.

Signal Data, if any.


In addition to the above, there may be other data which must be sent for a
particular signal name.
For example, in SS7 the first signal sent during call set-up is known as an
Initial Address Message (IAM) or an Initial Address message with
additional Information (IAI), the equivalent of a seizing signal.
The data which must be sent with the IAI includes -
B-Subscriber Number
A-Subscriber Number
A-Subscriber Category
Message Indicators telling -
Nature of address indicator (type of B-number)
Satellite circuit included in the connection
Continuity check required
Echo-suppressor included
Incoming international call
All digital path required (ISDN)
All SS7 signalling path required
Redirected Call
Other Miscellaneous Data
A simplified picture of the structure of the IAI is shown in Figure 2.5.

24 038 02-EN/LZM 111 012 R1B


Call Set-up

Calling Signal
Number Number Message
A-digits B-digits Party Type Label
of A-digits of B-digits Indicators
Category (IAI)

Circuit Originating Destination


(CIC) SP SP

Figure 2.5
Structure of the TUP Initial Address Message with Additional Information (Simplified)

The data for this message is gathered by TUP and the message is built up
and is sent to the MTP as data in a software signal, for the MTP to send to
the destination TUP.

2.3.4 Message Transfer Part MTP


The MTP takes the data from the TUP, selects the correct Signalling Link
to send the adds control data to the beginning and end to create a complete
MSU and transmits it. The control data is used by the MTP to ensure there
in no loss or corruption of data, it is removed by the receiving MTP which
then sends the User Signalling Data to the addressed TUP.

2.3.5 TUP Signalling


The IAI signal has been described above. There are many TUP signals for
call set-up, circuit control and handling abnormal situations in call set-up
for example.
In this overview we will only look at the signals used to set up a typical
outgoing call. Figure 2.6 shows the TUP signalling sequence for such a
call.

038 02-EN/LZM 111 012 R1B 25


SP SP
A B
TUP TUP
Request to seize
circuit & send IAI
digits
Check all digits
and information
received. Ringing
ACM tone sent.
Release register,
through connect
ANC B answers

Start charging
Conversation
CBK (B clears first)

CLF
A clears
Call cleared down
RLG
Call cleared down,
circuit released.

Figure 2.6
Signalling Sequence for a TUP Call

The Register function in TCS will analyse received digits as they are
keyed by A-subscriber. When a Routing Case is found, it is analysed and
the outgoing route and Sending Program determined. At a point defined by
the Sending Program, the Register asks the route-owning block (TUP in
this example) to select an outgoing circuit for the call and to send the B-
Number and other data to the distant exchange.
TUP selects a free circuit, builds up the data for an IAI and when told by
the Register, sends this to the MTP to transmit.
The receiving TUP analyses the signal, determines that it is an IAI and
then interworks with the Register to route the call. If the B-number
received is a subscriber in the B-exchange, the call is set up and ringing
tone and ringing current sent. The TUP is told by Register that all
necessary digits have been received, TUP puts together a backward signal,

26 038 02-EN/LZM 111 012 R1B


Call Set-up

Address Complete Message (ACM) and sends it to MTP to transmit to the


A-exchange. TUP in the A-exchange tells the Register which through
connects the call and releases.
When the B-subscriber answers the speech path is through connected,
TUP builds up an ANswer Charge (ANC) signal and sends it to MTP to
transmit to the A-exchange to commence charging.
The A and B subscribers can then talk.
If the A-subscriber clears first, the TUP in the A-exchange builds up a
CLear Forward message (CLF) which MTP transmits as another MSU.
The B-exchange clears the connection and TUP builds a ReLease Guard
(RLG) message for MTP to transmit. When the A-exchange TUP receives
this message it can then mark the traffic circuit idle.
If the B-subscriber clears first a CLear Back (CBK) message will be sent
before the CLF signal.
So for a typical call, 5 or 6 MSUs are sent or received, each containing a
TUP message with signal name and data.

2.3.6 Implementation

Message Transfer Part


The MTP consists of about 20 function blocks all implemented in Central
Software and one (C7ST2) with Regional Software and hardware. These
all have block names beginning with C7... and belong to the Common
Channel Signalling Subsystem, CCS-7. Most blocks are responsible for
signalling network supervision, test and maintenance and are not used
during traffic handling. The MTP blocks involved in normal traffic
handling are -

C7ST2 - Signalling Terminal


At each end of a Signalling Link there is a hardware Signalling Terminal,
ST, which controls the Signalling Link and transmits and receives the
MSUs. Each ST is an Extension Module connected to an RP and
controlled by Regional and Central Software. This is the only SS7
hardware and forms a function block known as C7ST2.
See Figure 2.7
C7ST2 sends incoming MSUs to block C7DR2 after checking the
messages have been received correctly and C7DR2 sends C7ST2 the
MSUs to transmit.
Since one Signalling Terminal is connected to one Signalling Link, they
can be considered to be the same function.

038 02-EN/LZM 111 012 R1B 27


SP 1 SP 2

Signalling Link
Hardware ST ST

Regional
RP RP
Software

Central
Software CP CP

Figure 2.7
Signalling Link showing Signalling Terminal

C7DR2 - Discrimination & Routing


This block receives the MSU from C7ST2, checks if it is for its own
Signalling Point and if so, sends it to the receiving block in the correct
User Part. If the MSU is for another Signalling Point it sends it back to
C7ST2 with a new destination to transmit it to.
C7DR2 also receives message data from User Parts, which it analyses to
see which Signalling Point to send it to and on which Signalling Link. It
then sends it to C7ST2 to package and transmit as an MSU.

Telephony User Part


TUP consists of 6 blocks in subsystem TSS. All have names beginning
C7... The blocks used during normal traffic handling are -

C7BTI
Controls the SS7 traffic routes and circuits, performing functions such as
circuit selection and blocking. It coordinates traffic handling and
interworks with C7OTH and C7ITH blocks.

C7OTH/C7ITH
Outgoing & Incoming Trunk Handling. These blocks perform circuit
related functions during call set-up, in cooperation with C7BTI.

C7LABT
This block receives the TUP messages from C7DR2 and uses the
Signalling Point and circuit number (CIC) to determine which C7BT block
to send the message to, this is known as Label Translation. There can be

28 038 02-EN/LZM 111 012 R1B


several different versions of TUP in one Signalling Point, hence the need
for C7LABT.

2.3.7 ISDN User Part - ISUP


The descriptions above describe a typical TUP call. ISUP call set-up and
release is performed in a very similar way, except that instead of TUP
blocks dealing with traffic handling, ISUP blocks are involved. ISUP uses
the MTP to transmit messages, it packages the signalling data and sends it
to C7DR2 and receives messages from C7DR2 in the same way as
described for TUP.
The main difference in ISUP signalling is that once a call is set up,
subscribers can perform additional signalling. These functions are
implemented using ISUP SS7 messages in addition to the ones described.
ISUP blocks are part of TSS in Central Software and have names
beginning with UP...
This has given a brief summary of the main points of SS7 only. SS7 is a
complex and very powerful signalling system with many other features
which have not been described.

038 02-EN/LZM 111 012 R1B 29


30 038 02-EN/LZM 111 012 R1B
Call Set-up - Outgoing SS7

3. Call Set-up - Outgoing SS7

In this chapter the traffic handling sequence for an outgoing PSTN call
will be described.
The traffic handling will contain a description of the blocks and software
signals used. The C7 signals between exchanges are also shown.
The calls shown are normal calls with no services or other functions
included. The idea behind this is to show the reader how a standard call is
handled.
It should be pointed out that only the main signals used in the traffic
handling process are shown here. Signals and function blocks dealing with
supervision, statistics, and so on have been omitted for the sake of clarity.

038 02-EN/LZM 111 012 R1B 31


A-Sub
Off Hook

LI3R LI3
CCALLT1 LOAS
SEIZECAPS1

CAPSEIZED
CJ
SEIZECJ

CJSEIZED

CALLCJ SC
RCAT1

RCAT1R
KR2
SEIZEDR TS
TSCSEIZE

TSCSEIZED
DRSEIZED

CLCOF
SEIZERE RE
SEIZETCNEW REIBA
SEIZEIBA

IBASEIZED
RESEIZED

REQUESTACAT SC
SENDACAT

SENDACATACK
REQUESTACATACK

SUSCS
CALLSUSCS
RCAT1

RCAT1R
CALLSUSCSR

SSSINFO2

SSSINFOACK

ENDSEIZEINFO
KR2
LI3R STARTDR
KR2R
REGSTS STARTS
CDIAL1

Dial Tone
sent

Figure 3.1
A-Subscriber Off-Hook

32 038 02-EN/LZM 111 012 R1B


Call Set-up - Outgoing SS7

3.1 A-subscriber off hook


CCALLT1 (LI3)
The signal is from the regional software to the central software of LI3
block and is sent by the EMRP in the LSM containing the calling LIC. The
device processor controlling the LICs on the line interface boards scans
the LICs every 5ms. After the device processor has informed LI3R that a
call attempt has been detected LI3R sends this signal to LI3U to inform it
of the new call. One data word only is carried: the LI pointer (LIP).

SEIZECAPS1 (LOAS)
This signal is sent to LOAS from LI3 to initiate the seizure of processor
capacity for the new call. LOAS (Load Supervision) is an APZ block that
protects the system from temporary and permanent overload. Each new
call attempt must be first accepted by LOAS before the call can continue.
The signal data concerns the sending block reference and sending
individual, LIP. LI3 and LOAS are thus linked by this signal.

CAPSEIZED (LI3)
This signal is sent back by LOAS when capacity exists in the APZ for the
new call. If the call is rejected, the signal REJCALL is sent back instead.

SEIZECJ (CJ)
CJ (Combined Junctor) is the block that coordinates the different blocks in
SSS and interfaces to the blocks in TCS during call setup and release. The
signal SEIZECJ is sent to seize a CJ individual to handle the call. CJ is a
software only block, thus the CJ individual is a software record in Data
Store. It stores the data sent in the signal, such as LI3 pointer and type of
call. The signal is a combined forward signal, meaning that a combined
backward signal will be sent back to LI3 so that the program execution can
continue in that block.

CJSEIZED (LI3)
The combined backward signal that informs LI3 that a CJ individual has
been seized for the call. The data contains only the calling LI individual
and the selected CJ individual. after this signal the blocks LI3 and CJ and
their respective individuals are linked together. If the call had been
rejected (no CJ individual available) a congestion signal would have been
returned instead to LI3 and no linking would take place.

CALLCJ (CJ)
LI3 uses this signal to continue the call setup. All data about the call
available to LI3 is transferred to CJ by this signal. The data includes
information about whether or not the call is from a PABX, or if special
equipment such as a coin box or private meter is used by the subscriber.
The signal only transfers data to the linked CJ individual and requires no
answer signal. Block LI3 plays very little part in the remainder of the call
setup.

038 02-EN/LZM 111 012 R1B 33


A-Sub
Off Hook

LI3R LI3
CCALLT1 LOAS
SEIZECAPS1

CAPSEIZED
CJ
SEIZECJ

CJSEIZED

CALLCJ SC
RCAT1

RCAT1R
KR2
SEIZEDR TS
TSCSEIZE

TSCSEIZED
DRSEIZED

CLCOF
SEIZERE RE
SEIZETCNEW REIBA
SEIZEIBA

IBASEIZED
RESEIZED

REQUESTACAT SC
SENDACAT

SENDAg34
REQUESTACATACK CK
SUSCS
CALLSUSCS
RCAT1

RCAT1R
CALLSUSCSR

SSSINFO2

SSSINFOACK

ENDSEIZEINFO
KR2
LI3R STARTDR
KR2R
REGSTS STARTS
CDIAL1

Dial Tone
sent

Figure 3.1
A-Subscriber Off-Hook

34 038 02-EN/LZM 111 012 R1B


Call Set-up - Outgoing SS7

RCAT1 (SC)
CJ sends this signal to SC block (Subscriber Categories) to fetch
information concerning the categories of the subscriber and services that
the subscriber has activated. Almost all subscriber-related information is
stored in the block SC. This includes all subscriber categories, e.g. if the
subscriber has call-barring facilities or has a private meter, and the type of
subscriber: POTS, ISDN, Business Group etc.

RCAT1R (CJ)
All the data for the subscriber that is required at this stage is handed over
to CJ with this signal.

SEIZEDR (KR2)
If a subscriber category has indicated that a key-set telephone exists then
CJ requests block KR2 (Keyset Code Receiver) to provide a KR2 device
for the call. The signal will cause KR2 to search for an idle device, starting
in the same EM where the LIC is situated and then in the remaining EMs if
no idle device was found in the LICs EM.
CJ starts a time supervision immediately prior to this signal being sent and
stops the supervision when the first digit arrives at CJ from KR2.

TSCSEIZE (TS)
Having found an idle KR2 device KR2 orders the block TS (Time Switch)
to select a path through the time switch hardware, connecting the LIC
hardware to the chosen KR2 device. The signal contains the positions of
both the LI3 and KR2 devices in the Time Switch.

TSCSEIZED (KR2)
KR2 is informed that the path in the Time Switch is selected and operated.

DRSEIZED (CJ)
KR2 informs CJ that a KR2 device has been selected and reserved for the
call. The signal data contains the CJ individual handling call setup and the
chosen KR2 individual. These individuals in CJ and KR2 are thus now
linked for the call.

SEIZERE (CLCOF)
CJ sends this signal to seize an RE individual. The signal is sent via block
CLCOF (Call supervision and co-ordination of functions) so that a TC
(traffic control) individual can be chosen for the call.

SEIZETCNEW (RE)
The TC individual and the data that came to CLCOF in the previous signal
are sent on to RE block. The RE individual selected has the same number
as the TC individual in CLCOF. For this individual certain initial data
values are set, such as origin zero for routing, charging and B-number
analysis.

038 02-EN/LZM 111 012 R1B 35


A-Sub
Off Hook

LI3R LI3
CCALLT1 LOAS
SEIZECAPS1

CAPSEIZED
CJ
SEIZECJ

CJSEIZED

CALLCJ SC
RCAT1

RCAT1R
KR2
SEIZEDR TS
TSCSEIZE

TSCSEIZED
DRSEIZED

CLCOF
SEIZERE RE
SEIZETCNEW REIBA
SEIZEIBA

IBASEIZED
RESEIZED

REQUESTACAT SC
SENDACAT

SENDACATACK
REQUESTACATACK

SUSCS
CALLSUSCS
RCAT1

RCAT1R
CALLSUSCSR

SSSINFO2

SSSINFOACK

ENDSEIZEINFO
KR2
LI3R STARTDR
KR2R
REGSTS STARTS
CDIAL1

Dial Tone
sent

Figure 3.1
A-Subscriber Off-Hook

36 038 02-EN/LZM 111 012 R1B


Call Set-up - Outgoing SS7

SEIZEIBA (REIBA)
Block REIBA cooperates with block RE and is used in connection with the
B-number analysis. This combined forward signal is used to seize an
individual in REIBA and set some initial data for the individual. (The data
sent with the signal is the same data as was sent to RE in signal
SEIZETCNEW. The individual chosen in REIBA has the same number as
that chosen in RE and CLCOF, see above). The initial data set for the
individual includes the permitted length of the B-number, the length of the
country code and information about the sending program.

IBASEIZED (RE)
The combined backward signal from REIBA after an individual has been
selected and marked as seized. The RE individual is now marked as
reseized.

RESEIZED (CJ)
RE informs CJ that a register individual has been seized for reception of
digits. CJ, RE and REIBA are now linked together after this signal has
been received in CJ.

REQUESTACAT (RE)
The block CJ sends the SCP of the calling line to RE to initiate a sequence
in which subscriber categories are obtained. The signal is a combined
forward signal.

SENDACAT (SC)
Another combined forward signal is used to send on the request to SC
(Subscriber Categories) block.

SENDACATACK (RE)
A set of data concerning the subscribers categories is sent back to RE in
this signal. The categories sent here are those of interest to the register, for
instance origins for B-number analysis and charging analysis, and
categories for charging services, for instance charging check and
immediate service.

REQUESTACATACK (CJ)
An acknowledgement that A-subscribers categories have been received
by RE is made in this combined backward signal.

CALLSUSCS (SUSCS)
CJ links itself to SUSCS block with this signal. Data concerning the type
of call, together with the SCP of the subscriber is sent with the signal.
Block SUSCS looks after such subscriber functions as hot-line (FDC), last
number repetition and flash services such as call completion at busy
subscriber and call completion at no reply.

038 02-EN/LZM 111 012 R1B 37


A-Sub
Off Hook

LI3R LI3
CCALLT1 LOAS
SEIZECAPS1

CAPSEIZED
CJ
SEIZECJ

CJSEIZED

CALLCJ SC
RCAT1

RCAT1R
KR2
SEIZEDR TS
TSCSEIZE

TSCSEIZED
DRSEIZED

CLCOF
SEIZERE RE
SEIZETCNEW REIBA
SEIZEIBA

IBASEIZED
RESEIZED

REQUESTACAT SC
SENDACAT

SENDACATACK
REQUESTACATACK

SUSCS
CALLSUSCS
RCAT1

RCAT1R
CALLSUSCSR

SSSINFO2

SSSINFOACK

ENDSEIZEINFO
KR2
LI3R STARTDR
KR2R
REGSTS STARTS
CDIAL1

Dial Tone
sent

Figure 3.1
A-Subscriber Off-Hook

38 038 02-EN/LZM 111 012 R1B


Call Set-up - Outgoing SS7

RCAT1 (SC), RCAT1R (SUSCS)


RCAT1 is sent to SC to get information about certain categories and
activated services that the subscriber has. The required data is sent back to
SUSCS in the signal RCAT1R. These categories and services differ to a
large extent from those sent to RE in the signal SENDACATACK, above.
They include such categories/services as call barring, A-number
presentation barring, last number repetition, and class of service (POTS,
ISDN, Business Group, etc.).

CALLSUSCSR (CJ)
This signal indicates that an individual in block SUSCS has been seized
for the call.

SSSINFO2 (RE), SSSINFOACK (CJ)


CJ sends a large amount of data from SSS concerning the subscriber to RE
with this combined forward signal. The data includes such things as A-
subscriber special equipment/meter pulse information, connection type (to
SSD, GSS, etc.), incoming side signalling system, type of seizure, charge
advice information (group or individual charging if PABX, etc.). The
signal is acknowledged with the backward signal SSSINFOACK.

ENDSEIZEINFO (RE)
CJ informs RE that all call information from SSS has been sent.

STARTDR (KR2), STARTS (KR2R)


STARTDR orders KR2 to send dial tone to the subscribers LIC and to
start scanning for digits sent by the subscriber. The signal STARTS is sent
to the regional software, KR2R. This software actually orders TSR to send
the dial tone as this is stored digitally in the Time Switch. Immediately
before sending STARTDR, CJ starts a time supervision on the time to wait
for the first digit.

REGSTS (LI3), CDIAL1 (LI3R)


Block LI3 is also told to start scanning for digits (pulses) from the
subscriber. Although the subscribers category indicated a key-set
telephone, he/she may have a dial telephone or, in some cases, both types
connected to the same line. If the digits are sent from a dial telephone then
the KR2 will be disconnected.
The software has now created a linked chain of records between certain
blocks by means of transferred pointers and block references, as described
in the module Software Interwork. These are stored in the records in Data
Store and used by the blocks when they interact again during call setup.
The primary linked chain here contains the blocks LI3-CJ-RE-REIBA.
CLCOF is not linked between CJ and RE. It selects the common traffic
control individual (TCP) in CLCOF / RE / REIBA. As CLCOF sends the
TCP and CJ pointer to RE, RE is then directly linked to the CJ individual.
Side linked chains exist between CJ - KR2 - TS and CJ - SUSCS.
Block SC, for instance, is not linked. A sending blocks pointer is sent to it
each time, to be used in the return signal. The pointer is not stored in SC.

038 02-EN/LZM 111 012 R1B 39


RE
ENDSEIZEINFO (From previous figure)
REIBA
STARTIBA SUPIA
FETCHANUM
CHCOOR IBASTARTED
TCCALLEVENT

TCCALLEVENTACK
CJ
SC IGRA
SCPTONUM

SCPTONUMACK
IANRANDINFO
OANRANDINFO

ANUMFETCHED

ANUMFETCHED

Figure 3.2
A-Number Analysis, preparation for B-Number Analysis

40 038 02-EN/LZM 111 012 R1B


Call Set-up - Outgoing SS7

3.2 A-number analysis, preparation for B-number


analysis
STARTIBA (REIBA)
This combined forward signal is used to transfer information required for
B-number analysis from RE to REIBA. (REIBA is the block that handles
the B-no analysis and reception and sending of B-number digits). The data
was earlier sent to RE from SC and CJ.

FETCHANUM (SUPIA)
REIBA asks block SUPIA for the A-number and the results obtained from
the A-number analysis. SUPIA is the block that handles interwork
between the incoming and outgoing sides. It consists of two modules:
SUPIA (which handles supplementary subscriber services) and REIAA
(which handles the A-number analysis).
It should be noted that the three traffic control (TC) blocks RE, REIBA
and SUPIA always use the same individual number in each block for a
given call.

IBASTARTED (RE)
REIBA informs RE that the block is ready to receive the B-number digits.

TCCALLEVENT (CHCOOR)
CHCOOR is the main block that coordinates the call charging. Several
blocks, including CHCOOR, subscribe to RE to be informed about call
events that take place when a call is in register position. (Register position
implies that RE is involved in the call setup).
In this signal RE informs CHCOOR of the call event RE seized. The signal
contains the call event, linking data and other data about the call, such as
the originating code. This will be used for charging any active subscriber
services that are used. (Each originating code has a parameter that must be
active if subscriber services are to be charged.) The originating code was
originally sent to RE from CJ in signal SEIZERE.
Examples of other call events are: RE Release of Incoming Side, B-digit
Received, RE Handover to CLCOF.

TCSETKIDPTR (RE), TCSETKIDPTRACK (CHCOOR)


RE is informed that a CHS kernel individual has been selected for the
charging and sends an acknowledgement. This individual will be the one
used in all the charging blocks coordinated by CHCOOR.

PREPCREVENT1 (CHEDR), PREPCREVENT1ACK (CHCOOR)


The call individual in CHEDR is reset. CHEDR collects and records data
relating to the charging of events (both call-related and non call-related).
The combined backward signal acknowledges the resetting.

038 02-EN/LZM 111 012 R1B 41


RE
ENDSEIZEINFO (From previous figure)
REIBA
STARTIBA SUPIA
FETCHANUM
CHCOOR IBASTARTED
TCCALLEVENT

TCCALLEVENTACK
CJ
SC IGRA
SCPTONUM

SCPTONUMACK
IANRANDINFO
OANRANDINFO

ANUMFETCHED

ANUMFETCHED

Figure 3.2
A-Number Analysis, preparation for B-Number Analysis

42 038 02-EN/LZM 111 012 R1B


Call Set-up - Outgoing SS7

TCCALLEVENTACK (RE)
The acknowledgement to the above combined forward signal. The data
contains the RE individual, the CHCOOR kernel individual and whether
or not CHCOOR is to continue subscribing to RE for call event
information at call setup. It will not continue to subscribe if the originating
codes parameter controlling registration of subscriber services is not set
to active.

IGRA (CJ)
This signal is sent by SUPIA after it receives the signal FETCHANUM
from REIBA, above. It is used to fetch the A-subscriber number or type of
subscriber from CJ. Here the A-number is requested.

SCPTONUM (SC), SCPTONUMACK (CJ)


This signal is sent to SC carrying the SCP of the subscriber. SC converts
the SCP into the A-number and sends this back to CJ with the backward
signal SCPTONUMACK.

IANRANDINFO (RE)
This signal transfers the A-number on to RE. Information concerning
validity of the number and screening (A-number Presentation/Presentation
Barring, etc.) is also included.

OANRANDINFO (SUPIA)
This signal simply passes on the incoming data about the A-number to
block SUPIA.

ANUMFETCHED (RE, REIBA)


In SUPIA the A-number is analysed. At the end of a successful analysis
the signal ANUMFETCHED is sent first to RE and then REIBA. This
signal contains data about the different origins for routing and charging
analysis, etc., obtained from the A-number analysis. REIBA now has the
A-number and A-number analysis results asked for above in signal
FETCHANUM.

038 02-EN/LZM 111 012 R1B 43


KR2R KR2
KSCODE2 CJ
Digit 1 DRCODE
LI3
ENDSELED RE
IGR1 REIBA
IGR1 PREA
BPREANA

BPREANRESOBAACK

DA
ANORIGB

DALINK

ANBDIG1

ANRES6A

ANBDIG1

ANRES32

ANBDIG1

ANRES7
INEXTBD

KR2R KR2
KSCODE2 RE
Digit 2 DRCODE
IGR1
IGR1
ANBDIG1

ANRES15
BANARESDATA

BANARESDATACK
ANBDIG1

ANRES32

ANBDIG1

ANRES11
INEXTBD

Figure 3.3
Reception & Analysis of Digits 1 &2

44 038 02-EN/LZM 111 012 R1B


Call Set-up - Outgoing SS7

3.3 Reception and analysis of digits


The reception and analysis of digits sent by the A-subscriber is handled in
this section. The text and figures describe a standard sequence without any
errors made by the subscriber (e.g. dialling non-existing numbers).

3.3.1 Reception and analysis of digits 1 & 2

KSCODE2 (KR2)
The first digit dialled by the subscriber is detected by the KR2 circuit to
which the subscriber is connected. The regional software of KR2 in the
EMRP sends the digit on to the central software.

DRCODE (CJ)
KR2 transfers the digit to CJ.

ENDSELED (LI3)
On reception of DRCODE, CJ sends the signal ENDSELED to LI3 to
inform this block if the subscriber can perform hook flash (category FLA)
and to change the state of the LI3 device to busy. CJ also starts a time
supervision on time between incoming B digits.

IGR1 (RE)
This signal is sent next by CJ to transfer the first digit to RE.

IGR1 (REIBA)
RE transfers the digit to REIBA.

BPREANA (PREA)
This combined forward signal is used to start the B-number pre-analysis.
Among the data sent in the signal is the origin for B-number analysis and
numbering plan information.

BPREANRESOBAACK (REIBA)
The combined backward signal after the pre-analysis has been started. In a
successful case, the reply contains the actual origin for B-number analysis
that will be used in DA (Digit Analysis) block. This value is extracted
from the value sent in signal BPREANA.

ANORIGB (DA)
This signal sends the actual origin for B-number analysis to DA

DALINK (REIBA)
The combined backward signal contains the DA-link, the pointer to the
origin (analysis tree) in the B-number analysis table used when analysing
the digits.

038 02-EN/LZM 111 012 R1B 45


KR2R KR2
KSCODE2 CJ
Digit 1 DRCODE
LI3
ENDSELED RE
IGR1 REIBA
IGR1 PREA
BPREANA

BPREANRESOBAACK

DA
ANORIGB

DALINK

ANBDIG1

ANRES6A

ANBDIG1

ANRES32

ANBDIG1

ANRES7
INEXTBD

KR2R KR2
KSCODE2 RE
Digit 2 DRCODE
IGR1
IGR1
ANBDIG1

ANRES15
BANARESDATA

BANARESDATACK
ANBDIG1

ANRES32

ANBDIG1

ANRES11
INEXTBD

Figure 3.3
Reception & Analysis of Digits 1&2

46 038 02-EN/LZM 111 012 R1B


Call Set-up - Outgoing SS7

ANBDIG1 (DA)
This combined forward signal sends the first B-digit and DA-link to DA.

ANRES6A
The first result of the analysis is a modification of the B-number. (In this
case the first digit will be removed after all analysis results have been
obtained from it, creating a new B-number).

ANBDIG1 (DA)
REIBA re-sends the first B-digit to DA, not yet modified, to obtain any
further data for the digit from the B-number analysis table.

ANRES32
This time the result contains Numbering Plan information.

ANBDIG1 (DA)
Re-sending the first B-digit to DA for any further analysis result.

ANRES7
This result says send the new first digit in the B-number now modified
according to the modification data received above in ANRES6A. It also
contains the new value of DA-link, i.e. the new origin or tree where the
digit will be analysed.

INEXTBD (CJ)
The register tells CJ to send the next digit.

ANBDIG1 (DA)
The second digit is sent by REIBA to RE.

ANRES15 (REIBA)
The Traffic Destination Code is sent back.

BANARESDATA (RE), BANARESDATACK (REIBA)


This signal contains data about Country Code Length, Traffic Destination
Code and type of charging, e.g. if Call Specification or Immediate Service.

ANBDIG1 (DA)

ANRES32 (REIBA)
The Numbering Plan is returned. (Also given after the first digit here.)
ANBDIG1 (DA)

ANRES11 (REIBA)
Send next digit in B-number.

INEXTBD (CJ)

038 02-EN/LZM 111 012 R1B 47


KR2R KR2
KSCODE2 CJ
Digit 3 DRCODE

RE
IGR1 REIBA
IGR1 DA
ANBDIG1

ANRES3
CHCOOR BDIGANARESCC
PRIMCHARGANA

PRIMCHARGANAR
CONTBANA
ANBDIG1

ANRES6A

ANBDIG1

ANRES2

ANBDIG1

CHMON ANRES11
INEXTBD
INEXTBD

KR2R KR2
Digit 4
KSCODE2
DRCODE
CHMON RE
IGR1
IGR1
ANBDIG1

ANRESCAC
BANARESDATA

BANARESDATAACK
ANBDIG1

CHMON ANRES11
INEXTBD

Figure 3.4
Reception & Analysis of Digits 3 & 4

48 038 02-EN/LZM 111 012 R1B


Call Set-up - Outgoing SS7

3.3.2 Reception and analysis of digits 3 & 4

ANRES3 (REIBA)
The first result from the third digit contains the Charging Case (CC).

BDIGANARESCC (RE)
REIBA sends the Charging Case (CC) obtained with ANRE3 on to RE.
The charging analysis is quite complex and only a small part is shown
here. Several charging blocks and many signals are involved. All charging
blocks are coordinated by CHCOOR and are described in the general
section in the software document for this block (PLEX/E-module).
Two of the main signals between RE and CHCOOR are shown below.

PRIMCHARGANA (CHCOOR)
The CC is sent to CHCOOR for primary charging analysis. The signal
contains all the data about the A-subscriber and other call parameters
required by CHCOOR.

PRIMCHARGANAR (RE)
Eventually, after involvement of further blocks to obtain Tariff Class and
Tariff data, CHCOOR sends the result of the primary charging analysis to
RE. As well as including the analysis result (charging/no charging) the
data can also include a tariff message (to be sent on to another exchange)
or if charging information is to be expected back from a superior exchange
on the outgoing trunk.
Finally CHCOOR also orders the block CHMON to link into the traffic
chain between CJ and RE/CLCOF. These signals are not shown here.
CHMON will later initiate the charging on reception of the Answer
Charge MSU at B-answer. CHMON also directs CHCOOR to initiate an
output of charging information to he subscribers call meter at call
disconnection.

CONTBANA (REIBA)
RE orders REIBA to continue the B-number analysis

ANRES6A (REIBA)
Modification of the B-number (in our case the first two digits of the new
B-number - the remaining area code - will be removed after all analysis
results have been obtained from them).

ANRES2 (REIBA)
The Routing Case is returned.

ANRES11 (REIBA)
Send next digit. In this case the analysis has specified that the fourth and
subsequent digits shall be analysed in a new origin (tree). The signal also
contains the DA-link for this new origin.

038 02-EN/LZM 111 012 R1B 49


KR2R KR2
KSCODE2 CJ
Digit 3 DRCODE

RE
IGR1 REIBA
IGR1 DA
ANBDIG1

ANRES3
CHCOOR BDIGANARESCC
PRIMCHARGANA

PRIMCHARGANAR
CONTBANA
ANBDIG1

ANRES6A

ANBDIG1

ANRES2

ANBDIG1

CHMON ANRES11
INEXTBD
INEXTBD

KR2R KR2
Digit 4
KSCODE2
DRCODE
CHMON RE
IGR1
IGR1
ANBDIG1

ANRESCAC
BANARESDATA

BANARESDATAACK
ANBDIG1

CHMON ANRES11
INEXTBD

Figure 3.4
Reception & Analysis of Digits 3 & 4

50 038 02-EN/LZM 111 012 R1B


Call Set-up - Outgoing SS7

INEXTBD (CHMON), INEXTBD (CJ)


REIBA now asks for the next digit from CJ. CHMON was linked into the
call between CJ and RE. This signal also passes via CHMON.
The fourth digit is sent to DA

ANRESCAC
The Carrier Access Code is returned.

BANARESDATA (RE), BANARESDATACK (REIBA)


Further call data from REIBA is sent to RE.
ANBDIG1 (DA)

ANRES11 (REIBA)
No further data so send next digit.
INEXTBD (CHMON), INEXTBD (CJ)
CJ is asked for the next digit.

038 02-EN/LZM 111 012 R1B 51


KR2R KR2
KSCODE2 CJ
Digit 5 DRCODE

RE
IGR1 REIBA
IGR1 DA
ANBDIG1

ANRES4

ANBDIG1

ANRES13
RA BDIGANARESRC

SELROUTE4

OROUTE4
OSENDINGINFO

INEXTBD

KR2R KR2
Digit 6
KSCODE2
DRCODE
RE
IGR1
IGR1

INEXTBD

KSCODE2
Digit 7 DRCODE RE
IGR1
IGR1

INEXTBD

KSCODE2
Digit 8 etc.

Figure 3.5
Reception & Analysis of Remaining Digits

52 038 02-EN/LZM 111 012 R1B


Call Set-up - Outgoing SS7

3.3.3 Reception and analysis of remaining digits

The fifth digit is sent to DA.

ANRES4 (REIBA)
The first result of the fifth digit gives the Number Length.

ANRES13 (REIBA)
This result says that no further information is available in this analysis tree
and that the analysis is ended. Further digits will not be sent to DA.

BDIGANARESRC (RE)
After the completion of the analysis in DA, the Routing Case (RC) can be
sent by REIBA to RE.

SELROUTE4 (RA)
The RC is sent from RE to RA block for analysis in this combined forward
signal.

OROUTE4 (RE)
The results of the route analysis, including sending program, block, global
route number, etc., are returned to RE in the combined backward signal.

OSENDINGINFO (REIBA)
Using the data obtained from the route analysis as well as data obtained
earlier, RE now sends information to REIBA to be used in connection with
seizure of outgoing side and digit sending, such as the sending program.

INEXTBD (CHMON), INEXTBD (CJ)


The next digit is asked for.
After the fifth digit, in this case, no more digits are sent on to DA with
signal ANBDIG1. REIBA merely asks CJ for the next digit until all the
digits have been sent, see Figure 3.5

038 02-EN/LZM 111 012 R1B 53


KR2R KR2
KSCODE2 CJ
Last Digit DRCODE

CHMON RE
IGR1 REIBA
IGR1

OSEIZEPOINT C7BTI3 C7OTHI3


SEIZEOLINK
OUTSEIZED

OSEIZED3

OSIDESEIZED
SUPIA
OSIDESEIZED

OSIDESEIZEDR
CHMON
ISELPA
JT2
ETCSEIZE

ETCSEIZED

TS
SELPAT1

SELPATR CHMON
ISELPAR

TSM GS
BSELOPA
TCT

TCTR
OPED
OREADYFORCALL

CHMON
IGRA

CALLPOINT

CALL

STARTDIGSEND

SUPIA
STARTDIGSEND

DISCDR
TSCRLSE
Continued in
next figure

TSCRLSED
DRCLEAR

Figure 3.6
Reception & Analysis of Last Digit, Setting up the Speech Path

54 038 02-EN/LZM 111 012 R1B


Call Set-up - Outgoing SS7

3.4 Setting up the Speech Path


Note: signals between CJ and RE pass through CHMON, although this
charging block is omitted below and in the diagrams.

OSEIZEPOINT (RE)
After the last digit has been received in REIBA this signal is used to
inform RE that the seizure point for the outgoing side has been reached.

SEIZEOLINK (C7BTI3)
This signal is used to select an outgoing device in the block containing the
route obtained from the route analysis. The device used for the speech is
thus a C7BTI3 device.

OUTSEIZED (C7OTHI3)
By this direct signal, C7OTHI3 is told to start the outgoing traffic
handling, i.e. activate the call for the selected outgoing C7BT device. (The
device individual in C7OTHI3 is automatically the same as the selected
device pointer in C7BTI3). Certain data values are set and the state of the
device in the block is marked as seized.

OSEIZED3 (RE)
C7OTHI3 now informs RE that an outgoing device has been selected.
Among the data sent in the signal is the outgoing device pointer, outgoing
block reference (C7OTHI3), the global route number, the inlet in the GSD
of the device, and signalling system capabilities information.

OSIDESEIZED (REIBA)
RE informs REIBA that an outgoing device has been selected, sending the
outgoing device pointer and the outgoing block reference (C7OTHI3). The
remaining data contains signalling system information received from
C7OTHI3 in the previous signal.
(RE actually sends the signal back to itself first, as a a direct signal. After
making some changes to the value of some states, the signal is sent to
REIBA).

OSIDESEIZED (SUPIA)
After storing the outgoing device pointer and block reference, REIBA
sends the same direct signal - with unchanged data - on to SUPIA.

OSIDESEIZEDR (RE)
After storing the incoming data this return signal is sent to inform RE that
SUPIA has received the message that an outgoing device is selected and
that SUPIA is now interworking with RE for the call.
The next part of the call is to prepare for the call setup through the
subscriber switch of the A-subscriber. The KR2 device is still connected to
the subscribers LIC and has to be disconnected, and a channel has to be
selected between the subscriber switch and the group switch.

038 02-EN/LZM 111 012 R1B 55


KR2R KR2
KSCODE2 CJ
Last Digit DRCODE

CHMON RE
IGR1 REIBA
IGR1

OSEIZEPOINT C7BTI3 C7OTHI3


SEIZEOLINK
OUTSEIZED

OSEIZED3

OSIDESEIZED
SUPIA
OSIDESEIZED

OSIDESEIZEDR
CHMON
ISELPA
JT2
ETCSEIZE

ETCSEIZED

TS
SELPAT1

SELPATR CHMON
ISELPAR

TSM GS
BSELOPA
TCT

TCTR
OPED
OREADYFORCALL

CHMON
IGRA

CALLPOINT

CALL

STARTDIGSEND

SUPIA
STARTDIGSEND

DISCDR
TSCRLSE
Continued in
next figure

TSCRLSED
DRCLEAR

Figure 3.6
Reception & Analysis of Last Digit, Setting up the Speech Path

56 038 02-EN/LZM 111 012 R1B


Call Set-up - Outgoing SS7

ISELPA (CJ)
RE tells CJ to select a path on the incoming side. The path will either be on
a timeslot in the EMTS for an internal call (both subscribers in the same
EMG), or on a JT/RT channel to the group switch for an outgoing call or a
call where the two subscribers are in the same exchange, but are connected
to different EMGs. The data in ISELPA tells CJ which case applies.
Also, CJ knows which of the blocks JT or RT is to be used, as it was told
earlier, in the signal CALLCJ, whether or not the A-subscribers EM
belonged to a local or remote subscriber stage.

ETCSEIZE (JT2), ETCSEIZED (CJ)


For our outgoing call, block CJ first orders selection of a channel between
the subscriber stage and the group switch. Block JT2, in our case, tries to
select a channel in the PCM system connected to the EM of the A-
subscriber. In case of congestion, or if there is no direct path to this EM
then any idle channel from the EMG is chosen. JT2 replies with the signal
ETCSEIZED which contains the JT individual, the EM containing the
individual and the position in the time switch in the EM.

SELPAT1 (TS) SELPATR (CJ)


CJ now asks TS to select and reserve in software a path between the LI3
and the selected JT2 channel through the subscriber switch. TS block will
need to use the Time Switch Bus if the LI3 and JT2 individuals are
connected to different EMs. TS replies with SELPATR saying that the
connection has been selected in software and reserved. (The path is not yet
operated in hardware - the LI3 device is still connected in hardware to the
KR2 device).

ISELPAR (RE)
Block CJ informs RE that a path through the subscriber switch has been
selected. The signal also contains the multiple position in GS of the
selected JT2 channel. This information will be used later by the register.

BSELOPA (GS)
RE now asks block GS to connect the multiple position (MUP) of the
selected JT2 channel to the MUP of the outgoing C7BTI3 channel. (This
MUP was sent to RE earlier in the signal OSEIZED3, above). To make the
connection, GS block first selects and busy-marks an idle timeslot for the
call.

TCT (TSM), TCTR (GS)


GS now sends the timeslot data together with the incoming and outgoing
multiple positions and respective TSMs to block TSM and orders it to set
up the connection and perform a through connection test. Signals are thus
sent to the regional software of TSM to operate the hardware. After a
successful connection and through connection test, the signal TCTR is sent
back to GS.

038 02-EN/LZM 111 012 R1B 57


KR2R KR2
KSCODE2 CJ
Last Digit DRCODE

CHMON RE
IGR1 REIBA
IGR1

OSEIZEPOINT C7BTI3 C7OTHI3


SEIZEOLINK
OUTSEIZED

OSEIZED3

OSIDESEIZED
SUPIA
OSIDESEIZED

OSIDESEIZEDR
CHMON
ISELPA
JT2
ETCSEIZE

ETCSEIZED

TS
SELPAT1

SELPATR CHMON
ISELPAR

TSM GS
BSELOPA
TCT

TCTR
OPED
OREADYFORCALL

CHMON
IGRA

CALLPOINT

CALL

STARTDIGSEND

SUPIA
STARTDIGSEND

DISCDR
TSCRLSE
Continued in
next figure

TSCRLSED
DRCLEAR

Figure 3.6
Reception & Analysis of Last Digit, Setting up the Speech Path

58 038 02-EN/LZM 111 012 R1B


Call Set-up - Outgoing SS7

OPED (RE)
GS informs RE that the path is now operating in the Group Switch.

OREADYFORCALL (REIBA)
RE informs REIBA that it is ready to send the call. A connection now
exists in between the LIC, JT and outgoing C7BT devices.

IGRA (CJ)
REIBA now sends a buffered signal to CJ to inform it that the complete B-
number has been received. It will be used in CJ to initiate disconnection of
the KR2 device as this is still connected

CALLPOINT (RE)
REIBA informs RE with this direct signal that the call can be sent to the
outgoing side.

CALL (C7OTHI3)
RE informs the traffic handling block for the outgoing trunk to send out a
call message (IAM or IAI), in this case an IAI (Initial Address message,
Additional information).

STARTDIGSEND (REIBA)
RE informs REIBA that digit sending by means of OGRA (outgoing group
A) signals is ready to be started. REIBA and block SUPIA will take part in
this signalling.

STARTDIGSEND (SUPIA)
REIBA passes on the signal to block SUPIA, the block handling the A-
number analysis.

DISCDR (KR2)
When the buffered signal IGRA - sent by REIBA above - arrives in CJ, it
causes CJ to send DISCDR to KR2 to disconnect the KR device.

TSCRLSE (TS)
KR2 orders TS block to release the connection LI2-KR3 in the Time
Switch.

TSCRLSED (KR2)
After test and disconnection TS will eventually reply with the signal
TSCRLSED. This signal and the following signal, concerning
disconnection of KR2, is shown at this point.

DRCLEAR (CJ)
On release of the connection in the Time Switch, a signal is sent by KR2 to
its regional software to initiate test and disconnection of the KR2 device.
KR2 sends DRCLEAR to CJ to say that the KR2 device has been
disconnected.

038 02-EN/LZM 111 012 R1B 59


RE C7OTHI3
CALL

OGRA H28

LONGDISTINFO

OGRA H29

OROUTINGINFOF

REIBA OGRA H11


SUPIA OGRA H11
OGRA H11

CHECKBDIGREQ

OGR5
OGR5

OGRA H23
OGRA H23

OBNUMINFO

OGRA H4
OGRA H4

OBNR

OREADSUPINFBACK
IREADSUPINFBACK

OANRANDINFO

OENDSUPINFFORW

OREADINFOBACK

OCALLCHARFORW
IREADINFOBACK

OENDINFOFORW
C7DR2
ROUTEMSU C7ST2
C7EMITMSU C7ST2R
C7MSUERP
C7EMITMSUACK
ROUTEMSUACK MSU (IAI) SENT
OENDBACK
IENDBACK

Figure 3.7
Formation & Sending IAI Message Signal Unit

60 038 02-EN/LZM 111 012 R1B


Call Set-up - Outgoing SS7

3.5 Formation and sending IAI Message Signal


Unit

3.5.1 Formation of IAI Message Signal Unit


The next sequence of the call setup continues after the signal CALL
arrives in C7OTHI3, as seen above. OGRA (outgoing group A) signals
will be used to collect the information required for creating the MSU
Initial Address message with additional Information (IAI) to be sent to the
remote exchange.
As C7 signalling is used, the OGRA signals do not come from the remote
exchange, but are sent by C7OTHI3 to the RE blocks and SUPIA to
collect the information required for this C7 message.

OGRA (RE)
The first OGRA signal sent was OGRA H28. This signal contains two
data words: the pointer in the RE individual and the number of the signal.
Signal H28 is used to obtain Long Distance information from RE.

LONGDISTINFOF (C7OTHI3)
The reply signal to the C7 block contains information about language
digits, echo suppressors and satellite connections.

OGRA (RE)
The next OGRA signal is number H29, which asks for information about
routing information.

OROUTINGINFO (C7OTHI3)
The signal gives information about required transmission medium, type of
signalling and type of call (national/international).

OGRA (RE, REIBA, SUPIA)


The next OGRA signal, number H11, requires information about
categories and restrictions on the A-subscriber and is therefore sent to
SUPIA, via REIBA.

CHECKBDIGREQ (REIBA)
This signal is sent to REIBA by SUPIA when the latter receives a request
for information (IGRA/OGRA), in case REIBA has to request B-digit
information from CJ (signal INEXTBD). This is determined in REIBA,
depending on the state of the REIBA individual when the signal is
received. No signal is sent from REIBA in this case.

OGR5 (RE, C7OTHI3)


The answer signal to OGRA H11. It contains special category
information for the A-subscriber, e.g. Access Barring, TCL-class, Priority
Class, etc.
RE passes the information on to C7OTHI3.

038 02-EN/LZM 111 012 R1B 61


RE C7OTHI3
CALL

OGRA H28

LONGDISTINFO

OGRA H29

OROUTINGINFOF

REIBA OGRA H11


SUPIA OGRA H11
OGRA H11

CHECKBDIGREQ

OGR5
OGR5

OGRA H23
OGRA H23

OBNUMINFO

OGRA H4
OGRA H4

OBNR

OREADSUPINFBACK
IREADSUPINFBACK

OANRANDINFO

OENDSUPINFFORW

OREADINFOBACK

OCALLCHARFORW
IREADINFOBACK

OENDINFOFORW
C7DR2
ROUTEMSU C7ST2
C7EMITMSU C7ST2R
C7MSUERP
C7EMITMSUACK
ROUTEMSUACK MSU (IAI) SENT
OENDBACK
IENDBACK

Figure 3.7
Formation & Sending IAI Message Signal Unit

62 038 02-EN/LZM 111 012 R1B


Call Set-up - Outgoing SS7

OGRA (RE, REIBA)


OGRA H23 is now sent to REIBA via RE. It requests information about
the B-number regarding type, Numbering Plan and Network Identification
information, etc.

OBNUMINFO (C7OTHI3)
The required B-number information is sent from RE.

OGRA (RE, REIBA)


OGRA H4 is now sent to REIBA requesting the B-number.

OBNR (C7OTHI3)
The B-number is sent, starting with the first digit according to the sending
program and ending with the last digit.

OREADSUPINFBACK (RE)
The data words in this signal consist of request bits, each bit stating
whether or not supplementary service data concerning the A-subscriber is
required. Examples are: Supplementary Service Indicators, Redirection
Information, A-number and A-number information and Call Completion
To Busy Subscriber.
The signal is concerned with a so-called event that relates to the signalling
between the exchanges. The event in this case is Forward Setup. (Note:
this type of event should not be confused with the call events in register
position as used by signal TCEVENTSUB, seen earlier).

IREADSUPINFBACK (SUPIA)
The signal passes on the above request for information, including the
event, to block SUPIA.

OANRANDINFO (C7OTHI3)
SUPIA replies to the C7 outgoing traffic handling block with the required
supplementary service data, including the A-number.

OENDSUPINFFORW (C7OTHI3)
SUPIA informs C7OTHI3 that the supplementary service data requested
for this event by signal OREADSUPINFBACK has now all been sent.

OREADINFOBACK (RE)
This signal requests further information for this event from RE. There
exists a large number of answer signals and the one to be sent is
determined by the event, here Forward Setup.

OCALLCHARFORW (C7OTHI3)
The answer to the previous signal, in this case supplying requested
information. It includes signalling and information transfer characteristics
for the call, such as if the call is wholly or partly ISDN, and if C7
signalling is used for all or part of the call.

038 02-EN/LZM 111 012 R1B 63


RE C7OTHI3
CALL

OGRA H28

LONGDISTINFO

OGRA H29

OROUTINGINFOF

REIBA OGRA H11


SUPIA OGRA H11
OGRA H11

CHECKBDIGREQ

OGR5
OGR5

OGRA H23
OGRA H23

OBNUMINFO

OGRA H4
OGRA H4

OBNR

OREADSUPINFBACK
IREADSUPINFBACK

OANRANDINFO

OENDSUPINFFORW

OREADINFOBACK

OCALLCHARFORW
IREADINFOBACK

OENDINFOFORW
C7DR2
ROUTEMSU C7ST2
C7EMITMSU C7ST2R
C7MSUERP
C7EMITMSUACK
ROUTEMSUACK MSU (IAI) SENT
OENDBACK
IENDBACK

Figure 3.7
Formation & Sending IAI Message Signal Unit

64 038 02-EN/LZM 111 012 R1B


Call Set-up - Outgoing SS7

IREADINFOBACK (SUPIA)
This is used to collect further information about the event Forward Setup.
The requested information is indicated by the request bits - in this case RE
asks SUPIA if it has any more information about call characteristics.

OENDINFOFORW (C7OTHI3)
SUPIA only has more information for ISDN calls and, as this call is not
ISDN, it sends the signal OENDINFOFORW to C7OTHI3 saying that the
reading of information is now complete for the event, Forward Setup.
The C7OTHI3 block now has all the information it requires to send the IAI
MSU to the next exchange via a signalling link. C7OTHI3 now assembles
the data into the routing label and octets of the MSU.

3.5.2 Sending of the Message Signal Unit

ROUTEMSU (C7DR2)
The MSU is sent on to C7DR2 where selection of a suitable signalling link
and its signalling terminal takes place. The signal is a combined forward
signal.

C7EMITMSU (C7ST2)
The MSU together with the chosen signalling terminal is sent in a
combined forward signal to C7ST2, the block that controls the signalling
terminals.

C7MSUERP (C7ST2R)
The MSU together with the signal terminal individual is sent to the
regional software of C7ST2 block. The RP in its turn sends on the message
via the signalling terminal.

C7EMITMSUACK (C7DR2)
The combined backward signal to confirm that the MSU has been sent. It
carries no other data.

ROUTEMSUACK (C7OTHI3)
The combined backward signal is sent directly from C7DR2 to confirm the
sending of the MSU. C7DR2 also inserts data about possible signalling
terminal congestion, if any for the STs belonging to the chosen route

OENDBACK (RE)
This signal is the return signal to signal CALL sent earlier, which was
used to initiate the outgoing signalling. C7OTHI3 replies that the outgoing
side has now finished the outgoing signalling for this event, Forward
Setup.

IENDBACK (SUPIA)
SUPIA is informed that the outgoing side has finished with the signalling
for this event. The program exits in this block and nothing will happen
until a backward signal comes in from the remote exchange.

038 02-EN/LZM 111 012 R1B 65


ACM
Received

C7ST2 C7ST2R
C7DR2 C7RPMSU
C7LABT C7DISCRMSU
C7BTI3
C7OTHI3 TAKEMSU
TAKEIMSU2
RE TAKEIMSU2
OSETUP6

REIBA OENDFORW
SUPIA STOPDIGSEND
STOPDIGSEND

STOPDIGSENDR

IBASETUP

IBASETUPR
OCLEAR

CJ TS
ISETUP
TSCOPERATE

TSCOPERATED
ICLEAR
CLCOF
TCINFO1

TCINFOACK

TCINFO2

TCINFOACK

TCINFO3

TCINFOACK

ITHCON

IRELINKED
CHSTART2
OTHCON
SUPIA
SUPIATHCON

SUPIATHCONACK
TAKEOVERCLCOF

ORELINKED

Figure 3.8
ACM Message Signal Unit Received

66 038 02-EN/LZM 111 012 R1B


Call Set-up - Outgoing SS7

3.6 ACM Message Signal Unit received


The next part of the call setup concerns reception of the return MSU,
Address Complete Message (ACM) from the remote exchange via the
signalling link, end-of-selection, the operation of the speech path through
the time switch in the subscriber stage and the handing over of the call
supervision to CLCOF.

3.6.1 Receiving the ACM Message Signal Unit

C7RPMSU (C7ST2)
An MSU has arrived at the RP controlling the signalling terminal and is
sent on to the CP. This MSU is an ACM, Address Complete Message,
which is sent when the complete B-number has been received and the B-
subscriber is free and ringing is started.

C7DISCRMSU (C7DR2)
C7ST2 translates the first data word in the signal, the incoming signal
terminal pointer, to an incoming signalling link and sends the MSU with
its data on to C7DR2.

TAKEMSU (C7LABT)
C7DR2 checks if the MSU is to be buffered, or, if not, either routes the
MSU to the Telephone User Part (TUP) in the own exchange (SP) with
signal TAKEMSU, or sends it back to C7ST2 if the message is for another
exchange (signal C7EMITMSU). The signal contains the pointer to the
user part, the signalling link and the MSU itself.

TAKEIMSU2 (C7BTI3)
C7LABT translates the CIC (Circuit Identification Code) in the MSU into
the C7BTI3 device and sends on the MSU to C7BTI3.

TAKEIMSU2 (C7OTHI3)
The message is sent on to the outgoing traffic handling block.

3.6.2 End-of-selection and handover to call supervision

OSETUP6 (RE)
This signal tells RE that the remote exchange has replied that call setup
has been successful, i.e. the B-subscriber is idle (i.e. ACM has been
received). The signal orders RE to perform end-of-selection in the
incoming side, i.e. connect the A-subscriber through TS. The signal
contains end-of-selection information from C7OTHI3 (time supervision of
B-answer, type of call release, B-subscriber is idle) and EOS from the
remote exchange about the B-subscriber.

038 02-EN/LZM 111 012 R1B 67


ACM
Received

C7ST2 C7ST2R
C7DR2 C7RPMSU
C7LABT C7DISCRMSU
C7BTI3
C7OTHI3 TAKEMSU
TAKEIMSU2
RE TAKEIMSU2
OSETUP6

REIBA OENDFORW
SUPIA STOPDIGSEND
STOPDIGSEND

STOPDIGSENDR

IBASETUP

IBASETUPR
OCLEAR

CJ TS
ISETUP
TSCOPERATE

TSCOPERATED
ICLEAR
CLCOF
TCINFO1

TCINFOACK

TCINFO2

TCINFOACK

TCINFO3

TCINFOACK

ITHCON

IRELINKED
CHSTART2

OTHCON
SUPIA
SUPIATHCON

SUPIATHCONACK
TAKEOVERCLCOF

ORELINKED

Figure 3.8
ACM Message Signal Unit Received

68 038 02-EN/LZM 111 012 R1B


Call Set-up - Outgoing SS7

OENDFORW (C7OTHI3)
RE replies with a return signal, sending only the C7OTHI3 pointer and the
event, Initial Backward Setup Information. This signal says that this event
is now terminated and is of no further interest for the outward side. It
causes the state of the C7OTHI3 individual to change from REG to
REGEND and the signal OCLEAR to be sent.

STOPDIGSEND (REIBA), (SUPIA)


This signal is sent to SUPIA via REIBA. It stops any possible digit
sending to RE.

STOPDIGSENDR (RE)
SUPIA acknowledges the above signal.

IBASETUP (REIBA), IBASETUPR (RE)


RE asks REIBA which end-of-selection information should be sent to the
incoming side. This information only concerns end-to-end signalling.

OCLEAR (RE)
This signal is a result of OENDFORW above. C7OTHI3 informs RE that
end-of-selection is finished in the outgoing junction.

EOSCHARGANA (CHCOOR) (Not shown in diagram)


RE now initiates the end-of-selection charging analysis by this signal.
This analysis uses B-subscribers charging information to modify or
completely change the charging program obtained earlier in the primary
charging analysis. Information concerning A and B-subscriber categories,
charging information for outgoing/incoming trunks (such as if charging
pulses will be received) etc., is sent to CHCOOR. (CHCOOR orders block
CHAP to perform the actual analysis).

PREPARECHARG (CHMON) (Not shown in diagram)


After the EOS charging analysis is complete CHCOOR orders CHMON to
prepare for charging. The signal data contains - as well as the charging
individual - Tariff Class information, Call Meter information, information
on A and B-subscribers, Charging Method: with or without pulses,
Charged Party, Charging Point, whether charging pulses are sent back
from a superior exchange, etc.

EOSCHARGANAR (RE) (Not shown in diagram)


The result of the end-of-selection charging analysis is sent to RE. The data
contains the Tariff Class, a message saying that charging is prepared (or an
EOS code if not), an indication whether or not A- subscriber is charged
and Charging Point information.

ISETUP (CJ)
RE tells CJ to set up the speech condition on the incoming side, passing on
data about end-of-selection and charging. The signal passes through
CHMON.

038 02-EN/LZM 111 012 R1B 69


ACM
Received

C7ST2 C7ST2R
C7DR2 C7RPMSU
C7LABT C7DISCRMSU
C7BTI3
C7OTHI3 TAKEMSU
TAKEIMSU2
RE TAKEIMSU2
OSETUP6

REIBA OENDFORW
SUPIA STOPDIGSEND
STOPDIGSEND

STOPDIGSENDR

IBASETUP

IBASETUPR
OCLEAR

CJ TS
ISETUP
TSCOPERATE

TSCOPERATED
ICLEAR
CLCOF
TCINFO1

TCINFOACK

TCINFO2

TCINFOACK

TCINFO3

TCINFOACK

ITHCON

IRELINKED
CHSTART2
OTHCON
SUPIA
SUPIATHCON

SUPIATHCONACK
TAKEOVERCLCOF

ORELINKED

Figure 3.8
ACM Message Signal Unit Received

70 038 02-EN/LZM 111 012 R1B


Call Set-up - Outgoing SS7

TSCOPERATE (TS), TSCOPERATED (CJ)


The path through the Time Switch was reserved in software earlier by
signal SELPAT1 (Figure 3.6). CJ now orders TS to connect the path in
hardware as well. The ring control tone will soon be sent back on the
speech path from the B-subscribers exchange to the A-subscriber.

ICLEAR (RE)
CJ reports to the register that the incoming side is prepared. This signal
also passes through CHMON on route to RE.

TCINFO1, 2, 3 (CLCOF), TCINFOACK (RE)


In these three combined forward signals RE passes on all the information
about the call to CLCOF, the block that will supervise the call. This data
includes data about the conditions that must be fulfilled for disconnection.

ITHCON (CJ), IRELINKED (RE)


The register tells the incoming side (A-side) to through-connect and
re-link to the CLCOF individual. CJ replies with signal IRELINKED.
(The block CHMON that monitors the charging also re-links in between
CJ and CLCOF. This is not shown in the figure here.

CHSTART2 (CHMON)
CJ orders CHMON to start charging with this signal. As the call has
reached end-of-selection, CHMON first checks if any charging tariff has
been specified for the time between end-of-selection and B-answer. As no
such charging has been specified in this application, the program exits and
no charging is started yet.

OTHCON (C7OTH3)
RE tells the outgoing side, C7OTH3 to through connect and re-link to the
CLCOF individual.

SUPIATHCON (SUPIA), SUPIATHCONACK (RE)


This combined forward signal is used to link SUPIA to the CLCOF
individual.

TAKEOVERCLCOF (CLCOF)
The RE block tells CLCOF that it is responsible for the call.

ORELINKED (RE)
C7OTH3 replies to the signal OTHCON above saying that it is re-linked to
block CLCOF. RE has now finished its work for this call. The RE
individual now takes the state idle and is available for selection by a new
call.
By this stage - after reception of the C7ACM message and the sending of
the above signals - end of selection has been reached. Ringing signals are
being sent at the B-subscribers exchange and ring control tones are being
sent back to the A-subscriber over the speech path.

038 02-EN/LZM 111 012 R1B 71


ANC
Received

C7ST2 C7ST2R
C7DR2 C7RPMSU
C7LABT C7DISCMSU
C7BTI3 TAKEMSU
C7OTHI3 TAKEIMSU2
TAKEIMSU2
CLCOF
MARKBANSW
BANSW1

OENDFORW
CHMON
BANSW2

CHSUB
STEPMETER1

STEPMETER1ACK

CJ
BANSW2

Figure 3.9
ANC Message Signal Unit Received

72 038 02-EN/LZM 111 012 R1B


Call Set-up - Outgoing SS7

3.7 Answer Charge Message received


The next part of the analysis concerns the part when B-subscriber answers.
This results in an MSU called ANC (Answer Charge Message) being
received at the ST connected to our signalling link and sent on via the RP.

C7RPMSU (C7ST2)
The MSU passes from the regional to the central software of block C7ST2.

C7DISCRMSU (C7DR2)
The MSU is passed on to routing and discriminating block which will
decide where the message is to be sent.

TAKEMSU (C7LABT)
Here, C7DR2 routes the message to block C7LABT in TUP.

TAKEIMSU2 (C7BTI3)
C7LABT performs the CIC-to-BT device translation and sends the
message to C7BTI3.

TAKEIMSU2 (C7OTHI3)
The message is sent on to C7OTHI3. Here the state of the device is
changed to B-answer, and the individual is marked answer-charge.

MARKBANSW (C7BTI3)
This signal is sent to mark the device B-answer in C7BTI3. This is used by
the seizure supervision of the trunks.

BANSW1 (CLCOF)
CLCOF is informed that the B-subscriber has answered. The A-subscriber
is marked charging, the B-subscriber as off-hook, and the time supervision
on B-answer is stopped.

OENDFORW (C7OTHI3)
This signal is sent to C7BTI3 to indicate that the current event, Answer, is
of no further interest to the outgoing side.

BANSW2 (CHMON)
CHMON is informed that B-subscriber has answered. The signal contains
information about which subscriber, if any, is charged and which
exchange carries out the charging. It is this signal that starts the charging:
CHMON then orders block CHCHARG to initiate pulse generation and
send back the start pulses (not shown). CHMON then sends the pulses to
block CHSUB with signal STEPMETER1 to step the subscribers call
meter.

BANSW2 (CJ)
This B-answer signal is passed on to CJ by CHMON. The state of the A-
subscriber in CJ is set as A-speech, substate is B-answer.

038 02-EN/LZM 111 012 R1B 73


74
Figure 3.10
LI3R LI3
CSTERM CJ CHMON
STERM
CLCOF

A-Subscriber Clears. CLF Sent


ATERM1 ATERM1

DISCGS DISCGS C7OTHI3


OGREL
GS
TSM RELA
DISCONN ODISC

DISCONNR SUPIA
OSIDEREL

C7BTI3
ODISCED C7DR2
IDISC OTRELEASE1 C7ST2
IDISC ROUTEMSU
TS ISIDEREL C7EMITMSU
C7ST2R
TSCRLSE C7MSUERP
C7EMITMSUACK
ROUTEMSUACK
TSCRLSED
IDISCED
IDISCED
JT2 CLF SENT
LI3 ETCRLSE
RLSELA4
RELEASESUPIA
RLSEDSUB1
SLCT
LTEST
CHCOOR
CALLDISC

038 02-EN/LZM 111 012 R1B


Call Set-up - Outgoing SS7

3.8 A-subscriber clears, Clear Forward sent


The next part of the call covered here is the case when the A-subscriber
hangs up. The case when the A-subscriber hangs up first is covered here,
but there is little difference in this part if the B-subscriber had hung up
first.

CSTERM (LI3)
LI3R informs LI3 that the A-subscriber has hung up.

STERM (CJ)
CJ is informed of the termination.

ATERM1 (CLCOF)
The fact that the A-sub has gone on hook is sent to CLCOF to initiate a
clear forward signal being sent to the other exchange. The signal passes
through CHMON where steps will be initiated to stop charging.

DISCGS (CJ)
CLCOF orders CJ to disconnect the through-connection in the Group
Switch. Again, the signal passes through CHMON which is linked
between CJ and CLCOF.

RELA (GS)
CJ orders GS to disconnect the path through the Group Switch.

DISCONN (TS)
GS orders TSM to disconnect the path through the TSM. The signal
contains the time slot and incoming and outgoing multiple positions in GS.

DISCONNR (GS)
After disconnection the individual in TSM handling the call is set to idle
and the answer signal saying the connection is released is sent to GS.

OGREL (C7OTHI3)
After sending DISCGS above, CLCOF orders a forced release of the
outgoing side.

ODISC (C7OTHI3)
CLCOF orders a release of the outgoing side from TCS. This means that
the linking between the CLCOF and C7OTHI3 individuals is released. The
signal contains data for stepping the quality supervision counter. The state
of the C7OTHI3 individual changes from speech to passive. For this
block, passive state means that the device is in fact idle.

OSIDEREL (SUPIA)
CLCOF informs SUPIA about the disconnection of the outgoing side.

038 02-EN/LZM 111 012 R1B 75


76
Figure 3.10
LI3R LI3
CSTERM CJ CHMON
STERM
CLCOF

A-Subscriber Clears. CLF Sent


ATERM1 ATERM1

DISCGS DISCGS C7OTHI3


OGREL
GS
TSM RELA
DISCONN ODISC

DISCONNR SUPIA
OSIDEREL

C7BTI3
ODISCED C7DR2
IDISC OTRELEASE1 C7ST2
IDISC ROUTEMSU
TS ISIDEREL C7EMITMSU
C7ST2R
TSCRLSE C7MSUERP
C7EMITMSUACK
ROUTEMSUACK
TSCRLSED
IDISCED
IDISCED
JT2 CLF SENT
LI3 ETCRLSE
RLSELA4
RELEASESUPIA
RLSEDSUB1
SLCT
LTEST
CHCOOR
CALLDISC

038 02-EN/LZM 111 012 R1B


Call Set-up - Outgoing SS7

ODISCED (CLCOF)
C7OTHI3 replies to CLCOF that the outgoing side is disconnected. It also
sends the signal OTRELEASE1 to C7BTI3. This will be covered later,
below.

IDISC (CJ)
CLCOF now orders CJ to release the incoming individual from TCS. The
signal contains data for stepping the speech quality supervision counter
and about the type of disconnection, e.g normal, subscriber busy,
congestion, etc. The signal passes via CHMON where it causes the pulse
generation to be stopped (in block CHCHARG) and the reason for call
release to be stored.

ISIDEREL (SUPIA)
CLCOF informs SUPIA about the disconnection of the incoming side.

TSCRLSE (TS)
On receiving IDISC, CJ checks if the Group Switch is disconnected, and,
as this was done above, sets the state of the call individual to
disconnection started, and the TS state to release. TSCRLSE is sent to TS
to release the connection between the LI3 and JT2 devices.

TSCRLSED (CJ)
TS replies that the TS connection is released.

IDISCED (CLCOF)
On reception of TSCRLSED, CJ sends this signal to CLCOF saying that
the incoming individual is released from CLCOF (TCS). As will be seen
later, this will cause CLCOF to start the disconnection procedure in TCS.
The signal passes CHMON where the charging individual is passivated
and the total charging call counter is stepped.

CALLDISC (CHCOOR)
After receiving IDISCED CHMON informs CHCOOR of the call
disconnection. The signal contains the individual, the call duration in
seconds and the number of recorded pulses for the call.

ETCRLSE (JT2)
CJ next checks to see if the call individual shows that a JT/RT device is
linked to the incoming side. As it is, it sends the signal to release the JT
channel. On reception of the signal, JT2 updates its seizure and quality
supervision counters, sets the state of the device to idle and puts the device
in the idle list. No return signal is sent in this case.

RLSELA4 (LI3)
CJ next sends this signal to LI3 to release the LI individual. The signal
contains the individual, information that B-subscriber has answered and
information about any line test that is to be made.

038 02-EN/LZM 111 012 R1B 77


78
Figure 3.10
LI3R LI3
CSTERM CJ CHMON
STERM
CLCOF

A-Subscriber Clears. CLF Sent


ATERM1 ATERM1

DISCGS DISCGS C7OTHI3


OGREL
GS
TSM RELA
DISCONN ODISC

DISCONNR SUPIA
OSIDEREL

C7BTI3
ODISCED C7DR2
IDISC OTRELEASE1 C7ST2
IDISC ROUTEMSU
TS ISIDEREL C7EMITMSU
C7ST2R
TSCRLSE C7MSUERP
C7EMITMSUACK
ROUTEMSUACK
TSCRLSED
IDISCED
IDISCED
JT2 CLF SENT
LI3 ETCRLSE
RLSELA4
RELEASESUPIA
RLSEDSUB1
SLCT
LTEST
CHCOOR
CALLDISC

038 02-EN/LZM 111 012 R1B


Call Set-up - Outgoing SS7

RLSEDSUB1 (CJ)
LI3 informs CJ that the subscriber line is released. The state of the
subscriber line is set to blocked prior to testing.

LTEST (SLCT)
LI3 asks SLCT to perform a test of the LI individual. The data includes the
individual, EM and EMG of the LIC, as well as whether B-answer was
obtained or not. B-answer implies a line test, a non B-answer leads to test
of the LIC.

RELEASESUPIA (SUPIA)
When CLCOF receives IDISCED, above, saying that the A-side is
released from TCS, it starts the complete disconnection procedure for the
call in TCS. It disconnects forlopp links and variables, releases all COF
individuals linked in (Coordination Of Functions) decreases traffic level
counters and sends this signal to release the connection to SUPIA. Finally
the CLCOF individual is set to idle. It has now finished its work for this
call.
The following part of the signal handling covers the sending of the MSU
containing the Clear Forward signal towards the remote exchange.

OTRELEASE1 (C7BTI3)
After signal ODISCSED was sent by C7OTHI3 to CLCOF, above,
C7OTHI3 orders C7BTI3 to initiate the release procedure for an outgoing
call, i.e. to send a clear forward signal. The data sent here includes the type
of release, here a normal release.
The following signals for sending the C7MSU have been covered earlier
when the MSU IAI was sent. It should be noticed that in this case the MSU
is created and sent by the block C7BTI3 and not C7OTHI3.

ROUTEMSU (C7DR2)
For selection of a suitable signalling link and its signalling terminal.

C7EMITMSU (C7ST2)
Sends the MSU together with the chosen signalling terminal to C7ST2

C7MSUERP (C7ST2R)
The MSU together with the signal terminal individual is sent to the
regional software of C7ST2 block. The RP sends on the message via the
signalling terminal.

C7EMITMSUACK (C7DR2)
The combined backward signal confirming that the MSU has been sent.

ROUTEMSUACK (C7BTI3)
The combined backward signal is sent directly from C7DR2 to confirm the
sending of the MSU.

038 02-EN/LZM 111 012 R1B 79


RLG
Received
C7ST2R
C7ST2
C7DR2 C7RPMSU
C7LABT C7DISCRMSU
C7BTI3 TAKEMSU
TAKEIMSU2

Figure 3.11
RLG Received

80 038 02-EN/LZM 111 012 R1B


Call Set-up - Outgoing SS7

3.9 Release Guard MSU received


Finally, the Release Guard MSU is received from the remote exchange. It
is received at the RP controlling the ST and sent on to C7BTI3 by the
signals already described above for the two previously received MSUs,
ACM and ANC:

C7RPMSU (C7ST2)
The Release Guard MSU has arrived at the RP and is sent on to the CP.

C7DISCRMSU (C7DR2)
C7ST2 sends the MSU with its data on to C7DR2.

TAKEMSU (C7LABT)
Here, C7DR2 routes the MSU to the Telephone User Part (TUP) in the
own exchange (SP). The signal contains the pointer to the user part, the
signalling link and the MSU itself.

TAKEIMSU2 (C7BTI3)
After translating the CIC information to a BT device C7LABT sends the
Release Guard message to CTBTI3, where the device state is set to idle.
No further signal is sent to C7OTHI3.

038 02-EN/LZM 111 012 R1B 81


82 038 02-EN/LZM 111 012 R1B

You might also like