Table of Contents

Table of Contents...........................................................................................................1
Table of Figures .............................................................................................................3
1. Introduction................................................................................................................4
1.1. PSTN Signaling ......................................................................................................4
1.1.1 Channel Associated Signaling (CAS)...............................................................4
1.1.2 Common Channel Signaling (CCS)..................................................................5
1.2. Signaling Modes .....................................................................................................5
1.2.1. Associated Signaling........................................................................................5
1.2.2. Non-Associated Signaling ...............................................................................6
1.2.3. Quasi-Associated Signaling .............................................................................6
1.3. The Evolution of SS7..............................................................................................7
1.4. SS7 Deployment Planes..........................................................................................7
2.1. SS7 Signaling Architecture.....................................................................................7
2.1.1. Signal Switching Point.....................................................................................7
2.1.2. Signal Transfer Point .......................................................................................8
2.1.2.1 National STP..............................................................................................9
2.1.2.2. International STP ......................................................................................9
2.1.2.3. Gateway STP ............................................................................................9
2.1.3. Signal Control Point.......................................................................................10
2.2. SS7 Links ..............................................................................................................11
2.2.1. A-Links ..........................................................................................................11
2.2.2. B- and D-Links ..............................................................................................11
2.2.3. C-Links ..........................................................................................................12
2.2.4. E- and F-Links ...............................................................................................13
2.3. Linksets .............................................................................................................13
2.4. Routes ...............................................................................................................13
2.5. Point Codes .......................................................................................................14
3.1. SS7 Protocol Stack................................................................................................15
3.1.1. SS7 Level 1: Physical Connection.................................................................15
3.1.2. SS7 Level 2: Data Link..................................................................................16
3.1.3. SS7 Level 3: Network Level..........................................................................16
3.1.3.1. Link Management ...................................................................................16
3.1.3.2. Route Management .................................................................................17
3.1.3.3. Traffic Management................................................................................17
3.1.3.4. Message Routing.....................................................................................17
3.1.4. SS7 Level 4: Protocols, User and Application Parts......................................18
TCAP ...................................................................................................................18
4.1. SS7 Signal Units ...................................................................................................19
4.2. Signal Unit Structure.............................................................................................20
4.2.1. Signal Unit Flow Control...............................................................................21
SU Error Detection ..............................................................................................21
4.3. Types of Signal Units............................................................................................21
4.3.1. Message Signal Units.....................................................................................21
SIO Structure .......................................................................................................22
SIF Structure ........................................................................................................22
4.3.2. Link Status Signal Unit..................................................................................23
4.3.3. Fill-in Signal Unit ..........................................................................................23

Link Alignment....................................................................................................24
5. ISUP and TCAP.......................................................................................................24
5.1. Basic ISUP Signaling............................................................................................24
5.2. ISUP Message Format ..........................................................................................25
5.3. ISUP Message Types ............................................................................................26
5.4. ISUP Call Sequence..............................................................................................26
5.4.1. Call Initiated...................................................................................................26
5.4.2. ISUP Call Answered ......................................................................................28
5.4.3. ISUP Call Released........................................................................................28
5.5. TCAP Functions....................................................................................................30
5.5.1. TCAP Transaction Portion.............................................................................30
5.5.2. TCAP Component Portion.............................................................................30
5.5.3. Sample TCAP Database Query......................................................................31

Table of Figures
Figure 1: End-to-End Signaling............................................................................... 4
Figure 2: Common Channel Signaling .................................................................... 5
Figure 3: Associated Signaling ................................................................................ 5
Figure 4: Non-Associated Signaling ........................................................................ 6
Figure 5: Quasi-Associated Signaling ..................................................................... 6
Figure 6: STP Levels................................................................................................ 9
Figure 7: A-Links ................................................................................................... 11
Figure 8: B/D-Links ............................................................................................... 12
Figure 9: C-Links ................................................................................................... 12
Figure 10: E- and F-Links...................................................................................... 13
Figure 11: SS7 Network ......................................................................................... 14
Figure 12 SS7 Protocol Stack ................................................................................ 15
Figure 13 Message Transfer Part Components ..................................................... 18
Figure 14 SS7 Level 4 Protocols, User and Application Parts.............................. 18
Figure 15 SS7 Signal Unit Types ........................................................................... 20
Figure 16 MSU Format.......................................................................................... 21
Figure 17 MSU SIF Structure ................................................................................ 23
Figure 18 LSSU Format......................................................................................... 23
Figure 19 FISU Format ......................................................................................... 24
Figure 20 Basic ISUP Signaling ............................................................................ 24
Figure 21 ISUP Message Format .......................................................................... 25
Figure 22 ISUP Call Initiation (1)........................................................................ 27
Figure 23 ISUP Call Initiation (2)........................................................................ 27
Figure 24 ISUP Call Answered.............................................................................. 28
Figure 25 ISUP Call Release (1) .......................................................................... 29
Figure 26 ISUP Call Release (2) .......................................................................... 29
Figure 27Sample TCAP 800 Number Query ..................................................... 31

