Service Specific Connection Oriented Protocol (SSCOP)

SSCOP

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

NAME

sscop - Service Specific Connection Oriented Protocol

SYNOPSIS

#include <sys/socket.h>
#include <netinet/sscop.h>
#include <sys/saal_sscop.h>
#include <sys/npi_sscop.h>
#include <sys/tpi_sscop.h>
#include <sys/xti_sccop.h>

int sscop_stream = open(sscop_device, flags);
int sscop_xtistr = t_open(sscop_device, flags);
int sscop_socket = socket(PF_INET, SOCK_SEQPACKET, IPPROTO_SSCOP);

DESCRIPTION

SSCOP
is an implementation of ITU-T Recommendation Q.2111 (SSCOP-MCE) as defined in Q.2110[1, 2] and Q.2111[3]. SSCOP provides reliable delivery of ordered or unordered packets over a full duplex connection between two streams on top of ip(4). SSCOP can guarantee that the data arrives in order, if requested, and retransmits lost packets. It generates and checks a per-packet checksum to catch transmission errors. SSCOP-MCE uses the services of the Internet Protocol, ip(4), to transfer packets.

SSCOP is implemented as a STREAMS(4) multiplexing driver for LiS(9)[4]. ip(4) streams are linked under the SSCOP multiplexing driver using I_LINK or I_PLINK commands of streamio(7), to provide network services to SSCOP. Once linked, the streams must be configured using sscop_ioctl(4).

SSCOP provides three stream types. To select one of the stream types, sscop_device can be one of the following:

/dev/sscop or /dev/inet/sscop: This device provides the SSCOP protocol service interface using the T-primitives of the Transport Provider Interface[5], tpi(7), used for the Service Specific Connection Oriented Protocol, as described in tpi_sccop(7). The tpi(7) interface provided on a stream opening this device is suitable for use with the xnet(3) or xti(3) library and provides SSCOP interface using XTI[6, 7] as described in xti_sscop(3).
/dev/sscop-npi: This device provides SSCOP protocol service interface using the N-primitive of the Network Provider Interface[8], npi(7), used for the Service Specific Connection Oriented Protocol, as described in npi_sscop(7). This stream provides connection-oriented NPI services.
/dev/sscop-saal: This device provides the SSCOP protocol services interface using the AAL-primitives of the Service Specific Connection Oriented Protocol Interface described in sscopi(7).

SSCOP provides one socket type for use by the sockets(3) library socket(7) calls. SSCOP provides sockets in the protocol family PF_INET using the protocol number IPPROTO_SSCOP. The socket_type argument can be one of the following:

SOCK_SEQPACKET: Provides a connection-oriented reliable packet services with regard to order. Message boundaries are preserved. This socket uses the underlying /dev/inet/sscop transport service provider.

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

PF_INET

SOCK_SEQPACKET

IPPROTO_SSCOP

/dev/sscop

tpi

cots_ord

For additional information, see socksys(4) and protosw(5).

IOCTLS

All interfaces upport a set of management IO controls using ioctl(2) and streamio(7) I_STR system calls on the sscop_stream, sscop_xtistr or sscop_socket. These management controls are documented in sscop_ioctl(4).

NOTICES

SSCOP is implemented as a STREAMS(4) implementation using LiS(9)[4], and supports sockets only with the socksys(4) driver.

FILES

<netinet/sscop.h>, <sys/npi.h>, <sys/npi_ip.h>, <sys/npi_sscop.h>, <sys/saal.h>, <sys/saal_ip.h>, <sys/saal_sscop.h>, <sys/socket.h>, <sys/tpi.h>, <sys/tpi_ip.h>, <sys/tpi_sscop.h>, <xti.h>, <xti_ip.h>, <xti_sscop.h>.

DEVICES

/dev/sscop, /dev/inet/sscop, /dev/sscop-npi, /dev/sscop-saal.

REFERENCES

[1]: ITU-T Recommendation Q.2110, Service Specific Connection-Oriented Protocol (SSCOP), (Geneva), ITU, ITU-T Telecommunication Standardization Sector of ITU. (Previously "CCITT Recommendation") <http://www.itu.int/rec/T-REC-Q.2110/>
[2]: ANSI T1.637/2000, Service Specific Connection-Oriented Protocol (SSCOP), 2000, ANSI, American National Standards Institute.
[3]: ITU-T Recommendation Q.2111, Service Specific Connection-Oriented Protocol in a Multi-link and Connectionless Environment (SSCOPMCE), (Geneva), ITU, ITU-T Telecommunication Standardization Sector of ITU. (Previously "CCITT Recommendation") <http://www.itu.int/rec/T-REC-Q.2111/>
[4]: LIS 2.18, Linux STREAMS (LiS) 2.18.6 Source Code, Brian Bidulock, ed., OpenSS7 Corporation. <http://www.openss7.org/>
[5]: 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/>
[6]: 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/>
[7]: 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/>
[8]: 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>

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 SS7 Stack: Package strss7 version 0.9a.8 released 2008-10-31.

This document was created by man2html, using the manual pages.
Time: 09:03:27 GMT, December 12, 2024