Sigtran Workshop

Alcatel-Lucent A5060 SigTran
All Rights Reserved Alcatel-Lucent 2007, #####
Agenda
SIGTRAN
SIGTRANIntroduction
Introduction
SCTP
SCTP
M3UA
M3UA
ALU
ALUA5060
A5060Sigtran
SigtranSolution
Solution
SIGTRAN
SIGTRANKPIs
KPIs
SIGTRAN
SIGTRANAlarms
Alarms&&Events
Events
SIGTRAN
SIGTRANDIAGNOSTIC
DIAGNOSTIC
Troubleshooting
TroubleshootingQQ&&AA
Monitoring
Monitoringin
inLive
LiveNetwork
Network(TMO)
(TMO)
References
References
2 | Introduction to SigTran
All Rights Reserved Alcatel-Lucent 2007, Plano, TX, USA
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
withSwitched
SwitchedCircuit
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
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
SUA
SUA
IUA
IUA
provides
providestransport
transportof
ofMTP3-User
MTP3-Usersignaling
signalingover
overIPIP[RFC4666
[RFC4666
supersedes
RFC3332]
supersedes RFC3332]
--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
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
allsubsequent
subsequentdata
data
For
Forexample:
example:IfIfTCP
TCPwere
wereused
usedfor
fordelivering
deliveringISUP
ISUPmessages,
messages,the
theloss
lossof
ofone
one
message
messagerelevant
relevantto
toone
onecall
callwould
wouldresult
resultin
inthe
thedelay
delayof
ofall
allother
otherISUP
ISUP
messages
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
IP
SCTP End Point
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
INIT(ACK)
(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
bySCTP
SCTPmust
mustbe
beacknowledged
acknowledged
IfIfacknowledge
acknowledgechunk
chunkXXisisnot
notreceived
received(GAP
(GAPisisdetected),
detected),retransmission
retransmission
of
ofthe
thechunk
chunkXXisis performed
performed
Acknowledgments
Acknowledgmentscan
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
TCAP
TCAP
SCCP
SCCP
STP - SG
Tekelec Eagle
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:
Interworking of messages
Interworking of 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
AS
IPS
A5060
STP - SS7 Signalling Transfer Point

SG - Signalling Gateway
IP
IPS
AS Application Server
IPS IP Server
EAGLE
IWF - Interworking Function = NIF
STP
SS7
SEP
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, Routing Key and Routing Context
NGN NODE
SCTP
endpoint
AS1
Routing Key10ax1
ASP 1
Routing Key10ax2
RC1
Routing Key10axn
ASP n
Tekelec Signaling Gateway

SGP 1
IP
networks
SS7
networks
SGP n
1
RC Routing Context. A value that uniquely identifies a Routing Key

to represent Application Server (AS).
M3UA SS7/IP Network Architecture

NOTES:
NOTES:
AS1
AS1isisprocessing
processingMAP
MAP
protocol
for
the
point
protocol for the pointcode
codeAAinin
SS7
SS7network
network11
AS
AS 1
Load-sharing
M3UA
M3UA
SCTP
SCTP
ASP
ASP 1
1
SCTP
association
Load-sharing
IP domain
SS7 domain
ASP
ASP n
n
IP
IP node
node
IP
IP
SCTP
endpoint
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
nnxxASP
ASPserve
serveAS1
AS1ininaaloadloadsharing
manner
sharing manner
Signaling
SignalingGateway
GatewaySG1
SG1gives
gives
access
to
SS7
network
1
access to SS7 network 1&&33
Signaling
SignalingGateway
GatewaySG2
SG2gives
gives
access
accesstotoSS7
SS7network
network11&&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 not sent
if IPSP-IPSP
NTFY (AS-INACTIVE) (RCn)
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
Alcatel-Lucent A5060 Solution
Hardware/Software
Hardware/SoftwareArchitecture
Architecture
SIGTRAN
SIGTRANConfiguration
Configuration
TMO
TMONetwork
NetworkStandard
StandardConfiguration
Configuration
SIGTRAN Solution for Atrium A5060 WCS

Introduction of SIGTRAN on a Dual Rack Atrium WCS
Sigtran Traffic Migration MOPs
Enabling Sigtran On Dual Rack System (3HP700171264RJZZA)
Traffic Migration From SS7 To Sigtran Part I SCCP Traffic Migration
(3HP700171266RJZZA)
Traffic Migration From SS7 To Sigtran Part II ISUP Traffic Migration
(3HP700171265RJZZA)
Introduction of SIGTRAN on a T2K Atrium WCS Greenfield T2K Deployment with SIGTRAN On Network Side
Hot Slide from Dual Rack (w/ Sigtran) to T2K (w/ Sigtran)
A5060 SIGTRAN Hardware/Software Architecture (Dual Rack)

To user part on CCM card
DDM
Netra DDM cards (3)
up to 3 interface cards
Daughter card
MTP3 or
MTP3b
DDM
MTP3 or
MTP3b
M3UA
SIM
DDM
up to 3 interface cards
SCTP
MTP3 or
MTP3b
M3UA
SIM
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)
BGE2 BGE3

