SIGTRAN Overview Training

Introduction to SigTran
An Alcatel-Lucent A5020 Solution
Prepared for Technical Training in GSE

Last update: May 1, 2007
All Rights Reserved Alcatel-Lucent 2007, #####
What is SIGTRAN ?
SIGTRAN
SIGTRANisisaaset
setof
ofprotocols
protocolsdefined
definedto
totransport
transportSS7
SS7messages
messagesover
overIP
IP
networks
networks
SIGTRAN
SIGTRANallows
allowsIP
IPnetworks
networksto
tointer-work
inter-workwith
withSwitches
SwitchesCircuit
CircuitNetwork
Network
(SCN)
(SCN)
MGC
MGC Media
MediaGateway
GatewayController
Controller
Call Control between SG and MG
Call Control between SG and MG
Controlling Access (IP PSTN)
Controlling Access (IP PSTN)
SG
SG Signalling
SignallingGateway
Gateway
Interface IP/SS7 networks
Interface IP/SS7 networks
Passing signalling messages to/from IP Nodes
Passing signalling messages to/from IP Nodes
MG
MG Media
MediaGateway
Gateway
Packetization of voice traffic
Packetization of voice traffic
Rate adaptation
Rate adaptation
Transmitting traffic towards the destination
Transmitting traffic towards the destination
SIGTRAN
All Rights Reserved Alcatel-Lucent 2007, Plano, TX, USA
2 | Introduction to SigTran |
SIGTRAN Stack
SIGTRAN
SIGTRANisiscomposed
composedof
ofthree
threeelements:
elements:
MAP/CAP/IN
TCAP
ISUP / BICC / TUP
Q.931
Adaptation layer, i.e. M2PA, M2UA, M3UA, etc

Adaptation layer, i.e. M2PA, M2UA, M3UA, etc
Stream Control Transmission Protocol (SCTP)
Stream Control Transmission Protocol (SCTP)
Standard IP stack
Standard IP stack
SCCP
SUA
(RFC 3868)
MTP3
IUA
(RFC 3057)
M3UA
(RFC 4666)
M2PA
(RFC4165)
M2UA
(RFC 3331)
SCTP
(RFC 2960)
IP
ALCATEL-LUCENT Solution
About Adaptation Layers
M2UA
M2UAMTP2
MTP2User
UserAdaptation
Adaptationlayer.
layer.MTP2-MTP3
MTP2-MTP3communication
communicationisis
remote
remoteand
andare
areM2UA
M2UAmessages.
messages.They
Theyare
arenon-primitives
non-primitivessent
sent
over
overIP.
IP.SG
SGisisnot
notan
anSS7
SS7node
nodeas
asthere
thereisisno
noMTP3
MTP3[RFC3331]
[RFC3331]
M2PA
M2PAMTP2
MTP2Peer-to-Peer
Peer-to-PeerAdaptation
Adaptationlayer
layerprovides
providespeer-to-peer
peer-to-peer
communication
communicationbetween
betweentwo
twoendpoints.
endpoints.MTP2-MTP3
MTP2-MTP3
communication
communicationisislocal
localand
anduses
usesstd
stdprimitives
primitives[RFC4165]
[RFC4165]
M3UA
M3UA--MTP3
MTP3User
UserAdaptation
Adaptationlayer
layersupports
supportsMTP3
MTP3functions
functionsand
and
provides
providestransport
transportof
ofMTP3-User
MTP3-Usersignaling
signalingover
overIPIP[RFC4666]
[RFC4666]
SUA
SUA
IUA
IUA
--SCCP
SCCPUser
UserAdaptation
Adaptationlayer
layersupports
supportsthe
thetransport
transportof
ofSCCP
SCCP
signaling
signalingover
overIP
IPusing
usingSCTP
SCTPwithout
withoutMTP3
MTP3[RFC3868]
[RFC3868]
-- ISDN
ISDNUser
UserAdaptation
Adaptationlayer
layersupports
supportsthe
thetransport
transportof
ofISDN
ISDN
signaling
signalingdirectly
directlybetween
betweenSG-MGC
SG-MGCover
overIP
IP[RFC3057]
[RFC3057]
Differences between M2UA and M2PA

AA: :M2UA:
M2UA:MTP2/MTP3
MTP2/MTP3(remote)
(remote)communication
communicationisis
defined
definedas
asM2UA
M2UAmessages
messagesand
andsent
sentover
overthe
the
IPIPconnection.
connection.
M2PA:
M2PA:IPSP
IPSPprocesses
processesMTP2/MTP3
MTP2/MTP3primitives.
primitives.
M
2
U
A
B:
B:M2UA:
M2UA:SG-MGC
SG-MGCconnection
connectionisisnot
notan
anSS7
SS7link.
link.
ItItisisan
extension
of
MTP
to
a
remote
entity.
an extension of MTP to a remote entity.
M2PA:
M2PA:SG-IPSP
SG-IPSPconnection
connectionisisan
anSS7
SS7link.
link.
C:
C:M2UA:
M2UA:SG
SGisisnot
notan
anSS7
SS7node
nodeand
andhas
hasno
nopoint
point
code.
code.
M2PA:
M2PA:SG
SGisisan
anSS7
SS7node
nodewith
withaapoint
pointcode.
code.
D:
D:M2UA:
M2UA:SG
SGdoes
doesnot
nothave
haveupper
upperSS7
SS7layers
layers
since
it
has
no
MTP3.
since it has no MTP3.
M2PA:
M2PA:SG
SGcan
canhave
haveupper
upperSS7
SS7layers,
layers,e.g.,
e.g.,
SCCP.
SCCP.
M
2
P
A
E:
E:M2UA:
M2UA:uses
usesM2UA
M2UAmanagement
managementprocedures.
procedures.
M2PA:
relies
on
MTP3
for
management
M2PA: relies on MTP3 for management
procedures.
procedures.
Why M3UA is chosen for mobile applications ?
M2UA
M2UAisisnot
notsuitable
suitable
designed
designedfor
forMTP2
MTP2backhauling
backhauling(invocation
(invocationof
ofremote
remoteMTP2
MTP2layer)
layer)
no
nofull
fullIPIPpeer
peerto
topeer
peermode,
mode,only
onlyIP-SS7
IP-SS7legacy
legacyinterworking
interworking
example
example::relay
relayof
oflegacy
legacySS7
SS7associated
associatedsignalling
signallingterminated
terminatedat
ataaMGW
MGW
toward
towardaaMGC
MGCthrough
throughIPIP
SUA
SUAisisnot
notsuitable
suitable
unable
unableto
totransport
transportISUP
ISUP&&BICC
BICCsignaling
signaling(SCCP
(SCCPonly)
only)
IUA
IUAisisnot
notsuitable
suitable
unable
unableto
totransport
transportISUP
ISUP&&BICC
BICCsignaling
signaling(ISDN
(ISDNonly)
only)
M2PA
M2PAcould
couldhave
havebeen
beensuitable
suitable
only
onlypeer
peerto
topeer
peermode,
mode,aalegacy
legacy SS7
SS7link
linkisisreplaced
replacedby
byan
anSS7
SS7IPIP
link
link(an
(anSCTP
SCTPassociation)
association)
MTP3
MTP3management
managementisiskept
keptunchanged
unchanged
M2PA
M2PAenabled
enabledSTP
STP(which
(whichisisnot
notpopular)
popular)needed
neededininnetworks
networks
SCTP
Stream Control Transmission Protocol