1. Introduction
Everything in the telecommunications network is based on signalingcall setup,
connection, teardown, and billing. The two forms of signaling used by the network
are:
Channel Associated Signaling (CAS)
Common Channel Signaling (CCS)
Signaling System Number Seven (SS7) is a form of common channel signaling, that
provides intelligence to the network, and allows quicker call setup and teardown
saving time and money.

1.1. PSTN Signaling

In order to route telephone traffic through the Public Switched Telephone Network
(PSTN), it is necessary to communicate with the switches that make up the PSTN.
Signaling is a means for transferring network-related information between switching
nodes, and also between the end office switches and their subscribers. (See Figure 1).
Signaling is used to do the following:
Request service from the central office switch
Provide central office switch with the information necessary to route a telephone
call.
Alert destination address of incoming call (ringing).
Provide status information and call supervision for billing.
Manage network lines/trunks (set up and teardown calls).

Figure 1: End-to-End Signaling

1.1.1 Channel Associated Signaling (CAS)

When used for in-band signaling:
Call setup information (off-hook, dialtone, address digits, ringback, busy) is
transmitted in the same band of frequencies as used by the voice signal.
Voice (talk) path is cut over only when the call setup is complete, using the same
path that the call setup signals used.
The principal advantage of CAS is that it is inexpensive to implement and can be used
on any transmission medium.
However, CAS has the following disadvantages:
Interference is possible between signaling tones used by the network and
frequencies of human Speech patterns.
Speed - call setup and teardown is slower, less efficient use of resources

1.1.2 Common Channel Signaling (CCS)

CCS employs a separate, dedicated path for signaling. (See Figure 2) Voice trunks are
used only when a connection is established, not before. Call setup time is quicker
because resources are more efficiently used. CCS is the technology that makes ISDN
(Integrated Service Digital Network) and SS7 possible.

Figure 2: Common Channel Signaling

1.2. Signaling Modes

Associated SignalingUses one dedicated path between switches as the signaling
link.
Examples: ISDN-PRI (Integrated Services Digital Network Primary Rate Interface)
and E1-CAS.
Non-Associated SignalingUses separate logical paths and multiple nodes.
Quasi-Associated SignalingUses a minimal number of nodes (preferred for SS7,
causes less delay).

1.2.1. Associated Signaling

With this type of signaling, the signaling link directly parallels associated voice
trunks. Thus, dedicated links must be provisioned between every interconnected
switch. (See Figure 3).

Figure 3: Associated Signaling

1.2.2. Non-Associated Signaling

With this type of signaling, voice/data and signaling are carried on separate, logical
paths. Multiple nodes in the signaling path to the final destination can causes delays.
Although used in the SS7 network, it is not preferred. (See Figure 4)

1.2.3. Quasi-Associated Signaling

This type of signaling employs a minimal number of nodes, thus minimizing delays.
Quasi-associated signaling is the preferred signaling mode for SS7. (See Figure 5).

Figure 4: Non-Associated Signaling

Figure 5: Quasi-Associated Signaling

1.3. The Evolution of SS7

In the mid-1960s, the CCITT (now the ITU) developed a digital signaling standard
called Signaling System #6. SS6 was based on a packet-switched, proprietary data
network. SS6 used 2.4 Kbps data links to send packets of data to distant switches to
request services.
This was the first use of packet switching in the PSTN. SS6 packets consisted of 12
signal units of 28 bits each placed into a data block.
SS7 began deployment in 1983, and gradually phased out SS6. It was initially used
only in the interoffice network (from central office to central office), but has gradually
expanded and is now deployed in local central offices as well. SS7 provides a global
standard for call setup, routing, and control.
SS7 is a worldwide telecommunications protocol for wire, wireless and data
networks.

1.4. SS7 Deployment Planes

