Cisco Itp in Eservglobal In: Sigtran and Itp Overview

Cisco ITP in eServGlobal IN
Sigtran and ITP Overview
Belgium Support and PS
Dennis Hagarty
Implementation Practice Lead
16 January 2006
2003 Cisco Systems 2006 eServGlobal Ltd
Agenda
Quick introduction to SS7, Sigtran, ITP, IOS
Introduction to Sigtran
ITP Model overview with a view of the innards
Functions of an ITP (especially as a Signalling Gateway)
Traffic modes and load distribution
GTT
IP Network Design to support the eSG IN
Time permitting
Reliance Designs (time permitting)
SCCP and SUA
Example traffic flows
Aligning ITP and hss configurations
SIGTRANandITPOverview|2|2003
The Trainer
Dennis Hagarty, Implementation Lead, eServGlobal
dennis.hagarty@eservglobal.com
Working with ITPs and Sigtran for about four years
Competed mobile, pre-paid, convergent billing, wireline IN

projects in Europe and Asia-Pacific, on both CDMA and GSM
More of an IT and less of a telecoms background
Tell me if my English is not easy to understand or I go too fast!
Delivered a lot of ITP training, last one was 5 days with Reliance.
Lets go!
SS7, Sigtran and ITP Basics
Quick Introduction to SS7, Sigtran, ITP, IOS
What is SS7?
What is Sigtran?
What is a signalling gateway?
What is an ITP?
What is IOS?
SS7: What is it?
Data network designed to transport CCS signalling traffic that

manages and facilitate call setup, routing and control.
SS7 was initially designed by the United International
Telecommunications Union (ITU) known than as the CCITT.
The CCITT created multiple books or standards.
First came the Yellow Book (1980)
Red Book (1984)
Blue Book (1988)
White Book (1992)
ANSI standard for US was developed from the Blue Book

The Bellcore version is based on the ANSI standard and is called
GR-246-CORE: Bell Communications Research Specifications of
SS7.
China, Japan (and others!) have their own flavors
SS7: What is it? SS7 and OSI Protocol Stack
Telnet, FTP,
POP3
TCP/UDP/SCTP
IP
Ethernet
Twisted Pair
SS7: What is it? Signalling Points and Point Codes
Signalling Points
SSP: Service Switching Point sends signalling messages to other SSPs

to setup, manage, and release voice circuits required to complete a
call (think end node)
SEP: Signalling End Point SS7 end node that performs similar
functionality to the SSP in an IP telephony network (think node)
STP: Signal Transfer Point is a signalling point that is capable of
routing control messages; that is, a message received on one
signalling link is transferred to another link. (think router)
SCP: Service Control Point contains centralized network databases for
providing enhanced services. An SCP accepts queries from an SP and
returns the requested information to the originator of the query (think
database such as DNS).
Signalling points have Point Codes (think IP addresses)
SS7 What is it? Transport Layers
Three Transport Layers
MTP1: the signalling data link layer, is concerned with the physical and
electrical characteristics of the signalling links.
MTP2: is a data link control protocol that provides for the reliable
sequenced delivery of data across a signalling data link.
MTP3: the signalling network layer, provides for routing data across
multiple STPs from source point to control destination.
Signalling points have Point Codes
Signalling Points are connected together by Linksets
User and Application Layers
SS7: What is it? Point Codes
A SEP on an SS7 network has a Point Code (node address)
There are two variants of point code:
ITU: Value up to 7.255.7 (14 bits)
ANSI: Varies, but up to 255.255.255 (24 bits)
Three types of point codes:
Originating Point Code (OPC) is point code of the source of the original
message
Destination Point Code (DPC) is the point code of the desired recipient
of the message
Adjacent Point Code (APC) is the point code for the next hop of the
signalling message
SS7: What is it? Link architecture

eSG
UAS Platform
Reliance GSM Pre-Paid
SS7: What is it? Application Parts
Application Layers
MAP: Mobile Application Part (MAP), provides the signalling functions

necessary for voice and non-voice applications in a mobile network.
ISUP: ISDN User Part (ISUP) provides the signalling needed for basic
ISDN circuit-mode bearer services as well as ISDN supplementary
services. ISUP is the protocol that supports ISDN in the PSTN.
TCAP: Transaction Capabilities Application Part (TCAP), provides the
mechanisms for transaction-oriented and is often used for database
access by the SS7 switches.
INAP: Intelligent Network Application Part
Signalling Connection Control Part (SCCP) is used as the

transport layer for TCAP-based services
SS7 What is it? SCCP and GTT/GTA
Signalling Connection Control Part (SCCP) provides

connectionless and connection-oriented network services and
global title translation (GTT) capabilities above MTP3
SCCP is used as the transport layer for TCAP-based services.
Global Titles are roughly equivalent to Names in SS7 and are
defined at the SCCP layer.
A global title address (GTA) can be translated by (e.g.) an STP
into a destination point code and subsystem number.
A subsystem number uniquely identifies an application at the
destination signalling point (think TCP port number)
GTT adds the ability to perform incremental routing and frees the
originating signalling point of having to know every possible
destination.
Sigtran: What is it?
Set of standards, proposed standards, and drafts
RFC 2719 Framework Architecture for Signalling Transport
RFC 2960 Stream Control Transmission Protocol (& 3286)
IUA = RFC 3057 - ISDN Q.921-User Adaptation Layer along with:

<draft-ietf-sigtran-iua-imp-guide-02.txt>
M2UA = RFC 3331 SS7 MTP2 User Adaptation Layer
SUA = SS7 SCCP-User Adaptation Layer

RFC 3868 SCCP User Adaptation Layer
M2PA = MTP2-User Peer-to-Peer Adaptation Layer
RFC 4165 MTP2 User Peer-to-Peer Adaptation Layer
LAPV5/V5.2 Adaptation Layer
<draft-ietf-sigtran-v5ua-04.txt >
Implements SS7 using the IP protocol as the underlying layers

Designed around a new IP protocol (mix of UDP and TCP) to meet
the requirements demanded by SS7 signalling:
reliability
dependability
speed
This is based on SCTP (Stream Control Transmission Protocol)
The following are probably the most interest to us:
M2PA = to run MTP3 SS7 linksets over IP
M3UA = to run non-SCCP traffic (ISUP) over IP (PGW2200, V.SSP)
SUA = to run SCCP traffic over IP (UAS, VPU)
Together known as SS7oIP or SIGnaling TRANsport (SIGTRAN)
Signalling Gateway: What is it?

SUA SG
INAP
TCAP
SCCP
SS7
MTP3
MTP2
MTP1
SSP
GTT
SCCP
MTP3
MTP2
MTP1
N
I
F
INAP
SUA
TCAP
SUA
SCTP
IP
Network
IP
SS7
SCTP/IP
SCTP
IP
IP
ASP
INAP is still carried by TCAP at the top of the stack
SCCP is translated into its very close cousin, SUA
IP, SCTP replace MTP layers
Applications remain the same, but the connectivity changes
ITP: What is it?
Cisco multifunction router (eg Cisco 2600)
A special purpose computer, with lots of memory but no disks
Real-time operating system (IOS)
Port (Interface) cards (Ethernet, E1, ATM, etc)
Talks TDM SS7 as well as SS7oIP
ITP: What is it?
Cisco multifunction router a box with CPU, memory, flash
Operating system (IOS) Ciscos Internet Operating System
Port (Interface) cards
Hardware is all traditional Cisco components
Software built into IOS makes the ITP system
IOS: What is it?
Real-time operating system for Cisco Multi-function routers
Common across just about all of their platforms
There are a vast number of versions and releases, depending on

