MTP

The MTP provides the means for reliable transport and delivery of UP information across the
SS7 network (see Figure 8-1). It also has the ability to react to system and network failures….
that
affect the information from the UPs ….and to take the necessary action to ensure that the
information is safely conveyed.

MTP is divided into three functional levels

MTP level 1 - the signaling data link functions

MTP level 2 - the signaling link functions
MTP level 3 - the signaling network functions

Level 1 Physical Level

Access the link
64 kb/s bit rate

Level 2 Link Level

Reliable transmission
Alignment
Fault detection
Correction by retransmission

Level 3 Network Level

Message handling
Network management

SCCP
A software packet called Signaling Connection Control Part (SCCP) has been introduced to meet
future demands. SCCP provides additional functions for MTP to cater for both connection
oriented signaling ,transfer circuit-related signaling information, and connectionless signaling to
transfer non-circuit related signaling messages via a SS7 network.
CO Connection-Oriented
CL Connectionless
BSSAP Base Station System Application Part
BTAP BSC/TRC Application Part
CAP CAMEL Application Part
ISUP ISDN User Part
MAP Mobile Application Part
TCAP Transaction Capabilities Application Part
SCCP connection oriented (CO) control - which handles establishment, data transfer and
supervision of logical signaling connections.

SCCP connectionless (CL) control - which handles the connectionless transfer of data units.

SCCP management - which handles the status information of the SCCP network. This
information, regarding the availability of other SPs and users of the network, is used to update
the message routing tables.

SCCP routing - which handles the routing of SCCP messages within the SS7 network. This
may include the translation of a global title to get a specific network address. The SCCP routing
function also provides message distribution based on the SCCP SubSystem Number (SSN).
The SSN identifies either an SCCP user or the SCCP management sub-function.

The called and calling party addresses contain the information necessary for the SCCP to
determine an originating and a destination node. In the case of CO procedures, the addresses
are the originating and destination points of the signaling connection, while in the case of CL
procedures the addresses are the originating and destination points of the message. When
transferring CO or CL messages, two basic addresses are distinguished by SCCP routing:

1. Global Title (GT) A GT is an address that does not explicitly contain information that would
allow routing in the signaling network. This means that the SCCP translation function is
required. The system in this case performs routing on GT (described further in this chapter).

2. DPC + SSN A DPC and an SubSystem Number (SSN) allows direct routing by the SCCP and
MTP. That is, the translation function of the SCCP is not required. In this case routing on SSN is
performed

In the first case, the called party address may contain:

SSN only - which indicates that the receiving SCCP is the termination point of the message.
The SSN is used to determine the local subsystem.

GT only - which indicates that translation is required. The translation results in a new DPC for
routing the message and possibly a new SSN or GT, or both in the called party address.

SSN and GT - An address indicator is used to determine whether the SSN or the GT should be
used for routing.

ROUTING ON GT

For addressing purposes SCCP may use the Global Title (and maybe SSN). This is the case in
the Switching System of GSM.
 TCAP

Transaction Capabilities Application Part (TCAP)

Intermediate Services Part (ISP) (not defined)
As currently specified, TCAP provides services based on connectionless network services. TC
provides the means to establish non-circuit related communication between two nodes
in the signaling network and to exchange messages via a dialogue.

Common functions like sending/receiving, coding/decoding, packing/unpacking are withdrawn

from each application and included in TCAP. TCAP has a buffer and handles the multiplexing
and timing of the information received from a TC user. It receives incoming messages from
SCCP, unpacks and delivers them and delivers to the correct TC user. TCAP makes it possible
for TC users to have several dialogues running concurrently. It can be seen as a secretary to the
manager e.g. MAP.

MOBILE APPLICATION PART (MAP)

INTRODUCTION
The Mobile Application Part (MAP) protocol is designed to support GSM signaling requirements
in the Switching System part of the GSM network. MAP functions are implemented in the MSC,
VLR, HLR, AUC, FNR and EIR as well as in the SMS and MIN nodes. The protocol is used on
all interfaces between the nodes with the exception of the B interface only (MSC—VLR) which
is implemented internally in software in Ericsson implementation of the GSM system. MAP
protocols are used, for example, in case of:
location registration/cancellation
handling/management/retrieval of subscriber services
inter-MSC handover
transfer of security/authentication data
MAP uses TCAP to utilize dialog and component handling facilities for peer-to-peer
communication between different nodes and NSP (Network Service Part, i.e. MTP and SCCP)
for transmission of information and messages in SS7 network. MAP uses SCCP connectionless
mode only, both basic and sequenced classes. Different versions like map v1 map v2