ATM HSL)
GE
SCCF
SSCOP
MAC
Netra SIM card (2)
BGE2 BGE3
Gigabit Ethernet
Service Specific Coordination Function
Service Specific Connection Oriented Protocol
Media Access Control address
M3UA
A5060 SIGTRAN Hardware/Software Architecture (T2K)

To user part on CCM card
T2K SIM003
T2K SIM006
SgwMtp3
SgwMtp3
MTP3 or MTP3b
SgwMtp2
SgwMtp2
SgwMtp3
SgwMtp3
M3UA
MTP3 or MTP3b
SgwSctp
SgwSctp
SgwMtp2
SgwMtp2
Daughter Card # 3
Daughter Card # 2
SSCF/SSCOP
AAL5/ATM

ATM HSL)
SgwSctp
SgwSctp
Daughter Card # 3
SCTP
Daughter Card # 1
MTP2
MTP1
M3UA
Daughter Card # 2
Daughter Card # 1
IP
MTP2
MTP1
MAC
e1000g1
e1000g3
SSCF/SSCOP
AAL5/ATM

ATM HSL)
SCTP
IP
MAC
e1000g1
e1000g3
e1000g1/e1000g3
- Gigabit Ethernet
SCCF - Service Specific Coordination Function
SSCOP - Service Specific Connection Oriented Protocol
MAC - Media Access Control address
SigTran
Hardware/Software
Architecture
SIGTRAN
Configuration
TMO
TMONetwork
NetworkStandard
Configuration
ALU A5060 SIGTRAN Solution - Configuration

SCTP End Points
PSP
M3UA AS
M3UA Route
SIGTRAN Configuration SCTP End Point
SCTP
Identifier
SIM Node ID
User of SCTP
End Point
SCTP Port
Primary Local
Address
Secondary Local
Address
SIGTRAN Configuration M3UA PSP
SIGTRAN Configuration M3UA AS (Local)
SIGTRAN Configuration M3UA AS (Remote)
SIGTRAN Configuration M3UA Route (Local)
SIGTRAN Configuration M3UA Route (Remote)
SigTran
Hardware/Software
Architecture
SIGTRAN
Configuration
TMO
TMONetwork
NetworkStandard
Configuration
TMO Network Standard Configuration
TMO Network Standard Configuration M3UA PSPs

T2K System:
The Standard Sigtran Configuration should

have 8 M3UA PSPs. Check that there are only
8 entries in SgwM3uaPSPConfig table
(SS7Configuration DB).
Verify that the following standard
configuration -
Dual Rack System:
The Standard Sigtran Configuration should

have 8 M3UA PSPs. Check that there are only
8 entries in SgwM3uaPSPConfig table
(SS7Configuration DB).
Verify the following standard configuration All Rights Reserved Alcatel-Lucent 2007, Plano, TX, USA
PSP Id
Card1
1,2
3,4
5,6
7,8
PSP Id
Card1
1,2,3,4
35
5,6,7,8
36
TMO Network Standard Configuration M3UA AS

T2K System or Dual Rack System (After Traffic Migration) :
Local AS (For Primary PC of WCS) is the first AS configured in the WCS.
EACH AS (Local + Remote) configured in the system must have 8 PSPs associated
with it.
For Local AS, the Routing Context value is set according to TMOs guidelines.
ALL Remote AS (LCLFLAG = 0), the Routing Context is set to 0.
TMO Network Standard Configuration M3UA Route

T2K System or Dual Rack System (After Traffic Migration) :
Local Route (For Primary PC of WCS) is the first M3UA Route configured in the
WCS.
EACH Route (Local + Remote) configured in the system has OPC set to Not
Specified.
Between M3UA-AS and M3UA-Route the 1 to 1 relationship must be

maintained.
ALL Remote Routes are configured correctly with SLS Range = SLS_8BITS and ISUP
Protocol = ANSI95
SigTran
SIGTRAN
SIGTRANKPIs
KPIsSCTP
SCTP
SIGTRAN
SIGTRANKPIs
KPIsM3UA
M3UA
SIGTRAN KPIs - SCTP

STARTTIMESTAMP
*STOPTIMESTAMP
*WSSNODENUM
*GATEWAYNO
SCTPINITTX
SCTPINITRX
SCTPINITACKTX
SCTPINITACKRX
SCTPSHUTDOWNTX
SCTPSHUTDOWNRX
SCTPDATATX
SCTPDATARX
SCTPOCTTX
SCTPOCTRX
No
No
No
No
No
No
No
No
No
No
of
of
of
of
of
of
of
of
of
of
SCTP - INIT messages transmitted

SCTP - INIT messages received
SCTP - INIT-ACK messages transmitted
SCTP - INIT-ACK messages received
SCTP SHUTDOWN messages transmitted
SCTP SHUTDOWN messages received
SCTP DATA messages transmitted
SCTP DATA messages received
OCTETS transmitted
OCTETS received
SIGTRAN KPIs - SCTP