the task (IP router, SS7 router, Backbone router, etc)
White paper The ABCs of Cisco IOS Software Release
The configuration and version of IOS makes it an ITP and defines
what flavour of ITP it will be, and what functions it will perform.
Sigtran
Introduction to Sigtran
What is it?
What must it do?
Reliable, fast, robust
How does it do it?
A set of IETF Standards to run signalling over IP networks
SCTP and IP
Why are we bothered with this stuff?
What does this mean to us?
Why not use DK cards?
Set of standards, proposed standards, and drafts
RFC 2719 Framework Architecture for Signalling Transport
RFC 2960 Stream Control Transmission Protocol (& 3286)
IUA = RFC 3057 - ISDN Q.921-User Adaptation Layer along with:

<draft-ietf-sigtran-iua-imp-guide-02.txt>
SUA = SS7 SCCP-User Adaptation Layer

RFC 3868 SCCP User Adaptation Layer
M2PA = MTP2-User Peer-to-Peer Adaptation Layer
RFC 4165 MTP2 User Peer-to-Peer Adaptation Layer
LAPV5/V5.2 Adaptation Layer
<draft-ietf-sigtran-v5ua-04.txt >
Sigtran: Requirements for Signalling Network
Not more than one in 1010 of all message signal units must contain
an error that is undetected by the MTP.
Not more than one in 107 messages will be lost due to failure in
the MTP.
The availability of any signalling communication path between two
SEPs has to be at least 0.99998 corresponding to a downtime of
at most 10 minutes/year.
Not more than one in 1010 messages will be delivered out-ofsequence to the User Parts due to failure in the MTP. This value
also includes duplication of messages.
In addition there are requirements on message transfer times in
STPs, which under normal conditions are supposed to be less than
100 mSec, and implicit requirements on limits for the outgoing
queuing delays.
Message length (payload accepted from SS7 user parts)
272 bytes for narrowband SS7, 4091 bytes for broadband SS7
Sigtran: How is this achieved?
SCTP: Stream Control Transmission Protocol
Reliable datagrams and connection oriented called an association
Concept of streams
An SCTP association provides multiple uni-directional streams
Message loss on one stream does not delay messages using other
streams, no head of line blocking.
Multihoming: an SCTP endpoint can have multiple IP addresses.
Timer based retransmission, highly configurable
Primary and Standby addresses, monitored using heartbeat
Runs on top of the potentially unreliable IP
More flexible than TCP: byte oriented, strictly ordered, single homed.
UDP is connectionless and uses unreliable datagrams.
Sigtran: Used in eServGlobal applications
M2PA = to run SS7 linksets over IP
M3UA = to run non-SCCP traffic (ISUP) over IP (PGW2200, UCA-I)
Sigtran - Reliability
Resilience Hierarchy
MTP
SCTP Multi-Homing
IP Routing
IP Routing
Level 3:
If SCTP/IP can not correct the issue, MTP3 is notified to initiate standard MTP3
rerouting procedures
Level 2:
When SCTP Multi-homing detects unresponsiveness in the current IP path, it
changes the IP path used for the session by changing the source and/or
destination IP address of the session. During this process, the SCTP session
remains active and MTP3 is unaware of the path change.
Level 1:
IP routing protocols can detect path outages and re-route (e.g. HSRP, etc).
Sigtran: M2PA
M2PA is a peer-to-peer protocol that provides a link between remotely

located MTP3 instances it replaces the MTP2 layer beneath MTP3. The
user of M2PA is MTP3 at both ends of the connection.
M2PA provides a means for peer MTP3 layers in SGs to communicate
directly. In essence, it extends the reach of SS7 over the IP network.
M2PA is a
way to
bridge
MTP3 over
IP
Peer to Peer M2PA

SSP
SSP
ISUP/SCCP/TCAP/MAP
MTP3
MTP3
M2PA
M2PA
SCTP
SCTP
IP
IP
M2PA through an SG Peer
MTP3 MSU
SEP
FISU
SS7
TDM
M2PA SG
MTP3
MSU
SG
M2PA
IP
SCTP
/IP
M2PA
SP
SEP/SG
Sigtran: M3UA
M3UA operates as a client-server to provide an upper layer SS7 with

protocol remote access to the lower layers.
M3UA provides a means by which an MTP3 service may be provided on an
UAS (eg, terminating the ISUP connection on the UAS) - essentially
extending the reach of SS7 into the IP network.
M3UA is for
USERS of
MTP3!!
Signalling Gateway M3UA

V.SSP
SSP
ISUP
Hughes
MTP3
M3UA
Legacy
M3UA
and
SCTP
MTP2
SCTP
MTP1
IP
Cisco ITP
Sun IP
M3UA via a Signalling Gateway
MTP3 MSU
MTP3
MSU
User
FISU
M3UA SG
MSU M3UA SCTP

ISUP
/IP
M3UA
SEP
ISUP
SEP
SS7
TDM
SG
IP
SEP
Sigtran: SUA
SUA provides a means by which an Application part (such as TCAP) on an

IP SCP may be reached via an SG.
The IP SCPs do not have local MTP3 instances, and so do not require their
own SS7 point codes (MTP3, and the point code, can reside on the SG).
SUA is for
USERS of
SCCP!!
Signalling Gateway - SUA

UAS
MSC
TCAP Application Data
GTT
SCCP
SUA
MTP3
Legacy
Hughes
SUA
and
SCTP
MTP2
SCTP
MTP1
IP
Cisco ITP
Sun IP
SUA via a Signalling Gateway
MTP3 MSU
SCCP
TCAP
SCCP
User
SEP
FISU
SS7
TDM
SUA SG
SCCP
User
SG
SUA
IP
SCTP
/IP
SUA
SEP
SG
ITP Protocol Architecture
Cisco IOS
GTT
SCCP
SUA
MTP3 / MTP3b
M3UA
M2PA
SSCF-NNI
MTP2
SCTP
SCCOP
AAL5
MTP1
IP
M3UA / SUA Advantages and Disadvantages

M3UA
Advantages
SUA
Advantages
ISUP, TUP, SCCP access
SG performs standard GTT
Disadvantages
MTP3 to M3UA mapping can be

more CPU intensive than MTP3
routing
NIF is implementation dependent
(undocumented) and could make
interoperability challenging
Designed for IP service end nodes
that do not perform STP MTP3
function
Simple for SCCP access only

IP service end node does not need
to implement a SS7 layer 3
adaptation routing protocol
Disadvantages
No ability to participate in ISUP

flows
GTT is adapted within SUA protocol
which is still being discussed in the
standards group
Sigtran: Used in eServGlobal applications
M2PA = to run SS7 linksets over IP
M3UA = to run non-SCCP traffic (ISUP) over IP (PGW2200, UCA-I)
This is too complicated!
Whats wrong with SS7 cards in the UAS?
Whats better with the ITP and Sigtran?
Traditional IN Protocol Architecture

SCP
MSC
SCCP
MTP3
SCCP
SINAP, OpenSS7
DataKinetics, etc
MTP3
MTP2
MTP2
MTP1
MTP1
eServGlobal Protocol Architecture

UAS
MSC
SCCP
SCCP
GTT
SUA
MTP3 / MTP3b
M3UA
MTP3
SSCF-NNI
MTP2
M2PA
MTP2
SCTP
SCCOP
MTP1
MTP1
Hughes
xUA
and
SCTP
AAL5
IP
Cisco ITP
Sun IP
With This Knowledge, Were Off To Look At
The ITP Model Range
Cisco ITP Platforms
Dual
Power /
Dual
Processor
265x
Low-End
7204/6
VXR
Low Midrange
7301
Mid
Range
7507/13
High-End
Dual ext
Power
Single
Processor
Number of
ATM HSL
Links
Max No.
of C7
Links
No. of
T1/E1
ports
4
N/A
(CPU
Limit)
N/A
24
48
48
80/160
800
176
Dual Power
Single
Processor
Dual Power
Single
Processor
Dual Power
Dual
Processor
SUA &
M2PA MSU
per Sec.
900
2,500
3,000
6,000
6,000
12,000
14,000
60,000
ITP Performance
2651
7200
7300*
7500
M2PA MSU/Sec
2,500
6,000
12,000
60,000
M3UA MSU/Sec
1,200
6,000
12,000
20,000
SUA MSU/Sec
900
3,000
6,000
15,000
SIM Authentication / Sec
N/A
1,800
3,600
1,800
SIM Authentication plus Auth/Sec
N/A
360
720
360
1,000
10,000
10,000
10,000
150,000
500,000
500,000
500,000
1,000
10,000
10,000
10,000
MTP2 Links per VIP4 / VIP6
N/A
N/A
N/A
60 / 80
MTP2 MSU per Second per VIP4 / VIP6

