Sub-System Number

Description

The Sub-System Number (SSN) is a fundamental addressing element within the SS7 (Signaling System No. 7) and its IP-based evolution, SIGTRAN. It operates at the Signaling Connection Control Part (SCCP) layer, which provides enhanced routing and management capabilities above the basic Message Transfer Part (MTP). While the Point Code (PC) identifies a specific signaling node in the network, the SSN identifies a particular application subsystem *within* that node. Think of the Point Code as the street address of a building, and the SSN as the specific apartment number or office suite inside.

Technically, the SSN is an 8-bit field (values 1-254, with 0 and 255 reserved) in the SCCP Called Party Address and Calling Party Address parameters. When a signaling message needs to be delivered—for instance, a MAP query to a Home Location Register (HLR)—the originating SCCP layer will set the Destination Point Code to the HLR's node and the Destination SSN to the value assigned to the HLR application (which is 6, as per standard assignment). The MTP routes the message to the correct node, and upon arrival, the node's SCCP layer examines the SSN to determine which internal application process (subsystem) should receive the message. This allows a single physical node with a single Point Code to host multiple logical functions, each with its own SSN.

Standard SSN values are defined by international and 3GPP standards to ensure global interoperability. Key examples include SSN=5 for the Mobile Switching Center (MSC), SSN=6 for the Home Location Register (HLR), SSN=8 for the Mobile Switching Center Visitor Location Register (MSC/VLR), and SSN=149 for the Gateway GPRS Support Node (GGSN). The SSN is crucial for the operation of all MAP (Mobile Application Part), CAP (CAMEL Application Part), and INAP (Intelligent Network Application Part) signaling. In SIGTRAN (e.g., using M3UA), the SSN is preserved and carried over IP, allowing seamless interworking between traditional SS7 and IP-based core networks.

Purpose & Motivation

The SSN was created to solve the addressing limitation of the basic MTP layer in SS7, which could only route messages to a node (via its Point Code). As telecommunications networks evolved and nodes began to host multiple, distinct application functions (like an MSC also containing a VLR, or a combined MSC/HLR), a mechanism was needed to direct messages to the correct internal software process. Without the SSN, each application would require its own dedicated physical node and Point Code, leading to massive inefficiency and cost.

Its introduction with SCCP enabled the efficient consolidation of network functions and the development of complex, layered signaling architectures. It is the cornerstone that allows application-layer protocols like MAP to operate independently of the underlying physical network topology. For 3GPP mobile networks, standardized SSN values are absolutely critical for global roaming; a German MSC must know that to query a subscriber's data, it must send a MAP message to the SSN for the HLR (value 6) at the home network's Point Code. This simple, numeric identifier underpins the entire global interoperability of cellular signaling, from 2G GSM through to 5G interworking with legacy SS7 networks.

Key Features

• 8-bit numeric identifier for application subsystems within a signaling point
• Used in SCCP Called/Calling Party Address for application-level routing
• Globally standardized values for key network functions (e.g., HLR=6, MSC=5)
• Enables multiple logical applications to share a single physical node and Point Code
• Essential for MAP, CAP, and INAP protocol message delivery
• Preserved and used in both traditional SS7 and IP-based SIGTRAN (M3UA) networks

Evolution Across Releases

Defining Specifications