M3UA stands for MTP Level 3 (MTP3) User Adaptation Layer as defined by the IETF SIGTRAN working group in RFC M3UA enables the SS7 protocol’s. MTP/SCCP/SSCOP and SIGTRAN (Message of SS7 over IP);. Message transfer part 3 User Adaptation layer (M3UA). [Endorsement of RFC (). RFC Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) – User . A is the Interface between two IP nodes that are equipped with SCTP, M3UA and.

Author: Arara Kagasho
Country: Belgium
Language: English (Spanish)
Genre: Politics
Published (Last): 21 June 2015
Pages: 79
PDF File Size: 18.82 Mb
ePub File Size: 6.64 Mb
ISBN: 455-3-45885-198-3
Downloads: 17034
Price: Free* [*Free Regsitration Required]
Uploader: Muzilkree

Network Working Group G. Sidebottom Request for Comments: Please refer to the current edition of the “Internet Official Protocol Standards” STD 1 for the standardization state and status of this protocol.

Distribution of this memo is unlimited. Table of Contents 1. Examples of M3UA Procedures The delivery mechanism should meet the following criteria: The AS contains a set of one or more unique Application Server Processes, of which one or more is normally actively processing traffic.

Note that there is a 1: Failover – The capability to reroute signalling traffic as required to an alternate Application Server Process, or group of ASPs, within an Application Server in the event of failure rtc unavailability of a currently used Application Server Process. Failover also applies upon the return to service of a previously unavailable Application Server Process.

Layer Management – Layer Management is a nodal function that handles the inputs and outputs between the M3UA layer and a local management entity. Linkset – A number of signalling links that rfv interconnect two signalling points, which are used as a module. An example scenario is where an SG appears as an element in multiple separate national SS7 networks and the same Signaling Point Code value may be reused in different networks. Most significant byte first, a.

A Routing Key describes a set of SS7 parameters and parameter values that uniquely define the range of signalling traffic to be handled by a particular Application Server. Routing Context – A value that uniquely identifies a Routing Key. Routing Context values are either configured using a configuration management interface, or by using the routing key management procedures defined in this document. It serves as an active, backup, load-sharing or broadcast process of a Signalling Gateway.

An SG contains a set of one or more unique Signalling Gateway Processes, of which one or more is normally actively processing traffic.

RFC – part 1 of 4

Signalling Process – A process instance that uses M3UA to communicate with other signalling processes. Stream – A stream refers to an SCTP stream; a unidirectional logical channel established from one SCTP endpoint to another associated SCTP endpoint, within which all user messages are 33322 in-sequence except for those submitted to the unordered delivery service. This is to take advantage of rrc SCTP features such as: Under certain scenarios, such as back-to-back connections without redundancy requirements, the SCTP functions above might not be a requirement and TCP MAY be used as the underlying common transport protocol.


However, in the case where an ASP is connected to more than one SG, the M3UA layer at an ASP should maintain the status of configured SS7 destinations and route messages according to the availability and congestion status of the routes to these destinations via each SG.

However, in the context of an SG, the maximum octet block size must 33332 followed when interworking to a SS7 network that does not support the transfer of larger information blocks to the final destination. The provisioning and configuration of the SS7 network determines the restriction placed on the maximum block size.

ss7 – Need ASN.1 specifications for M3UA protocol – Stack Overflow

The M3UA layer at an ASP keeps the state of the routes to remote SS7 destinations and may initiate an audit of the availability, the restricted or the congested state of remote SS7 destinations.

An SG may m3us logically partitioned to operate m3ya multiple SS7 network appearances. In such a case, the SG could be addressable with a Point Code in each network appearance, and represents a set of nodes in the IP domain into each SS7 network.

Alias Point Codes [ 8 ] may also be used within an SG network appearance. It is possible for the SGP Routing Key configuration data to 33332 temporarily out-of-sync during configuration updates. Inter-SGP protocol is outside of the scope of this document. The following example shows a signalling gateway partitioned into two network appearances. A Routing Key is essentially a set of SS7 parameters used to filter SS7 messages, whereas the Routing Context parameter is a 4-byte value integer that is associated to that Routing Key in a 1: The Routing Context therefore can be viewed as an index into a sending node’s Message Distribution Table containing the Routing M3ha entries.

Some example Routing Keys are: The particular information used to define an M3UA Routing Key is application and network dependent, and none of the above examples are mandated.


M3ua rfc 3332 pdf download

It is not necessary for the parameter m3ux values within a particular Routing Key to be contiguous. A Routing Key may be configured statically using an implementation dependent management interface, or dynamically using the M3UA Routing Key registration procedure. When using a management interface to configure Routing Keys, the message distribution function within the SGP is not limited rvc the set of parameters defined in this document.

Other implementation dependent distribution algorithms may be used. To support this message distribution, the SGP might, for example, maintain the equivalent of a network address translation table, mapping incoming SS7 message information to rfd Application Server for a particular application and range of traffic.

These ASPs provide dynamic status information regarding their availability, traffic handling capability and congestion to the SGP using various management messages defined in the M3UA protocol. The list of ASPs in an AS is assumed to be dynamic, taking into account the availability, traffic handling capability and congestion status of 33332 individual ASPs in the list, as well as configuration changes and possible failover mechanisms.

Normally, one or more ASPs are active i. Broadcast, loadsharing and backup scenarios are supported. Possible solutions are to provide a default Application Server at the SGP that directs all unallocated traffic to a set of default ASP sor to drop the message and provide a notification to layer management. The treatment of unallocated traffic is implementation dependent. This is accomplished by observing the Destination Rtc Code and possibly other elements of the outgoing message such as the SLS value.

Each ASP in this set may be active, inactive or unavailable. The function could optionally be used to control the start of traffic on to a newly available SCTP association. It also provides network status information to one or both sides of the network.

In addition, as an implementation and network option, restricted destinations are communicated from MTP network management to rrfc local M3UA-resident management function.

M3UA reports the status of an AS. M3UA reports that it has received a Notify message from its peer. M3UA reports that it has received an Error message from its peer m3us that a local operation has been unsuccessful.