SCTPINITTx / Rx : No of SCTP INIT Chunks Transmitted & Received
SCTPINITACKTx / Rx : No of SCTP INITAck Chunks Transmitted & Received
SCTPSHUTDOWNTx / Rx : No of SCTP SHUTDOWN Chunks Transmitted & Received
Description: Each of the above peg count respectively indicates the no of SCTP Chunks transmitted
and received as part of 3-way handshake during initialization and shutdown of SCTP Associations.
Reported By : Each SIM Node Running SgwSctp process independently reports these peg counts.
SCTPDATATx / Rx : No of SCTP DATA Chunks Transmitted & Received
Description: This peg count provides an aggregate no. of traffic messages (DATA Chunks)
transmitted and received over Sigtran (SCTP).
SCTPOCTTx / Rx : No of OCTETS transmitted & Received
Description: This peg count provides an aggregate no. of bytes transmitted and received over
Sigtran (SCTP). ALL SCTP messages (CHUNKS) including the traffic messages (DATA Chunks) are
covered by this peg count.
Note: Valid SCTP Chunk types DATA, INIT, INIT (ACK), Selective ACK (SACK), HEARTBEAT,
HEARTBEAT (ACK), ABORT, SHUTDOWN, SHUTDOWN (ACK), ERROR, COOKIE ECHO, COOKIE ACK,
SHUTDOWN COMPLETE.
SIGTRAN KPIs - SCTP

CHECK POINTS: Under Normal Condition (ALL 8 Sigtran Associations IN-SERVICE Carrying Traffic)
SCTPDATATx & SCTPDATARx reported by each SIM Node are not drastically different
Under Failure Condition (Any Sigtran Association DOWN)
Verify that in case of Sigtran Association Failure, the peg counts (SCTPSHUTDOWNTx +
SCTPSHUTDOWNRx + SCTPINITTx + SCTPINITRx, SCTPINITACKTx + SCTPINITACKRx) from the
associated SIM Node indicate non-zero values for above peg counts.
SIGTRAN KPIs SCTP (Kernel Stats)

Statistics Name
Value
Description
sctpRtoAlgorithm
vanj
The algorithm used to determine the timeout value used for retransmitting
unacknowledged chunks
sctpRtoMin
1000
The minimum value permitted by a SCTP implementation for the retransmission timeout
sctpRtoMax
60000
The maximum value permitted by a SCTP implementation for the retransmission timeout.
sctpRtoInitial
3000
Initial value for the Retransmission timer.
sctpMaxAssocs
-1
The limit on the total number of associations the entity can support. In entities where the
maximum number of associations is dynamic, this object should contain the value -1.
sctpValCookieLife
60000
Valid cookie life in the 4-way start-up handshake procedure.
sctpMaxInitRetr
The maximum number of retransmissions at the start-up phase.
sctpCurrEstab
number of SCTP association has made a direct transition to the CLOSED state from any
state using the ABORT primitive, denoting ungraceful termination of the association.
13
Number of SCTP association has made a direct transition to the ESTABLISHED state
from the COOKIE-ECHOED state, denoting that the upper layer has initiated the
association attempt.
The number of times that associations have made a direct

transition to the
ESTABLISHED state from the CLOSED state:
CLOSED -> ESTABLISHED. The remote endpoint initiated the association attempt.
sctpActiveEstab
sctpPassiveEstab

Statistics Name
Value
Description
The number of times that associations have made a direct transition to the CLOSED state
from any state using the primitive 'ABORT': Any State --Abort--> CLOSED. Ungraceful
termination of the association.
sctpShutdowns
12
The number of times that associations have made a direct

transition to the CLOSED
state from either the SHUTDOWN-SENT state or the SHUTDOWN-ACK-SENT state.
Graceful termination of the association.
sctpOutOfBlue
number of times SCTP packet is received for which the receiver is not able to identify the
association to which the packet belongs.
sctpChecksumError
The number of SCTP packets received with an invalid checksum.
sctpOutCtrlChunks
42053866
The number of SCTP control chunks sent . Control chunks are those chunks different
from DATA.
sctpOutOrderChunks
97478
The number of SCTP ordered data chunks sent .
sctpOutUnorderChunks
The number of SCTP unordered chunks (data chunks in which the U bit is set to 1) sent .
sctpRetransChunks
1383
Number of retransmitted chunks.
sctpOutAck
18904
Number of Ack sent out.
sctpOutAckDelayed
18889
Number of delayed acks.
sctpOutWinUpdate
sctpOutFastRetrans
sctpAborted
Number of data retransmitted using fast retransmission.


Statistics Name
Value
Description
sctpOutWinProbe
sctpInCtrlChunks
42067423
The number of SCTP control chunks received .
sctpInOrderChunks
36026
The number of SCTP ordered data chunks received.
sctpInUnorderChunks
The number of SCTP unordered chunks (data chunks in which the U bit is set to 1)
received .
sctpInAck
32532
Number of Ack received.
sctpInDupAck
Number of duplicate Acks received.
sctpInAckUnsent
Number of Acks unsent.
sctpFragUsrMsgs
The number of user messages that have to be fragmented because of the MTU.
sctpReasmUsrMsgs
The number of user messages reassembled, after conversion into DATA chunks.
sctpOutSCTPPkts
42087738
The number of SCTP packets sent. Retransmitted DATA chunks are included.
sctpInSCTPPkts
42069526
The number of SCTP packets received. Duplicates are included.
sctpInInvalidCookie
Number of invalid cookies received by SCTP.
sctpTimRetrans
1383
Number of time retransmission happened.

Statistics Name
Value
Description
sctpTimRetransDrop
Number of time assoc dropped due to prolonged failure to perform timer-based