SS7 is deployed on two distinct levels or planes:
InternationalITU-TS standard
National country specific (North AmericaUS and Canada - uses the ANSI
standard)
Bellcore is an extension of the ANSI protocol and ensures the ability to interoperate
with Bell Operating Company (BOC) networks.
Gateways convert national versions of SS7 to ITU-TS versions so that the networks of
all nations can interoperate with each other.

2.1. SS7 Signaling Architecture

The SS7 signaling architecture consists of three essential components, interconnected
via signaling links.

2.1.1. Signal Switching Point

SSPs are switches that have SS7 software and terminating signaling links. An SSP can
be a combined voice/SS7 switch or an adjunct computer system (front end) connected
to a voice switch.
SSPs create packets (signal units) and send those messages to other SSPs, as well as
queries to remote shared databases to find out how to route calls. They can originate,
terminate, or switch calls.
SSPs communicate with the voice switch via the use of primitives and have the ability
to send messages using ISUP (call setup and teardown) and TCAP (database lookup)
protocols.
The SSP uses the calling party information (dialed digits) to determine how to route
the call. It looks up the dialed digits in the SSP routing table to find the corresponding
trunk circuit and terminating exchange. The SSP then sends an SS7 message out to

the adjacent exchange requesting a circuit connection on the trunk which was
specified in the routing table.
The adjacent exchange sends an acknowledgement back, giving permission to use that
trunk. Using the calling party information contained in the setup info, the adjacent
exchange determines how to connect to the final destination. This might require
several trunks to be set up between several different exchanges.
SSP manages all of these connections until the destination is reached.
Table 1 lists these components and their associated symbols.

Table 1: SS7 Network Signaling Components

2.1.2. Signal Transfer Point

STPs are packet switches, and act like routers in the SS7 network. Messages are not
usually originated by an STP. An STP can act like a firewall, screening messages with
other networks.
STPs route SS7 messages (based on information contained in the message format) to
outgoing signaling links over the SS7 network. They are the most versatile of all the
SS7 entities, and are a major component in the network.
There are three levels of STPs. (See Figure 6.)
National Signal Transfer Point
International Signal Transfer Point
Gateway Signal Transfer Point

2.1.2.1 National STP

A National STP exists within the national network (will vary with the country). It can
transfer messages that use the same national standard of protocol.
Messages can be passed to an International STP, but can not be converted by the
National STP. Protocol converters often interconnect a National and an International
STP by converting from ANSI to ITU-TS.

2.1.2.2. International STP

An International STP functions within an international network. It provides for SS7
interconnection of all countries, using the ITU-TS standard protocol.
All nodes connecting to an International STP must use the ITU-TS protocol standard.

2.1.2.3. Gateway STP

A Gateway STP converts signaling data from one protocol to another. Gateway STPs
are often used as an access point to the international network. National protocols are
converted to the ITU-TS protocol standard. Depending on its location, the Gateway
STP must be able to use both the International and National protocol standards.
A Gateway STP also serves as an interface into another networks databases, such as
from an interexchange carrier (IXC) to an end office. The Gateway STP can also be
configured to screen for authorized users of the network.
Gateway STPs also provide measurements of traffic and usage via the following
means:
TrafficMeasures the peg counts of the type of messages entering or leaving the
network.
Network eventsTrack events such as link out-of-service or local processor
outage, for maintenance purposes.

Figure 6: STP Levels

2.1.3. Signal Control Point

An SCP is usually a computer used as a front end to a database system. It is an
interface to telco databases, not usually to other, application-specific databases. (Refer
to Table 2).
Abbreviation
BSDB

Name
Business Services Database

CMSD

Call Management Services Database

HLR

Home Location Register

LIDB

Line Information Database

LNP

Local Number Portability

OSS

Operations Support Systems

VLR

Visitor Location Register

Description
Allows
companies to
create
and
store
proprietary databases, as
well as create private
networks.
Provides
information
relating to call processing,
network
management
(prevent congestion), call
sampling (create reports
for traffic studies), and the
routing, billing and thirdparty billing for 800, 976
and 900 numbers.
Used in cellular networks
to
store
subscriber
information.
Provides
billing
instructions.
Allows people to change
telco service providers but
keep their same telephone
number.
Associated with remote
maintenance centers for
monitoring and managing
SS7 and voice networks.
Used when a cell phone is
not recognized by the
mobile switching center
(MSC).

Table 2: Telco Databases Accessible via SCP

2.2. SS7 Links