RFC2960
Motivation Why SCTP, but not TCP?

The
TheProblem
Problemwith
withTCP:
TCP:
TCP
TCPisisbyte-streamed.
byte-streamed.ItItprovides
providesaasingle
singlestream
streamof
ofdata
dataand
andguarantees
guarantees
that
thatdata
datato
tobe
bedelivered
deliveredin
inbyte-sequence
byte-sequenceorder
order
TCP
TCPisissensitive
sensitiveto
todelays
delayscaused
causedby
bynetwork
networkerrors
errors(loss
(lossof
ofbytes,
bytes,messages
messages
or
orsequence
sequenceviolation)
violation)
InIncase
caseerror
erroroccurs,
occurs,TCP
TCPwill
willhold
holdup
updelivery
deliveryof
ofall
alldata
data
For
Forexample:
example:IfIfTCP
TCPwere
wereused
usedfor
fordelivering
deliveringISUP
ISUPmessages,
messages,the
theloss
lossof
ofone
one
message
messagerelevant
relevantto
toone
onetelephone
telephonecall
callwould
wouldresult
resultininthe
thedelay
delayof
ofall
allother
other
ISUP
ISUPmessages
messages
The Solution
TCP
New Concepts
Multi-homing
Multi-streaming
Cookie and Bundling
Flow Control
Congestion Control
UDP
Unreliable
Message-based
Reliable
Sessions
Connection-less
Fragmentation
Framing
Fault correction
SCTP
SCTP Functional Overview
SCTP
SCTPcarrier-grade
carrier-gradeperformance
performanceisisassured
assured
by
bythe
thefollowing
followingfunctions:
functions:
Acknowledged
Acknowledgederror-free
error-freenon-duplicated
non-duplicated
transfer
of
signaling
information
transfer of signaling information
In-sequence
In-sequencedelivery
deliveryof
ofmessages
messageswithin
within
multiple
streams
multiple streams
Message
Messageoriented,
oriented,rather
ratherthan
thanbytes
bytes
oriented
as
in
TCP
oriented as in TCP
Capable
Capableof
ofbundling
bundlingmultiple
multiplemessages
messagesinto
into
aasingle
SCTP
packet
single SCTP packet
Data
Datafragmentation
fragmentationas
asrequired
required
Network-level
Network-levelfault
faulttolerance
tolerancethrough
through
support
of
multi-homing
at
either
support of multi-homing at eitheror
orboth
both
ends
endsof
ofan
anassociation
association
Congestion
Congestionavoidance
avoidanceand
andresistance
resistanceto
to
flooding
(denial-of-service)
and
masquerade
flooding (denial-of-service) and masquerade
attacks
attacks
Key SCTP Features:
Message
Messageoriented
orientedrather
ratherthan
thanbyte
byteoriented
oriented
Support
Supportmulti-stream
multi-streamcapability,
capability,i.e.
i.e.transmit
transmitdata
datathrough
throughmultiple
multiple
streams,
streams,each
eachwith
withindependent
independentsequenced
sequenceddelivery.
delivery.The
Thenumber
numberof
of
incoming
incomingand
andoutgoing
outgoingstreams
streamsisisnegotiated
negotiatedwhen
whenassociation
associationisis
established
established
Support
Supportmulti-homing,
multi-homing,i.e.
i.e.each
eachSCTP
SCTPendpoint
endpointmay
maybe
beknown
knownby
by
multiple
multipleIP
IPaddresses.
addresses.IfIfone
oneroute
routebecomes
becomesunavailable,
unavailable,another
anotherwill
will
be
beused.
used.
SCTP: Multi-Stream
To deliver ISUP messages there is a need to decouple messages based on

the calls (such as CIC) so that messages associated with different calls
can be delivered independently
Call 1
Call 2
Call 2
Call 3
Call 3
With multi-stream
Calls 2 & Call 3 are
processed normally.
SCTP: Multi-Stream
An
AnSCTP
SCTPpacket
packetmay
maybe
becomposed
composedof
ofmultiple
multiplechunks
chunks(contains
(containsSS7
SS7
messages)
messages)which
whichbelong
belongto
tomultiple
multiplestreams
streams
Chunks
Chunksare
arequeued
queuedififnecessary
necessaryand
andthen
thendelivered
deliveredto
toSCTP
SCTPUser
UserPart
Partin
in
sequence
sequenceper
perstream
stream
Multi-homing
Endpoint
EndpointAssociation
Associationisiscomposed
composedevenly
evenlyof
ofseveral
severalpaths
paths
Only
Onlyone
onepath
pathisisactive
activeat
ataagiven
giventime
time
Paths
Pathsare
aremonitored
monitoredto
todetect
detectfailures
failuresvia
viaexchanging
exchangingHeartbeat
Heartbeat
Active Path
Data & Acks
Heartbeats / Acks
inactive Path
SCTP Key Terms

Chunk
A unit of information within an SCTP packet, consisting of a chunk header and chunk-specific content (Init, Ack, Data,).
SCTP Packet
The unit of data delivery across the interface between SCTP and the connectionless packet network (e.g., IP). An SCTP
packet includes (i) common SCTP header, (ii) possible SCTP control chunks, and (iii) user data encapsulated within SCTP
DATA chunks.
Transmission Sequence Numbers (TSN)

A 32-bit sequence number used internally by SCTP. One TSN is attached to each chunk containing user data to permit the
receiving SCTP endpoint to acknowledge its receipt and detect duplicate deliveries.
Signalling Endpoint (SEP)

The logical sender/receiver of SCTP packets. On a multi-homed host, an SCTP endpoint is represented to its peers as a
combination of a set of eligible destination transport addresses to which SCTP packets can be sent and a set of eligible
source transport addresses from which SCTP packets can be received. All transport addresses used by an SCTP endpoint
must use the same port number, but can use multiple IP addresses. A transport address used by an SCTP endpoint must
not be used by another SCTP endpoint. In other words, a transport address is unique to an SCTP endpoint.
Association
A protocol relationship between SCTP endpoints, composed of the (i) two SCTP endpoints and (ii) protocol state
information including Verification Tags and the currently active set of Transmission Sequence Numbers (TSNs), etc. An
association can be uniquely identified by the transport addresses used by the endpoints in the association. Two SCTP
endpoints MUST NOT have more than one SCTP association between them at any given time.
Stream
A uni-directional logical channel established from one to another associated SCTP endpoint, within which all user
messages are delivered in sequence except for those submitted to the unordered delivery service
Illustration of SCTP Association Path and Stream