retransmission results in the association being aborted.
sctpTimHearBeatProbe
713091
Number of time heartbeat sent on all the paths.
sctpTimHearBeatDrop
Number of time heartbeat dropped.
sctpListenDrop
Number of incoming connection is dropped for any reason.
sctpInClosed
Number of time data received on a closed SCTP assoc.
SigTran
SIGTRAN
SIGTRANKPIs
KPIsSCTP
SCTP
SIGTRAN
SIGTRANKPIs
KPIsM3UA
M3UA
SIGTRAN KPIs M3UA

SYSM3UAPSPPERF:
STARTTIMESTAMP
Date and time performance interval started.
STOPTIMESTAMPDate and time performance interval stopped.
WSSNODENUM
WSS Node (SIM Card) to which this record applies
GATEWAYNO
Gateway Will always have a value of 1
PSPID
Peer Server Process ID.
SCTSAPID
User SAP ID (USAP id)
M3UAASSOCCONGTX
Number of PSP congestion messages transmitted.
M3UAASSOCCONGRX
Number of PSP congestion messages received.
M3UAASSOCTPTX
Number of transfer prohibited messages transmitted.
M3UAASSOCTPRX
Number of transfer prohibited messages received.
M3UAASSOCTRTX
Number of transfer restrict messages transmitted.
M3UAASSOCTRRX
Number of transfer restricted messages received.
M3UAASSOCTRATX
Number of transfer allowed messages transmitted.
M3UAASSOCTRARX
Number of transfer allowed messages received.
M3UAASSOCTCTX
Number of transfer controlled messages transmitted.
M3UAASSOCTCRX
Number of transfer controlled messages received.
ASPUPMSGTX
Number of ASP UP messages sent
ASPUPMSGRX
Number of ASP UP messages received
ASPUPACKMSGTX
Number of ASP UP ACK messages sent
ASPUPACKMSGRX
Number of ASP UP ACK messages received
ASPDNMSGTX
Number of ASP DOWN messages sent
ASPDNMSGRX
Number of ASP DOWN messages received
ASPDNACKMSGTX
Number of ASP DOWN ACK messages sent
ASPDNACKMSGRX
Number of ASP DOWN ACK messages received
ASPACMSGTX
Number of ASP ACTIVE messages sent
ASPACMSGRX
Number of ASP ACTIVE messages received
ASPACACKMSGTX
Number of ASP ACTIVE ACK messages sent
ASPACACKMSGRX
Number of ASP ACTIVE ACK messages received
SIGTRAN KPIs M3UA

Table SPATIAL.SYSM3UAPSPPERF:
ASPINACMSGTX
ASPINACMSGRX
ASPINACACKMSGTX
ASPINACACKMSGRX
M3UAASSOCUNAV
M3UAASSOCUNAVDUR
M3UAASSOCBYTETX
M3UAASSOCBYTERX
M3UAASSOCPDUTX
M3UAASSOCPDURX
M3UAASSOCCONGNBR
M3UAASSOCCONGDUR
RESERVED1
RESERVED2
RESERVED3
RESERVED4
RESERVED5
RESERVED6
RESERVED7
RESERVED8
RESERVED9
RESERVED10
Number of ASP INACTIVE messages sent

Number of ASP INACTIVE messages received
Number of ASP INACTIVE ACK messages sent
Number of ASP INACTIVE ACK messages received
Number of times Association was unavailable
Duration of Association unavailability (in seconds)
Byte count of PDU(s) sending on the association
Byte count of PDU(s) receiving on the association
Number of PDU(s) sending on the association
Number of PDU(s) receiving on the association
Number of association congestion occurrence
Duration of association congestion (in seconds)
Reserved field 1 for future use
Color scheme:
Peg counts with this color are reported by Node (SIM or DDM) Running SgwMtp3 with
Master M3UA.
Peg counts with this color are reported by ALL Nodes Running SgwMtp3.
SIGTRAN KPIs M3UA

M3UAASSOCCONGTX: No. of M3UA ASSOCIATION CONGESTION Transmitted.
Description: This peg count provides details of CONGESTION being reported by the specified PSP.
Reported By : SIM/DDM Node Running SgwMtp3 process with Master M3UA.
M3UAASSOCCONGRX: No. of M3UA ASSOCIATION CONGESTION Received.
Description: This peg count provides details of CONGESTION being reported by remote STP-SG
node. The CONGESTION is reported by M3UA Message Type = SCON with non-zero value for
congestion level.
M3UAASSOCTPTX : No. of Traffic Prohibited Messages Transmitted.
Description : This peg count provides no. of DUNA (Destination UNAvailable) transmitted by WCS.
DUNA message is used by SGP to declare Unavailability of a given Destination. For TMO
configuration (ASP SGP), WCS will not transmit DUNA messages. Hence M3UAASSOCTPTX peg
count will always be 0.
M3UAASSOCTPRX : No. of Traffic Prohibited Messages Received.
Description : This peg count provides no. of DUNA (Destination UNAvailable) received on the
specified Association by WCS.
SIGTRAN KPIs M3UA