An SS7 link is the physical transmission line (serial 56/64 Kbps or DS0 channel) that
connects the individual nodes in an SS7 network.
SS7 networks are built to be highly reliable and redundant. Link diversity is built into
the network design, providing multiple signaling paths, so that there is no single point
of failure. This practice ensures that redundant links have the capacity to handle all
rerouted network traffic.

2.2.1. A-Links
Access links (A-links) interconnect an STP and either an SSP or an SCP (signaling
end points). Their sole purpose is to deliver signaling to and from signaling end
points. End points always have at least two A-links (also called signaling beginning
points).
Any signaling that an SSP or SCP needs to send to any other node in the SS7 network
is sent on one of its A-links to its home STP, which processes and routes the
message along its way. Messages addressed to an SSP or SCP are routed to its
home STP, which forwards them to the addressed node over its A-links.
(See Figure 7)

Figure 7: A-Links

2.2.2. B- and D-Links

Bridge links (B-links) are the quad of links interconnecting peer pairs of STPs.
Diagonal links (D-links) are the quad of links interconnecting mated pairs of STPs at
different hierarchical levels. (See Figure 8)
Since the SS7 network has no clear hierarchy, these links are referred to as B-links,
D-links, or B/D-links.

2.2.3. C-Links
Cross links (C-links) interconnect mated STPs and are used to enhance the reliability
of the signaling network not regularly used by SS7 traffic. (See Figure 9) They are
used only when there has been a link failure which causes an STP to have no other
route.

Figure 8: B/D-Links

Figure 9: C-Links

2.2.4. E- and F-Links

Extended links (E-links) connect an SSP to an alternate STP to provide backup
connectivity to the network if the SSPs home STP cannot be reached on its A-link.
Fully associated links (F-links) directly connect two signaling end points (SSPs and/or
SCPs). They are not usually used in networks with STPs because they allow
associated signaling only, thus bypassing the security features provided with an STP.
(See Figure10).

Figure 10: E- and F-Links

2.3. Linksets
Links are put into groups called Linksets. Up to 16 links can be assigned to one
linkset. All links in a linkset must have the same adjacent node. Switches will
alternate traffic across all links in a linkset to ensure equal usage of all facilities in the
network.

2.4. Routes
The signal point must define linksets and routes in SS7 messaging. The following
entities are used in SS7 messaging:
RouteA collection of linksets to reach a particular destination. A linkset can
belong to more than one route.
RoutesetA collection of routes that are assigned to destinations and also provide
alternate routes.

 DestinationAn address entered into the routing table of a remote signaling point.
A destination need not be adjacent to the signaling point, but must be a point code that
can be reached by the signaling point.

2.5. Point Codes

In SS7, addresses are assigned using a three-level hierarchy.
MemberA signaling point within a cluster.
ClusterA collection of signaling points (members).
NetworkEach cluster is defined as being part of a network.
Any node in the SS7 network can be addressed by the three-level number defined by
its network, cluster, and member numbers. Each of these numbers is an 8-bit number
assigned a value from 0 to 255. This three-level address is called the point code of the
signaling point.
Whole SS7 network links (See Figure11).

Figure 11: SS7 Network

3.1. SS7 Protocol Stack

This section describes the components of the SS7 protocol stack. A stack is a set of
data storage locations that are accessed in a fixed sequence. The SS7 stack is
compared against the Open Systems Interconnection (OSI) model for communication
between different systems made by different vendors. Figure 12 shows the
components of the SS7 protocol stack.

3.1.1. SS7 Level 1: Physical Connection

This is the physical level of connectivity, virtually the same as Layer 1 of the OSI
model. SS7 specifies what interfaces will be used, both Bellcore (Telecordia) and
ANSI call for either the DS0A or the V.35 interface. Because central offices are
already using DS1 and DS3 facilities to link one another, the DS0A interface
is readily available in all central offices, and is preferred in the SS7 network. As the
demands on the SS7 network increase (local number portability), and as the industry
migrates toward ATM networks, the DS1 interface will become the link interface.

Figure 12 SS7 Protocol Stack

3.1.2. SS7 Level 2: Data Link

The data link level provides the network with sequenced delivery of all SS7 message
packets. Like the OSI data link layer, it is only concerned with the transmission of
data from one node to the next, not to its final destination in the network. Sequential
numbering is used to determine if any messages have been lost during transmission.
Each link uses its own message numbering series independent of other links. SS7 uses
CRC-16 error checking of data and requests retransmission of lost or corrupted
messages. Length indicators allow Level 2 to determine what type of signal unit it is
receiving, and how to process it.