This helps to maintain good interworking between different networks. This is important as one
network can utilize the equipment from different manufacturers and must also communicate with
other networks when subscribers are roaming internationally.

in the GMSC during the HLR interrogation at call setup, software route parameters are used to
choose a protocol version.

in the MSC/VLR when a new subscriber is being registered, an IMSI series analysis result
decides what MAP version is used.
in the HLR when data is sent to a serving MSC/VLR, the address of the VLR is analyzed to
select MAP version.
In cases of doubt the newest MAP version is used and a fallback procedure is applied when the
other node does not support this version.

BASE STATION SYSTEM APPLICATION PART

The BSSAP protocol has been specially developed for the Ainterface. It not only supports
messages between the MSC and BSS, but also messages between the MSC and MS. BSSAP uses
one signaling connection for each active MS, having one or more active transactions for the
transfer of layer 3 messages. BSSAP is split into two subparts (see Figure 10-2):

Direct Transfer Application Part (DTAP) - which is used to send Connection Management
(CM) and Mobility Management (MM) messages between the MSC and MS. These messages
are sent transparently through the BSS in connection oriented mode. The CM and MM protocols
are described in chapter 5 “Um interface”.

Base Station System Management Application Part

(BSSMAP) - which is used to send messages between the MSC and BSC that are related to:
– the MS (handover control, resource management)
– a cell within the BSS
– the whole BSS

BSSMAP uses both the connection oriented (CO) and the connectionless signaling (CL) services
of SCCP. Messages to support dedicated procedures for example handover procedures,
assignment procedures or initial MS messages; are sent using CO mode. Messages used to
support global procedures (messages that concern a complete cell or the complete BSS) are sent
using CL mode. Examples of messages sent in CL mode are:
– block (a trunk)
– reset (restart)
– paging

ISDN User Part

Network MTP Level 3 + SCCP

Data link MTP Level 2

Physical MTP Level 1

 v

 t

 e
The ISDN (Integrated Services Digital Network) User Part or ISUP is part of the Signaling System
No. 7 (SS7) which is used to set up telephone calls in the public switched telephone
network (PSTN). It is specified by the ITU-T as part of the Q.76x series. [1]

When a telephone call is set up from one subscriber to another, several telephone exchanges could
be involved, possibly across international boundaries. To allow a call to be set up correctly, where
ISUP is supported, a switch will signal call-related information likecalled party number to the
next switch in the network using ISUP messages.

Message types
An ISUP message contains a fixed header containing the circuit identification code and the ISUP message type, followed by a mandatory
fixed-length parameter part, a mandatory variable-length parameter part, and an optional parameter part that are dependent on the type of
message being sent. ISUP messages can be sent using the services of the Message Transfer Part, or, less often, the Signalling Connection
Control Part. These messages are transmitted in various stages of call setup and release. The most common messages are: [5]

 Initial address message (IAM) — First message sent to inform the partner switch that a call has to be established on the CIC contained
in the message. Contains the called number, type of service (speech or data) and optional parameters.
 Subsequent address message (SAM) — For networks that support overlap dialing procedures, and then in the case that the IAM did
not contain the full called number, one or more SAMs follow containing additional digits. This message is not supported by networks
that only support en bloc dialing procedures.
 Address complete message (ACM) — Message returned from the terminating switch when the subscriber is reached and the phone
starts ringing, or when the call traverses an interworking point and the intermediate trunk is seized.
 Call progress (CPG) — Contains additional information about the progress of a call. Normally sent after the ACM when the status of the
call changes from that reported in the ACM.
 Answer message (ANM) — Sent when the subscriber picks up the phone, a resource is connected or answer supervision is returned
by an interworking point. Normally charging starts at this moment. It is required that the call be cut through in both directions by this
point.
 Connect (CON) — Sent when the call is answered by an automatic terminal. This message replaces the ACM, CPG and ANM for calls
that are answered by automatic terminals.
 Release (REL) — Sent to clear the call when a subscriber goes on hook. This is also sent (in direct response to an IAM) if the
terminating switch determines that the call cannot be completed. In either case, the terminating switch provides a cause value in the
message to explain the reason for the release, e.g., "User busy".
 Release complete (RLC) — Acknowledgment of the release – the circuit is idle afterward and can be used again