RFC Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) – User Adaptation Layer (M3UA), September Canonical URL. RFC (part 1 of 5): Signaling System 7 (SS7) Message Transfer Part 3 ( MTP3) – User Adaptation Layer (M3UA). M3UA Overview. Protocol Architecture. Services Provided by the M3UA Layer. Support for the Transport of MTP3-User Messages. Full.

Author: Brasida Gular
Country: Saint Lucia
Language: English (Spanish)
Genre: Relationship
Published (Last): 2 December 2016
Pages: 339
PDF File Size: 4.33 Mb
ePub File Size: 6.22 Mb
ISBN: 946-8-32913-554-9
Downloads: 35699
Price: Free* [*Free Regsitration Required]
Uploader: Zolokazahn

RFC – Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) – User Adaptation Layer (M3UA)

Message Distribution at the ASP The M3UA layer at an ASP keeps the state of the routes to remote SS7 destinations and may initiate an audit of the availability and the restricted or the congested state of remote SS7 destinations. Routing Key Management Procedures [Optional] Routing Contexts and Routing Keys Stream – An SCTP stream; a unidirectional logical channel established from one SCTP endpoint to another associated SCTP endpoint, within which all user messages are delivered in-sequence except for those submitted to the unordered delivery service.

Definition of M3UA Boundaries Table of Contents 1. This can be achieved using the. Managing Routing Contexts and Routing Keys Signaling Transfer Point STP – A node in the SS7 network that provides network access and performs message routing, m3ha and transfer of signaling messages. It serves as an active, backup, load-sharing, or broadcast process of a Signalling Gateway. Routing Context – A value that uniquely identifies a Routing Key. Layer Management – Layer Management is a nodal function that handles the inputs and outputs between the M3UA layer and mm3ua local management entity.


M3UA RFC.4666 – SS7 MTP3 User Adaptation Layer

The AS contains a set of one or more unique Application Server Processes, of which one or more is normally actively processing traffic. An example scenario is where an SG appears as an. This tfc obsoletes RFC This is to take advantage of various SCTP features, such as: Message Distribution at the SGP Routing Context values are configured either using a configuration management interface, or by using the routing key management procedures defined in this document.

Message Classes and Types Signalling Process – A process instance that uses M3UA to communicate with other signalling processes. Distribution of this memo is unlimited. Examples of M3UA Procedures The provisioning and configuration of the SS7 network determines the restriction placed on the maximum block. However, in the context of an SG, the maximum octet block size must be followed when interworking to a SS7 network that does not support the transfer of larger information blocks to the final destination.

Signalling Point Code Representation 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. An SG contains a set of one or more unique Signalling Gateway Processes, of which one or more is normally actively processing traffic. Network Byte Order – Most significant byte first, a.


Receipt of Primitives from the Layer Management 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 or unavailability of a currently used Application Server Process. Protocol Architecture The framework architecture that has been defined for SCN signalling transport over IP [ 12 ] uses multiple components, including a common signalling transport protocol and an adaptation module to support the services expected by a particular SCN signalling protocol from its underlying protocol layer.

Note that there is a 1: Please refer to the current edition of the “Internet Official Protocol Standards” STD 1 for the standardization state and status of this protocol.

Network Working Group K.