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: Shaktishura Gardagis
Country: Azerbaijan
Language: English (Spanish)
Genre: Education
Published (Last): 8 January 2011
Pages: 87
PDF File Size: 7.67 Mb
ePub File Size: 15.79 Mb
ISBN: 202-6-28431-683-7
Downloads: 99702
Price: Free* [*Free Regsitration Required]
Uploader: Vudobei

Network Working Group K. Please refer to the current edition of the “Internet Official Protocol Standards” STD m3ya for the standardization state and status of this protocol. Distribution of this memo is unlimited.

This document obsoletes RFC Table of Contents 1. Signalling Point Code Representation Routing Contexts and Routing Keys Managing Routing Contexts and Routing Keys Message Distribution at the SGP Message Distribution at the ASP Signalling Gateway SS7 Layers Definition of M3UA Boundaries Message Classes and Types Receipt of Primitives from the Layer Management Routing Key Management Procedures [Optional] 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 rffc traffic as required to an alternate Application Server Process, or group m3uw ASPs, within an Application Server in the event of failure or unavailability of a currently 6466 Application Server Process.


M3UA RFC.4666 – SS7 MTP3 User Adaptation Layer

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 directly interconnect two signalling points, which are used as a module. An example scenario is where an SG appears as an. Network Byte 3mua – Most significant byte first, a.

RFC – part 1 of 5

Routing K3ua – 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 configured either using a configuration management interface, or by using the m3ja 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.

Signalling Process – A process instance that uses M3UA to communicate with other signalling processes. Signaling Transfer Point STP – A node in the SS7 network rf provides network access and performs message routing, screening and transfer of signaling messages. 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.


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. Frc is to take advantage of various SCTP features, such as: 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.

Information on RFC ยป RFC Editor

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. The provisioning and configuration of the SS7 network determines the restriction placed on the maximum block.

M3uz 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 rrc. This can be achieved using the.