3.1.3. SS7 Level 3: Network Level

The network level depends on the services of Level 2 to provide routing, message
discrimination and message distribution functions.
Message Discrimination determines to whom the message is addressed.
Message Distribution is passed here if it is a local message.
Message Routing is passed here if it is not a local message.
Message Discrimination
This function determines whether a message is local or remote using the
point code and data contained in a lookup table. Messages to remote destinations
are passed to the message routing function for additional processing.

Message Distribution
Message distribution provides link, route and traffic management
functions.

3.1.3.1. Link Management

This function uses the Link Status Signal Unit (LSSU) to notify adjacent nodes of link
problems. Level 3will send LSSUs via Level 2 to the adjacent node, notifying it of the
problems with the link and its status.
Diagnostics consists of realigning and resynchronizing the link.
RealignmentAll traffic is removed from the link, counters are reset to
zero, timers are reset and Fill-In Signal Units (FISUs) are sent in the meantime
(called the proving period).
Proving PeriodAmount of time FISUs are sent during link realignment.
The duration of the proving period depends on the type of link used. Bellcore
specifies the proving period for a 56 Kbps DS0 link is 2.3 seconds for normal
proving and 0.6 seconds for emergency proving.
Another form of link management uses changeover and changeback messages sent
using Message Signal Units (MSUs). MSUs advise the adjacent node to send traffic

over another link within the same linkset. The alternate link must be within the same
linkset.
The bad link is being realigned by Level 3 while traffic is rerouted over alternate
links. Changeback message is sent to advise the adjacent node that it can use the
newly restored link again. Changeback messages are typically followed by a
changeback acknowledgement message.

3.1.3.2. Route Management

This function provides a means for rerouting traffic around failed or congested nodes.
Route management is a function of Level 3 and works together with link
management.
Route management informs other nodes of the status of the affected node. It uses
Message Signal Units (MSUs) generated by adjacent nodes and is not usually
generated by the affected nodes. (Link management only informs adjacent nodes.)

3.1.3.3. Traffic Management

This function provides flow control if a node has become congested. It allows the
network to control the flow of certain messages based on protocol. Traffic
management deals with a specific user part within an affected node.
For example, if ISUP is not available at a particular node, a traffic management
message can be sent to adjacent nodes informing them that ISUP is not available,
without affecting TCAP messages on the same node.

3.1.3.4. Message Routing

Message discrimination in Level 3 will pass messages to message routing if it
determines the message is not local. Message routing reads the called and calling
party addresses to determine the physical address in the form of a point code.
Every SS7 node must have its own unique point code. Message routing determines the
point code from an address contained in the routing table.
Message Transfer Part
Protocols are used within the layers (levels) of the SS7 protocol to accomplish
functions called for at each level. Levels 1, 2 and 3 are combined into one part, the
Message Transfer Part (MTP). (See Figure 13.)
MTP provides the rest of the levels with node-to-node transmission, including basic
error detection and correction schemes and message sequencing. It provides routing,
message discrimination and distribution functions within a node.

Figure 13 Message Transfer Part Components

3.1.4. SS7 Level 4: Protocols, User and Application Parts

Level 4 consists of several protocols, user parts and application parts. (See Figure 14)

Figure 14 SS7 Level 4 Protocols, User and Application Parts

TCAP
Transactional Capabilities Application Part (TCAP) facilitates connection to an
external database. Information/data received is sent back in the form of a TCAP
message. TCAP also supports remote controlability to invoke features in another
remote network switch.
OMAP (Operations, Maintenance and Administrative Part) is an applications entity
that uses TCAP services for communications and control functions through the
network via a remote terminal.
MAP (Mobile Application Part) is used to share cellular subscriber information
among different networks. It includes information such as the mobile identification
number (MIN), and the serial number of the cellular handset. This information is used
by the IS-41 protocol during cellular roaming.

ASP
Application Service Part (ASP) provides the functions of Layers 4 through 6 of the
OSI model. These functions are not presently required in the SS7 network, and are
under further study. However, the ITU-T and ANSI standards do reference ASP as
viable.

SCCP
Signaling Connection Control Part (SCCP) is a higher level protocol than MTP that
provides end-to-endrouting. SCCP is required for routing TCAP messages to their
proper database.
TUP
Telephone User Part (TUP) is an analog protocol that performs basic telephone call
connects and disconnect. It has been replaced by ISUP, but is still used in some parts
of the world (China).

