| OpenSS7 SS7 for the Common Man | © Copyright 1997-2007 OpenSS7 Corporation All Rights Reserved. Last modified: Sat, 01 Nov 2008 10:42:34 GMT | ||||||||||||||||
| |||||||||||||||||
| Manpage of T_DATA_REQDescription: Manual PageKeywords: 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 compactpciT_DATA_REQSection: Transport Provider Interface (TPI) (7)Updated: 2008-10-31 Index Return to Main Contents NAMET_DATA_REQ - Data RequestSYNOPSISThis message consists of one M_PROTO message block followed by zero or more M_DATA message blocks where each M_DATA message block contains zero or more bytes of data. The format of the M_PROTO message block is as follows:
struct T_data_req {
t_scalar_t PRIM_type; /* Always T_DATA_REQ */
t_scalar_t MORE_flag;
};
DESCRIPTIONThis primitive indicates to the transport provider that this message contains a transport interface data unit. One or more transport interface data units form a transport service data unit (TSDU).Note that the maximum transport service data unit size allowed by the transport provider is indicated to the transport user via the T_INFO_ACK(7) primitive. This primitive has a mechanism which indicates the beginning and end of a transport service data unit. However, not all transport providers support the concept of a transport service data unit. PARAMETERS
RULESThe transport provider must also recognize a message of one or more M_DATA message blocks without the leading M_PROTO message block as a T_DATA_REQ primitive. This message type will be initiated from the write(2) operating system service routine.For example, on systems that support the tirdwr(4) STREAMS module, if that module is pushed onto a stream corresponding to a transport provider supporting the TPI, then the write(2) operating system service routine may be used to send data on that transport endpoint. In this case there are no implied transport service data unit boundaries. Data is passed down the stream as a series of M_DATA messages. This primitive does not require any acknowledgments, although it may generate a fatal error. This is indicated via a M_ERROR message type which results in the failure of all operating system service routines on the stream. ERRORSThe allowable errors are as follows:
MODESOnly connection-mode.ORIGINATORTransport user.SEE ALSOT_DATA_IND(7), T_EXDATA_REQ(7), T_EXDATA_IND(7), T_OPTDATA_REQ(7), T_OPTDATA_IND(7).HISTORYThe Transport Provider Interface first appeared in SVR 4[1]. CONFORMANCEThis interface conforms to TPI Version 2, Draft 2[2]. REFERENCES
TRADEMARKS
Other trademarks are the property of their respective owners. IDENTIFICATION
Copyright©1992UNIX International, Inc.
Index
This document was created by man2html, using the manual pages. Time: 22:47:20 GMT, May 22, 2013 | ||||||||||||||||
| OpenSS7 SS7 for the Common Man |
| ||||||||||||||||
| Last modified: Sat, 01 Nov 2008 10:42:34 GMT © Copyright 1997-2007 OpenSS7 Corporation All Rights Reserved. |