SS7 TCAP User Adaptation Layer (TUA)

TUA

Section: OpenSS7 STREAMS SIGTRAN Devices (4)
Updated: 2007-06-24
Index Return to Main Contents

NAME

TUA - SS7 TCAP User Adaptation Layer (TUA)

SYNOPSIS

#include <ss7/tcapi.h>
#include <ss7/tcapi_ioctl.h>
#include <ss7/tua_ioctl.h>

int tua_stream = open(device, flags);
int tua_xtistr = t_open(device, flags);
int tua_socket = socket(PF_SS7, socket_type, SS7PROTO_TUA);

DESCRIPTION

TUA
is an implementation of the SS7 TCAP User Adaptation Layer (TUA)[1]. TUA provides a back haul of the services of tcap(4) over an IP network using Stream Control Transmission Protocol, sctp(4), as defined in RFC 2960[2]. In addition it provides a building block of redundant and distributed SS7 systems. (See ``NOTICES'', below.)

TUA is implemented as a STREAMS(4) multiplexing driver for LiS(9)[3]. tcap(4) or sctp(4) streams are lined under the TUA multiplexing driver using the I_LINK or I_PLINK commands of streamio(7), to provide transport or direct TCAP services to TUA. Once linked, the streams must be configured using tuas_ioctl(4). This procedure is normally performed by the SS7 Configuration Daemon, ss7confd(8).

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

/dev/tua: This device provides the TCAP protocol service interface using the TR- and TC-primitives of the Transaction Component Interface (TCI) described in tcapi(7). This interface is suitable for use with other SS7 modules and drivers.
/dev/tua-tpi: This device provides the TCAP protocol service interface using the T-primitives of the Transport Provider Interface[4], tpi(7), used for the Transaction Capabilities Application Part as described in tcap_tpi(7). The tpi(7) interface provided on a stream opening this device is a suitable device for use with xnet(3) or xti(3) library t_open(3) call and provides the TCAP interface using XTI[5, 6] as described in xti_tcap(3).

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

SOCK_DGRAM: Provides a connection-less datagram service without regard to order. This is a TCAP operations class 1 or 2 service provider.
SOCK_RDM: Provides a connectiono-less reliable datagram service with regard to order. This is a TCAP operations class 3 or 4 service provider.
SOCK_SEQPACKET: Provides a connection oriented reliable datagram service with or without receipt confirmation and flow control. This is a TCAP operations class 5 service provider.

NOTICES

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

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

IOCTLS

All interfaces support a set of management IO controls using ioctl(2) system calls on the tua_stream, tua_xtistr or tua_socket file descriptor or socket. These management controls are documented in tua_ioctl(4).

In addition, tua supports tcap(4) IO controls. See tcap_ioctl(4).

DEVICES

/dev/tua, /dev/tua-tpi.

FILES

<ss7/tcapi.h>, <ss7/tcapi_ioctl.h>, <ss7/tua_ioctl.h>, <sys/tpi.h>, <sys/tpi_ss7.h>, <sys/tpi_mtp.h>, <sys/tpi_sccp.h>, <sys/tpi_tcap.h>, <xti.h>, <xti_tcap.h>, <sys/socket.h>.

REFERENCES

[1]: draft-bidulock-sigtran-tua-01.txt, SS7 TCAP-User Adaptation Layer (TUA),January 2, 2003,Brian Bidulock,ed.,Internet Engineering Task Force --- Signalling Transport Working Group. Work In Progress. (Expired) <http://www.ietf.org/internet-drafts/draft-bidulock-sigtran-tua-01.txt>
[2]: RFC 2960, Stream Control Transmission Protocol (SCTP),October 2000,Randall R. Stewart,ed.,The Internet Society. (Updated by RFC 3309) (Status: PROPOSED STANDARD) <http://www.ietf.org/rfc/rfc2960.txt>
[3]: LIS 2.18, Linux STREAMS (LiS) 2.18.6 Source Code,Brian Bidulock,ed.,OpenSS7 Corporation. <http://www.openss7.org/>
[4]: TPI Revision 2.0.0, Transport Provider Interface (TPI) Specification,No.Draft 2,1999,(Parsippany, New Jersey),OpenGroup,Open Group Publication. <http://www.opengroup.org/onlinepubs/>
[5]: XTI/TLI Revision 1.0, XOpen Transport Interface,n.d.,XPG,X Programmer's Group. <http://www.opengroup.org/onlinepubs/>
[6]: XNS Issue 5.2 Draft 2.0, Technical Standard: Network Services (XNS),1999,OpenGroup,Open Group Publication. [ISBN 1-85912-241-8] <http://www.opengroup.org/onlinepubs/>

Trademarks mentioned are the property of their owners.

IDENTIFICATION

OpenSS7 STREAMS SIGTRAN: Package sigtran version 0.9.2.3 released 2007-06-24.

This document was created by man2html, using the manual pages.
Time: 00:33:48 GMT, July 31, 2008