Sigtran Connectuon by Cisco

2008 Cisco Systems, Inc. All rights reserved.
Cisco Public 1
Next Generation
Signalling and
Applications
BRKMWI-3007
Ching-Ying Tong
chitong@cisco.com
2 2008 Cisco Systems, Inc. All rights reserved. Cisco Public
Agenda
SS7 background
Next Generation Signaling
SIGTRAN
SCTP
M2PA
M3UA
SUA
Sigtran in 3GPP
Applications
Sigtran design rules
Agenda
SS7 background
SIGTRAN
SCTP
M2PA
M3UA
SUA
Sigtran in 3GPP
Applications
SS7 background
Describe SS7 background and evolution
List SS7 nodes, describe their functions
Describe switching network hierarchies
Describe some traffic engineering and dimensioning rules
What is SS7 ? - Back to 60s
SS7 = Signalling System #7
- Derived from SS6 a Common Channel Signalling protocol
- SS6, signalling introduced in 60s in US between central offices
- SS6 initial deployment based on
2400 bps, upgraded to 4800 bps links
Proprietary communication protocol
Used to request voice channel from other network entities
- SS6 first use of packet switching in PSTN network
What is SS7 ? - Evolution to SS7
ITU-T derived SS7 from SS6
- More capability / flexibility as for example:
Bandwidth of 56 Kbps ANSI / 64 Kbps ITU-T extended to High
Speed Links later ( 2 Mbits links )
Variable length signalling units
Reliability improvements
- First application WATS ( Wide Area Telephony Service ), 800
number database access application
- First deployment starting from early 80s.
- Initial deployment between interoffice network
- Local office deployment years later
- SS6 phased out mid 80s
In parallel, network evolution to digital equipments
What is SS7 - SS7 nodes
SSP Switching Point ( C3/C4/C5/MSC )
TDM switches equipped with SS7 HW and SW
STP Signaling Transfer Point
Switches that receive & route SS7 messages only
SCP/SN Service Control Point and Service Node
IN services
HLR/VLR/AUC/SMSC
Specialized equipments for special call processing with embedded database
SSP
STP
SCP/SN
What is SS7 ? - PSTN network
common architecture / Quasi associated signalling
SSP
SSP
SSP
SSP
Signaling layer
STP
IN Apps. and DataBase
SCP SCP
STP
STP
STP
Transport
Access layer
C5/C4/C3
Bearer trunks
Signaling links
What is SS7 ? Mobile SP network
Common architecture Quasi associated signalling
MSC
MSC
MSC
MSC
Signaling layer
STP
HLR/AUC/SMSC
SCP SCP
STP
STP
STP
MSC Layer
Bearer trunks
Signaling links
What is SS7 ? Mobile SP network
Alternative architecture Fully associated signaling
STP/ and switching
Layer
MSC layer
Bearer trunks
Signaling links
SCP
MSC
MSC
MSC
MSC
HLR/AUC/SMSC
ISDN User
Part (ISUP)
TCAP
Non-Circuit Applications
SCCP
SCCP
MTP
Enhanced Addressing,
Connectionless/Connection Oriented Services
Enhanced Addressing,
Connectionless/Connection Oriented Services
Level 1
Level 2
Level 3
Null
Null
Presentation,
Session, Transport
Presentation,
Session, Transport
Application
CAMEL Operations, Maintenance and Administration Part
TCAPTransaction Capabilities Application Part
ISUPIntegrated Services Digital Network User Part
SCCPSignaling Connection Control Part
MTPMessage Transfer Part
TUPTelephone User Part (Before ISUP)
Circuit-
Related
Services
OSI Reference Model
Network
Network
Message Discrimination/Distribution/
Routing, Network Management
Message Discrimination/Distribution/
Routing, Network Management
Network
Network
Data Link
Data Link Data Link
Data Link
SU Delimitation/Alignment, Error Detection/Correction,
Retransmission, SUERM, Alignment, Flow Control
SU Delimitation/Alignment, Error Detection/Correction,
Retransmission, SUERM, Alignment, Flow Control
a
Physical
Physical
Physical
Physical Link Connection, Bit Rate, Voltages
Link Connection, Bit Rate, Voltages
T
U
P
IN-AIN
CAMEL
IN Services
MAP
Call
Processing
What is SS7
SS7 Protocol Stack
What is SS7 ? - MTP2 and MTP3
Only MSUs carry payload of higher level messages (e.g. MTP3 and higher stack layers)
All signaling associated with call setup and tear down, database query and response, and SS7
network management takes place using MSUs.
MSUs are the basic envelope within which all addressed signaling information is placed; Hence,
the MSUs are the message types upon which bandwidth requirements must be determined
The SS7 MTP2 (Message Transfer Part layer 2) is a point-to-point, reliable protocol. SS7 signaling
link alignment, error detection and corrections are performed at this level. MTP2 guarantees reliable
delivery of signal unit messages between SS7 nodes; Within the MTP2 layer, there are three Types of
SS7 Signal Units (SU), as show below:
Link Status Signal Units (LSSU)
Fill-In Signal Unit (FISU)
Message Signal Unit (MSU) e.g. MTP3
F BSN
BIB
FSN
FIB
LI SIO F CK SIF
8 7 1 7 1 6 8 8n, n>=2 8 16
Message Signal Unit (MSU) Format
F BSN
BIB
FSN
FIB
LI SF F CK
8 7 1 7 1 6 8 or 16 8 16
Link Status Signal Unit (LSSU) Format
F BSN
BIB
FSN
FIB
LI F CK
8 7 1 7 1 6 8 16
Fill-In Signal Unit (FISU) Format
BIB =backward Indicator Bit
BSN =Backward Sequence Number
CK =Check Bits
F =Flag
FIB =Forward Indicator Bit
FSN =Forward Sequence Number
LI =Length Indicator
SIF =Signaling information Field
SIO =Service Information octet
SF =Status Field
What is SS7 ? Protocol evolution
- SS7 specifications red book - 1984
- SS7 specifications blue book 1988
- SS7 specifications white book 1991 ( the final one )
- ISDN User Part specifications version 3 1997
- Bearer Independent Call Control specifications 2000
- SIP-I/SIP-T specifications 2004
SS7 as today is less than 30 years old
Traffic Engineering Dimensioning rules
Agner Krarup Erlang
Danish Scientist
1878-1929
Erlang
The unit used to measure telephony or
signalling traffic
1 Erlang is 60 minutes of traffic/hour
1 Erlang is 100% of the bandwidth
Erlang can be added/multiplied
So 300 calls of 3 mn average
= 900 call Minutes
= 15 call hours or 15 Erlangs
Traffic is normally measured in the busy hour
Busy Hour Call Attempts (BHCA) = number of calls arriving
in this hour
Erlang B used to design inter Central Office trunks
based on 3 parameters
Busy Hour Traffic in Erlang = CCPS * Mean Hold time
Blocking factor = X calls blocked per 100 calls due to
insufficient resource
Number of lines ( DS0 ) required in the trunk
BHCA
=
Calls Attemps per Second
(CAPS)
3600
Determining 70 Erlangs = 70x60 = 4200 call minutes per day
Busy hour 12% of 1000 calls = 120 BHCA
Busy hour 12% of 70 Erlangs = 8.4 Erlangs
Example
1000 calls completion per day and 70 Erlangs Busy Hours
12% in the busy hour
Blocking factor 0.02
Each SP has its own blocking factor for SLA
SS7 linkset and routeset
STP 1
A linkset is a collection of signaling links connecting 2 signaling points
A routeset is all of the routes from a signaling point to a particular
destination. A route is made of a collection of linksets
SCP Y
STP1 routeset to SCP Y
STP 3
STP 4 STP 2
SSP1
SCP X
SSP2
L1
L
2
L
3
Linkset Priority
L1 1
L2 1
L3 2
STP 1
Dimensioning SSP STP traffic
[(X)(Y)(Z)] + [(A)(B)(C)] / 3600 = n Bytes per second
STP 2
SSP
64 kbit/s
A
-
l
i
n
k
A
-
l
i
n
k
ISUP load determination:
X - ISUP messages for each call 2 upstream/3 downstream =>5
Y - Average length in Bytes of ISUP messages => 20 Bytes
Z - Busy Hour Call Attempts BHCA
TCAP load determination:
A - TCAP/ database messages per sequence =>2
B - Average length in Bytes of TCAP messages => 80 Bytes
C - Busy Hour Database Call Attempt
SSP-, STP- and SCP-links are often engineered at 0,4 Erlang = 40%
capacity, allowing the remaining node/links to carry 80% of the load in
case of any node or link failure
The remaining 20% is for traffic peaks
Traffic Engineering dimensioning rules
STP 1
Example dimensioning SSP STP traffic
[(X)(Y)(Z)] +[(A)(B)(C)] / 3600 sec =n Bytes per second
[(5)(20)(4.000.000)] +[(2)(80)(1.000.000)] / 3600 = 155,55 Kbytes/s
STP 2
A
-
l
i
n
k
A
-
l
i
n
k
A-links
64 Kbit/s x 2 links x 2 (duplex) =256 Kbit/s =>32 KBytes/s
32 KBytes x 40 % =12,8 KBytes/s
n Bytes per Second / 12,8 KBytes per Second =n A-link
155,55 / 12,8 =12,15 =>7 x 2 A-links
SSP capacity :
BHCA =4.000.000
Busy Hour Database Call Attempt=1.000.000
Erlang = 100.000
CPS (calls per second) =BHCA / 3600
CPS =4.000.000 / 3600 =>1111
SSP
Agenda
SS7 background
SIGTRAN
SCTP
M2PA
M3UA
SUA
Sigtran in 3GPP
Applications
Next Generation
signaling
Describe Sigtran motivation
Describe SCTP and some specific features
Describe M2PA architecture
Describe M3UA architecture
Describe SUA architecture
Cisco products with SS7 - Sigtran support
Cisco has several products with Sigtran capabilities
- Call control : PGW2200, BTS10200
- Voice gateways : MGX, AS5X00
- STP/SG : ITP - IP Transfer Point
This presentation will use the Cisco ITP as the reference for
examples
Rational for Cisco to develop the ITP :
1. Customer demand
2. IP convergence for SS7 transport over IP
3. SS7 nodes SCP/SMSC migration to IP
4. Unleash the CPU power of end nodes
ITP released to the market in J une 2001. To date a total
of 1500+ ITPs deployed across 200+ service providers
ITPs deployed primarily as STPs and Signaling
Gateways with approx 50/50 split between SG and STP
deployments
Key drivers for ITP deployments include subscriber
adds, application growth (IP text messaging, etc),
services, VoIP, transition to IP-based signaling, etc
ITP comes in several sizes from 2 up to 2000 SS7 links
for the largest platforms.
ITP Market Activity
Agenda
SS7 background
SIGTRAN
SCTP
M2PA
M3UA
SUA
Sigtran in 3GPP
Applications
Multi-vendor group that is designing SS7oIP
standards
Group includes all actors : Cisco, Lucent/ Alcatel,
Ericsson, Nokia, Siemens, Tekelec, Huawei, NT,
etc.
http://www.ietf.org/html.charters/sigtran-charter.html
Protocols include: SCTP, M2UA, M2PA,
M3UA, SUA
Cisco is co-author on all except SUA
IETF SIGTRAN Working Group
SIGTRAN Architecture Framework ( RFC2719 )
ISUP/SCCP
ISUP/SCCP
MTP3
MTP3
M2UA
M2UA
SCTP
IP
IP
ISUP/SCCP
ISUP/SCCP
M3UA
M3UA
SCTP
IP
IP
TCAP/MAP
TCAP/MAP
SUA
(SCCP)
SUA
(SCCP)
SCTP
IP
IP
IETF
Sigtran
SS7
SS7
ISUP/SCCP
ISUP/SCCP
MTP3
MTP3
M2PA
(Peer-to-peer)
M2PA
(Peer-to-peer)
SCTP
IP
IP
Q.931
Q.931
IUA (Q.921)
IUA (Q.921)
SCTP
IP
IP
A standard network layer protocol: IP (v4 or v6)
A common signaling transport protocol: SCTP
SCTP supports a common set of reliable transport functions for signaling transport
An adaptation sub-layer
Supports specific primitives, such as management indications, required by a particular
signaling application protocol
Sigtran Protocols
SCTP Stream Control Transmission Protocol, RFC3309 transport layer that provides reliable
data transfer.
M2PA MTP2-User Peer-to-Peer Adaptation, RFC4165 provides MTP3 with equivalent
transport layer services as MTP2.
M3UA MTP3-User Adaptation, RFC4666 client/server protocol providing a gateway to
legacy SS7 network for IP-based applications that interface at the MTP3 layer.
SUA SCCP-User Adaptation, RFC3868 client/server protocol providing a gateway to legacy
SS7 network for IP-based applications that interface at the SCCP layer.
M2UA MTP2-User Adaptation, RFC3331 client/server protocol providing a gateway to
legacy SS7 network for IP-based applications that interface at the MTP2 layer.
Security Considerations for SIGTRAN Protocols RFC 3788 - specifies an
Internet security standards track protocol (TLS/IPSec)
SIGTRAN Architecture
SCTP, has been defined for all SS7 signaling transport
over IP
Various protocol user adaptation layers provide
interworking functions between IP and various SS7 or
other PSTN signaling
Two basic Signaling Gateway architectures:
Backhaul model
SG (server) backhauls user adaptation application data to MGC
(client) through SCTP/IP
Peer-to-Peer model
SG/ASP to SG/ASP connection through SCTP/IP
SIGTRAN Architecture:
An Example Backhaul Model
M3UA
M3UA
SCTP
IP
IP
ISUP
ISUP
MTP3
MTP3
MTP2
MTP2
MTP1
MTP1
MTP3
MTP3
MTP2
MTP2
MTP1
MTP1
M3UA
M3UA
SCTP
IP
IP
ISUP
ISUP
Interworking Function
Interworking Function
IP Network
SEP
SEP
MGC
MGC
SG
SG
SS7 Link IP Link
Backhaul
Backhaul
SS7 IP
SIGTRAN Architecture:
An Example Peer-to-Peer Model
M2PA
M2PA
SCTP
IP
IP
MTP3
MTP3
MTP2
MTP2
MTP1
MTP1
M2PA
M2PA
SCTP
IP
IP
Full MTP3 or Link
Management Only
Full MTP3 or Link
Management Only
IP Network
SG
SG
SS7 Link IP Link
Peer-to-Peer
Peer-to-Peer
IP
MTP2
MTP2
MTP1
MTP1
Link
Protocol
Full MTP3 or Link
Management Only
Full MTP3 or Link
Management Only
Link
Protocol
SS7 SS7
SG
SG
M2PAMTP2 User Adaptation
for Peer-to-Peer Connection
Agenda
SS7 background
SIGTRAN
SCTP
M2PA
M3UA
SUA
Sigtran in 3GPP
Applications
SCTP
Stream Control Transmission Protocol (RFC 2960 last update RFC
4960)
ISUP/SCCP
ISUP/SCCP
MTP3
MTP3
M2UA
M2UA
SCTP
IP
IP
ISUP/SCCP
ISUP/SCCP
M3UA
M3UA
SCTP
IP
IP
TCAP/MAP
TCAP/MAP
SUA
(SCCP)
SUA
(SCCP)
SCTP
IP
IP
SS7
SS7
ISUP/SCCP
ISUP/SCCP
MTP3
MTP3
M2PA
(Peer-to-peer)
M2PA
(Peer-to-peer)
SCTP
IP
IP
Q.931
Q.931
IUA (Q.921)
IUA (Q.921)
SCTP
IP
IP
IETF
Sigtran
SCTP - Motivations
TCP imposes limitations for some emerging applications:
Reliability mechanisms
Some applications need reliable transfer without sequence
maintenance; others need only partial ordering of data
No support for multi-homing
Real-time issues
Head-of-line blocking caused by TCP adds unnecessary delay
and makes it inappropriate for real time traffic
Inability to tune parameters (e.g. retransmission timer)
Security issues
TCP is more vulnerable to denial-of-service attacks
SCTP - What Is It ?
Can be used anywhere TCP or UDP
would be used
Broader scope than just SIGTRAN, e.g.
Netflow, HTTP, other signaling H.248
Transport protocol for message
oriented data transfer
SCTP stream is a sequence of
messages
Each SCTP connection can have
multiple streams named association
Multi-homing support
Session monitoring and detection of
loss
Path/session through heartbeat
IP
IP
Physical
Physical
Adaptation Protocol
Adaptation Protocol
UDP
TCP SCTP
SCTP Main services
Acknowledged error-free, non-duplicated transfer of data
streams
Data fragmentation to conform to Message Transfer Unit (MTU)
size (Path MTU discovery built in)
Sequenced delivery of user messages within multiple streams
with an option for order of arrival and delivery of individual user
messages
Bundling of multiple user messages into a single SCTP packet
Multi-homing Network level fault tolerance at either or both ends
of an association
Heartbeat/Keep-alive mechanisms are integral part of the design
SCTP - What is a stream ?
A stream is a uni-directional flow of messages.
It is NOT a stream of bytes as in TCP.
Each SCTP association can have multiple streams allowing partial
ordering of messages.
Each side indicates how many outbound streams that it wants (OS)
and the maximum inbound streams (MIS) it can accept.
If a side cannot tolerate the number of streams it is limited to by the
other side it should ABORT the association.
Each side is limited to and agrees to min(OS,peers-MIS) if it accepts
the association.
SCTP How/when streams are used
Streams are used to provide a non-head-of-line blocking discipline
Common uses would be to route a given SLS from an SS7 link set
for ISUP over independent streams.
Another possible use might be to download and display in parallel
multiple pictures on a html page.
Another common use is H.248 signaling transport in a 3GPP or
TISPAN architecture
SG
SG
MGC
MGC
Network A
Network B
SG
SG
MGC
MGC
Network A
Network B
Held in the
Kernel Awaiting
Retransmission
SCTP Associations multi-homing
Machine " A" Machine " Z"
Network Y
Network X
Process2
Process2
Port 1120
Port 1120
IP:X2
IP:Y2
Process1
Process1
Port 2344
Port 2344
IP:Y1
IP:X1
Transport AddressA combination of an SCTP port and an IP address
EndpointA sender/receiver of SCTP packets, can be represented as a list of
transport addresses sharing the same SCTP port
AssociationA relationship or conversation between two endpoints
(in TCP we would call this a connection)
SCTP - Multi-Homing feature
SG
SG
MGC
MGC
Network A
Network B
Retransmission on B while checking status for A
Decreasing delay for failover recovery, more suitable for real-time
traffic
SACK = Selective
Acknowledgement
SACK = Selective
Acknowledgement
SG
SG
5 3 1
MGC
MGC
Network A
Network B
2
4
SCTP - SACK Built-In
SG
SG
4 2
MGC
MGC
Network A
Network B
Retransmission of dropped packets only instead of the entire group
as in TCP
SCTP - Heartbeat Built-In
SG
SG
MGC
MGC
Network A
Network B
HB
HB-ACK
While traffic is sent on streamA, HB is sent on streamB HB timer 30s
configurable
Allows proactive failure detection then recovery, similar to FISU in SS7
SCTP - Optional Unordered Delivery
SG
SG
MGC
MGC
Network B
Network A
6
6
U
U
2
2
5
5 1
For example, control message dont need to be ordered
Allows unreliable delivery ( U-SCTP )
SCTP bundling of Messages
Many of the message chunks can be bundled together.
Each message chunk is self descriptive, I.E. It describes its own
length.
Bundling is simply a matter of combining the chunks into one SCTP
datagram before transmission.
All chunks can be bundled with some exceptions, E.G., The following
types CAN NOT be bundled:
An INIT chunk
An INIT-ACK chunk
MTP2 TDM
M2PA/SCTP
MSU4
SCTP Chunk Bundling Timeout
(0 ~ 10 msec configurable)
FISUs will be terminated at ITP
FISU FISU MSU2 MSU1 MSU2 MSU1
0.4 Elrang
FISU FISUFISUFISU IP
Example: Up to 1480 bytes for Ethernet
MSU3
MSU2
MSU1
MSU4 MSU3 MSU2 MSU1 IP
Available Bandwidth
for Other MSU Transport
SCTP Bundling-Bandwidth Savings
SCTP Bundling-Bandwidth Savings (cont.)
8 Byte 200 Byte
ETH IP SCTP M2PA MSU
20 Byte 28 Byte 17 Byte 200 Byte
MTP1/2 MSU
64K Link IP SCTP Link
MSC
ITP ITP
Average Size of MSU : 200 Byte
Condition of Link Erlang : 0.4
No. of MSU per second : 16 ea
Average Size of MSU : 200 Byte
Condition of Link Erlang : 0.4
No. of MSU per second : 16 ea
Required IP BW for single Link :
279Byte * 16 * 8 = 35,712 bps (No bundle)
Required IP BW for single Link :
279Byte * 16 * 8 = 35,712 bps (No bundle)
14 Byte
208 Byte 279 Byte
ETH IP SCTP M2PA MSU SCTP M2PA MSU
20 Byte 28 Byte 17 Byte 200 Byte
Required IP BW for Bundled single Link :
(14+20+28+17+16+17) / 2 = 56 Byte (Header)
256Byte * 16 * 8 = 32,768 bps (2 Chunks bundled)
(14+20+28+17+16+17+16+17+16+17+16+17+16+17) / 6 = 41 Byte (Header)
241Byte * 16 * 8 = 30,848 bps (6 Chunks bundled Maximum 1480 )
Required IP BW for Bundled single Link :
(14+20+28+17+16+17) / 2 = 56 Byte (Header)
256Byte * 16 * 8 = 32,768 bps (2 Chunks bundled)
(14+20+28+17+16+17+16+17+16+17+16+17+16+17) / 6 = 41 Byte (Header)
241Byte * 16 * 8 = 30,848 bps (6 Chunks bundled Maximum 1480 )
14 Byte
512 Byte
16 Byte 17 Byte 200 Byte
SCTP common header 12 bytes
Chunk type 12 bytes
Chunk description 4 bytes
Agenda
SS7 background
SIGTRAN
SCTP
M2PA
M3UA
SUA
Sigtran in 3GPP
Applications
Adaptation Layer Protocols
ISUP/SCCP
ISUP/SCCP
MTP3
MTP3
SCTP
SCTP
IP
IP
ISUP/SCCP
ISUP/SCCP
SCTP
SCTP
IP
IP
TCAP/MAP
TCAP/MAP
SCTP
SCTP
IP
IP
IETF
Sigtran
SS7
SS7
ISUP/SCCP
ISUP/SCCP
MTP3
MTP3
SCTP
SCTP
IP
IP
Q.931
Q.931
SCTP
SCTP
IP
IP
M2UA
M2UA
M3UA
M3UA
SUA
(SCCP)
SUA
(SCCP)
M2PA
(Peer-to-peer)
M2PA
(Peer-to-peer)
IUA (Q.921)
IUA (Q.921)
M2PA
MTP2 Peer-to-Peer Adaptation Layer
M2PA defines a protocol supporting the transport of
SS7 MTP3 signaling messages over IP, using the services of SCTP
M2PA allows for full MTP3 message-handling and network-
management capabilities between any two SS7 nodes
communicating over an IP network
M2PA supports:
1. Operation of MTP3 protocol peers over an IP network connection
2. The MTP2/MTP3 interface boundary, management of SCTP transport
associations, and traffic instead of MTP2 links
3. Asynchronous reporting of status changes to management
MTP2 MTP2
MTP3 MTP3
MTP1 MTP1
M2PA M2PA
SCTP SCTP
IP IP
MTP2 MTP2
MTP1 MTP1
MTP3 MTP3
IP IP
SCTP SCTP
M2PA M2PA
MTP3 MTP3
MTP2 MTP2
MTP1 MTP1
SCCP
TCAP
MAP IS-41
I
S
U
P
MTP3 MTP3
MTP2 MTP2
MTP1 MTP1
SCCP
TCAP
MAP IS-41
I
S
U
P
SCTP
Associations
SEP SEP SEP SEP SS7 SG SS7 SG SS7 SG SS7 SG
SS7 SS7
SCTP/IP
MTP3 Adjacent
Nodes
TDM
TDM
PURE MTP3 Routing
M2PA - Architecture
IP
Network
M2PA - Architecture
Remote Remote
Existing TDM based SS7 Network
Before
STP1_1
STP1_2
STP2_1
STP2_2
MSC MSC
IP Core Network
After
SG2_1
SG2_2
Local Local
MSC MSC
SG1_1
SG1_2
M2PA
Reliability and dimensioning aspects
SG should have on TDM side
At least 2 linksets to the TDM node
Each linkset has the appropriate number of links
Usually each link is used at 0.4 Erlang
Each linkset has links distributed on different SS7 adpator
SG should have on IP side
Multi-homing defined on 2 separate NIC
Bandwidth required depends on bundling and traffic load
M2PA overhead
ETH IP SCTP M2PA MSU
20 Byte 28 Byte 17 Byte N Byte 14 Byte
Agenda
SS7 background
SIGTRAN
SCTP
M2PA
M3UA
SUA
Sigtran in 3GPP
Applications
MTP3 User Adaptation Layer (M3UA)
M3UA supports the transport of any SS7 MTP3 user signaling (e.g.
ISUP/SCCP), transparent to the MTP3-user, over IP; using the
services provided by SCTP
Allows flexible message distribution (e.g., SS7
OPC/DPC/SLS/CIC) to ASPs
Open/closes SCTP transport associations
n+k redundancy support (server pooling)
ASP fail-over support within AS list
Load-balancing support
Allows ASP signaling through redundant SGs to SS7 Network
MTP3
M3UA
SCTP
IP
MTP2
MTP1
N
I
F
ISUP/SCCP over MTP ISUP and SCCP messages
SEP SEP ASP ASP SS7 SG SS7 SG
IP
Network
M3UA
SCTP
IP
SCCP
TCAP
MAP IS-41
I
S
U
P
MTP2
MTP1
SCCP
TCAP
MAP IS-41
I
S
U
P
MTP3
SS7 SCTP/IP
SS7
Network
Signaling Gateway
M3UA - Architecture
M3UA - Architecture
Existing TDM based
SS7 Network
Before
STP2_1
STP2_2
MSC
HLR / SMC
STP1_1
STP1_2
After
HLR
/ SMSC
LAN Switch
SG1_1
SG1_2
SUA / M3UA / SCTP / IP
100Mbps/NIC
QoS Available
STP2_1
STP2_2
MSC
Existing TDM based
SS7 Network
SG2_1
SG2_2
MSC
M2PA / SCTP / IP
M3UA
SG should have on TDM side if any
Bandwidth required depends on bundling and traffic load
M3UA overhead for transfert message
ETH IP SCTP M3UA MSU
20 Byte 28 Byte
20 Byte 12 Byte
14 Byte
MSU header
N Byte
Agenda
SS7 background
SIGTRAN
SCTP
M2PA
M3UA
SUA
Sigtran in 3GPP
Applications
SUA - SCCP User Adaptation Layer
SUA defines a protocol for the transport of any SS7 SCCP user signaling,
mainly TCAP over IP using SCTP services
Designed to be modular and symmetric to allow it to work in diverse
architectures such as:
SG-to-IP signaling-endpoint
Peer-to-peer IP Signaling Endpoint
SUA supports the following:
Transfer of SCCP user part messages (TCAP, etc.)
SCCP connectionless service
SCCP connection oriented service
Management of SCTP transports associations between a SG and one or more
IP-based signaling nodes
Distributed IP-based signaling nodes
Asynchronous reporting of status changes to management
MTP3
SUA
SCTP
IP
MTP2
MTP1
I
W
F
SCCP
SCCP messages SCCP messages
Signaling Gateway
SEP SEP ASP ASP SS7 SG SS7 SG
IP
Network
SS7
Network
SS7 SCTP/IP
GTT GTT
SUA
SCTP
IP
TCAP
MAP IS-41
MTP2
MTP1
MTP3
SCCP
TCAP
MAP IS-41
SUA - Architecture
SUA - Architecture
Before
SMSC
IP Core Network
SG1_1
SG1_2
SG2_1
SG2_2
Router
LAN Switch
Router
LAN Switch
M2PA / SCTP / IP
MSC
After
IP Core Network
SMSC
LAN Switch
Router Router
SG1_1
SG1_2
M2PA / SCTP / IP SUA / SCTP / IP
Mated-SG
100Mbps/NIC
SG2_1
SG2_2
LAN Switch
MSC
TDM
links
SUA
SG should have on TDM side if any
Bandwidth required depends on protocol overhead and traffic load
Note each MAP message has up to 234 bytes ( 120 + SUA header )
SUA overhead is the following for connectionless data transfert
CLDT message
ETH IP SCTP SUA CLDT data
20 Byte 28 Byte
12 Byte 40 Byte
14 Byte
CLDT header
N Byte
Access
TDM
Signaling TDM Transport Network
Legacy
STP1_1
STP1_2
STP2_1
STP2_2
MSCs/Softswitch SMSC/HLR/IN
Access
TDM
Signaling Over IP, TDM as option
SS7oIP
IP Enabled STP
Access-Links
TDM
SUA or M3UA
MSCs/Softswitch
Signaling GW
SMSC/HLR/IN
Access-Links
TDM
SUA or M3UA
MTP1 MTP1 IP IP AAL5
MTP2 MTP2
MTP3b/MTP3 MTP3b/MTP3
SCTP SCTP
M2PA M2PA
M3UA M3UA
SUA SUA
SCCP/ISUP SCCP/ISUP
SCCOP
SSCF-NNI
IP or TDM
MTP3b Stack
HSL
SoIP Stack
SIGTRAN
Signaling Infrastructure: Migration to IP
Lower CAPEX and OPEX Preserving Fundamental SS7 Network Design
Agenda
SS7 background
SIGTRAN
SCTP
M2PA
M3UA
SUA
Sigtran in 3GPP
Applications
Gi
Sigtran in 3GPP
UMTS R5 architecture
GGSN
External VoIP
and IP MM Network
Legacy Mobile
Signaling Network
Application
and Services (SCP)
PSTN
Legacy/External
Application
and Services (SCP)
CS Domain
HLR HLR
EIR EIR
HSS HSS
BSC BSC
RNC RNC
BSS/
GERAN
UTRAN
Mw
Mm
Mg
Mr
Gi
Mc
Gi
Gi
Cx
C,D,Gc
Gc
Gn / Gp
Gf
Gr
Mc Mc
Nc
C
D
Mh
CAP
CAP
CAP
Nb
Gp
RANAP
Iu-ps
Iu-ps
Iu-cs
RANAP
RANAP
RANAP
VoIP Signal
VoIP Bearer
Legacy Signal
Legacy Bearer
Mi
Mj
Go
PS Domain
/ IM Domain
SGSN
CS-
MGW
SGW
SGW
GGSN
CS-
MGW
VLR
MSC
Server
GMSC
Server
SGW
SGW
MGC
BGCF CSCF
CSCF
MRFC/P MRFC/P
Candidate to SIGTRAN
Agenda
SS7 background
SIGTRAN
SCTP
M2PA
M3UA
SUA
Sigtran in 3GPP
Applications
Example - Customer M2PA network
Gateway-STP pair
Pair B
Internal
Pair A
OLOs
Internal
Pair C
SMSC
Pair D
M3UA
TDM
SLCs
M3UA
TDM
SLCs
SUA
M2PA core
Example - Customer deployment
TDM
SEP
TDM
SEP
IP
SEP
IP
SEP
STP
OLO
TDM
SEP
TDM
SEP
IP
MSC
IP
MSC
BTI
SMSC
IP
SCCPR
SCCPR
TDM
SEP
TDM
SEP
TDM
SEP
TDM
SEP
M3UA Associations
M2PA Associations (full mesh)
TDM signalling links
IP
HLR
IP
HLR
A mesh of M3UA
associations amongst
SigTran enabled MSCs,
HLRsand SCCP Relays
SigTran enabled
MSC
IP
MSC
IP
MSC
A full mesh of M2PA
associations only
between SGws(for
example an addition
of a SEP will not
change this mesh)
Note: the number of nodes in the diagram
does not represent the actual figures
An SCTP
association will
also be provisioned
between each co-
located SGs
Exemple
IP-enabled SMSC & Messaging Offload
SUA
SUA
SMSC
SMSC
O
p
e
n