ISUP
ISDN User Part (ISUP) supports basic telephone call connect/disconnect between end
offices. Used primarily in North America, ISUP was derived from TUP, but supports
ISDN and intelligent networking functions. ISUP also links the cellular and PCS
network to the PSTN.
BISUP (Broadband ISUP) will gradually replace ISUP as ATM is deployed.

BISUP
Broadband ISDN User Part (BISUP) is an ATM protocol intended to support services
such as high-definition television (HDTV), multilingual TV, voice and image storage
and retrieval, video conferencing, high-speed LANs and multimedia.

4.1. SS7 Signal Units

Signaling information is passed over the signaling links in messages, which are called
signal units. Signal units are continuously transmitted in both directions on any link
that is in service. (See Figure 15) SS7 uses three different types of signal units:
Message Signal Units (MSUs)
Link Status Signal Units (LSSUs)
Fill-In Signal Units (FISUs)

A signaling point sends FISUs over the link when it does not have any MSUs or
LSSUs to transmit.

4.2. Signal Unit Structure

All types of signal units (MSU, LSSU, FISU) have a set of common fields which are
used by MTP Level 2. Field types include the following:
FlagDelimiter in a signal unit which marks the end of one signal unit and the
beginning of another. All signal units begin with a distinct 8-bit pattern (0111 1110).
ChecksumAn 8-bit sum calculated from the transmitted message by the
transmitting signaling point and inserted in the message. It is recalculated by the
receiving signaling point, and if corrupted, a retransmission is requested.
Length IndicatorThe number of octets between itself and the checksum. Checks
the integrity of the signal unit and discriminates between different types of signal
units. The default values are: FISU=0, LSSU=1 or 2, MSU>2.
BSN/BIB FSN/FIBOctets that hold the backward sequence number (BSN) and
backward indicator bit (BIB); the forward sequence number (FSN) and the forward
indicator bit (FIB).

Figure 15 SS7 Signal Unit Types

4.2.1. Signal Unit Flow Control

The BSN/BIB and FSN/FIB fields in a signal unit (SU) confirm receipt of SUs and
ensure that they are received in the order in which they were transmitted. These fields
also provide flow control.
MSUs and LSSUs are assigned a sequence number when transmitted. That sequence
number is placed in the FSN field of the outgoing signal unit, which is stored by the
transmitting signaling point until it is acknowledged by the receiving signaling point.
Signaling points acknowledge receipt of SUs by putting the sequence number of the
last correctly received (and in sequence) SU in the backward sequence number (BSN)
of every SU they transmit.

SU Error Detection
The check bit field and the sequence number of the signal unit are used to detect
errors. Seven-bit sequence numbering is used. The forward sequence number (FSN) is
incremented by one after every transmission. The backward sequence number (BSN)
is used to acknowledge received signal units.
The transmitting signal point keeps all transmitted signal units in a buffer until
acknowledged. Once the BSN is received, all acknowledged signal units are dropped
from the buffer. Unacknowledged signal units stay in the buffer until a timer expires,
causing a link failure indication to be sent to Level 3. The link is then tested and
aligned.

4.3. Types of Signal Units

4.3.1. Message Signal Units
MSUs are the workhorses of the SS7 network. All signaling associated with call setup
and teardown, database query and response, and SS7 management requires the use of
MSUs. (See Figure 16 )
MSUs provide MTP protocol fields, service indicator octet (SIO) and service
information field (SIF). The SIO identifies the type of protocol (ISUP, TCAP) and
standard (ITU-TS, ANSI). The SIF transfers control information and routing label.

Figure 16 MSU Format

SIO Structure
The functionality of the MSU lies in the contents of the service indicator octet (SIO)
and the service information fields (SIF). The SIO is an 8-bit field that contains three
types of information:

Four bits to indicate the type of information contained in the service

information field (referred to as the service indicator). (Refer to Table 3)
Two bits to indicate whether the message is for use in a national or
international network.
Two bits to identify the message priority. Not used to control the order of
transmittal, but used when network is congested to determine if a message can
be discarded. Value is from 03, with 3 the highest priority.
Value
0
1
2
3

Function
Signaling Network Management
Signaling Network Testing and Maintenance
Signaling Connection Control Part (SCCP)
ISDN User Part (ISUP)
Table 3 : SIO Service Indicator Bits

