Reading The Structure Of An SS7 Message Signal Unit
An SS7 Message Signal Unit (MSU) is the basic frame used to transport signaling information across a Signaling System No. 7 network. It carries messages between signaling points, allowing switches, databases, service control points, and other network elements to coordinate calls and services.
Understanding the MSU requires separating two layers. MTP Level 2 controls reliable delivery across an individual signaling link, while MTP Level 3 identifies where the message came from and where it must go. Above these layers, a user part such as ISUP, SCCP, or TCAP provides the service-specific content.
This layered design explains why an MSU can look complicated at first. Each field has a defined responsibility, from link synchronization and sequence control to routing, error detection, and call signaling.
The Role Of An MSU In SS7
An MSU is one of three major Signal Units defined by MTP2. The other two are the Link Status Signal Unit (LSSU), used for link management, and the Fill-In Signal Unit (FISU), transmitted when no signaling message is waiting.
Unlike an LSSU or FISU, an MSU contains a Service Information Octet and signaling data. That data may represent an ISUP Initial Address Message, a release message, an SCCP transaction, or another upper-layer protocol message.
The frame travels over a signaling link between adjacent signaling points. MTP2 checks the frame locally, while MTP3 uses the routing label to forward the message through the wider SS7 network.
The Main Fields In The Frame
An MSU begins and ends with flag octets. A flag usually has the binary value 01111110 and marks the boundary of the signal unit. Bit stuffing prevents the same pattern from appearing accidentally inside the frame and being mistaken for a delimiter.
Between the flags are the control and payload fields. The Backward Sequence Number (BSN) and Forward Sequence Number (FSN) support acknowledgment and retransmission. The Backward Indicator Bit (BIB) and Forward Indicator Bit (FIB) help detect sequence errors and coordinate recovery.
The Length Indicator (LI) identifies the size of the information portion, within the limits defined for the signaling link. An MSU also includes a Check Sequence, commonly called the Frame Check Sequence (FCS), which allows the receiving node to detect transmission errors.
How Routing Information Is Encoded
The Service Information Octet identifies the network level and the type of user data being carried. Its Service Indicator (SI) distinguishes protocols such as ISUP, SCCP, and TUP. The subservice field includes network and priority-related information, helping the node interpret the message context.
The Routing Label normally follows the Service Information Octet. Its key elements are the Destination Point Code (DPC), Originating Point Code (OPC), and Signaling Link Selection (SLS) value. The DPC tells the network where the message should go, while the OPC identifies the sending signaling point.
The SLS value supports load sharing across parallel signaling links or linksets. Messages belonging to the same logical transaction are commonly assigned consistently so that they follow the same route and preserve sequence expectations.
Payload And User Parts
After the routing label comes the signaling information field. Its structure depends on the Service Indicator. For an ISUP message, the payload includes a message type code followed by mandatory and optional parameters. An Initial Address Message may contain called-party information, transmission requirements, and optional service indicators.
The payload can be inspected in a protocol analyzer by identifying the user part first, then decoding the message type and parameter fields. For example, an ISUP call setup sequence commonly progresses through IAM, ACM, ANM, and REL messages. The ISUP call setup guide provides useful context for connecting these message types to call-state transitions.
SCCP and TCAP payloads follow different encoding rules. They may support global title translation, database queries, mobility services, and intelligent network operations. The MSU envelope remains familiar even when the upper-layer signaling changes.
Field Functions At A Glance
The fields are easiest to understand when viewed as a sequence of responsibilities. Flags establish frame boundaries, MTP2 control fields manage delivery, MTP3 fields determine routing, and the user part carries the actual telecom transaction.
| Field | Layer Or Function | Purpose |
|---|---|---|
| Opening flag | MTP2 | Marks the start of the signal unit |
| BSN, BIB | MTP2 | Acknowledges received units and indicates recovery state |
| FSN, FIB | MTP2 | Numbers transmitted units and supports error recovery |
| LI | MTP2 | Indicates the information field length and unit type |
| Service Information Octet | MTP3 | Identifies the service indicator and network context |
| Routing label | MTP3 | Carries OPC, DPC, and SLS information |
| Signaling information | User part | Contains ISUP, SCCP, TCAP, or another protocol message |
| FCS | MTP2 | Detects bit errors in the frame |
| Closing flag | MTP2 | Marks the end of the signal unit |
Exact bit order and field presentation can vary between printed diagrams, capture tools, and national SS7 variants. Engineers should therefore distinguish the logical field sequence from the way octets and bits are displayed by a particular analyzer.
Reading An MSU During Troubleshooting
A practical analysis begins with the link layer. Check whether flags, sequence numbers, the LI value, and the FCS are valid. Repeated retransmissions, incorrect acknowledgments, or link congestion can indicate an MTP2 problem before the user message is examined.
Next, verify the DPC and OPC against the network plan. An incorrect point code, unavailable route, or inconsistent SLS distribution may cause messages to be discarded or sent toward the wrong destination. MTP3 signaling network management messages can reveal route-set and linkset failures.
Finally, decode the Service Indicator and payload. For ISUP, compare the message sequence with expected call states; for SCCP and TCAP, inspect subsystem numbers, global titles, and transaction identifiers. The SS7 learning products collection can support deeper study of protocol behavior, routing, and signaling security.
Recommended Learning And Analysis Practices
- Learn MTP2 and MTP3 separately before decoding ISUP or SCCP payloads.
- Mark every MSU field in a packet capture and relate it to its protocol layer.
- Compare DPC, OPC, and SLS values with the signaling network design.
- Trace a complete transaction instead of analyzing a single message in isolation.
- Check sequence errors, retransmissions, and FCS failures before assuming an application fault.
A clear understanding of the MSU turns raw hexadecimal captures into a readable account of network activity. Apply the field-by-field method to live traces, lab exercises, and call-flow investigations to build reliable SS7 analysis skills.