(IN / OUT)
N/A
N/A
N/A
Maximum Routing Table Entries

Maximum GTT Entries
Maximum M3UA/SUA Routing Keys
* = 7300 or 7200 with NPE-G1 processor

N.B. 7500 M3UA and SUA to improve by 30-50% with SUA offload.
VIP4: 4K / 4K
VIP6: 6k / 6K
ITP Platforms: 2651XM
2651XM
One NM
Two WIC cards
2 Fast Ethernet
40 K PPS
64MB/128MB DRAM
16MB/48MB Flash
External redundant power
Two x Dual-Port Multiflex

E1 cards
VWIC-2MFT-E1
2651 with 2691
ITP Platforms: 7200

7204 with various cards
7204/7206 VXR
Four slots in 7204
Six slots in 7206
Up to 4/6 FE (TX) available
400 K PPS
Dual power and NEBS
NPE-400 processor
PA-MCX-8TE1 Port Cards
I/O Controller with 2 FE
NPE-G1 processor doubles

performance.
ITP Platforms: 7200 NPE-400
CPU Processor
350-MHz RM7000A RISC
4MB L3 cache
128MB/512MB DRAM
64MB/256MB Flash
ECC support
PA-MCX-8TE1-M
Shared with 75xx platform
Comes as 2, 4, or 8 port version
Only support 24 LSL per 7200
NPE-400 Processor
ITP Platforms: 7301
7301
Single Slot for 8 Port E1
One RU form factor
Three FE/GE LAN ports
900 K PPS
ITP Platforms: 7507 and 7513

Route Switch
Processors (RSP)
Versatile Interface
Processors (VIP)
VIP4-80 / VIP6-80
Increase Performance
RSP8 / RSP16
Second RSP for HA (RPR+)
Port and Services
Industry Leading 70+ LAN &

WAN Adaptors To Choose From
Adaptors
Industry leading features

Scalable / high performance
Carrier-class high availability
2 Power Supplies
for Redundancy
PA-MCX-8TE1-M (LSL)
PA-A3-8E1IMA (HSL)
PA-2FE-TX (Ethernet)
ITP Platforms: 7500 VIP Cards
VIPs can take 2 port adapters with either IP or SS7 media cards
Lots of CPU intensive processing is pushed down to the VIP.
SS7 MTP2 Port Adapter and FE PA
PA-MCX-8TE1-M
Supports up to 126 MTP2

signalling links over 8 ports of
T1/E1
Minimum HW Requirements
T1/E1 SS7 Link Port Adapter for

Ciscos IP Transfer Point (ITP)
7507 or 7513: RSP8, RSP16, VIP480, or VIP6-80
7204/7206 VXR NPE 400, or G1
7301
PA-2FE-TX
Two FE Slots per PA
SS7 ATM HSL Port Adapter
PA-A3-8E1IMA
T1/E1 SS7 Link Port Adapter for

Ciscos IP Transfer Point (ITP)
Supports up to 8 ATM AAL5
signalling links over 8 ports of
T1/E1
SSCF and SSCOP run on VIP
Minimum HW Requirements
7507 or 7513: RSP8 or RSP16
7507 or 7513: VIP4-80 or VIP6-80
7301
ITP Standards Compliance
Protocol
Specification
MTP (1, 2, 3)
ITU-T Q.701-Q.709 White 1996 (inter-works with Blue)

ANSI T1.111-1996, China
SCCP
ITU-T Q.711-Q.719 White 1996 (inter-works with Blue)

ANSI T1.112-1996, China
High-speed links
ITU E1: Q.2140, Q.2110, Q.2210, Q.2144

ANSI T1: GR-2878, I.363, I.361
SCTP
IETF RFC 2960: Stream Control Transmission Protocol (SCTP)

IETF RFC 3309: SCTP Checksum Change
M2PA
IETF RFC 4165: Signaling Transport SS7 (Sigtran)

MTP2-User Peer-to-Peer Adaptation
M3UA
IETF RFC3332: Sigtran SS7 MTP3-User Adaptation Layer
SUA
IETF RFC 3868: Sigtran SS7 SCCP-User Adaptation Layer (SUA)
7500 Architecture
Backup RSP
GTT
Primary RSP
SUA
SCCP
GTT
MTP3 Mgmt RSP
M3UA
MTP3MTP3
MTP3
Routing
Routing
SCCPSCC
Mgmt
P
MTP3
RoutingHigh Speed DMA Memory Bus
Shared
Shared DMA Memory

MTP3 / MTP3b Routing
MTP3 / MTP3b Mgmt
g
n
i
a
t
a t in
D po
k
c
he
C
Shared High Speed DMA Memory

VIP
MTP3/SCCP
Forwarding
MTP3 Fast Cache
MTP3/SCCP
Screening
MTP3 Acct / Filter

MTP2
MTP2
SS7 LSL
PA
SS7 LSL
PA
VIP
MTP3/SCCP
Forwarding
MTP3/SCCP
Screening
VIP
MTP3/SCCP
Forwarding
MTP3/SCCP
Screening
SSCF-NNI
M2PA
SSCOP
SCTP
ATM AAL5
IP
SS7 HSL
PA
SS7 HSL
PA
SS7 Data Flow
VIP
Ethernet
PA
SCTP
IP
Ethernet
PAIP PA
Ethernet
PA
Sigtran Data Flow
Ethernet
PA
Why Use ITP in a Network?
No required architecture changes ITP supports pure TDM mode. When

using SS7oIP, routing translations are the same for TDM or IP linksets
Flexibility when adding capacity for new revenue-generating service
deployment (think Excelcom banana and FDA)
Cost next generation signalling transport lowers network capital and
operational costs.
Performance next generation signalling transport increases the
performance to price ratio per rack with a reduced footprint and power
consumption
Network efficiencies next generation signalling transport leverages
investments in both TDM and IP infrastructure
Intelligent Network Gateway allows for integration between TDM and IP
networks
Application layer routing TCAP, MAP and MAP-user based routing allows
for efficient deployment of new services
Manageability IP-based network monitoring and provisioning improve
operational efficiencies
Deployment Options for ITP in eSG IN
Functions of an ITP
What is it?
Does SS7 stuff!
What Functions is it used for?
Traditional STP
Next Generation Signalling Transport
SS7oIP backhaul
SS7 over High Speed Links
QoS over IP infrastructure
Signalling gateway
SMS Offload (MLR = Multi-layer Routing)
RADIUS to MAP Authentication
Why reasons would a carrier use it?
SS7oIP savings over TDM circuits
Signalling Gateway
ITP as an ordinary STP
Linkset
1234
SLC
SMSC
SLC
S5/
0/1
:0
S5/
0/1
:1
2345
C
SL
MSC
/
S5
0:0
0/
4321
ITP
Basic Configuration for STP
SS7 Variant (ANSI, ITU, China)
Point Code
Controllers in various slots
MTP2 encapsulation on the serial

