Stream Control Transmission Protocol
The Stream Control Transmission Protocol (English: , abbreviation: ) is a transport layer protocol defined by the Working Group in 2000. Defined in detail, introduces the documentation.
| internet kit |
|---|
| application layer |
| transport layer |
| network layer |
| connection layer |
As a transport layer protocol, it can be understood as and similar. The services it provides are a bit like UDP, while combining some of the advantages of UDP. It is a protocol that provides reliable, efficient, and orderly data transmission. By contrast, it is byte-oriented, but for framed messages.
The main contribution is the support for multiple external lines. An endpoint can be composed of multiple, so that the transmission can achieve transparent network fault-tolerant backup between hosts or network cards.
Originally designed for the transport of telephony protocols over IP (), some of the reliable features of SS7 signaling networks are introduced into IP. The IETF's work on this is called Signaling Transport SIGTRAN.
The way SCTP transmits data to the application layer is to treat data as a message (a collection of bytes). The characteristic of SCTP is message-oriented, which means that it transmits a series of messages (each message is a collection of bytes). Compared with TCP, which uses bytes as a unit, it transmits broken streams. The SCTP sending end uses an action to send a message, and the receiving end also uses an action to fetch the message and pass it to the corresponding application. Compared to TCP, it is a stream-oriented protocol that reliably and sequentially transmits streams in bytes. However, TCP does not allow the receiving end to know the number of times the sending end's application calls to send the bytes set. At the sending end, TCP simply appends more bytes to the queue and waits to be sent to the network, while SCTP maintains its own independent queue for outband messages to be sent.