Stream in each path
SCTP USER
SCTP USER
Transport Address
SCTP
IP Address
SCTP
Primary Path
Port
IP
SCTP End Point
IP
Path
SCTP End Point

Association
Illustration of SCTP Streams, Packets and Chunks

SS7 Network
Element
SS7 Network
Element
User Adaption Layer
User Adaption Layer

User Data
Uses
SCTP
SCTP
SCTP Association
end point
end point
Rx Stream_1
Rx Stream_j
Tx Stream_1
Tx Stream_k
SCTP
Layer
SCTP
Layer
IP datagram
IP Layer
SCTP
packet
DATA chunks
20
12
Message 1
4 Message 2
IP header
SCTP common header
DATA chunk header

SCTP control chunks
IP Layer
SCTP Packet Format
SCTP
SCTPpacket
packetisiscomposed
composedof
ofaacommon
commonheader
headerand
andchunks.
chunks.AA
chunk
chunkcontains
containseither
eithercontrol
controlor
oruser
userdata
data
Multiple
Multiplechunks
chunkscan
canbe
bebundled
bundledinto
intoone
oneSCTP
SCTPpacket
packetup
upto
tothe
the
MTU
MTUsize,
size,except
exceptfor
forINIT,
INIT,INIT-ACK,
INIT-ACK,and
andSHUNTDOWN
SHUNTDOWNCOMPLETE
COMPLETE
chunks.
chunks.
IfIfuser
userdata
datamessage
messagedoes
doesnot
notfit
fitinto
intoone
oneSCTP
SCTPpacket,
packet,ititcan
canbe
be
fragmented
fragmentedinto
intomultiple
multiplepackets
packets
Bits
+0
Bits 0 - 7
8 - 15
16 - 23
Source port
Destination port
32
Verification tag
64
Checksum
96
Chunk 1 type
Chunk
1
flags
Chunk 1 length
Chunk
N
flags
Chunk # 2
Chunk # 3
Chunk 1 data
Chunk N
type
Common Header
Chunk # 1
128
24 - 31
Chunk # 4
Chunk N length
Chunk N data
Chunk # n
MTU Max Transmission
Unit
SCTP Chunk Format

Bits 0 - 7
Chunk
type
8 - 12
13
Reserved
14
15
16 31
Chunk
length
TSN
TSN
Stream
SSN
Sequence
number
Stream Identifier
Payload protocol identifier
Data
EEach
achchunk
chunkhas
hastwo
twosequence
sequencenumbers:
numbers:
Transmission
TransmissionSequence
SequenceNumber
Number(TSN)
(TSN)isis
attached
attachedto
toeach
eachchunk
chunkininan
anincreasing
increasingorder
order
ininaapkt.
pkt.ItItisisused
usedfor
forper-association
per-associationreliability
reliability
ID
IDValue
Value Chunk
ChunkType
Type
----------------------- ------------------------------------------------------00
- -Payload
PayloadData
Data(DATA)
(DATA)
11
- -Initiation
(INIT)
Initiation (INIT)
22
- -INIT
INITACK)
ACK)
33
- -Selective
SelectiveACK
ACK(SACK)
(SACK)
44
- -HEARTBEAT
HEARTBEAT
55
- -HEARTBEAT
HEARTBEATACK
ACK
66
- -ABORT
ABORT
77
- -SHUTDOWN
SHUTDOWN
88
- -SHUTDOWN
SHUTDOWNACK
ACK
99
- -ERROR
ERROR
10
COOKIE
10
- COOKIEECHO
ECHO
11
COOKIE
ACK
11
- COOKIE ACK
14
- -SHUTDOWN
14
SHUTDOWNCOMPLETE
COMPLETE
Stream
StreamSequence
SequenceNumber
Number(SSN)
(SSN)isisthe
thecurrent
current
chunk
chunknumber
numberof
ofthe
thepiece
pieceinside
insidethe
thespecific
specific
stream.
It
is
for
per-stream
ordering
stream. It is for per-stream ordering
U Un-ordered bit
B Beginning fragment bit
E Ending fragment bit
Four-WAY Association Establishment
HHow
owcan
canSCTP
SCTPprotect
protectagainst
against
denial
denialof
ofservice
serviceattacks?
attacks?
AAcookie
cookieisisininthe
theINIT-ACK
INIT-ACK
sent
from
server
to
sent from server toclient.
client.
Server
Serverdoes
doesnot
notallocate
allocateTCB
TCB
and
andresource
resourceor
orafter
afterINIT.
INIT.
TCB
TCBisisderived
derivedfrom
fromthe
the
cookie
cookiesent
sentback
backfrom
fromthe
the
client
in
COOKIE-ECHO.
client in COOKIE-ECHO.
The
Theserver
serverhas
hasno
noknowledge
knowledgeof
of
the
theassociation
associationuntil
untilthe
theclient
client
responds
respondswith
withaaCOOKIE-ECHO,
COOKIE-ECHO,
ititbecomes
becomesresilient
resilientto
toDoS
DoS
attacks.
attacks.
Endpoint A
set asso w/ Z
build TCB
start T1-init
state=CK-WAIT
stop T1-init
copy cookie buf
send CK-Echo
start T1-C-ECHO
State=CK-ECHO
Endpoint Z
INIT (MOS, MIS, list of IP, A1, A2,..)
INIT-ACK (cookie, list of IP, Z1, Z2,..)
COOKIE-ECHO (cookie, data)
stop T1-C-ECHO
state=ESTABLISH
Stop T3-rtx
compute MAC
based on cookie
authenticate
compare time
rebuild TCB
save resource
send cookie-ack
ack data chunk
DATA
MAC
: Message Authentication Code
MOS : Max # of OG Stream
TCB
: Transmission Control Block
MIS : Max # of IN Stream
Cookie : A subset of association info required
to re-create TCB and its resultant MAC
COOKIE-ACK (SAK)
build temp TCB

