Escolar Documentos
Profissional Documentos
Cultura Documentos
Communication Networks
SUA tutorial
Authors:
Lode Coene
Gery Verwimp
Siemens Atea
Information and
Communication Networks
Application (+TCAP)
- replaces the functionality of SCCP and M3UA
over SCTP in an IP network
ISUP, SCCP SUA - required for 3G mobile networks (from Release
classic SS7 adapts SCCP 5 onwards) -> Nokia, Ericsson
Users to SCTP
gt
B1 D1
gt
A1 gt E1
gt
C1
B2 gt D2
gt
relayNodeEntitySet
PSTN IP interworking
Network border
SGSN
SRP SRP
., ...
HLR
. SRP Association:
.
.
.
SMSC SRP
Protocol Stack
:
MAP, IN,
RANAP...
SUA SUA SUA
SCTP SCTP SCTP
IP IP IP
AAL5/Ether AAL5/Ether AAL5/Ether
Routing for subsequent msgs of a SUA connection is done using the stored
association Id in the SCOC TCB, thus routing based on IP address or GT is not
done.
SPC2
SSb
AS
SG SCMG
SPC1 SPCx
ASP2 SSz SSy
SPC3
SSb
14 SUA tutorial 07.09.2017 Siemens Atea
Information and
Communication Networks
IP network operator 2
SUA uses a digit pattern which
is translated from node to node
until the final destination is
reached -> Global title
(e.g. MSISDN number :
CC + NDC + SN)
Useful for NAT crossing : no unknown NAT middlebox needed. The relay point
is the box and it is explicitly visible towards other SUA relay points or SUA
endpoints in both the normal internet and the NAT.
Can be used as a firewall for SUA traffic : example removal of SMS spam
traffic, enforcement of roaming agreements, ...
If relay point is used for transitioning into the NAT then IPSEC can be used.
Expands the addressing capabilities
E164 to E212
E164 to hostname
Hostname to hostname
hostname to E164
IPv4 - IPv6 network or NAT border crossing
Pseudo end-to-end :network architecture hiding
Allow for loadsharing across a pool of relay points (using Rserpool or own
SUA built in protocol)
DNS X
DNS A DNS B
gt
B1 D1
gt
A1 gt E1
gt
C1
B2 gt D2
gt
relayNodeEntitySet
Normal way of using DNS is to invoke GetHostname for every message that passes: More
negative points than positive
would create a DNS message flood in the DNS system as all connectionless msgs use E164/E212
numbers(if numbers gets cached, this problem may be reduced , but raises other issues)
the response time from the DNS is unpredictable due to its hierarchical architecture. Would produce a
WWW(world wide Wait) effect on SS7 traffic
Using the Time-to-live(TTL) from the DNS records is quite useless as SUA would have a direct
connection with the remote SUA node(and thus know far much better if the remote side is active or not).
That would mean that SUA should not be caching the DNS info but always have the up-to-date info of all
its adjacent SUA peers.
Is less flexible than the standard Global Title Translation function: a DNS name when distributed in DNS
will always map to the same set of IP addresses (= SUA nodes) independent from the place where the
resolving is requested, which would lead to a SUA hierarchical network design, something that is very
BAD for reliability and contrary to any SS7 network design up till now(SS7 favors greatly a peer-to-peer
network design and SS7-over-IP should benefit from that)
A name in the DNS can return many IP addresses and not all those address may belong to the same.
node -> DNS is sometimes used for loadbalancing across multiple nodes and it is impossible to make a
difference between a truly multihomed (SUA)node and a a bunch of replicated (SUA) nodes(with no
multihoming attached to each single node naturally) (Except if you start finding it out for yourself by
setting up association with each of the addresses)
SUA applicability
SUA can transport bigger SMS messages (nr of char >> 160)
however, this would also be true for traditional SCCP and TI-SCCP, but requires
adaptations to MAP protocol and raises interworking issues
SUA can transport bigger messages for all its applications
particularly useful in all-IP, where segmenting/reassembly can be left to SCTP
SUA is less complex than M3UA+SCCP, but has extended features
because it can be fine-tuned to SCCP applications
SUA supports the basic IP addressing architecture and DNS naming
this advantage depends of course on applications using the extended addressing
capabilities
Conclusion