Message Signalling Unit

Description

A Message Signalling Unit (MSU) is the primary packet-like structure used to convey signalling messages within the SS7 (Signalling System No. 7) protocol suite, which forms the backbone of traditional telecommunication signalling. In 3GPP specifications, particularly those dealing with legacy core network interworking (e.g., TS 29.163 on interworking between SIP and ISUP) and charging (e.g., TS 32.407), the MSU is a critical concept. An MSU is composed of several distinct fields: a Flag sequence for delineation, a Checksum for error detection, a Length Indicator, Service Information Octet (SIO), and the core Signalling Information Field (SIF) which contains the actual protocol message, such as an ISUP (ISDN User Part) message for call setup or a MAP (Mobile Application Part) message for location updating.

The architecture of SS7 signalling involves Signalling Points (SPs) interconnected via Signalling Links. MSUs are transmitted over these links by the Message Transfer Part (MTP) Level 2, which handles error detection and correction through retransmission. The MTP Level 3 provides routing functions, using the Routing Label within the SIF to direct the MSU from its Origin Point Code (OPC) to its Destination Point Code (DPC). The Service Information Octet indicates the type of user part (e.g., ISUP, SCCP, TUP) contained within, allowing the receiving node to pass the payload to the correct higher-layer protocol entity for processing.

In a 3GPP mobile network context, MSUs are essential for all circuit-switched services in 2G (GSM) and 3G (UMTS) cores. They carry MAP messages between the MSC, HLR, and VLR for mobility management (e.g., location updates, handovers) and subscriber data retrieval. They also carry CAP (CAMEL Application Part) messages for intelligent network services. Even as networks evolve to all-IP cores with Diameter and HTTP/2, understanding MSUs remains vital for interworking functions (IWF) that translate between SS7-based legacy networks and IP-based NFs (Network Functions). The reliable, connection-oriented nature of MSU transport via MTP is what enabled robust global telephony services for decades.

Purpose & Motivation

The Message Signalling Unit exists as the fundamental carrier of signalling information in the SS7 protocol stack, which was created to provide out-of-band signalling for the global Public Switched Telephone Network (PSTN). Before SS7, signalling was often in-band (using the same channel as voice), which was inefficient, slow, and prone to fraud. SS7 introduced a separate, high-reliability packet-switched network dedicated solely to signalling, with the MSU as its atomic data unit. This separation allowed for faster call setup, advanced services (like call forwarding), and more efficient use of voice circuits.

In the context of 3GPP mobile networks (GSM, UMTS), the purpose of the MSU was to adapt the proven SS7 signalling paradigm for mobile-specific needs. It solved the problem of how to perform complex mobility management (tracking a subscriber as they move), call routing to a mobile device, and integration with intelligent network services for prepaid or roaming. The MSU provided a standardized, reliable container for mobile application protocols like MAP and CAP, ensuring interoperability between network elements from different vendors across international borders. Its robust error-checking and delivery mechanisms were critical for maintaining service continuity and billing accuracy.

The continued reference to MSUs in later 3GPP releases (e.g., for interworking specifications) highlights the need to bridge legacy circuit-switched networks with new IP-based cores. As operators transition to LTE and 5G, they must often maintain connectivity to older 2G/3G networks and the PSTN. Therefore, understanding and handling MSUs is essential for functions like the Media Gateway Control Function (MGCF) which converts SIP signalling to/from ISUP messages carried within MSUs. The MSU represents a cornerstone of traditional telecom engineering that modern architectures must interface with during network evolution.