calculate MAC
build cookie
send INIT-ACK
delete TCB
delete resource
Selective Acknowledgement (SACK)
Every
Everychunk
chunkin
inaapacket
packetsent
sentout
outby
bySTCP
STCPmust
mustbe
beacknowledged
acknowledged
IfIfacknowledge
acknowledgechunk
chunkXXisisnot
notreceived
received(GAP
(GAPisisdetected),
detected),retransmission
retransmission
of
ofthe
thechunk
chunkXXisis performed
performed
Acknowledges
Acknowledgescan
canbe
becumulated
cumulatedand
andsent
sentout
outwithin
withinone
oneSACK
SACKmessage
message
Multiple
MultipleGAPs
GAPscan
canbe
bereported
reportedininone
oneSACK
SACKmessage
message
Criteria of retransmission
Retransmission
Retransmissionoccurs
occurswhen
when
Timeout
Timeout
SACK
SACKcontains
containsTSN
TSNGap
Gap
The
Theactual
actualvalue
valueisis
the
theoffset
offsettotothe
thenext
next
received
chunk
received chunk
(2)
(4)
SCTP Common header

12
IP header
20
(2)
(5)
The
Theoffset
offsettotothe
theend
end
ofofreceived
receivedblock
block
SACK chunk
SCTP packet
SAK
Chunk: A unit of info in an SCTP packet
: Selective Acknowledgement
M3UA
MTP3-User Adaptation Layer
RFC4666
What is M3UA and What is not?

What
WhatisisM3UA?
M3UA?
M3UA
M3UAstands
standsfor
forMTP3
MTP3User
UserAdaptation
AdaptationLayer
Layerand
andisisdefined
definedininRFC4666
RFC4666
M3UA
M3UAprovides
providestransport
transportof
ofMTP3-User
MTP3-Usersignaling,
signaling,e.g.,
e.g.,ISUP,
ISUP,TUP
TUPand
andSCCP
SCCP
messages,
messages,over
overIP
IPusing
usingSCTP.
SCTP.
M3UA
M3UAprotocol
protocolcan
canbe
beused
usedbetween
betweenSG
SGand
andMGC
MGCor
orbetween
betweentwo
twoMGCs.
MGCs.
M3UA
M3UAprovides
providesaaequivalent
equivalentset
setof
ofprimitives
primitivesat
atits
itsupper
upperlayers
layersas
as
provided
providedby
byMTP3
MTP3to
toits
itslocal
localusers.
users.
What
WhatisisM3UA
M3UAnot?
not?
M3UA
M3UAisisnot
notan
anMTP3
MTP3over
overIP.
IP.M3UA
M3UAdoes
doesnot
notprovide
providesome
someof
ofthe
theservices
services
in
inMTP3.
MTP3.
For
Forexample,
example,M3UA
M3UAon
onSG
SGdoes
doesnot
notsupport
supportMTP3
MTP3network
networkmanagement
management
messages,
messages,such
suchas
asTFA,
TFA,TFP,
TFP,etc.
etc.
M3UA Protocol Architecture
NIF
NIF
SEP or STP
TCAP
TCAP
SCCP
SCCP
SG (STP)
A7570
I
I
S
S
U
U
P
P
MGC
A5020
TCAP
TCAP
NIF
NIF
SCCP
SCCP
I
I
S
S
U
U
P
P
MTP3
MTP3
MTP3
MTP3
M3UA
M3UA
M3UA
M3UA
MTP2
MTP2
MTP2
MTP2
SCTP
SCTP
SCTP
SCTP
MTP1
MTP1
MTP1
MTP1
IP
IP
IP
IP
SS7 Network
SS7 Network
IP Network
IP Network
NIF
NIFisisthe
theinterface
interfacebetween
betweenMTP3
MTP3
and
andM3UA.
M3UA.ItItprovides
providesseamless
seamless
mapping
mappingbetween
betweenMTP3
MTP3and
andM3UA
M3UAon
on
Signalling
SignallingGateway.
Gateway.ItItperforms
performs
protocol
protocoltermination,
termination,translation
translation
and
anduser
userpart
partprotocol
protocol
encapsulations.
encapsulations.
Main
Mainfunctions
functionsof
ofNIF:
NIF:
Exchange data messages
Exchange data messages
between
betweenSS7
SS7and
andIPIPnetworks
networks
SEP
SEP - -SS7
SS7Signalling
SignallingEndpoint
Endpoint
STP
STP - -SS7
SS7Signalling
SignallingTransfer
TransferPoint
Point
Relay IP or SS7 messages back to

Relay IP or SS7 messages back to
the
theoriginator
originatorininthe
thesame
same
format
format
SG
SG - -Signalling
SignallingGateway
Gateway
MGC
MGC Media
MediaGateway
GatewayController
Controller
NIF
NIF--Nodal
NodalInter-working
Inter-workingFunction
Function
Provide global network

Provide global network
management
managementservices
servicesininsupport
support
ofofdata
flows
between
MTP3
data flows between MTP3and
and
M3UA
layers
M3UA layers
M3UA Network Entities
SEP - SS7 Signalling Endpoint

