SS7 MTP Level 3 User Adaptation Layer (M3UA)

M3UA

Section: OpenSS7 STREAMS SIGTRAN Devices (4)
Updated: 2008-10-31
Index Return to Main Contents

NAME

m3ua - SS7 MTP3 User Adaptation Layer (M3UA)

SYNOPSIS

#include <sys/mtpi.h>
#include <sys/mtpi_ioctl.h>
#include <sys/m3ua_ioctl.h>

int m3ua_stream = open(device, flags);
int m3ua_xtistr = t_open(device, flags);
int m3ua_socket = socket(PF_SS7, socket_type, SS7PROTO_M3UA);

DESCRIPTION

M3UA
is an implementation of the SS7 MTP3 User Adaptation Layer (M3UA) defined in RFC 3332[1], TS 102 142[2], and RFC 4666[3]. M3UA provides a back haul of the services of the mtp(4) over an IP network using Stream Control Transmission Protocol, sctp(4), as defined in RFC 2960[4], RFC 3309[5], TS 102 144[6], and RFC 4460[7]. Also, it provides a building block for redundant and distributed SS7 systems. (See ``NOTICES'', below.)

M3UA is implemented as a STREAMS(4) multiplexing driver. mtp(4) or sctp(4) streams are linked under the M3UA multiplexing driver using the I_LINK or I_PLIHK commands of streamio(7), to provide transport or direct MTP services[8..11] to M3UA. Once linked, the streams must be configured using m3ua_ioctl(4).

M3UA provides the following stream types that are directly compatible with the stream types provided by mtp(4). To select one of these stream types, device can be one of the following:

/dev/m3ua: This device provides the MTP protocol service interface using the M-primitives of the Message Transfer Part Interface described in mtpi(7). This interface is suitable for use with other SS7 modules and drivers.
/dev/m3ua-npi-cl, /dev/m3ua-npi-co: This devices provides the MTP protocol service interface using the N-primitives of the Network Provider Interface[12], npi(7), used for the Message Transfer Part as described in mtp_npi(7). The npi(7) interface provided on a stream opening this device is suitable for use with the sockets(3) library socket(3) call and provides the MTP interface using sockets as described in mtp_socket(7). /dev/m3ua-npi-cl provides a connectionless N_CLNS network service provider; /dev/m3ua-npi-co provides a connection-oriented N_CONS network service provider.
/dev/m3ua-tpi-cl, /dev/m3ua-tpi-co: This device provides the MTP protocol service interface using the T-primitives of the Transport Provider Interface[13], tpi(7), user for the Message Transfer Part as described in mtp_tpi(7). The tpi(7) interface provided on a stream opening this device is suitable for use with the xnet(3) or xti(3) library t_open(3) call and provides the MTP interface using XTI[14, 15] as described in xti_mtp(3). /dev/m3ua-tpi-cl provides a connectionless T_CLNS transport service provider; /dev/m3ua-tpi-co provides a pseudo-connection-oriented T_CONS transport service provider.

M3UA provides two socket types used by the sockets(3) library socket(3) call. M3UA provides sockets in the protocol family PF_SS7 using the protocol number SS7PROTO_M3UA. The socket_type argument can be one of the following:

SOCK_RDM: Provides a connectionless datagram service with reliable delivery including retransmission. Message boundaaries are preserved. This socket uses the underlying /dev/m3ua-tpi-cl transport service provider.
SOCK_SEQPACKET: Provides a pseudo-connection-oriented packet service with reliable delivery including retransmission. Message boundaries are preserved. Messages can be sent and received in order. This socket uses the underlying /dev/m3ua-tpi-co transport service provider.

The following entries in /etc/protosw provide the information necessary for socksys(4) to use these devices:

PF_SS7	SOCK_RDM	SS7PROTO_M3UA	/dev/m3ua-tpi-cl	tpi	clts
PF_SS7	SOCK_SEQPACKET	SS7PROTO_M3UA	/dev/m3ua-tpi-co	tpi	cots

For additional information, see protosw(5).

NOTICES

M3UA can be configured on a system as a drop in transparent replacement for mtp(4). In such a configuration, users opening streams or sockets as defined in mtp(4) will be opening m3ua streams and sockets, but will be unaware of the difference. In OpenSS7, m3ua is used as the primary mechanism of redundancy and distribution at the MTP level, and, when properly configured (see ss7confd(8)), m3ua functions transparently to the MTP-User.

Also, opening and binding a m3ua stream or socket may result in the opening and binding of a mtp(4) stream on the local or remote host in direct support of the local MTP-User.

IOCTLS

All interfaces support a set of management IO controls using ioctl(2) system calls on the m3ua_stream or m3ua_socket. These management controls are documented in m3ua_ioctl(4).

DEVICES

/dev/m3ua, /dev/m3ua-npi-cl, /dev/m3ua-npi-co, /dev/m3ua-tpi-cl, /dev/m3ua-tpi-co.

FILES

<ss7/mtpi.h>, <ss7/m3ua_ioctl.h>, <sys/npi.h>, <sys/npi_ss7.h>, <sys/npi_mtp.h>, <sys/tpi.h>, <sys/tpi_ss7.h>, <sys/tpi_mtp.h>, <xti.h>, <xti_mtp.h>, <sys/socket.h>.

VERSIONS

The M3UA driver is specific to the OpenSS7 stack. This is Version 2 of the interface.