M
e
s
s
a
g
i
n
g

G
a
t
e
w
a
y
Signaling & SMS Platform
STP
STP
MSC
MSC
MSC
MSC
-Increased bandwidth and capacity to SMSC
-Decreased signaling transport/infrastructure costs
M2PA
M2PA
MLR
MLR
SS7 LSL or HSL
ARD Application Routing Director
PSTN
HLR2
1) MAP SRI 2) MAP SRI
3) MAP SRI
w/ new
DPC/SSN
M3UA enabled AS
Exemple
Flexible numbering HLR Management
HLR1 HLRn
SRI = Where is mobile station?
Agenda
SS7 background
SIGTRAN
SCTP
M2PA
M3UA
SUA
Sigtran in 3GPP
Applications
Sigtran design rule of thumbs
Full physical and logical network redundancy is required in IP
networks carrying SIGTRAN (path diversity)
All L2 and L3 switches, routers and Gateways have to be fully
redundant (mated pairs) and carrier class
If QoS is used for SIGTRAN, QoS policies need to be configured and
enforced throughout the IP cloud
Routing protocols need to be appropriately configured to minimize
routing convergence times in case of network congestion and/or IP
node failure
MPLS VPNs may be used to segregate SIGTRAN traffic from other
types of traffic (GPRS, management, corporate etc..)
Refer to BRKMWI-3006 sessions
Sigtran design rule of thumbs
Basic SS7 design rules ALL apply
Use M2PA in the core (inter-STP) and TDM/ATM/xUA to the edge
(SMSC, SCP etc.)
Ensure bandwidth available for Max throughput rate in failover
scenario (remember erlang)
QoS and Traffic Engineering becomes essential if Network is
Shared
SCTP relies on IP and IP-based routing protocols. As such Ensure
appropriate IP design and appropriate routing protocol used
Average IP network delay should not exceed 50 ms, Maximum
delay should not exceed 100 ms
Why Sigtran and the ITP ?
Sigtran = SS7, everything old is new again
No more bandwidth limits with Sigtran!
The ITP supports all relevant SS7 (TDM and ATM) and
Sigtran (SUA, M3UA and M2PA) protocols in a any-to-
any fashion
The ITP is widely deployed and has a proven track
record for investment protection and interoperability
The ITP is available on multiple hardware platforms
The ITP is based on Cisco IOS and as such supports
many IP features for a true merge of the SS7 and IP
world
Q and A

Sigtran Connectuon by Cisco

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Sigtran Connectuon by Cisco

Transféré par

Droits d'auteur :

Formats disponibles

2008 Cisco Systems, Inc. All rights reserved.

Vous aimerez peut-être aussi