sli.2

No7信令,我需要交换类似的代码, 请店长审核,谢谢了,急着交换,谢谢

'\"t
.\" -*- nroff -*-
.\"
.\" @(#) sli.2,v 0.7 2000/11/15 10:56:26 brian Stab
.\"
.\" =========================================================================
.\"
.\"  Copyright (C) 1997-2000  Brian Bidulock.  All Rights Reserved.
.\"
.\"
.\"                               PUBLIC LICENSE
.\"
.\"  This license is provided without fee, provided that the above copy-
.\"  right notice and this public license must be retained on all copies,
.\"  extracts, compilations and derivative works.  Use or distribution of
.\"  this work in a manner that restricts its use except as provided here
.\"  will render this license void.
.\"
.\"  The author(s) hereby waive any and all other restrictions in respect
.\"  of their copyright in this software and its associated documentation.
.\"  The authors(s) of this software place in the public domain any novel
.\"  methods or processes which are embodied in this software.
.\"
.\"  The author(s) undertook to write it for the sake of the advancement
.\"  of the Arts and Sciences, but it is provided as is, and the author(s)
.\"  will not take any responsibility in it.
.\"
.\" =========================================================================
.\"
.\" Last Modified 2000/11/15 10:56:26 by brian
.\"
.\" sli.2,v
.\" Revision 0.7  2000/11/15 10:56:26  brian
.\" Added man file for streams modules.
.\"
.\" =========================================================================
.TH SLI 2 "30 Oct 2000" "Linux Man Page" "LiS Programmer's Manual"
.SH NAME
sli \- SS7 Signalling Link Interface (SLI) for STREAMS
.SH SYNOPSIS
.B #include <ss7/sli.h>
.br
.IB fdesc " = open(const char *" name ", int " flags ");"
.SH DESCRIPTION

This is an implementation of the Signalling Link Interface described in the
OpenSS7 Signalling Link Interface Specification and documented in ITU-T
Recommendation Q.703.  It provides the signalling link service.

The SLI supports two styles of driver.
When an SLI driver is opened, it's physical point of appearance may be
specified or unspecified depending on the style of the driver.

.TP 4
.I Style 1
\fIStyle 1\fR drivers have a Physical Point of Attachment (PPA) address which
is bound to the opened stream at the time that the stream is opened.  These
drivers are typically allocated a \fImajor\fR and \fIminor\fR device number
and a per-device character special device file entry in the \fB/dev\fR
directory.

.TP
.I Style 2
\fIStyle 2\fR drivers do not have a Physical Point of Attachment (PPA) address
bound at the time that the device is opened.  These drivers are typically
allocated a \fImajor\fR and \fIminor\fR device number using the
\fBclone open\fR and then are attached to a PPA using the
\fBSL_ATTACH_REQ\fR command.

.SH M_PROTO COMMANDS

The following protocol commands are supported by drivers which conform to the
Signalling Link Interface:

.TP 4
.BR SL_INFO_REQ ", " SL_INFO_ACK
When the SLI user wishes to obtain information about the driver's
implementation of the interface, it issues an \fBSL_INFO_REQ\fR command.  In
response, the Signalling Link Service (SLS) provider will respond with an
\fBSL_INFO_ACK\fR message with the following information:
.RS
.in +4
.sp
.nf
typdef struct {
    sl_ulong    sl_primitive;
    sl_ulong    sl_state;
    sl_ulong    sl_max_sdu;
    sl_ulong    sl_min_sdu;
    sl_ulong    sl_addr_length;
    sl_ulong    sl_ppa_style;
    sl_ulong    sl_version;
} sl_info_ack_t;
.fi
.RE

.TP 4
.BR SL_ATTACH_REQ ", " SL_OK_ACK ", " SL_ERROR_ACK
This command and response are used in directing the device to attached to the
specified Physical Point of Attachment address (PPA).  The precise format of
the PPA is device-specific and is provided in the specific device sections,
e.g. \fBacb56\fR(7).  Typically the address has two components: a signalling
data terminal (SDT) component and a signalling data link (sdl) component.  The
PPA is provided in the \fBSL_ATTACH_REQ\fR command as follows:
.RS
.in +4
.sp
.nf
typedef struct {
    sl_ulong    sl_primitive;
    sl_ulong    sl_ppa_addr;
} sl_attach_req_t;
.fi
.RE

.IP
If the attach is successful, the SLS provider responds with an
\fBSL_OK_ACK\fR; otherwise, it responds with an \fBSL_ERROR_ACK\fR.
In addition to the normal errors which may be contained in the
\fBSL_ERROR_ACK\fR, the following additional error codes may be returned:

.RS
.in +4
.TP
.B SL_OUTSTATE
The device is not in the \fBSL_UNATTACHED\fR state.  The \fIsl_state\fR
component of the \fBSL_ERROR_ACK\fR contains the actual state of the
interface.
.TP
.B SL_BADADDR
The address was invalid.
.TP
.B SL_BADADDRTYPE
Invalid address type.
.TP
.B SL_BADPPA
Invalid PPA identifier.
.TP
.B SL_PPAINUSE
The PPA specified in the attach command is already in use by another
signalling link.  The SLS does not permit multiiple SLS users to open streams
through the same PPA: only one stream per PPA is allowed.
.RE

.TP 4
.BR SL_DETACH_REQ ", " SL_OK_ACK ", " SL_ERROR_ACK
The detach request is sent as an \fBM_PROTO\fR or \fBM_PCPROTO\fR message by
the SLS User when it wishes to detach a \fBIStyle 2\fR driver stream from a
particular PPA.  The stream must already be disabled.  If the detach is
successful, the SLS Provider response with an \fBSL_OK_ACK\fR; otherwise, it
responds with an \fBSL_ERROR_ACK\fR with one of the following error codes:
.RS
.in +4
.TP
.B SL_OUTSTATE
The device is not in the \fBSL_ATTACHED\fR state.  The \fIsl_state\fR
component of the \fBSL_ERROR_ACK\fR contains the actual state of the
interface.
.RE

.TP 4
.BR SL_ENABLE_REQ ", " SL_ENABLE_CON
.RS
.in +4
.sp
.nf
.fi
.RE

.TP 4
.BR SL_DISABLE_REQ ", " SL_DISABLE_CON
.RS
.in +4
.sp
.nf
.fi
.RE

.SH COPYRIGHT NOTICE

.sp
Copyright \(co 1997-2000  Brian Bidulock.  All Rights Reserved.

.ce 1
PUBLIC LICENSE

This license is provided without fee, provided that the above copyright notice
and this public license must be retained on all copies, extracts, compilations
and derivative works.  Use or distribution of this work in a manner that
restricts its use except as provided here will render this license void.

The author(s) hereby waive any and all other restrictions in respect of their
copyright in this software and its associated documentation.  The authors(s)
of this software place in the public domain any novel methods or processes
which are embodied in this software.

The author(s) undertook to write it for the sake of the advancement of the
Arts and Sciences, but it is provided as is, and the author(s) will not take
any responsibility in it.