SIF Structure
The service information field (SIF) provides the first piece of information necessary
for routing and decoding the message. The SIF transfers control information and the
routing label used by Level 3.
The service information field (SIF) provides the first piece of information necessary
for routing and decoding the message. The SIF transfers control information and the
routing label used by Level 3. The routing label consists of the destination point code
(DPC), originating point code (OPC) and signaling link selection (SLS) fields.
The SIF can contain up to 272 octets and is used by network management, ISUP,
TCAP and MAP. (See Figure 17).

Figure 17 MSU SIF Structure

4.3.2. Link Status Signal Unit

LSSUs communicate information about the signaling link between the nodes on either
end of the link. This information is contained in the status field of the signal unit. (See
Figure 18) They signal the initiation of link alignment, quality of received traffic, and
status of processors at either end of the link.
LSSUs do not require any addressing information because they are only sent between
signaling points.

Figure 18 LSSU Format

4.3.3. Fill-in Signal Unit

FISUs do not carry any information; they simply occupy the link when there are no
LSSUs or MSUs. FISUs support the monitoring of link traffic because they undergo
error checking. They can also be used to acknowledge the receipt of messages using
backward sequence number (BSN) and backward indicator bit (BIB). (See Figure 19)

Figure 19 FISU Format

Link Alignment
When all signal units are received in sequence without ones-density violations and
with the proper number of octets, the link is considered to be in alignment. The link is
considered in error if the signal unit is not in 8-bit multiples or if the SIF exceeds the
maximum 272-octet capacity.
The system uses a counter called the Signal Unit Error Rate Monitor (SUERM). Each
link keeps its own unique counter. When more than 64 errors occur, the link is taken
out of service, tested, and realigned by Level 3.

5. ISUP and TCAP

This section focuses on the ISUP and TCAP protocols and their functions within the
Public Switched Telephone Network (PSTN).

5.1. Basic ISUP Signaling

ISDN User Part (ISUP) defines the protocol and procedures used to set up, manage
and release trunk circuits that carry voice and data calls over the PSTN. ISUP is used
for both ISDN and non-ISDN calls. Calls that terminate within the same switch do not
use ISUP signaling. (See Figure 20)

Figure 20 Basic ISUP Signaling

In some parts of the world, such as China, the Telephone User Part (TUP) protocol
supports basic call processing. TUP handles analog circuits only; digital circuits and
data transmission capabilities are supported by the Data User Part protocol.

5.2. ISUP Message Format

ISUP information is carried in the service information field (SIF) of an MSU. The SIF
contains the routing label followed by a 14-bit (ANSI) or 12-bit (ITU) circuit
identification code (CIC). The CIC indicates the trunk circuit reserved by the
originating switch to carry the call.
The CIC is followed by the message type field IAM, ACM, ANM, REL, RLC
which defines the contents of the remainder of the message.
Each ISUP message contains a mandatory part that includes fixed-length parameters.
Sometimes the mandatory fixed part is comprised only of the message type field.
The mandatory fixed part may be followed by a mandatory variable part and/or an
optional part. The optional part contains parameters which are identified by a oneoctet parameter code followed by a length indicator (octets to follow) field.

Figure 21 ISUP Message Format

5.3. ISUP Message Types

IAM
An initial address message (IAM) is sent in the forward direction by each switch in
the circuit between the calling party and the destination switch of the called party. An
IAM contains the called party number in the mandatory variable part and may contain
the calling party name and number in the optional part.

ACM
An address complete message (ACM) is sent in the backward direction to indicate
that the remote end of a trunk circuit has been reserved. The originating switch
responds to an ACM message by connecting the calling partys line to the trunk to
complete the voice circuit from the calling party to the called party. The calling party
hears ringing on the voice trunk.

REL
A release message (REL) is sent in either direction indicating that the circuit is being
released due to a specified cause indicator. An REL is sent when either calling or
called party hangs up the call (cause = 16). An REL is also sent back to the calling
party if the called party is busy (cause = 17).

RLC
A release complete message (RLC) is sent in the opposite direction of an REL to
acknowledge the release of the remote end of a trunk circuit and to end the billing
cycle, if appropriate.

5.4. ISUP Call Sequence

5.4.1. Call Initiated
See Figure 22 and Figure 23 as you review the following messaging sequence:
1. Calling party goes off hook on an originating switch (SSP) and dials the
directory number of the called party.
1a. Originating SSP transmits ISUP IAM to reserve an idle trunk circuit. The IAM
includes OPC, DPC, CIC, dialed digits, CPID, and calling party name (Caller
ID option).
1b. IAM is routed via home STP of originating SSP.
2. Destination switch (SSP) checks the dialed number against its routing table
and confirms that the called partys line is available for ringing.
2a. Destination SSP transmits ACM to the originating SSP via its home STP to
confirm that the remote end of the trunk circuit has been reserved.

