Professional Documents
Culture Documents
Common Channel Signaling System #7 ( SS7) transports SS7 messages over an SS7
network (normally a DS0A connection) and then there is SIGTRAN. SIGTRAN is a set of
protocols defined to transport SS7 messages over IP networks. SIGTRAN allows IP networks
to inter-work with the Public Switched Telephone Network (PSTN) and vice versa.
Notes: There are two other IETF standards which define transport of PSTN signaling (nonSS7) over IP networks: ISDN User Adaption (IUA) which provides adaption at the the Q.921
layer to allow transparent transport of Q.931 messages to, say, a VoIP gateway. IUA is
defined by RFC4233. V5.2 User Adaption (V5UA) which provides for the transport of ETSI
standard V5.2 messages in an IP network by adaption at the LAPV5 level. V5UA is defined
by RFC3807.
Contents
SIGTRAN Stack
SCTP Overview
A standard IP layer.
An Adaptation layer: Protocols defined for this layer are M2PA, M2UA, M3UA, and
SUA.
Sequenced Delivery: Allows for messages to be delivered in the order in which there
were sent.
Self-Fragmentation: SCTP uses MTU path discovery to ensure that messages are not
fragmented by intermediate nodes.
Heart-Beat: SCTP uses periodic heart-beat messages to confirm the status of each
end point.
Notes:
1. MTP3, which is preserved in every IPSP with M2PA, uses Point Codes as its address
mechanism and thus all IPSP require a Point Code.
2. The term UL (Upper Layer) has been used to indicate any layer which runs over
TCAP, for example, MAP.
3. With M2PA the SG may act as an STP simply routing messages (based on Point
Codes) from the SS7 network to the IPSP (IP Signaling Point).
4. In essense M2PA adaption allows SS7 functionality to be located within an IP
network.
5. The Signaling Gateway (SG) will be a fully function SS7 SP and therefore can have
any SS7 functionality such as SCP, STP or SSP.
6. If ISUP is supported by any IPSP then it would be acting as a SSP and have a VoIP
stack, such as SIP, which is not shown to keep the diagram simple.
7. Other STPs may be present in the path between the SEP (SSP) and the SG.
8. M2PA allows for one or more IPSP in the network. Each IPSP must have its own point
code.
9. M2PA can transport any MTP3 user messages, for example, SCCP and ISUP).
10. M2PA supports all primitives between MTP3 and MTP2 and is essentially transparent
to MTP3.
11. M2PA provides MTP2 functionality that is not provided by SCTP, so that together
M2PA and SCTP provide functionality similar to that of MTP2.
are sent to the MGC through the SG. The MGC converts from the M2UA protocol to
another protocol ( such as SIP or Megaco) and vise versa.
8. M2UA allows for only one IPSP (MGC) in the network.
9. Any messages that arrive at the SG, from the IP domain or SS7 domain are simply
relayed to the SS7 or IP domain respectively.
10. While Figure 2 shows a SIP stack this would only be present is the IPSP were
providing VoIP gateway functionality in the case of an SCP this function would not be
present.
the DPC is the same as the SG's Point Code, the message is sent to the layer above.
If the DPC differs from the SG's Point code, the message is routed by the SG to its
proper destination via the NIF.
6. ISUP messages are always routed by the SG, they can never be destined for the SG
(or any STP).
7. An ISUP message from the SS7 network destined for the IP network, is sent by the
SG's MTP3 to the local M3UA via the NIF. M3UA then routes the message to the
appropriate IPSP. Similarly, an ISUP message from the SS7 network destined for the
IP domain, is sent by the SG's M3UA to the local MTP3 also via the NIF. MTP3 routes
the message back to the origination SP.
8. In the SG, if the result of an application request or a GTT yields an SCP address
located in the SS7 domain or the IP domain, the resulting request is sent to the local
MTP3 or M3UA respectively for proper routing.
9. M3UA provides functionality similar to MTP3 but routing is IP aware through the use
of the Routing Key.
Boundary between M3UA and an MTP3-User (ISUP /SCCP)
From ITU Q.701:
MTP-TRANSFER request
MTP-TRANSFER indication
MTP-PAUSE indication
MTP-RESUME indication
MTP-STATUS indication
In general, the protocol stack based on SUA is less complex compared to the protocol stack
based on SCCP and M3UA. SUA can enhance the efficiency of the network and provides a
means for simpler implementations.
M3UA and SUA Differences:
1. M3UA: Needs the SCCP services.
SUA: Does not need SCCP services, reducing the complexity of the node and thereby
reducing cost.
2. M3UA: Supports ISUP services.
SUA: Cannot support ISUP services.
3. M3UA: Each IP node is required to have a point code and an IP address.
SUA: Each IP node does not require a point code.
4. M3UA: Messages are handled from point code to point code.
SUA: Allows the IP network to route the messages using global title information or
SSN.