M3UAASSOCTRTX : No. of Traffic Restricted Messages Transmitted
Description : This peg count provides no. of DRST (Destination ReSTricted) messages transmitted
by WCS. DRST message is used by SGP node to declare restricted traffic towards any given
destination. For TMO configuration (ASP SGP), WCS does not transmit DRST messages. Hence
M3UAASSOCTRTX peg count will always be 0.
M3UAASSOCTRRX : No. of Traffic Restricted Messages Received
Description : This peg count provides no. of DRST (Destination ReSTricted) messages received on
the specified Association (PSP) by WCS.
M3UAASSOCTRATX : No. of Traffic Allowed Messages Transmitted
Description : This peg count provides no. of DAVA (Destination AVAilable) messages
transmitted by WCS. DAVA message is used by SGP node to declare restored traffic
towards a given destination. For TMO configuration (ASP SGP), WCS does not
transmit DAVA messages. Hence M3UAASSOCTRATX peg count will always be 0.
M3UAASSOCTRARX : No. of Traffic Allowed Messages Received
Description : This peg count provides no. of DAVA (Destination AVAilable) messages received on
specified Association (PSP) by WCS.
SIGTRAN KPIs M3UA

ASPUPMSGTX : Number of ASP UP messages sent
Description : This peg count indicates no. of ASPUP messages transmitted for the specified
Association (PSP) from WCS to remote STP-SG node. The ASPUP message is used during activation
procedure for each Association (PSP).
ASPUPMSGRX : Number of ASP UP messages received
Description : This peg count indicates no. of ASPUP messages received for the specified Association
(PSP) from STP-SG node to WCS. ASPUP messages is used during activation procedure for each
Association (PSP).
ASPUPACKMSGTX : Number of ASP UP ACK messages sent
Description : This peg count indicates no. of ASPUP-ACK messages transmitted for the specified
Association (PSP) from WCS to STP-SG node. The ASPUP-Ack message is used during activation
ASPUPACKMSGRX : Number of ASP UP ACK messages received
Description : This peg count indicates no. of ASPUP-ACK messages received for the specified
Association (PSP) from STP-SG node to WCS. The ASPUP-ACK message is used during activation
SIGTRAN KPIs M3UA

ASPDNMSGTX : Number of ASP DOWN messages sent
Description : This peg count indicates no. of ASP DOWN messages transmitted for the specified
Association (PSP) from WCS to STP-SG node. The ASP DOWN message is used while Association (PSP)
is going down.
ASPDNMSGRX : Number of ASP DOWN messages received
Description : This peg count indicates no. of ASP DOWN messages received for the specified
Association (PSP) from STP-SG node to WCS. The ASP DOWN message is used while Association (PSP)
is going down.
ASPDNACKMSGTX : Number of ASP DOWN ACK messages sent
Description : This peg count indicates no. of ASPDOWN-ACK messages transmitted for the specified
Association (PSP) from WCS to STP-SG node. The ASPDOWN-ACK message is used while Association
(PSP) is going down.
ASPDNACKMSGRX : Number of ASP DOWN ACK messages received
Description : This peg count indicates no. of ASPDOWN-ACK messages received for the specified
Association (PSP) from STP-SG node to WCS. The ASPDOWN-ACK message is used while Association
(PSP) is going down.
SIGTRAN KPIs M3UA

ASPACMSGTX : Number of ASP ACTIVE messages sent
Description : This peg count indicates no. of ASP ACTIVE messages transmitted for the specified
Association (PSP) from WCS to STP-SG node. The ASP ACTIVE message is used to indicate the remote
peer M3UA that the specified Association (PSP) is ready to handle traffic.
ASPACMSGRX : Number of ASP ACTIVE messages received
Description : This peg count indicates no. of ASP ACTIVE messages received for the specified
Association (PSP) from STP-SG node to WCS. The ASP ACTIVE message is used to indicate the remote
ASPACACKMSGTX : Number of ASP ACTIVE ACK messages sent
Description : This peg count indicates no. of ASPACTIVE-ACK messages transmitted for the specified
Association (PSP) from WCS to STP-SG node. The ASPACTIVE-ACK message is used to acknowledge
ASP ACTIVE message received from remote M3UA peer.
ASPACACKMSGRX : Number of ASP ACTIVE ACK messages received
Description : This peg count indicates no. of ASPACTIVE-ACK messages received for the specified
Association (PSP) from STP-SG node to WCS. The ASPACTIVE-ACK message is used to acknowledge
ASP ACTIVE message received from remote M3UA peer.
SIGTRAN KPIs M3UA

ASPINACMSGTX : Number of ASP INACTIVE messages sent
Description : This peg count indicates no. of ASP INACTIVE messages transmitted for the specified
Association (PSP) from WCS to STP-SG node. The ASP INACTIVE message is used to indicate the
remote peer M3UA that the specified Association (PSP) is unavailable to handle traffic.
ASPINACMSGRX : Number of ASP INACTIVE messages received
Description : This peg count indicates no. of ASP INACTIVE messages received for the specified
Association (PSP) from WCS to STP-SG node. The ASP ACTIVE message is used to indicate the remote
ASPINACACKMSGTX : Number of ASP INACTIVE ACK messages sent
Description : This peg count indicates no. of ASP INACTIVE ACK messages transmitted for the
specified Association (PSP) from WCS to STP-SG node. The ASP INACTIVE ACK message is used to
acknowledge an ASP INACTIVE message received from a remote M3UA peer.
ASPINACACKMSGRX : Number of ASP INACTIVE ACK messages received
Description : This peg count indicates no. of ASP ACTIVE messages transmitted for the specified
Association (PSP) from WCS to STP-SG node. The ASP INACTIVE ACK message is used to acknowledge
an ASP INACTIVE message received from a remote M3UA peer.
SIGTRAN KPIs M3UA