STP - SS7 Signalling Transfer Point
SG - Signalling Gateway
AS Application Server
IPS IP Server
IWF - Interworking Function = NIF
M3UA Terms
SS7
Signalling
SignallingGateway
Gateway(SG):
(SG):
SG
SGisisaasignalling
signallingagent
agentcapable
capableof
ofsending
sending//
receiving
receivingSwitched
SwitchedCircuit
CircuitNetwork
Network(SCN)
(SCN)native
native
messages
at
the
edge
of
the
SS7
/
IP
networks.
messages at the edge of the SS7 / IP networks.
SG
SGcontains
containsone
oneor
ormore
moreSignalling
SignallingGateway
GatewayProcess
Process
(SGP)
providing
serves
as
an
active,
backup,
load(SGP) providing serves as an active, backup, loadsharing
sharingor
orbroadcast
broadcastprocess
process
IP
SG
AS
SGP1
ASP1
IP
SGP2
ASP2
AS
AS
IPSP1
IPSP1
Application
ApplicationServer
Server(AS):
(AS):
AS
ASisisaalogical
logicalentity,
entity,such
suchas
asvirtual
virtualswitch
switchor
or
database
element
capable
of
handling
call
database element capable of handling call
processing
processing//transaction
transactionfor
foraaspecific
specificrouting
routingkey
key
AS
ASisisidentified
identifiedby
byaarouting
routingkey,
key,which
whichisisaaset
setof
of
SS7
parameters,
such
as
SIO/OPC/DPC/SSN.
SS7 parameters, such as SIO/OPC/DPC/SSN.
AS
ASisismodelled
modelledas
asone
oneor
ormore
moreApplication
ApplicationServer
Server
Processes
(ASP),
Signalling
Gateway
Process
Processes (ASP), Signalling Gateway Process(SGP)
(SGP)
or
IP
Server
Process
(IPSP)
or IP Server Process (IPSP)
IP
IPSP2
IPSP2
Signalling Peer Processes
Application
Application Server
Server Process
Process (ASP):
(ASP):
AAprocess
processinstance
instanceof
ofan
anApplication
ApplicationServer,
Server,such
suchas
asMGC,
MGC,IP
IPSCP,
SCP,or
orIP
IPHLR.
HLR.
An
AnApplication
ApplicationServer
ServerProcess
Processserves
servesas
asan
anactive
activeor
orbackup
backupprocess
processof
ofan
an
Application
ApplicationServer
Server
An
AnASP
ASPcontains
containsan
anSCTP
SCTPendpoint
endpointand
andmay
maybe
beconfigured
configuredto
toprocess
process
signalling
signallingtraffic
trafficfor
formore
morethan
thanone
oneApplication
ApplicationServers.
Servers.
IP
IPServer
Server Process
Process (IPSP):
(IPSP):
AAprocess
processinstance
instanceof
ofan
anIP-based
IP-basedapplication.
application.An
AnIPSP
IPSPisisessentially
essentiallythe
the
same
sameas
asan
anASP,
ASP,except
exceptthat
thatitituses
usesM3UA
M3UAininaapoint-to-point
point-to-pointfashion.
fashion.
Conceptually,
Conceptually,an
anIPSP
IPSPdoes
doesnot
notuse
use(interface
(interfacewith)
with)the
theservices
servicesof
ofaa
Signalling
SignallingGateway
Gatewaynode.
node.
Signalling
Signalling Gateway
Gateway Process
Process (SGP):
(SGP):
An
AnApplication
ApplicationProcess
Processinstance
instancerunning
runningon
onSG.
SG.ItItisisidentified
identifiedby
byaaunique
unique
SCTP
SCTPendpoint.
endpoint.
Illustration of AS, ASP, SGP, IPSP, Routing Key and Routing Context
NGN NODE
AS1
Routing Key10ax1
ASP 1
Routing Key10ax2
RC1
ASP n
Routing Key10axn
Signaling Gateway
SCTP
endpoint
NIF
SGP 1
IP
networks
Routing Key10x1
Routing Key10x2
SGP n
Routing Key10xn
MTP3
RC M3UA MTP3
SCTP
SCTP MTP2
MTP2
IP
IP
SS7
networks
1
MTP1
MTP1
2
AS2
IPSP 1
Routing Key10b
x1
SCTP
association
s
NGN NODE
Routing Key10b
x2
RC2
IPSP 2
IPSP 1
Routing Key10b
xn
IP networks
AS3
IPSP 1
IPS
Routing Key10xz
Routing Key10xz
RC
Routing Key10xc1
IPSP n
Routing Key10xc2
RC3
IPSP n
Routing Key10xzn
Routing Key10xcn
RC Routing Context. A value that uniquely identifies a Routing Key

to represent Application Server (AS).
M3UA SS7/IP Network Architecture
AS
AS 1
AS
AS 2
Load-sharing
M3UA
M3UA
SCTP
SCTP
ASP
ASP 1
1
SCTP
endpoint
ASP
ASP n
n
IP
IP node
node
IP
IP
SCTP
association
Load-sharing
IP domain
SS7 domain
NOTES:
NOTES:
AS1
AS1isisprocessing
processingMAP
MAP
protocol
for
the
point
protocol for the pointcode
codeAAinin
SS7
SS7network
network11
IP networks
Load-sharing
SGP
SGP 1
1
SS7
network
3
SG1
SG1
SGP
SGP n
n
SGP
SGP 1
1
A
SS7
network 1
Load-sharing
SG2
SG2
SGP
SGP n
n
SS7
network
2
AS2
AS2isisprocessing
processingISUP
ISUP
protocol
for
the
point
protocol for the pointcode
codeAAinin
SS7
SS7network
network11
nnxxASP
ASPserve
servethe
theAS1
AS1&&AS2
AS2
ininaaload-sharing
manner
load-sharing manner
Signaling
SignalingGateway
GatewaySG1
SG1gives
gives
access
to
SS7
network
1
access to SS7 network 1&&33
Signaling
SignalingGateway
GatewaySG2
SG2gives
gives
access
to
SS7
network
1
access to SS7 network 1&&22
From
FromSS7
SS7network
network1,1,SG1
SG1&&
SG2
SG2are
areseen
seenas
asSTPs
STPs
ASPs
ASPsload
loadshare
sharetraffic
traffic
between
betweenSGs
SGsand
andbetween
between
SGPs
in
SG1
and
SG2
SGPs in SG1 and SG2
OPC: X
SPC
SPC
IP
SG
DPC: Z
PC:
PC: Z
SPC
SPC
DPC: X
MGC
IP
PC:
PC: Y
Y
IF OPC: X
IF DPC: Y
SG
OPC: Z
MGC
PC:
PC: X
X
OPC:Y
DPC:X
DATA
PC:
PC: Z
DATA
M3UA modes
SPC
SPC
Pipe
DPC: Z
OPC: Y
DATA
DATA
OPC: Z
DPC: Y
SS7 network
Backhauling
Backhaulingmode
mode
Internally MG and MGC share the same Signalling
Internally MG and MGC share the same Signalling
Point
PointCode
Code(SPC)
(SPC)
M3UA is used to transfer MTP3 primitives between
M3UA is used to transfer MTP3 primitives between
SG
SGand
andMGC.
MGC.
The link between SG-MSC is not an SS7 link
The link between SG-MSC is not an SS7 link
M3UA is transparent to MTP3 User layers, such as
M3UA is transparent to MTP3 User layers, such as
ISUP/BICC/SCCP.
ISUP/BICC/SCCP.
SS7
network
STP
STPMode
Mode
From SS7 network, SG is seen as an STP
From SS7 network, SG is seen as an STP
MG and MGC have different SS7 Point
MG and MGC have different SS7 Point
Codes.
Codes.
SG functions as an STP, but not exactly
SG functions as an STP, but not exactly
SG is required to perform Point Code
SG is required to perform Point Code
Translation
Translation
Router
AS-SG-SEP Model (AS/SG Model)
SEP
MAP
AS
MAP
SG
TCAP
TCAP
SCCP
Interworking Fct
MTP3
MTP3
M3UA
M3UA
MTP2
MTP2
SCTP
SCTP
MTP1
MTP1
IP
IP
SS7
SCCP
This
Thismodel
modelallows
allowsan
anIPIPnode
nodeto
to
dialog
with
legacy
SS7
node
dialog with legacy SS7 node
through
throughthe
theinter-working
inter-workingof
ofaa
signaling
signalinggateway
gateway
IP
Non
Non standardized
standardized
M3UA
M3UA SG-SG
SG-SG
communication
communication or
or
legacy
legacySS7
SS7 links
links
IP node
SG
AS
AS : :Application
ApplicationServer
Server
SEP:
Signaling
End
SEP: Signaling EndPoint
Point
IP
domain
SG
IP node
STP
SEP
IP node
SG
SG : :Signaling
SignalingGateway
Gateway
SEP
STP
SS7
legacy
SEP
IPS-IPS Model
IPS
IPS
MAP
MAP
TCAP
TCAP
SCCP
SCCP
M3UA
M3UA
SCTP
SCTP
IP
IP
This model allows to build a full SS7oIP network using M3UA