interfaces
Define linkset
Define links in each linkset
Define Routes
Linkset
Low Speed LINK (LSL)
ITP Functions: ITP versus Traditional STP
Legacy STP
Cisco
ITP
ITP Functions: Next Generation Signalling Transport
Traditional STP
Next-Gen Signalling Transport
MTP3
SS7oIP Transport:
Low and High-Speed Links
ANSI, ITU, China, Japan, etc
High Availability:
6 Nines per 7500 Chassis
Guarantee bandwidth or latency for high

priority SS7 or IP traffic
Address Conversion:
Integrating SS7 and IP Routing
Industry Leading QoS:
SIGTRAN M2PA, M3UA, SUA
Single Box Solution
National Variants:
Full GTT, Management, Screening,

Accounting, etc
Traditional SS7 Transport:
SCCP:
Routing, Management, Screening,

Accounting
Variable length GT digit conversion (Ex:

E.164 to E.212)
Multiple Point Codes/Instances

Price / Performance Leader by an order
of magnitude
Efficient Footprint and Power
SMS Offload
ITP Functions: SS7oIP to Supplement the STP Plane

SEP Site
MSC
Classical SS7 Transport Network

STP
STP
STP
STP
AAA for
WLAN
Next Generation
Signalling Transport
SEP Site
SMSC
HLR
or
SCP
SGSN
Softswitch
Links can be:

56/64 Kbits/s
HSL Unchannelised T1/E1
VHSL Sigtran M2PA
Sigtran M3UA/SUA
SGM
ITP Next-Gen Signalling Transport: SS7 over HSL
SCCP
SCCP
GTT
GTT
MTP3 / MTP3b
MTP2
MTP2
MTP3 / MTP3b
MTP2
SSCF-NNI
SCCOP
MTP1
MTP1
T1 or E1
MTP1
AAL5
SS7 Layer
1 and 2
transport
T1 or E1
SS7 layer 2 changes with no layer 3 Changes
ITP Next-Gen Signalling Transport: SS7 over IP
MSC
SS7
Appl
MTP3
MTP2
MTP1
SS7
IP
SS7
SCCP
SCCP
GTT
GTT
MTP3
MTP2
MTP1
M2PA
SCTP
IP
SMSC
ITP
ITP
MTP3
Peer
Transport
M2PA
MTP3
MTP2
MTP2
MTP1
MTP1
SCTP
IP
SS7
Appl
Sigtran and SS7 Packets through an SG
MTP3
MSU
FISU
M2PA SG
MTP3
MSU+
User
FISU
M3UA SG
FISU
SUA SG
SCCP +
User
SEP
SS7
TDM
MTP3
MSU
SCTP
M2PA / IP
M2PA
SP
MSU M3UA
MTP3
User
SCTP
/ IP
M3UA
SEP
MSU
SCCP
User
SCTP
/ IP
SUA
SEP
SG
IP
SUA
SEP
ITP Next-Gen Signalling Transport: SS7 over IP (cont)

MTP2 TDM
M2PA/SCTP
ITP
MSU4
MSU3
SCTP Chunk Bundling Timeout

(0 ~ 10 msec configurable)
MSU2
MSU1
MSU4
MSU3
MSU2
MSU1
IP
Example: Up to 1480 bytes for Ethernet

FISUs will be terminated at ITP
FISU FISU MSU FISU
MSU FISUFISUFISU
MSU
MSU
IP
Available Bandwidth
for Other MSU Transport
0.4 Erlang
QOS in SS7oIP Networks Classify, Queue, Preserve
ITP map MSUs to IP QoS by using any combination of MSU values
Input link set (ex: link set from SMSC)
Service Indicator (ex: ISUP or SCCP)
Destination Point Code (ex: MSU destined to SMSC)
Global Title Address (ex: TT or MSIDN of SMSC)
M3UA/SUA Routing Key
IP
IP Packet Header
TOS
Protocol Type
(DSCP/ IPPrec)
Source
Address
Destination
Address
Source/Destn
Port
Core Router
SS7 / MTP
ITP
Sigtran / IP
IP Core
Network
Classification / Marking By Input Linkset

Link from MSC
T1 / E1
Link from SCP
T1 / E1
Ethernet
Interface
SCTP Links
Physical Facility
IP Prec=1
SS7 Traffic from MSC
IP Prec=3
SS7 Traffic from SMSC
IP Prec=5
SS7 Traffic from SCP
Link from SMSC
Classification / Marking By Service Indicator Classification

MSC
T1 / E1
MSC
T1 / E1
Ethernet
Interface
SCTP Links
Physical Facility
SMSC
IP Prec = 1
ISUP Traffic: SI=5
IP Prec=5
SCCP (SMS) Traffic

SI=3
Functions of a Signalling Gateway
A Signalling Gateway is a bridge between SS7 and SS7oIP world:
Converts SCCP to SUA
Converts MTP3 to M3UA
Allows peer-to-peer connections with M2PA
What Functions is it used for?
Global Title Translation
MTP3 routing, failover and aggregation
SS7oIP traffic routing, load-balancing and failover
Traffic accounting, management and debug
Why do we want to use it?
Means we dont need MTP hardware and SCCP stacks on our UAS
Means we can easily scale with customer load
CHEAP! IP technology is open, universal and fiercely competitive
ITP Functions: Signalling Gateway

SUA SG
MAP
TCAP
SCCP
MTP3
MTP2
MTP1
SEP
MAP IS-41I T
S U
TCAP U P
SCCP P
GTT
SCCP
MAP
N
I
F
MTP3
SUA
SUA
SCTP
MTP2
TCAP
MTP1
IP
Network
IP
SS7
SCTP/IP
ITP
N
I
F
IP
ASP
MAP IS-41 I T
S U
TCAP U P
SCCP P
GTT
SCCP
SCTP
MTP3
MTP3
MTP2
MTP2
SCTP
MTP1
MTP1
IP
M3UA
M3UA
IP
Network
M3UA SG
SCTP
IP
SUA/M3UA: Traffic Modes
Broadcast
Override
Traffic sent to all Active ASPs within an AS.
One Active ASP in an AS. One ASP takes over all traffic for an AS
(primary/backup operation), possibly overriding any currently active
ASP in the AS.
Fail-over to backup ASP.
Loadshare
Traffic shared among all Active ASPs within an AS.
Algorithm is one of:
bindings - SLS-based load share (default)
Round robin distributed equally amongst the ASP in the AS
Weighted Round Robin distributed in a weighted fashion
Traffic Mode Broadcast
SCCP messages to 2109

Signalling Gateway
ASPA
ACTIVE
AS BLUE
ASPB
ACTIVE
ASPC
ACTIVE
AS Blue
Routing Key = DPC 2109, SI SCCP
ASP List = ASPA, ASPB, ASPC
Traffic Mode = Broadcast
Traffic Mode Override

Signalling Gateway
ASPA
ACTIVE
AS BLUE
ASPB
INACTIVE
ASPC
INACTIVE
AS Blue
Traffic Mode = Override
CDMA Override 1 PC
CDMA Override 2 PC
CDMA Override Example (Failure)
Traffic Mode Loadshare (Bindings)
0, 3,
Signalling Gateway
ASPA
ACTIVE
AS BLUE
1, 4,
ASPB
ACTIVE
2, 5,
ASPC
ACTIVE
AS Blue
Traffic Mode = loadshare bindings
Traffic Mode Loadshare (Round Robin)
every
Signalling Gateway
ASPA
ACTIVE
AS BLUE
third
ASPB
ACTIVE
packet
ASPC
ACTIVE
AS Blue
Traffic Mode = loadshare roundrobin
Traffic Mode Loadshare (Weighted Round Robin)
50%
Signalling Gateway
ASPA
ACTIVE
AS BLUE
30%
ASPB
ACTIVE
20%
ASPC
ACTIVE
AS Blue
Traffic Mode = loadshare roundrobin weighted
Loadshare Example
SUA: Multiple SSN Scenario
SCCP messages to SSN 8