M3UAASSOCUNAV : Number of times Association was unavailable
Description : This peg count indicates no. of times the specified Association (PSP) became
unavailable during the reporting interval.
M3UAASSOCUNAVDUR : Duration of Association unavailability (in seconds)
Description : This peg count indicates duration (in seconds) the specified Association (PSP) was
unavailable.
M3UAASSOCBYTETX : Byte count of PDU(s) sent on the association
Description : This peg count indicates total no. of bytes transmitted on the specified Association
(PSP) from WCS.
Reported By : Each SIM/DDM Node Running SgwMtp3 process.
M3UAASSOCBYTERX : Byte count of PDU(s) received on the association
Description : This peg count indicates total no. of bytes received on the specified Association (PSP)
by WCS.
Reported By : Each SIM/DDM Node Running SgwMtp3 process.
SIGTRAN KPIs M3UA

M3UAASSOCPDUTX : Number of PDU(s) sent on the association
Description : This peg count indicates no. of M3UA PDUs (Message Type - DATA) transmitted on the
specified Association (PSP) from WCS.
M3UAASSOCPDURX : Number of PDU(s) received on the association
Description : This peg count indicates no. of M3UA PDUs (Message Type DATA) received on the
specified Association (PSP) by WCS.
M3UAASSOCCONGNBR : Number of association congestion occurrence
Description : This peg count indicates no. of times congestion happened on the specified
Association (PSP).
M3UAASSOCCONGDUR : Duration of association congestion (in seconds)
Description : This peg count indicates duration of congestion happened on the specified Association
(PSP).
SIGTRAN KPIs M3UA

CHECK POINTS :Under Normal Condition (ALL 8 Associations In-Service Carrying Traffic)
Verify that M3UA_ASSOC_PDU_RX is not drastically different for ALL PSPs.
Verify that M3UA_ASSOC_PDU_TX is not drastically different for ALL PSPs.
Verify that M3UA_ASSOC_UNAV_DUR is 0 for ALL PSPs.
Under Failure Condition (Any Association DOWN).
Verify that M3UA_ASSOC_UNAV_DUR indicates unavailability duration of the Associations DOWN.
Verify that M3UA_ASSOC_PDU_RX is not drastically different for the remaining PSPs.
Verify that M3UA_ASSOC_PDU_TX is not drastically different for the remaining PSPs.
SigTran
SIGTRAN
SIGTRANAlarms
Alarms&&Events
Events--SCTP
SCTP
SIGTRAN
SIGTRANAlarms
Alarms&&Events
EventsM3UA
M3UA
SIGTRAN Alarms / Events
Micros oft Excel

