N_UNITDATA_REQ

Section: Network Provider Interface (NPI) (7)
Updated: 2008-10-31
Index Return to Main Contents

NAME

N_UNITDATA_REQ, N_unitdata_req_t - unitdata request

DESCRIPTION

This primitive requests that the NS provider send the specified datagram to the specified destination.

SYNOPSIS

The format of the message is one M_PROTO(9) message block followed by one or more M_DATA(9) message blocks. The structure of the M_PROTO(9) is as follows:

typedef struct {
    ulong PRIM_type;         /* always N_UNITDATA_REQ */
    ulong DEST_length;       /* destination address length */
    ulong DEST_offset;       /* destination address offset */
    ulong RESERVED_field[2]; /* reserved field for DLPI compat */
} N_unitdata_req_t;

PARAMETERS

PRIM_type: Indicates the primitive type.
DEST_length: Indicates the length of the destination address.
DEST_offset: Indicates the offset of the destination address from the beginning of the M_PROTO(9) message block.
RESERVED_field: This is a reserved field (for compatibility with dlpi(7)) whose value must be set to zero for both entries of the array.

STATE

This primitive is valid in state NS_IDLE.

NEW STATE

The resulting state remains unchanged.

RESPONSE

Successful:
There is no acknowledgment for the successful completion of this primitive.
Non-Fatal Error:
If a non-fatal error occurs, it is the responsibility of the NS provider to report it via the N_UDERROR_IND(7) primitive.
Fatal Error:
Fatal errors are indicated via an M_ERROR STREAMS message type (issued to the NS user with the errno(3) value of EPROTO), which results in the failure of all Linux system calls on the stream.

ERRORS

The following non-fatal error codes are allowed:

[NBADADDR]: The network address as specified in the primitive was in an incorrect format, or the address contained illegal information.
[NBADDATA]: The amount of user data specified was outside the range supported by the NS provider.
[NOUTSTATE]: The primitive was issued from an invalid state.

The fatal errors are as follows:

[EPROTO]: This indicates one of the following unrecoverable protocol conditions:
-: The network service interface was found to be in an incorrect state.
-: The amount of NS user data associated with the primitive defines a network service data unit larger than that allowed by the NS provider.

HISTORY

The Network Provider Interface first appeared in SVR 4[1].

CONFORMANCE

This interface conforms to NPI Revision 2[2].

REFERENCES

[1]: SVR 4, UNIX® System V Release 4 Programmer's Manual, 1990, (Englewood Cliffs, New Jersey), AT&T UNIX System Laboratories, Inc., Prentice Hall.
[2]: 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>
[3]: Magic Garden, The Magic Garden Explained: The Internals of UNIX® System V Release 4 / An Open Systems Design, 1994, (Australia), B. Goodheart, J. Cox, Prentice Hall. [ISBN 0-13-098138-9]
[4]: Advanced Programming in the UNIX®Environment, 15th edition, December 1997, (Reading, Massachusetts), W. R. Stevens, Addison Wesley. [ISBN 0-201-56317-7]

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 XNS Networking: Package strxns version 0.9.2.7 released 2008-10-31.

This document was created by man2html, using the manual pages.
Time: 21:56:21 GMT, May 18, 2013

Description: Manual Page

Keywords: ss7 ss7/ip ss7 over ip ss7 mtp ss7 sccp ss7 tcap sigtran mtp sccp tcap openss7 acb56 linux telephony pstn linux telephony linux nebs linux compactpci