Signalling Gateway
ASPA
ACTIVE
ASPB
ACTIVE
ASPC
INACTIVE
AS BLUE
AS GREEN
AS Blue
Routing Key = DPC 2109, SSN 8, SI SCCP
Traffic Mode = Loadshare
AS Green
ASP List = ASPB, ASPC
SUA: Multiple SSN Scenario
SCCP messages to SSN 11

Signalling Gateway
ASPA
AS BLUE
ASPB
ACTIVE/STANDBY
ASPC
OVERRIDE
AS GREEN
AS Blue
Routing Key = DPC 2109, SSN 8, SI ISUP
Traffic Mode = Loadshare
AS Green
ASP List = ASPC, ASPB
Loadshare Example (Voice and SMS)
Loadshare Failover (Voice + SMS)
Global Title: Intermediate versus Final
Final GTT is a translation that inserts a PC into the SCCP header

that is the final destination
Result is usually an End Point (SEP)

Routing indicator (RI) bit is set to route on PC/SSN
Intermediate GTT is a translation that inserts a PC into the

SCCP packet to an intermediate point that will again perform GTT
Result is another node which will perform GTT

Routing indicator (RI) bit is left cleared to keep routing on GT
DPC = ITP1
RI = GT
Intermediate
GTT
DPC = ITP2
RI = GT
Final
GTT
MSC
ITP1
ITP2
DPC = UAS
RI = PC/SSN
UAS
GTT and Cost Based Load-Sharing
This is how cost based load sharing works:
Final:
Intermediate:
GTT and SLS Based Load-Sharing
This is how cost based load sharing works:
Final:
Intermediate:
Debug Commands
We have to be VERY careful with DEBUG
DONT EVER, EVER, EVER turn it on in production
Network Designs
Network Design to Support eSG IN
We need to design a solid, reliable network to support the IN
It must be redundant, fast and (mostly) dedicated

Network
Function
Enables access to
Facility
Machines
External Access
NTP, SNMP, syslog, Users
FWT
All
Replication
Service Data (IN Internal)
Both
All non ITP
Billing
IN Billing elements
GSM
UAS, USMS, UBE
Sigtran
IP Signalling elements
Both
UAS and ITP
Cluster
Private Cluster I/C
GSM
USMS
Alarm
NTP, SNMP, syslog, Users
GSM
All
Backup
Path to backup server
FWT
UAS, USMS
GSM UAS/USMS Connectivity
Server Port Allocation (GSM)

Server
1st QFE Quad LAN Card
Port
ce0
USMS
Replcn.
UAS
Replcn.
UBE
Replcn.
ce1
ce2
Billing
Billing
Sigtran
ce3
ce4
ce5
Cluster
Replcn.
Replcn.
Billing
Billing
ce7
Cluster
Sigtran
B
Replcn.
Billing
Motherboard
Port 0
Port 1
USMS
Alarm
UAS
Alarm
UBE
Alarm
ce6
Billing
Server
Port
2nd QFE Quad LAN Card
Same failures as before, although alarms failover could be better
Server Port Allocation (CDMA FWT)

Server
Mother Board
QFE Quad LAN Card
Port
ce0
ce1
ce2
ce3
ce4
ce5
USMS
Replication
External
Replication
N/A
External
Backup
UAS
Replication
Sigtran A
Replication
Sigtran B
External
Backup
Any single board or switch failure can be tolerated
Each cable on the same network uses a different IP switch
Any two port/cable failures can be tolerated (not on the same net
on the same machine i.e. ce0 and ce2 above on the one machine)
Really requires one more port on the UAS (GSM has that)
CDMA Replication Network Design
CDMA Signalling Network Design
CDMA External Network Design
Planning is Essential!
References 1/1
Tutorials and External References

http://www.pt.com/tutorials/ss7/
Signaling transport over IP-based networks using IETF standards
Klaus D. Gradischnig and Michael Txen
RFC 3286 An Introduction to the Stream Control Transmission Protocol (SCTP)
Signaling System #7 by Travis Russell
SCCP standard is Q.713
http://www.itu.int/itudoc/itu-t/rec/q/q500-999/q713_23786.html
Cisco ITP documentation

http://www.cisco.com/en/US/products/sw/wirelssw/ps1862/index.html
Cisco IOS documentation

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/ffun_
c/fcfbook.pdf
References
Cisco ITP web site
Thorough, but a little difficult to find your way around, use Google!!
www.cisco.com/en/US/products/sw/wirelssw/ps1862/index.html
The ITP is generally a Wireless Product
I can supply PDF of the command and operations guides
Cisco IOS Documentation (also on the Production CD)
http://www.cisco.com/univercd/cc/td/doc/product/index.htm
Sigtran, especially SCTP and SUA
http://www.ietf.org/rfc/rfc2960.txt for the SCTP RFC
http://www.ietf.org/rfc/rfc3868.txt for the SUA RFC
http://www.sigtran.org/ for pointers to a large number of references
Glossary
ETSI
European Telecommunications
Standardisation Institute
IETF
Internet Engineering Task Force
GTT
Global Title Translation
HDLC
High Level Data Link Control
IP
Internet Protocol
ISUP
ISDN User Part
ITU
International Telecommunications Union
IUA
ISDN User Adaptation layer
M2PA
MTP2 Peer-to-peer user Adaptation layer
M2UA
MTP2 User Adaptation layer
M3UA
MTP3 User Adaptation layer
MEGACO
Media Gateway Control (IETF WG)
MG
Media Gateway
MGC
Media Gateway Controller
MGCP
Media Gateway Control Protocol
MTP
Message Transfer Part
PSTN
Public Switched Telephone Network
RTP
Real Time Protocol
SCCP
Signalling Connection Control Part
SCP
Service Control Point
SCTP
Stream Control Transport Protocol
SG
Signalling Gateway
Sigtran
Signalling transport (IETF Working Group)
SIP
Session Initiation Protocol (IETF WG)
SP
SS7 Signalling Point
SS7
Signalling System No. 7
SSN
Sub-System Number
SSP
Service Switching Point
STP
Signalling Transfer Point
TCAP
Transaction Capabilities Application Part
UA
User Adaptation layer
V5UA
V5.2-User Adaptation layer
Whos Hungry?
Thats all Folks!
Reliance Designs
GSM Overview
CDMA Overview
CDMA Override Example
CDMA Override Example (Failure)
GSM Loadshare Configuration
GSM Loadshare Configuration (Failure)
SCCP and SUA
SCCP and GTT/Routing
Groan
The most important thing to get out of this is:
There are UDT, XUDT packet formats (amongst others)
XUDT has HOPCOUNT and SEGMENTATION parameters
There is Class 0 and 1 connectionless traffic
The format is complicated (dont try to decode on paper)
Routing, GTT (covered more in the SUA section)
SCCP Protocol Classes
The SCCP protocol classes are defined as follows:
Protocol class 0 provides unordered transfer of SCCP-user messages in

a connectionless manner.
Protocol class 1 allows the SCCP-user to select the in-sequence
delivery of SCCP-user messages in a connectionless manner.
Protocol class 2 allows the bi-directional transfer of SCCP-user
messages by setting up a temporary or permanent signalling
connection.
Protocol class 3 allows the features of protocol class 2 with the
inclusion of flow control. Detection of message loss or mis-sequencing
is included.
Protocol classes 0 and 1 make up the SCCP connectionless

service.
Protocol classes 2 and 3 make up the SCCP connection-oriented
service.
SCCP Message Types

Message type
Classes
Message
Reference
Code
CR Connection request
4.2
0000 0001
CC Connection confirm
4.3
0000 0010
CREF Connection refused
4.4
0000 0011
RLSD Released
4.5
0000 0100
RLC Release complete
4.6
0000 0101
DT1 Data form 1
4.7
0000 0110
DT2 Data form 2
4.8
0000 0111
AK Data acknowledgement
4.9
0000 1000
UDT Unitdata
4.10
0000 1001
UDTS Unitdata service
X1
X1
4.11
0000 1010
X = Type of message of this protocol class.