Works heet
SigTran
DIAGNOSTIC
DIAGNOSTIC
DIAGNOSTIC
From MSC Node (SIM/DDM) running SgwMtp3 process, run the general diagnostic.
DDM_1_7_1 DDM015:> cd /opt/Spatial/msc/active/tools/scripts
DDM_1_7_1 DDM015:> diagnosticReq . SGW_MTP3_ID gen
_________________ M3UA SCT Sap Info ________
| suId | spId | spEndpId | state | actAssocs |
__________________________________________
| 0 | 0 |
0
| READY |
2 |
| 1 | 0 |
1
| READY |
2 |
| 2 | 0 |
2
| READY |
2 |
| 3 | 0 |
3
| READY |
2 |
__________________________________________
M3UA SCT SAP Info: This section of the diagnostic result provides details for SCTP Endpoint configuration and their
operational state.
where
spEndpId represents SCTP end point configuration from each SIM node. For Dual Rack system there are
total 2 SCTP endpoints configured, where as for a T2K system there are total 4 SCTP end points
configured (above example).
state indicates the operational state of each end point. The possible values are - UNBOUND,
WAIT_BNDCFM, BOUND, OPENCFM, READY, UNKNOWN. The expected state is READY.
actAssocs indicates no. of active associations established using an end point. Based on the standard
configuration in TMO Sigtran deployment, each end point will have 2 active associations (one to each
STP-SG node) for a T2K system (above example). In case of a Dual Rack system, each end point will
have 4 active associations (two to each STP-SG node)
DIAGNOSTIC
___________________________________________________________ (T2K) M3UA PSP Info _____________________________________________________________
| pspId | suId | spAssocId | assocSt | aspSt | inhibited | nmbActPs | nmbRegPs | congQ | congActive | nmbPs | aspmType | retryCount | outStreams |
____________________________________________________________________________________________________________________________________________________
| 1 | 0 |
0
| ACTIVE | ACTIVE | FALSE |
49
|
0
|
0 |
FALSE | 49 |
NONE |
0
|
2
|
| 1 | 1 |
0
|
DOWN | DOWN | FALSE |
0
|
0
|
0 |
FALSE | 49 |
NONE |
0
|
10
|
| 1 | 2 |
0
|
0
|
0
|
0 |
FALSE | 49 |
NONE |
0
|
10
|
| 1 | 3 |
0
|
0
|
0
|
0 |
FALSE | 49 |
NONE |
0
|
10
|
| 2 | 0 |
1
47
|
0
|
0 |
FALSE | 47 |
NONE |
0
|
2
|
| 2 | 1 |
0
|
0
|
0
|
0 |
FALSE | 47 |
NONE |
0
|
10
|
| 2 | 2 |
0
|
0
|
0
|
0 |
FALSE | 47 |
NONE |
0
|
10
|
| 2 | 3 |
0
|
0
|
0
|
0 |
FALSE | 47 |
NONE |
0
|
10
|
| 3 | 0 |
0
|
0
|
0
|
0 |
FALSE | 47 |
NONE |
0
|
10
|
| 3 | 1 |
0
47
|
0
|
0 |
FALSE | 47 |
NONE |
0
|
2
|
| 3 | 2 |
0
|
0
|
0
|
0 |
FALSE | 47 |
NONE |
0
|
10
|
| 3 | 3 |
0
|
0
|
0
|
0 |
FALSE | 47 |
NONE |
0
|
10
|
| 4 | 0 |
0
|
0
|
0
|
0 |
FALSE | 47 |
NONE |
0
|
10
|
| 4 | 1 |
1
47
|
0
|
0 |
FALSE | 47 |
NONE
|
0
|
2
|
| 4 | 2 |
0
|
0
|
0
|
0 |
FALSE | 47 |
NONE |
0
|
10
|
| 4 | 3 |
0
|
0
|
0
|
0 |
FALSE | 47 |
NONE |
0
|
10
|
| 5 | 0 |
0
|
0
|
0
|
0 |
FALSE | 47 |
NONE |
0
|
10
|
| 5 | 1 |
0
|
0
|
0
|
0 |
FALSE | 47 |
NONE |
0
|
10
|
| 5 | 2 |
0
47
|
0
|
0 |
FALSE | 47 |
NONE |
0
|
2
|
| 5 | 3 |
0
|
0
|
0
|
0 |
FALSE | 47 |
NONE |
0
|
10
|
| 6 | 0 |
0
|
0
|
0
|
0 |
FALSE | 47 |
NONE |
0
|
10
|
| 6 | 1 |
0
|
0
|
0
|
0 |
FALSE | 47 |
NONE |
0
|
10
|
| 6 | 2 |
1
46
|
0
|
0 |
FALSE | 47 |
NONE |
0
|
2
|
| 6 | 3 |
0
|
0
|
0
|
0 |
FALSE | 47 |
NONE |
0
|
10
|
| 7 | 0 |
0
|
0
|
0
|
0 |
FALSE | 47 |
NONE |
0
|
10
|
| 7 | 1 |
0
|
0
|
0
|
0 |
FALSE | 47 |
NONE |
0
|
10
|
| 7 | 2 |
0
|
0
|
0
|
0 |
FALSE | 47 |
NONE |
0
|
10
|
| 7 | 3 |
1
47
|
0
|
0 |
FALSE | 47 |
NONE |
0
|
2
|
| 8 | 0 |
0
|
0
|
0
|
0 |
FALSE | 47 |
NONE |
0 |
10
|
| 8 | 1 |
0
|
0
|
0
|
0 |
FALSE | 47 |
NONE |
0 |
10
|
| 8 | 2 |
0
|
0
|
0
|
0 |
FALSE | 47 |
NONE |
0 |
10
|
| 8 | 3 |
0
47
|
0
|
0 |
FALSE | 47 |
NONE |
0
|
2
|
_____________________________________________________________________________________________________________________________________________________
DIAGNOSTIC
________________________________________________ (Dual Rack) M3UA PSP Info _____________________________________________________________
| pspId | suId | spAssocId | assocSt | aspSt | inhibited | nmbActPs | nmbRegPs | congQ | congActive | nmbPs | aspmType | retryCount | outStreams |
____________________________________________________________________________________________________________________________________________________
| 1 | 0 |
0
49
|
0
|
0 |
FALSE | 49 |
NONE |
0
|
2
|
| 1 | 1 |
0
|
0
|
0
|
0 |
FALSE | 49 |
NONE |
0
|
10
|
| 2 | 0 |
1
47
|
0
|
0 |
FALSE | 47 |
NONE |
0
|
2
|
| 2 | 1 |
0
|
0
|
0
|
0 |
FALSE | 47 |
NONE |
0
|
10
|
| 3 | 0 |
0
0
|
0
|
0 |
FALSE | 47 |
NONE |
0
|
10
|
| 3 | 1 |
0
47
|
0
|
0 |
FALSE | 47 |
NONE |
0
|
2
|
| 4 | 0 |
0
|
0
|
0
|
0 |
FALSE | 47 |
NONE |
0
|
10
|
| 4 | 1 |
1
47
|
0
|
0 |
FALSE | 47 |
NONE
|
0
|
2
|
| 5 | 0 |
0
|
0
|
0
|
0 |
FALSE | 47 |
NONE |
0
|
10
|
| 5 | 1 |
0
|
0
|
0
|
0 |
FALSE | 47 |
NONE |
0
|
10
|
| 6 | 0 |
0
|
0
|
0
|
0 |
FALSE | 47 |
NONE |
0
|
10
|
| 6 | 1 |
0
|
0
|
0
|
0 |
FALSE | 47 |
NONE |
0
|
10
|
| 7 | 0 |
0
|
0
|
0
|
0 |
FALSE | 47 |
NONE |
0
|
10
|
| 7 | 1 |
0
|
0
|
0
|
0 |
FALSE | 47 |
NONE |
0
|
10
|
| 8 | 0 |
0
|
0
|
0
|
0 |
FALSE | 47 |
NONE |
0 |
10
|
| 8 | 1 |
0
|
0
|
0
|
0 |
FALSE | 47 |
NONE |
0 |
10
|
_____________________________________________________________________________________________________________________________________________________
DIAGNOSTIC
_______________________ M3UA PS Info ___________________
| psId | nwkId | state | spmc | congLevel | pendMsgs |
______________________________________________________
| 1 |
6 | ACTIVE | 13882323 |
0
|
0
|
| 2 |
6 | ACTIVE | 12434620 |
0
|
0
|
| 3 |
6 | ACTIVE | 6579202 |
0
|
0
|
______________________________________________________
Where
state
is the current operational state of M3UA PS and corresponding M3UA Route.

