SCTP DATA chunks: TSN, SSN and payload fields
The Stream Control Transmission Protocol (SCTP) uses the DATA chunk to carry application bytes across an association. Its header separates two sequence concepts: the Transmission Sequence Number (TSN) tracks chunks, while the Stream Sequence Number (SSN) orders data within a stream.
For engineers moving from MTP3 and ISUP towards IP-based signalling, that distinction prevents subtle faults in retransmission, reassembly and application parsing.
Why the DATA chunk matters
Traditional SS7 networks rely on MTP3 for reliable transport and ISUP for call-related signalling. Modern IP networks often carry SIP, Diameter and other protocols over SCTP, so packet traces can mix legacy interconnects with SCTP-based control traffic.
A DATA chunk is therefore more than a payload envelope. It records enough state for recovery, selective acknowledgement, stream ordering and fragmented-message handling, while leaving interpretation of the user data to a negotiated application protocol.
Field-by-field wire layout
The SCTP DATA chunk format contains an 8-bit type with value 0, 8-bit flags, a 16-bit length, a 32-bit TSN, a 16-bit Stream Identifier, a 16-bit SSN and an optional 32-bit Payload Protocol Identifier (PPID). The variable-length User Data follows. The first 12 bytes are fixed; including PPID extends the fixed portion to 16 bytes.
The length field covers the chunk header and user data but excludes trailing alignment padding. For example, 18 user-data bytes with PPID produce a chunk length of 34, followed by two padding bytes on a 4-byte boundary. A decoder must not mistake that padding for payload.
TSN, SSN and delivery semantics
The TSN belongs to the association-wide sequence space. Each DATA chunk receives a new TSN, including each fragment, and cumulative or Selective Acknowledgement (SACK) reports refer to those values. A missing TSN can therefore stall delivery even when another stream is healthy.
The SSN belongs to a particular stream. On an ordered stream, the receiver uses SSN to place bytes in message order; on an unordered stream, SSN is ignored and normally set to zero. Every fragment of one ordered message carries the same SSN, while each fragment still receives a distinct TSN.
| Field | Width | Scope | Purpose |
|---|---|---|---|
| TSN | 32 bits | Association | Identifies DATA chunks and supports acknowledgement |
| Stream Identifier | 16 bits | Stream | Selects the ordered or unordered stream |
| SSN | 16 bits | Stream | Tracks message order within that stream |
| PPID | 32 bits | Payload | Identifies the application protocol for interpreting the data |
| User Data | Variable | Message | Holds the bytes delivered to the application |
Payload identifiers and application data
PPID bridges transport state and application meaning. Its value is application-specific and must not be confused with an SS7 Message Type or ISUP cause value. Where SCTP expertise is still developing, the site's SCTP and SIGTRAN training offers a useful bridge from legacy signalling principles to IP transport.
The receiver uses PPID, stream context and any negotiated application rules to interpret User Data. SCTP does not make the bytes self-describing: a malformed Diameter attribute, SIP message or vendor payload remains an application-layer fault even when every chunk was delivered correctly.
Fragmentation, flags and troubleshooting
The DATA flags describe handling. U marks unordered delivery, B marks the beginning of a fragmented message and E marks its end. I requests prompt acknowledgement, which can help interactive traffic. A complete unfragmented message normally has neither B nor E; a single-chunk fragment may carry both.
Troubleshooting starts by separating recovery errors from ordering errors. A TSN gap suggests loss or a path fault, while an SSN gap within an otherwise continuous TSN sequence suggests stream-level reordering or a reset. Packet captures should also expose the U, B and E flags, PPID, chunk length and padding before engineers infer that the application generated bad content.
Signals in the Australian market
Australian carriers such as Telstra, Optus and TPG Telecom operate fixed, mobile and enterprise networks over a mix of fibre, NBN access, 4G and 5G. That market supports IP-based signalling, but many interconnects still preserve legacy SS7 and ISUP relationships, making mixed-protocol monitoring routine.
Distance adds another local constraint. Traffic can cross Perth, Adelaide, Melbourne, Sydney and Brisbane, while eastern states observe daylight saving and national teams work across UTC+8 to UTC+10. Overnight paths, daylight-saving transitions and 24/7 on-call duties can combine to create fatigue; broader shift-worker wellbeing guidance can support safer handovers.
Identifiers also reflect local regulation. ACMA's Australian Numbering Plan governs 04xx mobile prefixes, which may appear in application payloads even when the SCTP header remains generic. Operators subject to Australian critical-infrastructure and privacy duties should also restrict payload logging because decrypted signalling can expose customer and network details.
Deployment checklist and durable takeaways
A compact operational review should cover transport, streams and payload semantics before changes reach production.
- Confirm that TSNs remain continuous for the affected association and inspect SACK gap reports.
- Validate Stream Identifier and SSN values separately for every ordered stream.
- Check B, E and U flags when reconstructing fragmented or unordered messages.
- Derive expected User Data length from the chunk length, PPID presence and padding rules.
- Compare PPID values with the application protocol expected by each endpoint.
- Redact sensitive payload data and retain the header fields needed for fault analysis.
The durable rule is simple: TSN moves DATA reliably across the association, SSN restores order within a stream, and PPID together with User Data tells the receiver what the delivered bytes mean.