X1 = Type of protocol class is indeterminate (absence of protocol class parameter).
SCCP Message Types

Message type
Classes
Message
Reference
Code
ED Expedited data
4.12
0000 1011
EA Expedited data acknowledgement
4.13
0000 1100
RSR Reset request
4.14
0000 1101
RSC Reset confirm
4.15
0000 1110
ERR Protocol data unit error
4.16
0000 1111
IT Inactivity test
4.17
0001 0000
XUDT Extended unitdata
4.18
0001 0001
XUDTS Extended unitdata service
X1
X1
4.19
0001 0010
LUDT Long unitdata
4.20
0001 0011
LUDTS Long unitdata service
X1
X1
4.21
0001 0100
X = Type of message of this protocol class.

X1 = Type of protocol class is indeterminate (absence of protocol class parameter).
SUA Packet Formats and Reference
Do you want to know some of the details of SUA?

Well, you are going to see more than some, but you need to see
the detail to get the big picture.
The most important thing to get out of this is
The destination and source address formats and tags.
There are CLDT and CLDR
We wont cover DUNA, DAVA, etc in much detail.
SUA Message Formats-CLDT 1/3
Connectionless Data Transfer (CLDT) message transfers data

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Tag = 0x0006
Length
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/
Routing Context
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Tag = 0x0115
Length
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Protocol Class
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Tag = 0x0102
Length
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/
Source Address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Tag = 0x0103
Length
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/
Destination Address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Tag = 0x0116
Length
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Sequence Control
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Tag = 0x0101
Length
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
SS7 Hop Count
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Tag = 0x0113
Length
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Importance
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Tag = 0x0114
Length
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Message Priority
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Tag = 0x0013
Length
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Correlation ID
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Tag = 0x0117
Length
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Segmentation
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Tag = 0x010b
Length
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/
Data
/
\
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
A Connectionless Data Response (CLDR) is a service message
SUA Message Formats-Source/Destination Address
SUA Source Address

0
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Tag = 0x0102
Parameter Length
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Routing Indicator
Address Indicator
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/
Address parameter(s)
/
\
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The following combinations of address parameters are valid:
Global Title (e.g. E.164 number) + optional PC and/or SSN, SSN may be zero, when routing is
done on Global Title
SSN (non-zero) + optional PC and/or Global Title, when routing is done on PC + SSN. The PC
is mandatory in the source address when sending from SGP to ASP, and in the destination
address when sending from ASP to SGP to reach the SS7 SEP.
Hostname + optional SSN, when routing is done by Hostname
SSN (non-zero) and optional IP address when routing is done on IP address + SSN
SUA Message Formats-S/D Address-Routing Indicator
Routing Indicator
The following values are valid for the routing indicator:
Reserved
Route on Global Title
Route on SSN + PC
Route on Hostname
Route on SSN + IP Address
The ROUTING indicator determines which address parameters are

to be used in routing the traffic to the destination.
SUA Message Formats-S/D Address-Address Indicator
Address indicator is coded as follows:
Bit 1 is used to indicate inclusion of the SSN
Do not include SSN when optional
Include SSN
Bit 2 is used to indicate inclusion of the PC
Do not include PC, regardless of the routing indicator value
Include PC
Bit 3 is used to indicate inclusion of the Global Title
Do not include GT when optional (routing indicator /= 1)
Include GT
The remaining bits are spare and SHOULD be coded zero, and
MUST be ignored by the receiver.
The ADDRESS indicator determines which address parameters
need to be present in the address parameters field.
SUA Message Formats-S/D Address-Global Title 1/5
Global Title
0
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Tag = 0x8001
Length
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Reserved
GTI
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
No. Digits
| Trans. type
Num. Plan
| Nature of Add |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/
Global Title Digits
/
\
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Number of Digits:
This is the number of digits contained in the Global Title.
Global Title Indicator

0000
Reserved
0001
Nature of Address is ignored. Translation Type = Unknown

and Numbering Plan = E.164 (value 1).
0010
This is most commonly used in North American networks.

The Translation Type implicitly determines Nature of Address
and Numbering Plan. This data can be configured in the SG.
The number of digits is always even and determined by the
SCCP address length.
0011
Numbering Plan and Translation Type are taken over. It is

implicitly assumed that the Nature of Address = Unknown.
0100
This format is used in international networks and most

commonly in networks outside North America. All information
to populate the source address is present in the SCCP
Address.
Numbering Plan:
0
unknown
ISDN/telephony numbering plan (E.163 and E.164)
generic numbering plan
data numbering plan (Recommendation X.121)
telex numbering plan (Recommendation F.69)
maritime mobile numbering plan (E.210, E.211)
land mobile numbering plan (E.212)
ISDN/mobile numbering plan (E.214)
8 13
spare
14
private network or network-specific numbering plan
15 - 126 spare
127
reserved.
Translation type:
0
Unknown
1 63
International services
64 127
Spare
128 254
National network specific
255
Reserved
Nature of Address:
0
unknown
subscriber number
reserved for national use
national significant number
international number
5 255
Spare
Global Title:
Octets contain a number of address signals and possibly filler as shown:
0
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|2 addr.|1 addr.|4 addr.|3 addr.|6 addr.|5 addr.|8 addr.|7 addr.|
|
sig. | sig.
sig. | sig.
sig. | sig.
sig. | sig.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
.............
|filler |N addr.|
|if req | sig.
filler
|
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
All filler bits SHOULD be set to 0.
SUA Message Formats-S/D PC and SSN
Point Code
1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Tag = 0x8002
Length = 8
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Point Code
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Subsystem Number
1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Tag = 0x8003
Length = 8
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
Reserved
SSN value
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SUA Message Formats-S/D-SSN Values
The Subsystem Number (SSN) identifies an SCCP user function