No extra-hop SG is needed between the IP nodes (less
overhead)
IP
IP node
It leads to a network with a flat organization and has the following

It leads to a network with a flat organization and has the following
consequences
consequencesfor
forlarge
largenetworks
networks: :
All Network Elements that have to dialog each other have to be interAll Network Elements that have to dialog each other have to be interconnected
connectedthrough
throughaamesh
meshofofSCTP
SCTPassociation
association
The number of SCTP associations increases with the number of NE in
The number of SCTP associations increases with the number of NE in
the
thenetwork,
network,ififSCTP
SCTPmulti-homing
multi-homingisisused
usedtotoprovide
providenetwork
networkpath
path
resilience,
SCTP
heartbeat
traffic
flows
on
inactive
paths
also
resilience, SCTP heartbeat traffic flows on inactive paths also
increases,
increases,thus
thusdemanding
demandingmore
morenetwork
networkbandwidth
bandwidthand
andCPU
CPUpower
power
Depending on the NEs architecture/implementation, signaling
Depending on the NEs architecture/implementation, signaling
capacity
capacityextension
extensionofofone
oneNE
NEcan
canlead
leadtotoconfiguration
configurationimpacts
impactson
onall
all
other
NEs
it
is
connected
to
other NEs it is connected to
IP node
IP
domain
IP node
M3UA Protocol
M3UA
M3UAHeader
Header
Version:
Version:88bits
bitsof
ofversion
versionnumber
number
Class:
Class:
Type:
Type:
88bits
bitsof
ofmessage
messageclass
class
88bits
bitsof
ofmessage
messagetype
type(refer
(referto
to
section
3.1.2
RFC
4666)
section 3.1.2 RFC 4666)
Length:
Length: 32
32bits
bitsof
ofmessage
messageininbytes,
bytes,incl.
incl.
header
and
parameter
padding
header and parameter padding
Data:
Data: Variable
Variablelength,
length,contains
contains
parameters,
if
any
parameters, if any
M3UA protocol
Single ASP in Application Server
Single ASP in an Application Server
Dynamic Registration Client sends RC and RK to server
No Registration RC is provisioned
SGP
ASP1
ASP UP
SGP
ASP1
Ready to receive
ASP Sate Mgt Msg
ASP UP
ASP UP ACK
ASP UP ACK
NTFY (AS-INACTIVE) (RCn)
NTFY not sent

if IPSP-IPSP
Register Req (LRCn, RKn)

Register RESP (LRCn, RKn)
ASP ACTIVE (RCn)
NTFY (AS-INACTIVE) (RCn)
ASP ACTIVE ACK (RCn)

ASP ACTIVE (RCn)
NTFY (AS-ACTIVE) (RCn)
ASP ACTIVE ACK (RCn)
NTFY (AS-ACTIVE) (RCn)
LRC: Local Routing Key ID
RC : Routing Context
RK : Routing Key
SigTran
An Alcatel-Lucent A5020 Solution
SigTran An Alcatel-Lucent A5020 Solution
System
SystemCapability
Capabilityand
andLimitation:
Limitation:
--WCS
WCSsupport
supportASP/IPSP
ASP/IPSP
--Max
Maxnumber
numberof
ofPeer
PeerServer
ServerProcess
Process(PSP)
(PSP)supported:
supported:40
40(TBD)
(TBD)
--Max
Maxnumber
numberof
ofPeer
PeerApplication
ApplicationServer
Server(PS)
(PS)supported:
supported:128
128(TBD)
(TBD)
H/W
H/Wand
andinitial
initialS/W
S/WInstallation:
Installation:
--For
ForR4.1.12.0
R4.1.12.0load
loadrefer
referto
toA5020
A5020Wireless
WirelessCall
CallServer
Server--W4.1
W4.1Software
Software
Installation
Installation(3HP700081016RJZZA)
(3HP700081016RJZZA)
WEM
WEMConfiguration
ConfigurationStrategy:
Strategy:Bottom-up
Bottom-up
--Start
Startfrom
fromprovisioning
provisioningthe
thelowest
lowestIP
IPlayer
layerfirst
first
--Move
Moveup
upuntil
untilreaches
reachesApplication
ApplicationServer
Server(AS)
(AS)
A5020 SIGTRAN Architecture
To user part on CCM card
DDM
MTP3 or
MTP3b
Netra DDM card (2-3)
MTP3 or
MTP3b
M3UA
SIM
up to 3 interface cards
Daughter card
DDM
DDM
SCTP
Daughter card
MTP2
SSCF/SSCOP
IP
MTP2
SSCF/SSCOP
IP
MTP1
AAL5/ATM
MAC
MTP1
AAL5/ATM
MAC
4 E1/T1 (TDM NSL/HSL/

ATM HSL) or 1 OC3 ATM
GE
GE
GE
GE
SCCF
SSCOP
MAC
Netra SIM card (24)
GE
Gigabit Ethernet
Service Specific Coordination Function
Service Specific Connection Oriented Protocol
Media Access Control address
M3UA
SIM
up to 3 interface cards
SCTP
MTP3 or
MTP3b
M3UA
A5020 SIGTRAN distribution principles

To user part on CCM card
AS & ASP instances are present on DDM

Out going messages:
Selection of DDM card for
outgoing messages by user part
(ISUP/BICC/SCCP):
First message DDM selection
based on round robin
Following message : same
DDM as first message
Selection of the SCTP end point
is based on SLS (static table)
Incoming messages:
DDM card is selected based on
SLS (static table)
M3UA
M3UA
AS
AS
AS
ASP
AS
AS
Distribution based on SLS
SCTP end point
M3UA
SCTP end point
A5020 SIGTRAN defense principles
Three
Threelevels
levelsof
ofdefense:
defense:
Network
Networkissues
issuesor
orport
portoutage
outageon
onSIM
SIMcard
card::
Multi-homing
Multi-homingmechanism
mechanism
Global
Globaltraffic
trafficof
ofthe
theSCTP
SCTPassociation
associationisiscarried
carriedon
onthe
theremaining
remainingpath
path
SIM
SIMoutage:
outage:
N+1
N+1load
loadsharing
sharing
After
Afterdetection,
detection,at
atASP
ASPlevel
level,,the
theglobal
globaltraffic
trafficof
ofthe
theAS
ASisishandled
handledon
onthe
the
remaining
SCTP
association
present
on
another
SIM
remaining SCTP association present on another SIM
Static
StaticSLS
SLStable
table for
foroutgoing
outgoing&&incoming
incomingmessages
messagesare
areupdated
updatedto
totake
takeinto
into
account
the
new
configuration
account the new configuration
DDM
DDMoutage:
outage:
N+1
N+1load
loadsharing
sharing
After
Afterdetection,
detection,distribution
distributionmechanisms
mechanismsexclude
excludethe
theDDM
DDMfor
forthe
theelection
election
of
ofthe
theDDM
DDMfor
forthe
thefirst
firstmessage
messageto
tosend
send
Static
StaticSLS
SLStable
tablefor
foroutgoing
outgoing&&incoming
incomingmessages
messagesare
areupdated
updatedto
totake
takeinto
into
account
the
new
configuration
account the new configuration
A5020 SIGTRAN Dimensioning capacities Model C
2 SAM Netra 240+ (1+1)