REFERENCES

[1]: draft-ietf-sigtran-rfc3332bis-05.txt, Signaling System 7 (SS7) Message Transfer Part 3 (MTP3)-User Adaptation Layer (M3UA), October 2005, Javier Pastor, ed., Internet Engineering Task Force --- Signalling Transport Working Group. Work In Progress <http://www.ietf.org/internet-drafts/draft-ietf-sigtran-rfc3332bis-05.txt>
[2]: ESTI TS 102 142-V1.1.1 (2003-05), Services and Protocols for Advanced Networks (SPAN) --- MTP/SCCP/SSCOP and SIGTRAN (Transport of SS7 over IP) --- Message transfer part 3 User Adaptation layer (M3UA), May 2003, (Sophia Antipolis, Valbonne), ETSI, European Telecommunications Standards Institute. [DTS/SPAN-130263] (Endorsement of RFC 3332 (2002), modified) <http://www.etsi.org/>
[3]: RFC 4666, Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) --- User Adaptation Layer (M3UA), September 2006, K. Morneault, J. Pastor-Balbas, (eds), The Internet Society. <http://www.ietf.org/rfc/rfc4666.txt>
[4]: RFC 2960, Stream Control Transmission Protocol (SCTP), October 2000, Randall R. Stewart, ed., The Internet Society. (Obsoleted by RFC 4960) (Updated by RFC 3309) (Status: PROPOSED STANDARD) <http://www.ietf.org/rfc/rfc2960.txt>
[5]: RFC 3309, Stream Control Transmission Protocol (SCTP) Checksum Change, September 2002, Jonathan Stone, ed., The Internet Society. (Obsoleted by RFC 4960) (Updates RFC 2960) (Status: PROPOSED STANDARD) <http://www.ietf.org/rfc/rfc3309.txt>
[6]: ESTI TS 102 144-V1.1.1 (2003-05), Services and Protocols for Advanced Networks (SPAN) --- MTP/SCCP/SSCOP and SIGTRAN (Transport of SS7 over IP) --- Stream Control Transmission Protocol (SCTP), May 2003, (Sophia Antipolis, Valbonne), ETSI, European Telecommunications Standards Institute. [DTS/SPAN-130265] (Endorsement of RFC 2060 and RFC 3309, modified) <http://www.etsi.org/>
[7]: RFC 4460, Stream Control Transmission Protocol (SCTP) Specification Errata and Issues, April 2006, R. Stewart, I. Aria-Rodriguez, K. Poon, A. Caro and M. Tuexen, The Internet Society. (Status: INFORMATIONAL) <http://www.ietf.org/rfc/rfc4460.txt>
[8]: ITU-T Recommendation Q.704, Message Transfer Part --- Signalling Network Functions and Messages, March 1993, (Geneva), ITU, ITU-T Telecommunication Standardization Sector of ITU. (Previously "CCITT Recommendation") <http://www.itu.int/rec/T-REC-Q.704/>
[9]: ETSI EN 300 008-1 V1.3.1, Integrated Services Digital Network (ISDN); Signalling System No. 7; Protocol Specification, September 2000, (Sophia Antipolis, Valbonne), ETSI, European Telecommunications Standards Institute. [REN/SPAN-01074-1] (ITU-T Recommendations Q.701, Q.702, Q.703, Q.704, Q.705, Q.706, Q.707 and Q.708, modified) <http://www.etsi.org/>
[10]: ANSI T1.111, Signalling System No. 7 --- Message Transfer Part, 1992, ANSI, American National Standards Institute.
[11]: TTC Standard JT-Q)704, Message Transfer Part --- Signalling Network Functions and Messages, April 28, 1992, (Japan), TTC, Telecommunication Technology Committee (TTC).
[12]: NPI, Open Group CAE Specification: Network Provider Interface (NPI) Specification, Revision 2.0.0, Draft 2, August 17, 1992, (Parsippany, New Jersey), UNIXInternational,Inc., UNIX International Press. <http://www.openss7.org/docs/npi.pdf>
[13]: TPI Revision 2.0.0, Open Group CAE Specification: Transport Provider Interface (TPI) Specification, Revision 2.0.0, Draft 2, 1999, (Berkshire, UK), OpenGroup, Open Group Publication. <http://www.opengroup.org/onlinepubs/>
[14]: XTI/TLI Revision 1.0, Open Group CAE Specification: XOpen Transport Interface, Revision 1, n.d., (Berkshire, UK), XPG, X Programmer's Group. <http://www.opengroup.org/onlinepubs/>
[15]: XNS, Open Group CAE Specification: Technical Standard: Network Services (XNS), Issue 5.2, Draft 2, 1999, (Berkshire, UK), OpenGroup, Open Group Publication. [ISBN 1-85912-241-8] <http://www.opengroup.org/onlinepubs/>

TRADEMARKS

OpenSS7tm: is a trademark of OpenSS7 Corporation.
Linux®: is a registered trademark of Linus Torvalds.
UNIX®: is a registered trademark of The Open Group.
Solaris®: is a registered trademark of Sun Microsystems.

Other trademarks are the property of their respective owners.

IDENTIFICATION

OpenSS7 STREAMS SIGTRAN: Package sigtran version 0.9.2.4 released 2008-10-31.

This document was created by man2html, using the manual pages.
Time: 07:35:47 GMT, November 12, 2014