00
SSN not known/not used
01
SCCP management
02
reserved for ITU-T allocation
03
ISDN user part
04
OMAP (Operation, Maintenance and Administration Part)
05
MAP (Mobile Application Part)
06
HLR (Home Location Register
07
VLR (Visitor Location Register)
08
MSC (Mobile Switching Centre)
09
EIC (Equipment Identifier Centre)
0A
AUC (Authentication Centre)
0B
ISDN supplementary services
0C
reserved for international use
0D
broadband ISDN edge-to-edge applications
0E
TC test responder
0F-1F
reserved for international use
20-FE
reserved for national networks
FF
reserved for expansion of national and international SSN.
SUA Protocol Parameters
These parameters are specific to the SUA protocol:

Parameter Name
ID
Parameter Name
ID
SS7 Hop Counter
0x0101
Source Address
0x0102
Destination Address
0x0103
Source Reference No.
0x0104
Destination Reference No.
0x0105
SCCP Cause
0x0106
Sequence Number
0x0107
Receive Sequence No.
0x0108
ASP Capabilities
0x0109
Credit
0x010A
Data
0x010B
Cause / User
0x010C
Network Appearance
0x010D
Routing Key
0x010E
DRN Label
0x010F
TID Label
0x0110
Address Range
0x0111
SMI
0x0112
Importance
0x0113
Message Priority
0x0114
Protocol Class
0x0115
Sequence Control
0x0116
Segmentation
0x0117
Congestion Level
0x0118
SCCP Message Formats-Source/Destination Address
For comparison, this is an SCCP header:
SUA is quite a bit longer
8
OCTET
Nat/Intnl Routing
Indicator Indicator
Global Title Indicator
2
Point
Code
Indicator
Subsystem Number
Signaling Point Code
Global Title
1
Subsystem
Number
Indicator
Bit
Pos
SUA Management Message Mapping
SUA Primitive to/from ASP
MTP Primitive to/from SS7
CLDT (Payload data)
UDT/XUDT
CLDR (Payload data)
UDTS/XUDTS
DUNA (Destination Unavailable)
MTP-PAUSE (TFP) or SSP
DAVA (Destination Available)
MTP-RESUME (TFA) or SSA
SCON (Network Congestion State)
MTP-STATUS (TFC) or SSC
DUPU (Destination User Part

Unusable
MTP-STATUS (UPU)
DRST (Destination Restricted)
MTP-STATUS (TFR)
DAUD (Destination State Audit)
Link or subsystem status
SPMC* network congestion
TFC
SPMC* network unavailable
TFP
* SPMC signalling Point Management Cluster (Group of ASs sharing a single PC).
Some Example Traffic Flows
Initial Trigger
Initial Response
Subsequent
Aligning ITP and UAS Configurations
Example Sigtran Configuration UAS
hssScIf.sh
#!/bin/ksh
exec ../bin/hssSccpTcapInterface \
-pc 3212 -ssns 12,146 \
-sendorigaddr true \
-port 14001 \
-rcbase 101 -netaddr 172.20.66.66 \
-secondary_netaddr 172.20.66.98 \
-stps 3210,3211 \
-maxdids 132000 \
-asmode 1 conntimer 5 \
-rto_init 1000 -rto_max 5000 -rto_min 500 -hb_interval 10 \
-assoc_max_retrans 6 -path_max_retrans 3 -maxSctpModeRetry 10 \
-sccp itu -proto any \
-inapssns 12 \
>> /IN/service_packages/SLEE/tmp/hssScIf.log 2>&1
peers.conf
peers
# Signalling Gateway Peers
peer ( 2 SG 1 3210 15000 172.20.66.68 172.20.66.100 )
peer ( 2 SG 1 3211 15000 172.20.66.69 172.20.66.101 )
dummy 2:
Example Sigtran Configuration - ITP
SUA
Defines the local IP port for incoming SUA connections
cs7 point-code 3210

cs7 sua 15000
local-ip 172.20.66.68
local-ip 172.20.66.100
assoc-retransmit 6
path-retransmit 3
retransmit-timeout 500 5000
tx-queue-depth 2000
ASP
Builds the IP streams for each ITP UAS connection
cs7 asp SYDSCP01-ASP 14001 15000 sua

remote-ip 172.20.66.66
remote-ip 172.20.66.98
AS
Sets the Point Code and SSN for each ASP
cs7 as SYDSCP01-AS sua

routing-key 101 3212 si sccp ssn 12
asp SYDSCP01-ASP
Sigtran Configurations
hssScIf.sh
#!/bin/ksh
-pc 3212 -ssns 12,146 -port 14001 \
-rcbase 101 -rcstep 10
-netaddr 172.20.66.66 \
-stps 3210,3211 -maxdids 132000 \
-asmode 1 -conntimer 5 \
-rto_init 1000 -rto_max 5000 \
-rto_min 500 -hb_interval 10 \
-assoc_max_retrans 6 \
-path_max_retrans 3 \
-inapssns 12,146 \
peers.conf

peer ( 2 SG 1 3210 15000 172.20.66.70
172.20.66.102 )
peer ( 3 SG 2 3211 15000 172.19.40.197
172.19.40.229 )
SUA
cs7 point-code 3210

cs7 sua 15000
assoc-retransmit 6
path-retransmit 3
local-ip 172.20.66.70
local-ip 172.20.66.102
ASP

remote-ip 172.20.66.66
remote-ip 172.20.66.98
AS
cs7 as SYDSCP1-AS1 sua

asp SYDSCP1-ASP
asp SYDSCP1-ASP
Sigtran Configurations - STP/ITP Point Code
UAS
hssScIf.sh
#!/bin/ksh
-pc 3212 -ssns 12,146 -port 14001 \
-netaddr 172.20.66.66 \
-stps 3210,3211 -maxdids 132000 \
-inapssns 12,146 \
peers.conf

peer ( 2 SG 1 3210 15000 172.20.66.70
172.20.66.102 )
peer ( 3 SG 2 3211 15000 172.19.40.197
172.19.40.229 )
ITP
SUA
cs7 point-code 3210

cs7 sua 15000
assoc-retransmit 6
path-retransmit 3
local-ip 172.20.66.70
local-ip 172.20.66.102
ASP
remote-ip 172.20.66.66
remote-ip 172.20.66.98
AS
asp SYDSCP1-ASP

asp SYDSCP1-ASP
Sigtran Configurations ITP SUA Port
UAS
hssScIf.sh
#!/bin/ksh
-pc 3212 -ssns 12,146 -port 14001 \
-netaddr 172.20.66.66 \
-stps 3210,3211 -maxdids 132000 \
-inapssns 12,146 \
peers.conf

peer ( 2 SG 1 3210 15000 172.20.66.70
172.20.66.102 )
peer ( 3 SG 2 3211 15000 172.19.40.197
172.19.40.229 )
ITP
SUA
cs7 point-code 3210
cs7 sua 15000

assoc-retransmit 6
path-retransmit 3
local-ip 172.20.66.70
local-ip 172.20.66.102
ASP
remote-ip 172.20.66.66
remote-ip 172.20.66.98
AS
asp SYDSCP1-ASP

asp SYDSCP1-ASP
Sigtran Configurations IP Addresses
UAS
hssScIf.sh
#!/bin/ksh
-pc 3212 -ssns 12,146 -port 14001 \
-netaddr 172.20.66.66 \
-stps 3210,3211 -maxdids 132000 \
-inapssns 12,146 \
peers.conf

peer ( 2 SG 1 3210 15000 172.20.66.70
172.20.66.102 )
peer ( 3 SG 2 3211 15000 172.19.40.197
172.19.40.229 )
ITP
SUA
cs7 point-code 3210
cs7 sua 15000

assoc-retransmit 6
path-retransmit 3
local-ip 172.20.66.70
local-ip 172.20.66.102
ASP
remote-ip 172.20.66.66
remote-ip 172.20.66.98
AS
asp SYDSCP1-ASP

asp SYDSCP1-ASP
Sigtran Configurations Retransmission Parameters
UAS
hssScIf.sh
#!/bin/ksh
-pc 3212 -ssns 12,146 -port 14001 \
-netaddr 172.20.66.66 \
-stps 3210,3211 -maxdids 132000 \
-inapssns 12,146 \
peers.conf

peer ( 2 SG 1 3210 15000 172.20.66.70
172.20.66.102 )
peer ( 3 SG 2 3211 15000 172.19.40.197
172.19.40.229 )
ITP
SUA
cs7 point-code 3210
cs7 sua 15000

assoc-retransmit 6
path-retransmit 3
local-ip 172.20.66.70
local-ip 172.20.66.102
ASP
remote-ip 172.20.66.66
remote-ip 172.20.66.98
AS
asp SYDSCP1-ASP

asp SYDSCP1-ASP
Sigtran Configurations Timeout Parameters
UAS
hssScIf.sh
#!/bin/ksh
-pc 3212 -ssns 12,146 -port 14001 \
-netaddr 172.20.66.66 \
-stps 3210,3211 -maxdids 132000 \
-inapssns 12,146 \
peers.conf

peer ( 2 SG 1 3210 15000 172.20.66.70
172.20.66.102 )
peer ( 3 SG 2 3211 15000 172.19.40.197
172.19.40.229 )
ITP
SUA
cs7 point-code 3210
cs7 sua 15000

assoc-retransmit 6
path-retransmit 3
local-ip 172.20.66.70
local-ip 172.20.66.102
ASP
remote-ip 172.20.66.66
remote-ip 172.20.66.98
AS
asp SYDSCP1-ASP

asp SYDSCP1-ASP
Sigtran Configurations UAS SUA Port
UAS
hssScIf.sh
#!/bin/ksh
-pc 3212 -ssns 12,146 -port 14001 \
-netaddr 172.20.66.66 \
-stps 3210,3211 -maxdids 132000 \
-inapssns 12,146 \
peers.conf

peer ( 2 SG 1 3210 15000 172.20.66.70
172.20.66.102 )
peer ( 3 SG 2 3211 15000 172.19.40.197
172.19.40.229 )
ITP
SUA
cs7 point-code 3210
cs7 sua 15000

assoc-retransmit 6
path-retransmit 3
local-ip 172.20.66.70
local-ip 172.20.66.102
ASP
remote-ip 172.20.66.66
remote-ip 172.20.66.98
AS
asp SYDSCP1-ASP

asp SYDSCP1-ASP
Sigtran Configurations ITP ASP and SUA Instance
UAS
hssScIf.sh
#!/bin/ksh
-pc 3212 -ssns 12,146 -port 14001 \
-netaddr 172.20.66.66 \
-stps 3210,3211 -maxdids 132000 \
-inapssns 12,146 \
peers.conf

peer ( 2 SG 1 3210 15000 172.20.66.70
172.20.66.102 )
peer ( 3 SG 2 3211 15000 172.19.40.197
172.19.40.229 )
ITP
SUA
cs7 point-code 3210
cs7 sua 15000

assoc-retransmit 6
path-retransmit 3
local-ip 172.20.66.70
local-ip 172.20.66.102
ASP
remote-ip 172.20.66.66
remote-ip 172.20.66.98
AS
asp SYDSCP1-ASP

asp SYDSCP1-ASP
Sigtran Configurations UAS IP Addresses
UAS
hssScIf.sh
#!/bin/ksh
-pc 3212 -ssns 12,146 -port 14001 \
-netaddr 172.20.66.66 \
-stps 3210,3211 -maxdids 132000 \
-inapssns 12,146 \
peers.conf

peer ( 2 SG 1 3210 15000 172.20.66.70
172.20.66.102 )
peer ( 3 SG 2 3211 15000 172.19.40.197
172.19.40.229 )
ITP
SUA
cs7 point-code 3210
cs7 sua 15000

assoc-retransmit 6
path-retransmit 3
local-ip 172.20.66.70
local-ip 172.20.66.102
ASP
remote-ip 172.20.66.66
remote-ip 172.20.66.98
AS
asp SYDSCP1-ASP

asp SYDSCP1-ASP
Sigtran Configurations Routing Keys
UAS
hssScIf.sh
#!/bin/ksh
-pc 3212 -ssns 12,146 -port 14001 \
-netaddr 172.20.66.66 \
-stps 3210,3211 -maxdids 132000 \
-inapssns 12,146 \
peers.conf

peer ( 2 SG 1 3210 15000 172.20.66.70
172.20.66.102 )
peer ( 3 SG 2 3211 15000 172.19.40.197
172.19.40.229 )
ITP
SUA
cs7 point-code 3210
cs7 sua 15000

assoc-retransmit 6
path-retransmit 3
local-ip 172.20.66.70
local-ip 172.20.66.102
ASP
remote-ip 172.20.66.66
remote-ip 172.20.66.98
AS
asp SYDSCP1-ASP

asp SYDSCP1-ASP
Sigtran Configurations UAS Point Codes
UAS
hssScIf.sh
#!/bin/ksh
-pc 3212 -ssns 12,146 -port 14001 \
-netaddr 172.20.66.66 \
-stps 3210,3211 -maxdids 132000 \
-inapssns 12,146 \
peers.conf

peer ( 2 SG 1 3210 15000 172.20.66.70
172.20.66.102 )
peer ( 3 SG 2 3211 15000 172.19.40.197
172.19.40.229 )
ITP
SUA
cs7 point-code 3210
cs7 sua 15000

assoc-retransmit 6
path-retransmit 3
local-ip 172.20.66.70
local-ip 172.20.66.102
ASP
remote-ip 172.20.66.66
remote-ip 172.20.66.98
AS
asp SYDSCP1-ASP

asp SYDSCP1-ASP
Sigtran Configurations Sub-System Numbers
UAS
hssScIf.sh
#!/bin/ksh
-pc 3212 -ssns 12,146 -port 14001 \
-netaddr 172.20.66.66 \
-stps 3210,3211 -maxdids 132000 \
-inapssns 12,146 \
peers.conf

peer ( 2 SG 1 3210 15000 172.20.66.70
172.20.66.102 )
peer ( 3 SG 2 3211 15000 172.19.40.197
172.19.40.229 )
ITP
SUA
cs7 point-code 3210
cs7 sua 15000

assoc-retransmit 6
path-retransmit 3
local-ip 172.20.66.70
local-ip 172.20.66.102
ASP
remote-ip 172.20.66.66
remote-ip 172.20.66.98
AS
asp SYDSCP1-ASP

asp SYDSCP1-ASP

Cisco Itp in Eservglobal In: Sigtran and Itp Overview

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Cisco Itp in Eservglobal In: Sigtran and Itp Overview

Hochgeladen von

Copyright:

Verfügbare Formate

Cisco ITP in eServGlobal IN

Sigtran and ITP Overview

Belgium Support and PS

2003 Cisco Systems 2006 eServGlobal Ltd

Quick introduction to SS7, Sigtran, ITP, IOS

ITP Model overview with a view of the innards

Functions of an ITP (especially as a Signalling Gateway)

Traffic modes and load distribution

IP Network Design to support the eSG IN

Reliance Designs (time permitting)

SCCP and SUA

Example traffic flows

Aligning ITP and hss configurations

Dennis Hagarty, Implementation Lead, eServGlobal

Working with ITPs and Sigtran for about four years

Competed mobile, pre-paid, convergent billing, wireline IN

More of an IT and less of a telecoms background

Tell me if my English is not easy to understand or I go too fast!

SS7, Sigtran and ITP Basics

Quick Introduction to SS7, Sigtran, ITP, IOS

What is a signalling gateway?

SS7: What is it?

Data network designed to transport CCS signalling traffic that

First came the Yellow Book (1980)

Red Book (1984)

Blue Book (1988)

White Book (1992)

ANSI standard for US was developed from the Blue Book

SS7: What is it? SS7 and OSI Protocol Stack

SS7: What is it? Signalling Points and Point Codes

SSP: Service Switching Point sends signalling messages to other SSPs

Signalling points have Point Codes (think IP addresses)

SS7 What is it? Transport Layers

Three Transport Layers

Signalling points have Point Codes

Signalling Points are connected together by Linksets

User and Application Layers

SS7: What is it? Point Codes

A SEP on an SS7 network has a Point Code (node address)

There are two variants of point code:

ITU: Value up to 7.255.7 (14 bits)

ANSI: Varies, but up to 255.255.255 (24 bits)

Three types of point codes:

SS7: What is it? Link architecture

Reliance GSM Pre-Paid

SS7: What is it? Application Parts

MAP: Mobile Application Part (MAP), provides the signalling functions

Signalling Connection Control Part (SCCP) is used as the

SS7 What is it? SCCP and GTT/GTA

Signalling Connection Control Part (SCCP) provides

Sigtran: What is it?

Set of standards, proposed standards, and drafts

RFC 2719 Framework Architecture for Signalling Transport

RFC 2960 Stream Control Transmission Protocol (& 3286)

IUA = RFC 3057 - ISDN Q.921-User Adaptation Layer along with:

M2UA = RFC 3331 SS7 MTP2 User Adaptation Layer

M3UA = RFC 3332 SS7 MTP3 User Adaptation Layer

SUA = SS7 SCCP-User Adaptation Layer

Sigtran: What is it?

Implements SS7 using the IP protocol as the underlying layers

This is based on SCTP (Stream Control Transmission Protocol)

The following are probably the most interest to us:

M2PA = to run MTP3 SS7 linksets over IP