March 28, 2026 MOBITELSMS Engineering 13 min read

Global Title is one of the most important and least understood concepts in SS7 signaling. It is the addressing mechanism that allows an SMS message sent from a phone in Tokyo to find the correct HLR in New York, determine which MSC the recipient is connected to, and deliver the message -- all within a few seconds, across multiple networks and international boundaries. If you work with SS7 gateways, SMSC configuration, HLR lookups, or number portability, Global Title addressing and translation are fundamental to understanding how your traffic is routed.

What Is a Global Title?

In SS7 networks, every signaling node (switch, HLR, SMSC, STP) has a Point Code -- a numeric network address analogous to an IP address. Point Codes are fine for routing within a single network, but they are not globally unique. Two operators in different countries might both assign Point Code 1-2-3 to their HLR. And there are far more telephone numbers in the world than there are Point Codes in any SS7 addressing scheme.

A Global Title (GT) is an address that looks like a telephone number (E.164 format) and is used in the SCCP (Signaling Connection Control Part) layer of SS7 to route messages to the correct destination. The key insight is that a GT is not directly routable -- it must be translated into a Point Code (and optionally a Subsystem Number) before the message can be delivered. This translation process is called Global Title Translation (GTT).

Think of it this way: a Point Code is like a street address that the postal system can directly route to. A Global Title is like a person's name -- you need a directory (the translation tables) to convert the name into an address before you can deliver the mail.

GT Format and Components

A Global Title contains several fields, defined in the ITU-T Q.713 recommendation for SCCP:

E.164, E.212, and E.214 Numbering

Three ITU numbering plans are commonly used in Global Titles:

Global Title Translation (GTT)

Global Title Translation is the process of converting a Global Title into a Point Code (and optionally a Subsystem Number) so the SCCP layer can route the message to the correct destination. GTT is performed by Signal Transfer Points (STPs) -- the routers of the SS7 network.

The GTT process works as follows:

  1. A signaling message arrives at the STP with a Called Party Address containing a Global Title (e.g., the destination phone number +12125550100).
  2. The STP examines the GT fields (Translation Type, Numbering Plan, and the address digits) and looks up the address in its translation table.
  3. The translation table maps the GT (or a prefix of the GT) to a destination Point Code and Subsystem Number.
  4. The STP replaces or supplements the Called Party Address with the resolved Point Code and SSN, then forwards the message toward the destination.

Translation Table Structure

A GTT table is essentially a prefix-based routing table, similar in concept to an IP routing table. An entry might look like:

# GT Translation Table (simplified)
# GT Prefix     → Destination PC    SSN    Action
+1212           → 3-8-1             6      Final (HLR)
+1              → 2-1-0             8      Intermediate (route to US STP)
+44             → 5-3-2             8      Intermediate (route to UK STP)
+4917           → 7-12-3            6      Final (German mobile HLR)
+49             → 6-0-1             8      Intermediate (route to Germany STP)

The STP matches the GT digits against the table using longest-prefix matching (most specific prefix wins). If the message is destined for +12125550100, the STP matches the +1212 entry and routes to Point Code 3-8-1 with SSN 6 (the HLR).

Intermediate vs. Final Translation

GTT can be performed in one step (final translation) or multiple steps (intermediate translations):

SCCP Routing: Route-on-GT vs. Route-on-SSN

The SCCP Called Party Address contains a Routing Indicator (RI) that tells the network how to route the message:

A typical international SMS delivery uses route-on-GT for the initial hop (the sending SMSC does not know the destination HLR's Point Code), with each STP along the path performing GTT until the message reaches the destination network, where the final STP resolves the GT to the HLR's Point Code and switches to route-on-SSN.

Subsystem Numbers (SSN)

The Subsystem Number identifies which application at the destination Point Code should receive the message. Common SSNs in mobile networks:

When an SMSC sends an SRI-SM (Send Routing Info for Short Message) MAP operation, the Called Party Address contains the recipient's MSISDN as a Global Title with SSN=6, indicating the message should be routed to the HLR that serves that subscriber.

GT in Practice: SMS Routing Example

Let us trace how Global Title routing works for an international SMS from a US phone to a UK phone:

  1. The US SMSC receives the SMS for delivery to +447700900123. The SMSC needs to query the recipient's HLR to find out which MSC/VLR is currently serving the subscriber.
  2. The SMSC sends a MAP SRI-SM (Send Routing Info for Short Message) message. The Called Party Address contains: GT = +447700900123, NP = E.164, SSN = 6 (HLR), RI = route-on-GT.
  3. The message reaches the US national STP. The STP performs GTT: prefix +44 maps to the UK international gateway STP (Point Code of the UK interconnect). The STP forwards the message to the UK STP.
  4. The UK STP performs GTT: prefix +44770 maps to the Vodafone UK HLR (Point Code 5-3-7, SSN 6). The STP resolves the GT to the final destination and sets RI = route-on-SSN.
  5. The Vodafone HLR receives the SRI-SM and responds with the IMSI of the subscriber and the address of the MSC/VLR currently serving them (e.g., their location has been updated to show they are registered on a specific MSC in London).
  6. The US SMSC uses the response to send the SMS (via MAP ForwardSM) to the serving MSC, which delivers it to the subscriber's phone.

This entire process -- multiple GTT lookups across international boundaries -- typically completes in under 2 seconds. The efficiency of GT translation is what makes international SMS delivery seem instantaneous to users.

GT and Number Portability

Number portability introduces a complication for GT routing. When a subscriber ports their number from Carrier A to Carrier B, the GT prefix no longer correctly identifies the serving network. The digits +44770 might normally route to Vodafone, but if the subscriber has ported to EE, the message needs to go to EE's HLR instead.

The solution is the Number Portability Database (NPDB), which is queried during GTT. When the STP encounters a GT for a potentially ported number, it queries the NPDB to determine the current serving network. The GTT then routes based on the ported status rather than the original prefix assignment.

In practice, this is implemented through a specialized STP function or a dedicated number portability server that intercepts SRI-SM queries and modifies the routing based on portability data. MOBITELSMS provides MNP/LNP lookup services that leverage this infrastructure to determine the current serving network for any mobile number.

GT Provisioning

Provisioning Global Title translations is one of the most critical operational tasks in SS7 network management. Incorrect GT translations cause routing failures that can affect millions of messages and calls. Key provisioning considerations:

GT in the Transition to Diameter and 5G

As networks transition from SS7 to Diameter (4G) and HTTP/2-based SBI (5G), Global Title addressing is being replaced by Diameter realm-based routing and FQDN (Fully Qualified Domain Name) addressing. In Diameter, the equivalent of GT translation is realm-based routing through Diameter Routing Agents (DRAs), which map realm names to destination hosts.

However, interworking between SS7 and Diameter networks requires GT-to-Diameter address translation at the boundary. An IWF (InterWorking Function) or DEA (Diameter Edge Agent) sits at the border between SS7 and Diameter domains, translating Global Titles to Diameter realm/host combinations and vice versa. This interworking will be needed for as long as SS7 networks remain operational -- which, given current timelines, means at least another decade.

For operators and service providers working with the MOBITELSMS SS7 gateway, GT configuration and translation remain essential operational knowledge. Whether you are setting up SMS routes, configuring HLR lookup paths, or troubleshooting delivery failures, understanding how Global Titles are structured, translated, and routed is the foundation of effective SS7 network operation.