Routing Labels in STP Global Title Translation
Signalling System No. 7 networks use Global Title Translation (GTT) to turn a dialled address, such as an international mobile number or service identifier, into a routable destination. The translation process is performed by a Signalling Transfer Point (STP), which examines the global title and selects the appropriate point code, subsystem number, and signalling link.
Routing labels are central to that decision. They connect the result of a translation with the MTP3 information required to forward a signalling message through the network. A sound design improves call routing, roaming support, SMS delivery, and protection against misdirected or looping traffic.
How A Routing Label Directs Signalling Traffic
A routing label normally contains the destination point code (DPC), originating point code (OPC), and signalling link selection (SLS) field. MTP3 uses these values to identify the next signalling destination, the message source, and the link or link set selected for load sharing. The label is separate from the Global Title, although the GTT result determines much of its content.
An STP may receive a message with a global title instead of a directly usable point code. It analyses elements such as Translation Type (TT), Numbering Plan (NP), Nature of Address Indicator (NAI), and address digits. Once the matching translation rule is found, the STP replaces or supplements the address information and creates the routing context needed for onward delivery.
This separation is useful in large networks. A mobile subscriber's number can remain stable while the underlying destination point code changes between an HLR, HSS, SMSC, or another service platform. It also allows operators to distribute traffic across several nodes without changing every originating switch.
From Global Title To MTP3 Destination
GTT is usually processed in stages. An STP can first identify the numbering plan, then select a translation table, examine a prefix, and finally choose a destination point code and subsystem number. The routing label is therefore the practical output of a chain of policy decisions rather than a simple copy of the dialled digits.
Operators should define whether the original global title is retained, modified, or removed after translation. The choice depends on the signalling application and the receiving node's expectations. Incorrect handling can cause repeated translation, an unusable return address, or a message to be rejected because the destination does not recognise the address format.
| Element | Function in routing | Typical operational concern |
|---|---|---|
| DPC | Identifies the next signalling destination | Incorrect or obsolete point-code data |
| OPC | Identifies the originating signalling node | Misconfigured screening or return routing |
| SLS | Distributes messages across links | Uneven load or dialogue reordering |
| TT | Selects a translation context | Mismatch between roaming partners |
| NP and NAI | Describe numbering and address format | National and international format errors |
| SSN | Identifies an application at the destination | HLR, MSC, SMSC, or service mismatch |
The SLS value deserves particular attention. Messages belonging to the same transaction should normally follow a consistent path, while separate transactions can be spread across a link set. Poor SLS handling may create congestion on one link even when total capacity appears sufficient.
Australian Network Conditions And Compliance
Australian signalling environments must support nationwide services across dense metropolitan areas and long regional routes. Traffic patterns from Sydney, Melbourne, Brisbane, Perth, Adelaide, and regional centres can differ sharply, especially during commuting periods, major events, and holiday travel. A translation plan that works for a metropolitan test load may behave differently when roaming and SMS traffic rises across the broader national footprint.
Number portability and mobile roaming add further complexity. A translated destination may sit in a different operator domain from the one suggested by the original number range. Inter-carrier arrangements therefore need precise point-code ownership, screening rules, and escalation paths. Operators also need to account for Australian privacy and telecommunications obligations, including controls around signalling data that can reveal subscriber or location information.
Emergency services create an especially sensitive case. Routing associated with Triple Zero must be tested separately from ordinary subscriber traffic, with clear failover behaviour and strict change control. STP teams should retain auditable records of translation changes and ensure that operational procedures align with Australian Communications and Media Authority expectations.
Controls For Reliable Translation
Routing labels should be validated alongside the complete GTT rule, not reviewed as an isolated field. A correct DPC is still ineffective if the SSN is wrong, the destination has no route, or the selected link set cannot carry the required traffic. Engineers should test successful delivery, unknown numbers, malformed addresses, unavailable destinations, and translation loops.
Timers and link health also influence the outcome. Excessive retries can amplify congestion when a destination becomes unreachable, while delayed responses may leave transactions occupying resources. Teams reviewing timeout behaviour can use this SS7 timer guide when checking T1–T33 values and application-specific expectations.
Useful operational checks include:
- Confirm that each DPC, OPC, and SSN matches the current network inventory.
- Test national, international, ported, roaming, and malformed address formats.
- Verify SLS distribution across every active link set.
- Monitor translation failures, loops, congestion, and unexpected return causes.
- Record approvals, rollback steps, and timestamps for every GTT change.
Link deactivation deserves the same discipline. If an MTP2 link is unstable, taking it out of service automatically can protect the wider signalling network, but aggressive thresholds may remove healthy capacity. The principles in this MTP2 monitoring guide help relate error-rate monitoring to controlled link management.
Building A Maintainable GTT Design
A maintainable design starts with an authoritative inventory of point codes, subsystems, link sets, numbering plans, and partner responsibilities. Translation tables should use clear naming, version control, and an explicit default action. A reject or quarantine result is often safer than sending an unknown global title towards a broad or unintended destination.
Capacity planning should combine signalling rates with transaction behaviour. SMS bursts, roaming registrations, location updates, and service queries may use different routes and response patterns. In Australia, backhaul distance between capital cities and regional sites makes latency and failure domains important when choosing alternate STPs.
The next practical step is to export one production GTT rule set, map each translation result to its DPC, SSN, SLS policy, and failover route, and test that map against controlled traces before approving any change.