8 CCM Netra 240+ (4+4)
2 SIM Netra 240 + (1+1)

2 IPM or CCM Netra 240+ (1+1)
3 DDM Netra 240 + (2+1)
A5020 SIGTRAN Dimensioning capacities Model F
2 SAM Netra 240+ (1+1)

18 CCM Netra 240+ (9+9)
4 SIM Netra 240 + (3+1)

4 IPM or CCM Netra 240+ (1+1)
3 DDM Netra 440 + (2+1)
Netra SIM Hardware

Each SIM is comprised of a Netra 240 (contains two 1.5GHz cpus, 4GB RAM, two 146 GB
15 krpm hard drives) and optionally the previously mentioned daughter boards.
SIM Server Configuration w/ T1/E1 Cards
SIM Server Configuration w/ T1/E1 & OC-3
For specifications on the iSPAN 5539F PCI Multiprotocol T1/E1/J1 Communications Controller:
http://www.interphase.com/beans/ProdDocumentRepository/public/4/5539F_DS_02-07-05.pdf
For specifications on the iSPAN 4532 OC3/STM1 Controller, Multimode (4532-031):

http://www.iphase.com/beans/ProdDocumentRepository/public/4/4532_DS_03-02-05.pdf
SIM Dimensioning (Netra)

SIM
SIMprovides
providesthe
thefollowing
followinginterfaces:
interfaces:
NB
NBSS7
SS7(MTP3)
(MTP3)::
E1/T1
E1/T1NSL
NSL(64
(64K/56K)
K/56K) or
orE1/T1
E1/T1HSL
HSL(2,048
(2,048/1544)
/1544)
BB
BBSS7
SS7(MTP3B)
(MTP3B)
E1/T1
E1/T1ATM
ATMHSL
HSLor
orOC3/STM1
OC3/STM1ATM
ATM
SIGTRAN
SIGTRAN(M3UA)
(M3UA)::IPIPFE
FE(100Mbps)
(100Mbps)or
orGE
GE(1000Mbps)
(1000Mbps)
MTP3/MTP3B
MTP3/MTP3BInterfaces
Interfacesare
areprovided
providedon
ondaughter
daughterboards:
boards:
E1/T1
E1/T1NSL&
NSL&E1/T1
E1/T1HSL
HSL&&E1/T1
E1/T1ATM
ATMHSL
HSL::same
samedaughter
daughterboard
boardwith
with44
connections
connections(Interphase
(Interphase5539F)
5539F)
OC3/STM1
OC3/STM1ATM
ATM:: daughter
daughterboard
boardwith
with11connection
connection(Interphase
(Interphase5500+4532)
5500+4532)
AANetra
NetraSIM
SIMhosts
hosts33daughter
daughterboards:
boards:
configuration 1slot 1 slot 2 slot 3

Nb GE Nb E1/T1 Nb OC3/STM1
number 1
2
0
0
number 2 E1/T1 DB E1/T1 DB E1/T1 DB
2
12
0
number 3 E1/T1 DB E1/T1 DB OC3/STM1 ATM DB 2
8
1
List of Tables used for SCTP and M3UA in A5020 WCS
SystemConfiguration
SystemConfiguration
CONFIGPARAMS
CONFIGPARAMS
--Define
Definethe
themaximum
maximumnumber
numberof
ofin/out
in/outstreams
streams
"GTWGEN",
"GTWGEN","SGW",
"SGW","SCTP",
"SCTP", "maxNmbInStrms",
"maxNmbInStrms","Integer",
"Integer",4,4,"MaximumNumberofIncomingStreams",
"MaximumNumberofIncomingStreams","10",
"10","10",
"10",
"10",
"10",
0,
"SGW_SCTP_ID
"10", "10", 0, "SGW_SCTP_ID
GTWGEN",
GTWGEN","SGW",
"SGW","SCTP",
"SCTP","maxNmbOutStrms",
"maxNmbOutStrms","Integer",
"Integer",4,4,"MaximumNumberofOutgoingStreams",
"MaximumNumberofOutgoingStreams","10",
"10","10",
"10",
"10",
"10",
0,
"SGW_SCTP_ID
"10", "10", 0, "SGW_SCTP_ID
SS7Configuration
SS7Configuration
SGWSCTPCONFIG
--SCTP
SGWSCTPCONFIG
SCTPEnd
EndPoint
PointDefinition
Definition(local)
(local)
SGWM3UAPSPCONFIG
SGWM3UAPSPCONFIG --Peer
Peer(remote)
(remote)Server
ServerProcess
Process(PSP)
(PSP)
SGWM3UAPSCONFIG
--Local
SGWM3UAPSCONFIG
Localand
andPeer
Peer(remote)
(remote)Application
ApplicationServer
Server(AS)
(AS)
SGWM3UAPSPASCONFIG
SGWM3UAPSPASCONFIG --PSP
PSPIds
Idsfor
for(local)
(local)Application
ApplicationServer
Server
SGWM3UAROUTECONFIGSGWM3UAROUTECONFIG
SGWM3UAROUTECONFIGAssociate(remote)
(remote)AS
ASto
torouting
routingKey,
Key,i.e.
i.e.ISO/DPC
ISO/DPC
SGWM3UAROUTECONFIG Associate
Configuration Sigtran on A5020 WCS (R4.1) - Configure SCTP End Points:
Must set to M3UA
SIM Number
Local IP PORT Num
Local IP address on SIM card
STEP 1: Click Signaling Gateway -> SIGTRAN -> SCTP END POINT -> ADD. TABLE: SGWSCTPCONFIG
Configuration Sigtran on A5020 WCS (R4.1) - Configure SCTP End Points (cont):
User Service Access Point ID
Local SIM Num
Number of IP address for

SCTP Association. Max is
five, but limited by SIM
card with 2 IP address
NOTE: USAP ID, which binds lower Service Access Point (SAP) to upper SAP in SCTP, must be unique.
Configuration Sigtran on A5020 WCS (R4.1) - Peer (remote) Server Process (PSP):
Remote Type can be

either SG or IPSP
ID must be unique
True if uses NA
Remote IP Addr
Remote IP Port Num
Local SIM Num