The valid values are - UNKNOWN; DOWN; INACTIVE; ACTIVE; PENDING
spmc is the M3UA Route (decimal value of DPC) associated with M3UA PS.
congLevel is the current congestion level reported by STP-SG for the M3UA Route
pendMsgs
is no. of M3UA DATA messages currently pending to be delivered.
Under normal conditions, this count should be 0.
SigTran
Troubleshooting
Troubleshooting
Know Issues
SYMPTOM: After SIM Node Restart, the Associations DID NOT Recover.
Corresponding Error Logs:
Oct 24 13:15:22 VGMSS861_sim_1_4_1 WssLog: [ID 132624 local0.debug]
13:15:22.325 SIM004 SgwSctp(I) ../CmSsrvInt.c(870) ERROR - StackError:
ent: 136 inst: 000 proc id: 007 file: ../sb_acceptor.c line: 263 errcode:
00000 errcls: ERRCLS_DEBUG errval: 00515 errdesc: sb_accept_thr: Peel off
failed
RESOLUTION: Lock / Unlock Associations
Know Issues
SYMPTOM: After SIM Node Restart, the Associations DID NOT Recover.
Corresponding Error Logs:
Dec 11 11:06:03 Sust8_sam_1_5_1 WssLog: [ID 912396 local0.debug]
11:06:03.502 SIM023 SgwSctp(I) ../CmSsrvInt.c(871) ERROR - StackError:
ent: 136 inst: 000 proc id: 008 file: ../sb_osif.c line: 277 errcode: 00000
errcls: ERRCLS_DEBUG errval: 00000 errdesc: SbInetConnect:Connect
Failed:sockFd=19, port=2905 , AddrType=v4, Addr=2071690107
,Err=Connection timed out
Possible Root Cause: Configuration mismatch or End to end IP
connectivity problem
RESOLUTION: Resolve configuration mismatch or IP network problem.
Know Issues
SYMPTOM: After SIM Node Restart, the Associations DID NOT Recover. WCS
Not Responding to Association Initialization from remote node (STP-SG).
Troubleshooting SCTP Association

Association Establishment Sequence
From WEM Check

Status of PSP
Is
Card1 State
ACTIVE?
No
Login to SIM node.
Ping remote IP Address
Is
Ping test
Successful ?
No
Yes
Using netstat command, check
Association state
From WCS side,

Lock / Unlock the affected Association (PSP)
Resolve IP Connectivity
problems
Troubleshooting SCTP Association

A
Is
Association
ESTABLISHED ?
netstat a |grep ESTABLISHED

TERMINAL_SERVER_IP_ADDR
TERMINAL_SERVER_IP_ADDR 0 0 102400 0 32/32
CLOSED
*.2905
TERMINAL_SERVER_IP_ADDR 4096 0
262144 0 10/10 LISTEN
NVMSS970_sim_1_30_1 SIM035:> snoop -d bge2 sctp

Using device /dev/bge2 (promiscuous mode)
10.162.183.3 -> 10.177.34.26 SCTP D=2905 S=2905
10.162.183.3 -> 10.177.34.26 SCTP D=2905 S=2905
10.162.183.3 -> 10.177.34.26 SCTP D=2905 S=2905
10.162.183.3 -> 10.177.35.26 SCTP D=2905 S=2905
INIT
INIT
INIT
INIT
N
o
Using snoop, check the
IP packets being exchanged
Between WCS and STP-SG
Is
INIT INIT-ACK
OK?
No
Engage TMO team to investigate

WHY Association Initialization IS NOT OK?
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
Thank you !
www.alcatel-lucent.com

Sigtran Workshop

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 Workshop

Transféré par

Droits d'auteur :

Formats disponibles

Alcatel-Lucent A5060 SigTran

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

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

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

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

Differences between M2UA and M2PA

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

Why M3UA is chosen for mobile applications ?

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

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

STP - SS7 Signalling Transfer Point

IWF - Interworking Function = NIF

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

Illustration of AS, ASP, SGP, Routing Key and Routing Context