2b. The STP routes the ACM to the originating SSP which connects the calling
partys line to the trunk to complete the voice circuit. The calling party hears
ring back tone.

Figure 22 ISUP Call Initiation (1)

Figure 23 ISUP Call Initiation (2)

5.4.2. ISUP Call Answered

See Figure 24 during reviewing the following messaging sequence:
3a. Called party goes off-hook. Destination switch terminates ringing tone and
transmits an ISUP answer message (ANM) to the originating switch via its
home STP.
3b. STP routes ANM to originating switch which verifies that the calling party is
connected to the reserved trunk. Billing is initiated.

Figure 24 ISUP Call Answered

5.4.3. ISUP Call Released

See Figure 25 and Figure 26 as you review the following messaging sequence:
4a./b.If the calling party hangs up first, the originating switch sends an ISUP
release message (REL) to release the trunk between the two switches. If the
called party releases first, the destination switch sends an REL message to the
originating switch to release the circuit.
5a. When the destination switch receives the REL, it disconnects and idles the
trunk, and transmits an ISUP release complete message (RLC) to the
originating switch to acknowledge the release of the remote end of the circuit.

5b. When the originating switch receives or sends an RLC, the billing cycle ends
and the trunk state is returned to idle.

Figure 25 ISUP Call Release (1)

Figure 26 ISUP Call Release (2)

5.5. TCAP Functions

Transactional Capabilities Application Part (TCAP) enables deployment of advanced
intelligent network (AIN) services by supporting information exchange between
signaling points using SCCP. TCAP messages are contained within the SCCP portion
of a Message Signal Unit (MSU). TCAP messages consist of a transaction portion and
a component portion.
An SSP uses TCAP to query an SCP to find out the routing number for an 800, 888 or
900 number. Calling cards are validated using TCAP query and response messages.
Mobile subscribers roaming into a new mobile switching center (MSC) area cause the
integrated Visitor Location Register (VLR) to request a service profile from the
subscribers Home Location Register (HLR) using the Mobile Application Part (MAP)
information carried in TCAP messages.

5.5.1. TCAP Transaction Portion

The transaction portion contains the package type identifier. There are several
package types:
UnidirectionalTransfers component(s) in one direction only (no reply
expected).
Query with PermissionInitiates a TCAP transaction. The destination node may
not end the transaction.
ResponseEnds the TCAP transaction. A response to a 1-800 query with
permission may contain the routing number(s) associated with the 800
number.
Conversation with PermissionContinues a TCAP transaction. The destination
node may not end the transaction.
Abort Terminates the transaction due to an abnormal situation.
The transaction portion also contains the Originating Transaction ID and Responding
Transaction ID which associate the TCAP transaction with a specific application at
the originating and destination signaling points.

5.5.2. TCAP Component Portion

The TCAP component portion contains several possible kinds of components:
Invoke (Last)Invokes an operation. For example, a Query with Permission
transaction may include an Invoke (Last) component to request SCP

translation of a dialed 800 number. The component is the last component in

the query.
Invoke (Not Last)Similar to the Invoke (Last) component except that the
component is followed by one or more components.
Return Result (Last)Returns the result of an invoked operation. The
component is the last component in the response.
Return Result (Not Last)Similar to the Return Result (Last) component except
that the component is followed by one or more components.
Return ErrorReports the unsuccessful completion of an invoked operation.
RejectIndicates that an incorrect package type or component was received.

5.5.3. Sample TCAP Database Query

This sample query describes how a dialed 800 number is processed using TCAP. See
Figure 27 as you review the messaging sequence described below.
1.

A subscriber goes off-hook and dials an 800 number. The end office switch
(SSP) parses the digit string and sends an 800 query message to either of its
STPs over its A-link.

2.

The STP recognizes the 800 query and routes it to an appropriate database via
an SCP.

3.

The SCP receives the query, extracts the passed information and retrieves a
real telephone number to which the call should be routed.

4.

The SCP sends a response message with the information necessary to process
the call to the originating SSP via an STP and an A-link.

5.

The STP receives the response and routes it to the SSP.

6.

The SSP receives the response and uses the information to route the call. It
generates an IAM message and proceeds with ISUP call setup.

Figure 27Sample TCAP 800 Number Query