See notes
STEP 2: Click Signaling Gateway -> SIGTRAN -> SCTP END POINT -> ADD. TABLE: SGWM3UAPSPCONFIG
NOTES: RX/TX ASP ID specifies if RX/TX Application Server Process ID (in Self ASP ID) is available in ASPUP and NTFY msg
Configuration Sigtran on A5020 WCS (R4.1)- Peer (remote) Server Process (PSP) (cont):
WCS send INIT
Choose logical network

Set to 1 if there is 2nd IP address
Differentiated Service Code Point
NOTES: Different remote IP addresses or port number shall be used if adding more than one PSPs to the same remote
SG / AS. The same rule applies to SIM card number under SCTP association.
Configuration Sigtran on A5020 WCS (R4.1) - Configure Application Server (AS): Local
Load Share or Active Stand-by

(must set the same as in remote AS)
Local AS
Specify if the AS needs

to be active for Point
Code availability
STEP 3: Click Signaling Gateway -> SIGTRAN -> Gateways -> <Logical SGW> -> ADD. TABLE: SGWM3UAPSCONFIG
Configuration Sigtran on A5020 WCS (R4.1) - Application Server (AS): - Local (cont)
Local Routing Context
Select one that matches peer AS

Number of PSPs required
to have this AS shown in
available state
NOTE 1: Local Routing Context (RC) must be consistent with the Peer RC provisioned on the remote Application
Server
Configuration Sigtran on A5020 WCS (R4.1) - Application Server (AS): - Local (cont)
STEP 4: After click Apply the above window is shown. Click Add Row to add PSP Ids for this AS. TABLE: SGWM3UAPSPASCONFIG
Configuration Sigtran on A5020 WCS (R4.1) - Application Server (AS): - Remote
Set to the same as local AS

Remote RC
Local Flag must be set to False
STEP 5: The configuration is the same as provisioning local AS, except Local Flag needs to be set to False.
Configuration Sigtran on A5020 WCS (R4.1) - Application Server (AS) Remote (cont)
STEP 6: click on the Network Appearance and use Add Row to add the PSP Ids for this remote AS
Configuration Sigtran on A5020 WCS (R4.1) - Configure M3UA Route: - Local
Set to Local
Select Not Specified
Local AS ID
Local Point Code
STEP 7: Click Signaling Gateway -> SIGTRAN -> Gateways -> <Logical SGW> -> M3UA Route -> ADD
Configuration Sigtran on A5020 WCS (R4.1) - Configure M3UA Route: - Remote
Set to PS
Local Point Code
Remote AS ID
Remote Point Code
STEP 8: Click Signaling Gateway -> SIGTRAN -> Gateways -> <Logical SGW> -> M3UA Route -> ADD. TBL: SGWM3UAROUTECONFIG
Configuration Sigtran on A5020 WCS (R4.1) - Configure M3UA Route: - Properties
STEP 9: For remote there is need to specify ISUP protocol and SLS Range
References
http://rfc.net/rfc2190.html:
Stream Control Transmission Protocol, October 2000
Signaling System 7 (SS7) Message Transfer Part 2 (MTP2) - User Adaptation
Layer , September 2002
Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) - User Adaptation
Layer (M3UA), September 2006
Sigtran Overview, by Horst Kirschbnaum, January, 2007
Signaling backhaul using SIGTRAN by third party SG, by Xuemei Zhang, March
2007
WCS 5020 MG 7570 SIGTRAN ALU Training Manual
Thank you !
www.alcatel-lucent.com

SIGTRAN Overview Training

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

SIGTRAN Overview Training

Diunggah oleh

Hak Cipta:

Format Tersedia

Introduction to SigTran

An Alcatel-Lucent A5020 Solution

Prepared for Technical Training in GSE

All Rights Reserved Alcatel-Lucent 2007, #####

All Rights Reserved Alcatel-Lucent 2007, Plano, TX, USA

ISUP / BICC / TUP

Adaptation layer, i.e. M2PA, M2UA, M3UA, etc

All Rights Reserved Alcatel-Lucent 2007, Plano, TX, USA

About Adaptation Layers

Differences between M2UA and M2PA

Why M3UA is chosen for mobile applications ?

Stream Control Transmission Protocol

All Rights Reserved Alcatel-Lucent 2007, #####

Motivation Why SCTP, but not TCP?

All Rights Reserved Alcatel-Lucent 2007, Plano, TX, USA

All Rights Reserved Alcatel-Lucent 2007, Plano, TX, USA

SCTP Functional Overview

All Rights Reserved Alcatel-Lucent 2007, Plano, TX, USA

Key SCTP Features:

All Rights Reserved Alcatel-Lucent 2007, Plano, TX, USA

To deliver ISUP messages there is a need to decouple messages based on

All Rights Reserved Alcatel-Lucent 2007, Plano, TX, USA

All Rights Reserved Alcatel-Lucent 2007, Plano, TX, USA

Data & Acks

SCTP Key Terms

Transmission Sequence Numbers (TSN)

Signalling Endpoint (SEP)

Illustration of SCTP Association Path and Stream

SCTP End Point

SCTP End Point

All Rights Reserved Alcatel-Lucent 2007, Plano, TX, USA

Illustration of SCTP Streams, Packets and Chunks

User Adaption Layer

User Adaption Layer

DATA chunk header

SCTP Packet Format

SCTP Chunk Format

Four-WAY Association Establishment

INIT-ACK (cookie, list of IP, Z1, Z2,..)

COOKIE-ECHO (cookie, data)

All Rights Reserved Alcatel-Lucent 2007, Plano, TX, USA

build temp TCB

Selective Acknowledgement (SACK)

All Rights Reserved Alcatel-Lucent 2007, Plano, TX, USA

SCTP Common header

Chunk: A unit of info in an SCTP packet

All Rights Reserved Alcatel-Lucent 2007, Plano, TX, USA

What is M3UA and What is not?

All Rights Reserved Alcatel-Lucent 2007, Plano, TX, USA

M3UA Protocol Architecture

Relay IP or SS7 messages back to

Provide global network

All Rights Reserved Alcatel-Lucent 2007, Plano, TX, USA

M3UA Network Entities

SEP - SS7 Signalling Endpoint

All Rights Reserved Alcatel-Lucent 2007, Plano, TX, USA

All Rights Reserved Alcatel-Lucent 2007, Plano, TX, USA

Signalling Peer Processes

All Rights Reserved Alcatel-Lucent 2007, Plano, TX, USA

RC Routing Context. A value that uniquely identifies a Routing Key

M3UA SS7/IP Network Architecture

All Rights Reserved Alcatel-Lucent 2007, Plano, TX, USA

All Rights Reserved Alcatel-Lucent 2007, Plano, TX, USA

AS-SG-SEP Model (AS/SG Model)